Regular Procedures › Multi-User Facility › Activation

Activation

As part of the CA Datacom/AD installation process, a sample CA Datacom/DB MUF startup job AD14STRT for z/OS is provided. The MUF must be enabled prior to the time the CA Technologies product you are using wants to access it.

If CA Datacom/AD is being utilized with another CA Technologies system product, run the AD14STRT job/STC (where STC refers to a Started Task) at a priority just under the priority of the JES subsystem.

The DBMUFPR is the program that activates the MUF and performs the following functions. This step stays active until the MUF is terminated.

Note: The DBMUFPR program must be executed from authorized libraries.

Typical MUF Start-up Messages and Phases

Messages are displayed on the console or to the JESMSGLG that are informational or concerning things that require an action to be performed. The details about these messages can be found in the CA Datacom/DB Message Reference Guide.

Echo the MUF startup options to the console in DB01900I

These messages are reflected in part on the JESMSGLG and in their entirety in the SYSOUT. Descriptions of these parameters can be found in the CA Datacom/DB Database and System Administration Guide.

Restart the MUF

During the restart process you can get the following messages:

• DB01201I RESTART, LOG NOT OPEN, NO ACTION REQUIRED - If the MUF did not abend the previous time it was active, you receive this message which means that the Log Area (LXX) was emptied and closed cleanly when the MUF was previously terminated.
• DB01202I RESTART, STARTING LOG SCAN, BLOCKS -n - If the MUF has abended the previous time that it was active, you receive this message followed by different restart messages.
• DB01207I RESTART, COMPLETE - This message means that the restart is successful.

Enable the MUF and Identify DB Software Level

When the MUF becomes enabled, the message DB00201I MULTI-USER ENABLED CXX=cxxname MUFNAME=mufname displays on the console followed by the message DB00215I CA-DATACOM/DB SYSTEM VERSION: v.r.

The DBMUFPR uses the following main required data sets. All access either to or from these data sets must be done through the MUF or DBUTLTY.

• The CXX is a control data set and is required. It contains the definitions for all the databases. Some of the information is constant and only updated when the database is defined. Other information is updated when a database is closed or when the DBUTLTY LOAD or RETIX function is used.

  z/OS

  When using CA Datacom/DB dynamic allocation, the CXX data set contains a DSNAME field which is updated when a database data set is initialized. CA Datacom/DB uses this DSNAME to dynamically allocate the file.

• For each database, CA Datacom/DB uses one or more Index Area (IXX) data sets and one or more data area data sets. The DD or DLBL names for an IXX are IXXnnnn or IZZnnnn, where nnnn is the numeric database ID, and where ZZ can be 01-99. The DD or DLBL names for a data area are aaannnn where aaa is the 3-character area name assigned in CA Datacom Datadictionary and nnnn is the numeric database ID.
• The Log Area (LXX) is read to determine how the MUF last terminated. If the MUF reached a normal end-of-job, this step completes without any further action.

  If the MUF ended with an abend, this step tries to perform the following:

  1. Reset any databases that were left open.

  2. Re-apply all checkpointed (that is, committed) transactions so that the databases are in a stable state.

  3. After reading the Force Area (FXX), any changes that were not checkpointed are removed. (CA Datacom/DB checkpoints at the end of every batch program and at the end of each CICS transaction. Programs may also issue explicit checkpoints.)

  4. Marks the LXX as spillable

• MUF startup option SYSOUT already has the format dumps or Snaps. SYSPRINT has the EOJ Stats that can be used for monitoring and tuning for CA Datacom/AD. MUF startup option PXXSTATS EOJPRT turns this on.

  Note: If the MUF abends, CA Support must have the region dump and the report produced by the MUF. SYSPRINT has MUF options and EOJ stats that were collected at the time MUF abended or EOJ. A SVC dump can be generated as well. Collect all the output that the abending MUF generated and the SVC dump that is related for CA Support.