Disconnection from DBCTL has failed to complete
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 using,
for example, CEMT INQ TASK to see how far disconnection has progressed.
You will probably find that CDBT is waiting on resource type DBCTL
and resource name DLSUSPND, in which case the request is being processed
by DBCTL.
- If CDBT is waiting on DBCTL, what you do next depends on
whether you have requested “orderly” or “immediate” disconnection.
- If you have requested “orderly” disconnection, it is likely that DBCTL is waiting for conversational tasks to finish. You can override an “orderly” disconnection by requesting “immediate” disconnection, in which case the process should end at once.
- If you have requested “immediate” disconnection, and this does not happen, there is an unexpected wait within IMS. See the IMS™ Diagnosis Guide and Reference for guidance about investigating the problem.
- If CDBT is not waiting on DBCTL, this indicates a problem with CICS code. Contact the IBM® Support Center for further assistance.