0 Read successful, active and alternate signed on
1 Read successful, active signed on
2 Read successful, alternate signed on.
3 Read successful, nothing signed on
4 Same SMF MVS name; IPL time of active earlier than MVS IPL
time
5 Same SMF MVS name; IPL time of alternate earlier than MVS
IPL time
8 CAVM data set access not initialized
10C DBLID not known
1xx Read subtask problem.
If a completion code of ‘0’ through ‘5’ is returned to register 15, each doubleword of
the DBLLIST contains the address (4 bytes) and the length (2 bytes) of the output
from this read. A completion code of ‘8’, ‘10C’, or ‘1xx’ indicates a READ failure.
Reading DBCTL status information from the CAVM data sets
If you are using DBCTL and have active and alternate DBCTL subsystems, status
information about the subsystem connected to the active CICS is written to the
CAVM data sets. However, the supplied sample overseer program does not read
the DBCTL information from the CAVM data set. If you want the overseer to retrieve
this information and to display or use it, you must write your own overseer program.
The information in the CAVM data set about the connected DBCTL subsystem is
updated when the active CICS:
v Establishes a connection to a DBCTL subsystem
v Disconnects normally from a DBCTL subsystem
v Loses a connection to a DBCTL subsystem.
If more than one active CICS is connected to a single DBCTL subsystem, the
CAVM data set for each CICS contains information about the same DBCTL
subsystem. The overseer can recognize this situation because in every case the
DBCTL startup time stamp is the same.
Copy book DFHDXGHD contains the information shown in Figure 70 on page 703.
702 Customization Guide