Skip to content
CA Datacom/AD - 15.0
Documentation powered by DocOps

CA Datacom/AD Environment Configuration

Last update December 1, 2017

A single CA Datacom®/AD environment consists of the following:

  • A set of data sets containing unique information about and for the environment
  • One logical server/controller known as a Multi-User Facility (MUF)

Because a site has many z/OS systems and multiple Sysplex occurrences, more than one CA Datacom® environment can be needed.

To separate the identity of each environment, assign a unique name. The name can be seven or fewer positions long and meet the requirements to be part of a data set name node. It is a best practice to make the name a node in each data set. This practice makes data set ownership clear. It also prevents problems caused by having data sets used by multiple (or wrong) environments. 

The CA Datacom® system data set controlling the environment is the Directory with a data set DDNAME of CXX. The name that is selected for each environment is provided to CA Datacom® as the CXXNAME. Access to the data set environment is primarily through the MUF and secondarily through the utility function processor named DBUTLTY. The MUF is often a single instance of an executing program DBMUFPR to provide services to all accesses to the data in this environment. In this configuration, the name of the MUF is the same as the CXX name. You can also configure the MUF as two instances or Jobs. One as the primary active server and the second doing tracking as a shadow to take over processing quickly should the primary fail. In this configuration, the CXX name would become the MUFPLEX name as the identity of the group of MUF instances. Each MUF instance would need its own identity or MUF name> This name would be the CXX name suffix with numbers 1 and 2 or the letters A and B.

Choosing to use a full 8-byte name at this time causes the customization member AXCUSNEW to receive a condition code 1. The only way to rectify a condition code 1 is to follow the best practices by using a 1 to 7 byte name. Using the 1 to 7 byte name allows member AXCUSNEW to end with condition code zero.

To define the specific environment, CA Datacom® provides one Macro (DBSYSID) with key word options> These options provide the names of the CXX and the MUF instances. Additionally, it provides many other options that define the environment configuration.

Was this helpful?

Please log in to post comments.