Connection to DBCTL has failed to complete

In this situation, the DRA may be in a wait state because you attempted to connect CICS® to DBCTL using the CDBC transaction, but the connection process failed to complete.

Connection to DBCTL using the CICS-supplied transaction CDBC takes place in two phases. In phase 1, CDBC passes the request for connection to IMS and returns. In phase 2, IMS processes the request asynchronously and returns to CICS when connection is complete. To discover where the problem occurred, try to find out how far the connection attempt has progressed by:

Pressing PF2 on the CDBC menu panel to refresh this display, as described in CDBC transaction for connect and disconnect; or
Using the CDBI inquiry panel, as described in CDBI transaction for inquiry.

If connection is in phase 1, the following message is issued:

DFHDB8291 I DBCTL CONNECT PHASE 1 IN PROGRESS

It is very unlikely that a wait will occur during this phase, unless there is a problem with the CICS transaction.

If connection is in phase 2, the following message is issued:

DFHDB8292 I DBCTL CONNECT PHASE 2 IN PROGRESS

If phase 2 fails to complete, the failure is associated with IMS. This may be because:

The DRA startup table is pointing to the wrong system because the DBCTL subsystem ID is incorrect. If this is so, CICS issues a WTO message saying:
```
SUBSYSTEM xxxx NOT ACTIVE.  REPLY WAIT OR CANCEL
```
where xxxx is the subsystem ID indicated on the CDBC panel.
See Defining the IMS DRA startup parameter table for information on specifying the DBCTL subsystem ID.
DBCTL has been initialized, but no restart command has been issued. Remember that DBCTL needs a restart command unless you are using AUTO start. See Connecting to DBCTL:overview and Restarting DBCTL for information on restarting DBCTL and on the implications of different restart options.

If neither of these situations applies, the problem is in IMS; see Diagnosis in IMS product documentation for further guidance.

For an example of the trace entries produced by CICS for a successful connection to DBCTL, see Connection to DBCTL.