Datacom test XCF connection to remote MUF
Article ID: 17476
Updated On:
Products
Issue/Introduction
Many Datacom/DB or Datacom/AD applications may be using Cross-System Coupling Facility (XCF) to connect and communicate to a Multi-user (MUF) that is running on a different z/OS image (Lpar) than the MUF.
After MUF has been customized to allow for XCF, is there a way to test that the XCF communication to a MUF is working before executing or starting an application running remotely in a different Lpar than the MUF?
Environment
Resolution
First, ensure that the Datacom MUF is up and enabled. Check the MUF jeslog for message:
DB00201I - MULTI-USER ENABLED, CXX=…
To see if XCF is activated, check the MUF jeslog for message:
DB00226I - MULTI-USER ACTIVATED XCF SUPPORT ...
Then, submit from the remote Lpar a batch Datacom DBUTLTY job with SYSIN:
//SYSIN DD *
COMM OPTION=STATUS
/*
You can add JCL entry /*JOBPARM SYSAFF=remoteLpar to assure that it executes on the remote Lpar.
If the MUF is up and the XCF communication is successful, the DBUTLTY job output will return showing a status, whether there are any active tasks running in the MUF.
If the MUF is not up or was not properly customized for XCF, you will get a Datacom RC 68 and the DBUTLTY job will terminate within the time delay for RC 68:
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
Additional Information
Also, assure that the MUF's STEPLIB/JOBLIB libraries (CUSLIB, etc) have been APF authorized on each Lpar.
For more information about connecting to the MUF using XCF, please refer to the Datacom Core - 15.1 section "Connecting to z/OS Using Cross-System Coupling Facility (XCF)"
For information about setting up XCF connectivity, refer to Knowledge Base article 38170, titled "Configuring Datacom MUF for XCF use"
As always, please contact Broadcom support for Datacom if you have further questions.
Feedback
