Troubleshooting CICS ONC/RPC

This section provides some hints on troubleshooting. It follows the general outline:

  1. Define the problem.
  2. Obtain information (documentation) on the problem.

Defining the problem

When you have a problem, first try to define the circumstances that gave rise to it. If you need to report the problem to the IBM® software support center, this information is useful to the support personnel.

  1. What is the system configuration?
  2. What is the connection manager configuration?
  3. When did the problem first occur?
  4. What were you trying to accomplish at the time the problem occurred?
  5. What changes were made to the system before the occurrence of the problem?
  6. What is the problem?
  7. At what point in the processing did the problem occur? (Use Figure 36.)
  8. What was the state of TCP/IP for MVS? (Try the rpcinfo command.)

Documentation about the problem

To investigate most problems, you must look at the dumps, traces, and logs provided with MVS and CICS.

To identify which are likely to be useful for your problem, try to work out the area of CICS ONC RPC giving rise to the problem, and read the relevant section in the rest of this section.

Related concepts
ONC RPC concepts
CICS ONC RPC problem determination
Related tasks
CICS ONC RPC recovery procedures
CICS ONC RPC operational considerations
Using messages and codes for ONC RPC
CICS ONC RPC trace information
ONC RPC dump and trace formatting
Debugging the ONC RPC user-replaceable programs
[[ Contents Previous Page | Next Page Index ]]