Multi-User Facility

This section contains information about MUF activation, status reports related to the MUF, and MUF termination.
cdat
This section contains information about MUF activation, status reports related to the MUF, and MUF termination.
The following list provides a summary of the relationship between the 
CA Datacom®
 functions to z/OS functions:
 
MUF
 
 
MVS
 
CXX
OS CATALOG
Area
OS DATASET
LXX/RXX
SMF
PXX
SYSI.DUMP
Task
INITIATOR
URT
JCL
COMM STATUS
D A
COMM EOJ
P jobname
COMM SNAP
DUMP jobname
RUNUNIT
JES #
The following topics are discussed in this section:
 
 
Activation
As part of the 
CA Datacom®/AD
 installation process, a sample 
CA Datacom®/DB
 MUF startup job AD15STRT for z/OS is provided. The MUF must be enabled before the 
Broadcom
 product you are using wants to access it.
If 
CA Datacom®/AD
 is being used with another 
Broadcom
 system product, run the AD15STRT job/STC at a priority just under the priority of the JES subsystem. STC refers to a Started Task.
The DBMUFPR is the program that activates the MUF and performs the following functions. This step stays active until the MUF is terminated.
 
Note:
 Execute the DBMUFPR program from authorized libraries.
Typical MUF Start-up Messages and Phases
 
Messages are displayed on the console or to the JESMSGLG. These messages are informational or require an action to be performed. For details about these messages, see CA Datacom/DB Messages.
  •  
    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. For details about these parameters, see the CA Datacom/DB Database and System Administration topic. 
  •  
    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 previously since it was active, you receive this message. 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 abended previously since 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 DB00201I MULTI-USER ENABLED CXX=cxxname MUFNAME=mufname message displays on the console. The DB00215I CA-DATACOM/DB SYSTEM VERSION: v.r. message follows it.
    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.
    • (Required) The CXX is a control data set that 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. This field is updated when a database data set is initialized. CA Datacom/DB uses this DSNAME to allocate the file dynamically.
    • (For each database) CA Datacom/DB uses one or more Index Area (IXX) and data area data sets. The DD names for an IXX are IXX
      nnnn or 
      IZZ
      nnnn.
       The 
      nnnn
       is the numeric database ID, and ZZ can be 01-99. The DD names for a data area are 
      aaannnn
      . The 
      aaa
       is the three-character area name that is 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 tasks:
      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. Programs might 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 is used for monitoring and tuning for 
      CA Datacom®/AD
      . MUF startup option PXXSTATS EOJPRT turns this on.
       
      Note:
       If the MUF abends, 
      Broadcom
       
      must
       have the region dump and the MUF report. SYSPRINT has MUF options and EOJ stats that were collected at the time MUF abended or EOJ. An SVC dump can also be generated. Collect all the output that the abending MUF generated and the SVC dump that is related for 
      Broadcom
      .
Standard Communication Messages
When a program establishes a connection with the MUF initially through a User Requirements Table (URT), the MUF issues the following job-started message. These messages are located in  the message log of the program:
DB00101I STARTED JOB-jjjjjjjj NUMBER-nnnnn CXX=cxxname MUFNAME=mufname 
 
If the job referenced in DB00101I is executing from another environment using XCF or CCI as its communication protocol, the following messages can follow the DB00101I message.
  • DB00118I XCF TOGROUP=
    name
     SYSTEM=
    system name
     
  • DB00111I CCISYS=CAICCI 
    system name
     SYSTEM=MVS 
    system name
     
The message can contain the following additional information:
  • Job name of the MUF
  • Unique RUN-UNIT assigned to this job to identify it for logging and recovery
  • MUFNAME used to communicate to a particular MUF
  • CXXNAME reflects the internal name of the CXX Directory this MUF is using
  • And more
When a program completely drops connectivity with the MUF, the following job-ended message is posted in the MUF region. You receive this message only if you have installed 
CA Datacom® CICS Services
CA Datacom®/AD
 Version 15.1 does not deliver 
CA Datacom® CICS Services
 because it was delivered in Version 12.0.
 
DB00102I ENDED JOB-jjjjjjjj NUMBER-nnnnn [TTT-FROM=mmmmmmmm] 
 
The message shows the job name, RUN-UNIT number, and other items. You can use the RUN-UNIT number on the DB00101I and DB00102I to determine when a job started and stopped.
MUF Status
You can run a batch job or enter a console command to request the current status of the MUF at any time. This status provides specific information about all jobs currently accessing the MUF. We recommend that you issue two to three STATUS commands to see progress over time. For more information about this function, see the DBUTLTY COMM OPTION=STATUS or the COMM STATUS command in DBUTLTY Reference. AD15COMM is a sample JOB that is provided. CA SYSVIEW can optionally be used to monitor the activity within the MUF.
Sample Report
 
The following example shows a sample report page. For an example report header, see Sample Report Headers.
MULTI-USER DBDVM02 AVAILABLE TASKS - ATTACHED-----1, AVAILABLE----24 JOBNAME R-UNIT TASK STATUS CMD DBID TBL SEQ TIME I/O ID TSN OWNR/Y TSN-TM DBDVL132 14160 1 READY TO RUN ADDIT 997 C02 95727 DBDBBBDA :01 JOBNAME R-UNIT TASK VALUE/RID STATJOB2 33654 1 1 PAY
AUTOINFO Function
The DBUTLTY AUTOINFO function allows you to select a given MUF and quickly generate information about that environment. This information can be helpful for you and for your communications to Support about a MUF problem.
Execute AUTOINFO while the MUF is experiencing the problem. However, AUTOINFO can be executed after the MUF has come down or has been cycled. While it does not furnish as much information about a particular situation from the previous MUF execution, valuable environmental information is provided.
Sample Report
 
The following example shows a sample report page. For an example report header, see Sample Report Headers.
MUF IS AVAILABLE, INFORMATION IS PROVIDED BY THE MUF. MUFNAME: MUF4 RELEASE: 15.1 JOB/STC NAME: QA12MUF4 CXXNAME: QAMUF4 JOBID: JOB11528 SYSTEM: CA31 ENABLED TIME: 2008/11/11 13:12:17 CURRENT MUF TIME: 2008/11/11 13:14:59 MUF IS SHADOW: N MUF HAS SHADOW: N DB SUBSYS PRESENT: Y SQL: Y EXTERNAL SECURITY: N ACCOUNTING ON: N DBIDS: DST: 1000 HISTORY: 1007 CBS TEMP: 0006 CBS HEUR: 1006 TASKS: TOTAL: 00250_ XCF: 00250_ CCI: 00050_ SIZE: 46080_
If AUTOINFO is executed after a MUF has ended but has not been restarted, the function ends with a U0004 condition code. This code notifies you that while the report has executed, certain data was not available.
MUF Termination
The MUF can be shut down in the following ways:
 
Note:
 In z/OS, a sample shutdown proc AD15STOP is provided in the INSTJCL library.
The DBUTLTY COMM OPTION=EOJ function or the COMM EOJ console command provides a controlled shutdown. After the EOJ command is received, the MUF allows no new tasks or programs to start accessing the DBMS. Until all existing tasks or programs using the MUF have finished, the MUF does not stop. This condition could apply to CA Datacom Server, TSO, and other CA products processing, if they are being used. A COMM STATUS reflects jobs are still running but it also reflects an EOJ IN PROGRESS.
For more information about both options, see DBUTLTY Reference. AD15STOP is a sample job that the installation provides.
 
Note:
 
Broadcom
 
must
 have the region dump and the report or snaps produced by the MUF to determine the problem if the MUF abends.