Dealing with messages from DBCTL and CICS
Messages from DBCTL (in the form DFSnnnn) are sent to one or more consoles as specified in the MCS parameter of the IMSCTRL macro in the IMS generation. These messages include notification of change in status and of abnormal events.
About this task
There are many additional messages in the DBCTL environment.
You can direct them to the console from which DBCTL commands are entered.
However, if the volume of messages is such that it is impractical
to view them live
at the console, you can direct them to the
console log and process them with the tool that your installation
uses to review console output.
The DFS554 message is a notification of the abnormal termination of a BMP region or a thread from a CICS® transaction. If this message is caused by an abnormal termination of a thread that originated from CICS, the message text contains the CICS job name or CICS started procedure name. The text also contains the abend code in the form SSS, UUU where SSS is a system abend code and UUU is an IMS user abend code. See Return codes in DBCTL. The message might contain the characters PSB. If it does, the PSB contained in the message has been stopped. All attempts to schedule that PSB will fail until a /START PROGRAM command is issued for that PSB. For guidance on interpreting DFSnnnn messages, see IMS messages and codes in IMS product documentation .
Messages from CICS that relate to DBCTL (for example, those relating to the CDBC transaction) are sent to the transient data destination CDBC so that they are located in one place. You can reroute these messages from CDBC, as you can with CSMT.
You can suppress or reroute messages sent to transient data queues such as CDBC. You can reroute from CDBC to a list of consoles, from CDBC to a different transient data queue, or reroute console messages from their transient data queues to CDBC. For programming information about coding the CICS-supplied user exit used to reroute messages and the example user exit provided to help you do so, see Global user exit points (by function).
Messages DFHDB8103 and DFHDB8104 are issued if there is a failure to connect to DBCTL. They contain the DBCTL reason codes for the connection failure.
- A schedule request has failed.
- DBCTL has abnormally terminated a thread and, as a result, CICS abnormally terminates the transaction.
You can use message DFHDB8109 to identify the IMS reason for which this CICS transaction has failed. For guidance on interpreting the IMS abend and reason codes, see IMS messages and codes in IMS product documentation.