Connecting to DBCTL: overview

You can perform CICS® and DBCTL startup from a TSO terminal or an MVS™ console. Before DBCTL can begin accepting transactions, several things must happen, as shown in Figure 10. The numbers in the figure and corresponding step numbers indicate the sequence of events.

Figure 10. Connecting to DBCTL
 The sequence of events is described fully in the list which follows.

  1. CICS is started by submitting a job or starting a procedure, as described in CICS Operations and Utilities Guide.
  2. DBCTL is started by submitting a job or starting a procedure, as described in Starting DBCTL, DLISAS, and DBRC.
  3. After receiving a DBCTL READY message, indicating that startup is complete, the IMS™ console operator enters a start command, as follows:

    The / used in these commands is explained in Operator communication with DBCTL -- overview. See Restarting DBCTL for information on restart options.

    When the start has completed, the following message is issued:

    DFS994I rtype START COMPLETED

    where rtype is the type of start requested (COLD, WARM, or EMERGENCY).

  4. The CICS operator requests connection to DBCTL using the CDBC transaction.

Step 1 can be done before, during, or after steps 2 and 3. Steps 2 and 3 must be done in the sequence described, and all three steps must be completed successfully before step 4 can begin.

Related concepts
Operations with DBCTL
Connecting DBCTL to CICS automatically
Connection, disconnection, and inquiry transactions for the CICS DBCTL interface
Operator communication with DBCTL -- overview
Dealing with messages from DBCTL and CICS
[[ Contents Previous Page | Next Page Index ]]