Configuring Datacom MUF for XCF use
search cancel

Configuring Datacom MUF for XCF use

book

Article ID: 38170

calendar_today

Updated On:

Products

Datacom/DB Datacom Datacom/AD

Issue/Introduction

Accessing a Multi-User Facility (MUF) from an LPAR in a Sysplex other than the one where the MUF is executing requires the definition of specific parameters to support IBM Cross-system Coupling Facility (XCF) processing. This configuration allows remote tasks to establish communication with the MUF across z/OS images.

Resolution

Follow these steps to enable XCF support for both local and remote processing.

  1. Modify DBSIDPR Assembly Update the DBSIDPR assembly (found in INSTJCL member AXCUSNEW for Datacom/AD or BDCUSNEW for Datacom/DB):

    • Set CONNECT_ALLOW_PRIORITY=(LOCAL,XCF).
    • Use a unique 1–7 character name in TARGET_MUF_LIST. This should already have been defined in your original MUF creation. Note that if using a Shadow MUF, TARGET_MUF_LIST =(<MUFnameA>,<MUFnameB>), where MUFname is the same 1-7 root name used in the CXXname plus a one-character suffix (preferably A and B).
    • Define a unique 1–8 character TOGROUP name that differs from the MUF name.
    • Submit the JCL to reassemble and link the DBSIDPR module.

  2. Update MUF Startup Options Modify the MUF startup options (member AXDATIN1 for Datacom/AD or DBDATIN2 for Datacom/DB):

    • Ensure that the setting for MUF uses an asterisk (*) in the first parameter:
    MUF *,####,NO
    • Uncomment the XCF_FROM option and ensure the group name matches the TOGROUP defined in Step 1:
    XCF_FROM *,*,<groupname>,YES
    • Set the 5th parameter of the TASKS option to a value that supports the expected number of remote tasks (typically 50–80% of the total TASKS value):
    TASKS 250,32K,0,0,100

  3. Configure Remote LPARs Perform the following actions on every LPAR where remote tasks will execute:

    • APF authorize the Datacom load libraries (CAAXLOAD/CABDLOAD) and the CUSLIB.
    • Load the Datacom PC Call module DBPCCPR using CAS9/CAIRIM.
    • Add the CAIRIM commands to the CAS9 procedure to ensure the modules remain available after an IPL.

  4. Verify Connectivity Test the XCF connection from the remote LPAR using a DBUTLTY job:

    //SYSIN DD *
      COMM OPTION=STATUS
     /*

Additional Information

References

Powered by Wolken Software