Messages for CICS DBCTL

DBCTL-related messages fall into the following categories:

CICS and IMS™ messages relating to CICS tasks that issue DL/I requests include the recovery token. See also Dealing with messages from DBCTL and CICS.

CICS messages relating to DBCTL begin with DFHDB81 or DFHDB82. CICS messages relating to DBCTL with XRF begin with DFHDX83. See the CICS Messages and Codes manual for help on interpreting, and responding to, DFHDBnnnn and DFHDXnnnn messages.

All DBCTL-related messages are routed to a separate destination called CDBC. If you prefer, you can direct them elsewhere (for example to 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 to CDBC. For programming information on coding the CICS-supplied user exit used to re-route messages and on the sample user exit provided to help you do so, see the CICS Customization Guide.

Messages produced with DBCTL dumps and traces are sent to the DBCTL master terminal operator. IMS messages begin with "DFS". See the IMS Messages and Codes manual manual for guidance on interpreting, and responding to, IMS messages.

Return codes in DBCTL

When DBCTL responds to CICS with a return code, this can be an MVS™ system abend code, an IMS user abend code, or a DBCTL return code. The return code includes an indicator to help you determine what kind of abend it is. The DBCTL return code (also known as the PAPLRETC) displayed in the CICS trace can contain:

The return code is 4 bytes long and is in the following form:

 The format of the return code is: hhsssuuu.

If the top bit (bit 0 of the HH byte) is set:

 hh is 1000 0000, sss is 324, uuu is 000. 324 (hexadecimal) represents the MVS system abend code 804.

which indicates an MVS system abend code (as explained in the OS/390 MVS System Codes),

 hh is 1000 0000, sss is 000, uuu is 34D. 34D (hexadecimal) represents the IMS user abend code 845.

which indicates a user abend code (as explained, for guidance, in the section on user abend codes in the IMS Messages and Codes manual manual).

If the top bit (bit 0 of the HH byte) is not set, and the DBCTL return code in the CICS trace is nonzero, then UUU is a DBCTL nonzero return code, for example:

hh is 0000 0000, sss is 000, uuu is 030. 30 (hexadecimal) represents the DBCTL return code 48.

as explained, for guidance, in the DBCTL return codes section of the IMS Messages and Codes manual manual.

Using return codes to find out what kind of dump has been produced

The top byte of the return codes indicates whether a dump has been produced and, if so, whether it is an SDUMP or a SNAP dump.

See the IMS Messages and Codes manual manual for guidance on interpreting IMS return codes and DBCTL return codes (also known as DRA return codes). Messages issued by CICS also distinguish the kind of return code you are receiving. See the CICS Messages and Codes manual for help on interpreting and responding to CICS messages.

PAPL request and return codes

The trace examples given contain a number of 4-digit hexadecimal request codes issued by the participant adapter parameter list (PAPL). These request codes are a concatenation of a 2-digit PAPL function code and a 2-digit PAPL subfunction code. For further guidance on the contents of the PAPL, see the appropriate IMS Customization Guide.

Table 10 summarizes the PAPL request codes that are sent from CICS to the DRA, and are displayed in CICS trace output as 4-digit request codes. See Trace entries produced by CICS for examples of traces containing these request codes.

Table 10. PAPL request codes
Event Request code
Connection 0100
Disconnection 0400
Disconnection due to CICS failure 0404
PSB schedule 0301
DL/I request 0303
COMMIT request 0307
PREPARE request 0304
Single-phase SYNCPOINT request 030A
ABORT request 030D
Terminate thread 030F
COMMIT request during resynchronization 0201
ABORT request during resynchronization 0202
Lost because CICS was initial started before resynchronization 0203
DBCTL should not be in-doubt 0204

Table 11 summarizes the PAPL return codes that are sent from the DRA to CICS. CICS intercepts these return codes and displays them as explanatory text in trace output.

Table 11. PAPL return codes
Event Return code
Connection complete 0500
Identify failure 0501
Connection request (DRA INIT) canceled in reply to DFS690 message 0502
DBCTL has terminated abnormally 0503
The DRA has terminated abnormally 0504
/CHECKPOINT FREEZE or /CHECKPOINT PURGE command was issued to terminate DBCTL normally 0505

Related concepts
Problem determination for DBCTL
Interactions between CICS and DBCTL
DBCTL error scenarios
Trace for CICS DBCTL
Dumps for CICS DBCTL
Using CICS EDF to debug application programs in DBCTL
[[ Contents Previous Page | Next Page Index ]]