Many CA Datacom/DB applications or CA Datacom/AD "using products" such as CA-11 (CA Workload Automation Restart Option for z/OS Schedulers) may be using Cross-System Coupling Facility (XCF) to connect and communicate to the 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 CA Datacom MUF is working before executing or starting an application, such as a CA-11, running remotely in a different Lpar than the MUF?
First, assure that the CA 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 CA Datacom DBUTLTY job with SYSIN of COMM OPTION=STATUS.
You can add JCL /*JOBPARM SYSAFF=remoteLpar to assure that it really executes in the remote Lpar.
This saves actually starting the user application until communication can be confirmed and any problems can be addressed.
If the MUF is up and the XCF communication is successful, the DBUTLTY job output will return showing a status, whether there are no or some 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
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 CA Datacom Core - 15.1 section "Connecting to z/OS Using Cross-System Coupling Facility (XCF)"
Refer to Article Id: 38170
Article title: How to configure CA Datacom MUF for XCF use