Starting Your Product › CA Datacom/AD Environment

CA Datacom/AD Environment

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 sometimes be needed.

To separate the identity of each environment, a unique name must be assigned. The name should be seven or fewer positions long and meet the requirements needed to be part of a data set name node. To make data set ownership clear and prevent problems caused by having data sets used by multiple (or wrong) environments, it is a best practice (though not a requirement) to make the name a node in each data set.

The CA Datacom system data set controlling the environment is the Directory with a data set DDNAME of CXX. The name 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 would be the same as the name of the CXX. The MUF can also be configured as two instances or Jobs with one the primary and 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, and each MUF instance would need its own identity or MUF name that 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 AXCUS01 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 AXCUS01 to end with condition code zero.

To define the specific environment, CA Datacom provides one Macro (DBSYSID) with key word options providing the names of the CXX and the MUF instances. In addition, it provides many other options that define the environment configuration.