CICS ONC RPC recovery procedures

Software errors within the server controller may cause it to perform an immediate disable (if this is not prevented by the nature of the error). After an immediate disable of CICS® ONC RPC, CICS continues to run.

CICS ONC RPC is not included in CICS recovery. Registration details are not saved on the CICS catalog. If CICS abends and is then restarted, RPC interface registrations from the previous run are not preserved. After a CICS abend, you must enable CICS ONC RPC as described in Enabling CICS ONC RPC. However, 4-tuple definitions can be stored in the CICS ONC RPC data set. Each time you enable CICS ONC RPC, the definitions can be retrieved from the CICS ONC RPC data set.

If TCP/IP for MVS™ abends, CICS ONC RPC enters immediate disable processing, but CICS continues to run.

The abending of an alias transaction might cause changes to recoverable resources to be backed out. See Updating recoverable resources.

CICS immediate shutdown might leave 3-tuples registered with TCP/IP for MVS. These 3-tuples can be registered again when CICS ONC RPC is enabled without loss of TCP/IP for MVS resources, since CICS ONC RPC always unregisters a 3-tuple before it registers it.

Related concepts
ONC RPC concepts
CICS ONC RPC problem determination
Related tasks
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
Debugging the ONC RPC user-replaceable programs
[[ Contents Previous Page | Next Page Index ]]