Disconnection from DBCTL failed to complete

The DRA might be in a wait state because you attempted to disconnect CICS® from DBCTL using the CDBC transaction, but the disconnection process failed to complete.

For an example of the trace entries produced by CICS for a successful disconnection from DBCTL, see Disconnection from DBCTL.

When you use CDBC to disconnect from DBCTL, it invokes another CICS transaction, CDBT. CDBT makes the disconnection request to DBCTL, and is suspended by CICS while DBCTL services the request asynchronously.

If disconnection fails to complete, you can inquire on CDBT by using CEMT INQ TASK to see how far disconnection has progressed. You might find that CDBT is waiting on resource name DLSUSPND and resource type DBCTL, which means the request is being processed by DBCTL. For an illustrated example, see the description of CEMT INQ TASK in Purging a transaction that is using DBCTL.
  • If CDBT is waiting on DLSUSPND, the next step depends on whether the disconnection requested was orderly or immediate. To find out, you can use the CDBI inquiry panel, as described in CDBI transaction for inquiry.
    • If you requested orderly disconnection, DBCTL is probably waiting for a task that is issuing many DL/I requests, or for a conversational task, perhaps one that is waiting for input from an unattended terminal.

      If necessary, you can override an orderly disconnection by requesting immediate disconnection, in which case the process should conclude at once. However, be aware that immediate disconnection can cause indoubt UOWs, and leave database records unavailable to other CICS systems using that DBCTL until it is reconnected, as described in Deciding whether to use orderly or immediate disconnection.

    • If you requested immediate disconnection, and it has not taken place, an unexpected wait in IMS has probably occurred. For further guidance, see Diagnosis in IMS product documentation.
  • If CDBT is not waiting on DLSUSPND, this indicates a problem in CICS.