Testing XCF connectivity to a remote Multi-User Facility (MUF) - Datacom/DB
Article ID: 17476
Updated On:
Products
Issue/Introduction
Verify the operational status of IBM Cross-system Coupling Facility (XCF) communication between a Multi-User Facility (MUF) and a remote LPAR. This procedure ensures that Datacom/DB or Datacom/AD applications executing on a different z/OS image can successfully connect to the MUF before application startup.
Cause
Technical verification step to confirm successful configuration of CONNECT_ALLOW_PRIORITY=(LOCAL,XCF) and corresponding MUF startup options.
Resolution
Execute these steps from the remote LPAR to validate the XCF connection.
Step 1: Verify MUF Status and XCF Activation
On the LPAR where the MUF is executing, review the JESLOG for the following messages to confirm the facility is ready:
DB00201I - MULTI-USER ENABLED, CXX=####DB00226I - MULTI-USER ACTIVATED XCF SUPPORT
Step 2: Submit Connectivity Test Job
Submit a batch DBUTLTY job from the remote LPAR using the following control statement:
//SYSIN DD * COMM OPTION=STATUS
/*
To ensure execution on the specific remote LPAR, add the following JCL entry: /*JOBPARM SYSAFF=<remoteLpar>
Step 3: Evaluate Results
- Success: The DBUTLTY job output displays the MUF status and lists any active tasks.
- Failure: The job terminates with Return Code 68 and the following messages appear in the log:
DB00121I - UNAVAILABLE - <mufname>
DB00122I - ACCESS TYPE - LOCAL TASKS=1
DB00123I - WAITING FOR MUF AVAILABILITY
DB00124W - REMAINING DELAY68 TIME - 2 MINUTES
DB00501E - OPEN ERROR - RETURN CODE 68 (001) CXX...
Step 4: Verify Authorization
If the test fails, confirm that the MUF load libraries (including the CUSLIB) are APF authorized on the remote LPAR, and that the necessary changes have been made as shown in Knowledge Base article 38170, titled "Configuring Datacom MUF for XCF use".
Additional Information
References
Feedback
