Troubleshooting intersystem problems
Messages that report CICS® recovery actions and examples of how to resolve indoubt and resynchronization failures can help you troubleshoot problems between systems.
- Messages that report CICS recovery actions
When a communications failure occurs, the connected systems might resolve their local parts of a distributed unit of work in ways that are inconsistent with each other. To warn of this possibility, when a CICS region loses communication with a partner, for each session on which the UOW is in the indoubt period, it issues a DFHRMxxxx message. - Problem determination examples
This section contains examples of how to resolve indoubt and resynchronization failures. - APPC connection quiesce processing
When an APPC parallel-session connection with a CICS Transaction Server for z/OS® region is shut down normally, CICS exchanges information with its partner to discover if there is any possibility that resynchronization is required when the connection is restarted. - Syncpoint exchanges
- Recovery functions and interfaces
This section describes the functions and interfaces provided by CICS for recovery after a communication failure, or a CICS system failure. - Connections that do not fully support shunting
This section describes exceptions that apply, for example, to connections to back-level systems. - Initial and cold starts
This section describes functions to manage the exceptional conditions that can occur in a transaction-processing network when one system performs an initial or cold start.
Related information:
dfht161.html |
Last updated: Monday, 5 June 2017