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.

The message can be issued at the time of a session failure, a failure of the partner, or during emergency restart.

When the connection has been reestablished, on each affected session the UOW is unshunted, its state is determined, and another message is issued. For LUTYPE6.1 conversations, these messages might appear only on the initiator side.

All messages contain the following information, so they can be correlated:
  • The time and date of the original failure
  • The transaction identifier and task number
  • The netname of the remote system
  • The operator identifier
  • The operator terminal identifier
  • The network-wide unit of work identifier
  • The local unit of work identifier.
The following types of messages associated with intersystem session failure and recovery are produced:
  • Messages when contact is lost with the coordinator of the UOW. See Table 1 and Table 2.
  • Messages when WAIT(YES) is specified on the transaction definition and shunting is possible. See Table 1.
  • Messages when WAIT(NO) is specified, or when shunting is not possible. See Table 2.
  • Messages when contact is lost with a subordinate in the UOW. See Table 3.
For full details about a message, see CICS messages.
Table 1. WAIT(YES) session failure messages. The failure is between the session and the coordinator of the UOW, WAIT(YES) is specified on the transaction definition, and shunting is possible. In each stage (1 and 2), the messages that CICS issues depend on the circumstances that apply, as shown in columns 2 and 4. Stage 1 applies to MRO messages, and Stage 2 applies to IPIC and APPC messages.
Sequence of messages Circumstances Messages issued Meaning of messages
Stage 1 Session failure DFHRM0106 Intersystem session failure. Resource changes are not committed or backed out until session recovery.
Stage 1 System failure or restart — —
Stage 2 Session recovery successful DFHRM0108 Intersystem session recovery. Suspended resource changes now being committed.
Stage 2 Session recovery successful DFHRM0109 Intersystem session recovery. Suspended resource changes now being backed out.
Stage 2 Wait time exceeded or SET UOW ACTION issued DFHRM0104 DFHRM0105 See next table.
Stage 2 SET CONNECTION NOTPENDING or XLNACTION (FORCE) or NORECOVDATA issued DFHRM0125 DFHRM0126 Local resources committed or backed out.
Stage 2 Session recovery after a cold start of local resources. DFHRM0209 UOW backed out.
Stage 2 Session recovery after a cold start of local resources DFHRM0208 UOW committed.
Stage 2 Session recovery error; for example, partner started cold 1 DFHRM0112 DFHRM0113 DFHRM0115 DFHRM0116 DFHRM0118 DFHRM0119 DFHRM0121 DFHRM0122 Intersystem recovery error. Local resource changes are committed or backed out.
Note:
  1. LU6.1 only
Table 2. WAIT(NO) session failure messages . The failure is between the session and the coordinator of the UOW. WAIT(NO) is specified on the transaction definition or shunting is not possible. In each stage (1 and 2), the messages that CICS issues depend on the circumstances that apply, as shown in columns 2 and 4. Stage 1 applies to MRO messages, and Stage 2 applies to IPIC and APPC messages.
Sequence of messages Circumstances Messages issued Meaning of messages
Stage 1 Session failure DFHRM0104 DFHRM0105 Intersystem session failure. Resource changes are being committed or backed out and might be out of sync with partner.
Stage 1 System failure or restart — —
Stage 2 Session recovery successful DFHRM0110 Intersystem session recovery. Resource updates found to be synchronized.
Stage 2 Session recovery successful DFHRM0111 Intersystem session recovery. Resource updates found to be out of sync.
Stage 2 SET CONNECTION NOTPENDING or XLNACTION (FORCE) or NORECOVDATA issued DFHRM0127 SET NOTPENDING issued.
Stage 2 Session recovery error; for example, partner started cold 1 DFHRM0112 DFHRM0113 DFHRM0115 DFHRM0116 DFHRM0118 DFHRM0119 DFHRM0121 DFHRM0122 Local resource changes committed or backed out.
Note:
  1. LU6.1 only
Table 3. Subordinate session failure messages. The failure is between the session and a subordinate in the UOW. In each stage (1 and 2), the messages that CICS issues depend on the circumstances that apply, as shown in columns 2 and 4. Stage 1 applies to MRO messages, and Stage 2 applies to IPIC and APPC messages.
Sequence of messages Circumstances Messages issued Meaning of messages
Stage 1 UOW shunted because of failure of session to coordinator — —
Stage 1 Session failure DFHRM0107 Intersystem session failure. Notification of decision might not reach the remote system.
Stage 1 System failure or restart — —
Stage 2 Session recovery successful DFHRM0135 DFHRM0148 1 Intersystem session recovery. Resource updates found to be synchronized.
Stage 2 Session recovery successful DFHRM0110 Intersystem session recovery. Resource updates found to be synchronized, after a unilateral decision on the remote system.
Stage 2 Session recovery successful DFHRM0111 DFHRM0124 Intersystem session recovery. Resource updates found to be out of sync, after a unilateral decision on the remote system.
Stage 2 SET CONNECTION NOTPENDING or XLNACTION (FORCE) or NORECOVDATA issued DFHRM0127 SET NOTPENDING issued.
Stage 2 Session recovery error; for example, partner started cold 2 DFHRM0114 DFHRM0117 DFHRM0120 DFHRM0123 Intersystem session recovery error. Resource changes might be out of sync.
Notes:
  1. DFHRM0124 and DFHRM0148 might occur without a preceding session failure message (DFHRM0107) or shunt.
  2. LU6.1 only


dfht12k.html | Timestamp icon Last updated: Monday, 5 June 2017