In order to access a CA Datacom Multi-User Facility (called MUF) from an LPAR in the Sysplex other than where the MUF is running, it is necessary to define a number of parameters to the MUF to support XCF (IBM Cross-system Coupling Facility) processing.
This document describes what is needed.
This applies to z/OS systems.
Here are a few things that you need to do to set up your MUF in support of both local and remote (XCF) processing:
In summary, you need these in the DBSIDPR assembly
CONNECT_ALLOW_PRIORITY=(LOCAL,XCF)TOGROUP=<<1-8 character unique group name that you create>>TARGET_MUF_LIST=<<1-7 character unique MUF/CXX name that you create>>
* Note that the MUF name must be different from the TOGROUP name and in the case of a Shadow MUF, both MUFs have the same 1-7 root name plus a one-character suffix (preferably A and B, or something like that).
You need these MUF startup options
These points will cover the greatest majority of causes for applications on remote LPARs to not connect to a MUF.
As always, please contact Broadcom support for CA Datacom if you have further questions.