Debugging the ONC RPC user-replaceable programs

The user-replaceable programs are:

The debugging of the CICS programs is not dealt with in this manual.

XDR routines

The XDR routines, inbound and outbound, run under the RP TCB. The CICS application programming interface is not available under the RP TCB, so you cannot use EDF, CICS abend handling, or CICS trace to diagnose problems. The printf function must not be used. If an XDR routine has a program check, a C run-time message is written to the CICS job log.

Converter and resource checker

The converter and resource checker run under the QR TCB, and the CICS application programming interface is available.

Using EDF

EDF is available for debugging the resource checker and the Encode function. If you want to use EDF, you must:

Using trace entries

Diagnostic information can be output to the CICS trace by the use of the EXEC CICS ENTER TRACENUM command. The amount of trace information and the information contained within trace entries is at your discretion. See the CICS Application Programming Reference for more information about this command.

Writing messages

Diagnostic messages can be output by using EXEC CICS WRITEQ TD. Message information content, message format, frequency, and destination are at your discretion.

Abends

You are recommended to use EXEC CICS HANDLE ABEND to trap abends. You should collect the diagnostic information you need by tracing, and other forms of diagnostic output, and then return a URP_DISASTER response.

Related concepts
ONC RPC concepts
CICS ONC RPC problem determination
Related tasks
CICS ONC RPC recovery procedures
CICS ONC RPC operational considerations
Troubleshooting CICS ONC/RPC
Using messages and codes for ONC RPC
CICS ONC RPC trace information
ONC RPC dump and trace formatting
[[ Contents Previous Page | Next Page Index ]]