DFHRMxxxx messages

DFHRM0001
applid An abend (code code) has occurred at offset X'offset' in module module.
Explanation:

An unexpected program check or abend occurred with abend code aaa/bbbb.

The program status word (PSW) at the time of the program check or abend indicated that CICS was executing at offset X'offset' in module modname. This may have been caused by corruption of CICS code or control blocks.

System action:

A system dump is taken and the system attempts to continue operation unless otherwise directed by entries in the dump table.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Investigate the cause of the program check or abend using the system dump and any previously output diagnostic information provided by CICS, the access methods, or the operating system.

If you cannot resolve the problem, you will need further assistance from IBM. See CICS® Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHRMCD, DFHRMCD1, DFHRMCD2, DFHRMCI2, DFHRMCI3, DFHRMCI4, DFHRMDM, DFHRMLKQ, DFHRMLK1, DFHRMLK2, DFHRMLK3, DFHRMLK5, DFHRML1D, DFHRMLN, DFHRMRS, DFHRMLSF, DFHRMLSP, DFHRMLSD, DFHRMLSO, DFHRMLSS, DFHRMLSU, DFHRMNM, DFHRMNM1, DFHRMNS1, DFHRMNS2, DFHRMOFI, DFHRMRO, DFHRMROO, DFHRMROV, DFHRMRO1, DFHRMROS, DFHRMROU, DFHRMRO2, DFHRMRO3, DFHRMRO4, DFHRMR1D, DFHRMR1E, DFHRMR1K, DFHRMR1S, DFHRMSL, DFHRMSLF, DFHRMSLJ, DFHRMSLL, DFHRMSLD, DFHRMSLV, DFHRMSL1, DFHRMSL2, DFHRMSL3, DFHRMSL4, DFHRMSL5, DFHRMSL6, DFHRMSL7, DFHRMST, DFHRMST1, DFHRMUO, DFHRMUW, DFHRMUWB, DFHRMUWE, DFHRMUWF, DFHRMUWH, DFHRMUWJ, DFHRMUWL, DFHRMUWN, DFHRMUWP, DFHRMUWQ, DFHRMUWS, DFHRMUWU, DFHRMUWV, DFHRMUWW, DFHRMUW0, DFHRMUW1, DFHRMUW2, DFHRMUW3, DFHRMU1C, DFHRMU1D, DFHRMU1E, DFHRMU1F, DFHRMU1G, DFHRMU1J, DFHRMU1K, DFHRMU1N, DFHRMU1R, DFHRMU1S, DFHRMU1U, DFHRMU1V, DFHRMU1W, DFHRMU1Q, DFHRMU1L, DFHRMVP1, DFHRMXNE, DFHRMXN2, DFHRMXN4, DFHRMXN5

XMEOUT Parameters: applid, code,X'offset', module

DFHRM0002
applid A severe error (code X'code') has occurred in module module.
Explanation:

The recovery manager domain has received an unexpected error response from some other part of CICS. The operation requested by recovery manager is described by code X'code'.

For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.

System action:

A system dump is taken and the system attempts to continue operation unless specifically inhibited by dump table entries.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Investigate the cause of the problem as follows:

  1. Determine if the problem can be explained by any previous messages issued from some other CICS component.
  2. Examine the symptom string.
  3. Examine the dump.

If you cannot resolve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHRMDM, DFHRMCD1, DFHRMCD, DFHRMCI2, DFHRMCI3

XMEOUT Parameters: applid, X'code',module

DFHRM0104
date time applid Intersystem communication failure. Resource updates are being committed. Local resources may be out of sync with those on the remote system. Failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been interrupted. The remote system contains the coordinator of this unit of work and the notification of the outcome of the distributed unit of work has not been received.

The unit of work is unilaterally committing the local resource updates rather than waiting for the return of the coordinator system. The unit of work may not shunt for one of the following reasons:

Even if the unit of work was shunted, one of the following reasons will cause it to take unilateral action:

The local resource updates are being committed since either

One system may have committed its resource updates and the other backed out, leaving updates out of synchronization. This is checked for when communication is re-established, and one of the following messages is issued:

The original failure information provides correlation between this message and its follow-up.

System action:

The system commits the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action, if any, to protect data integrity until the remote and the local data can be synchronized.

Destination:

CSMT

Modules:

DFHRMLSO

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0105
date time applid Intersystem communication failure. Resource updates are being backed out. Local resources may be out of sync with those on the remote system. Failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been interrupted. The remote system contains the coordinator of this unit of work and the notification of the outcome of the distributed unit of work has not been received.

The unit of work is unilaterally backing out the local resource updates rather than waiting for the return of the coordinator system. The unit of work may not shunt for one of the following reasons:

Even if the unit of work was shunted, one of the following reasons will cause it to take unilateral action:

The local resource updates are being backed out since either

One system might have committed its resource updates and the other backed out, leaving updates out of synchronization. This is checked for when communication is re-established, and one of the following messages is issued:

The original failure information provides correlation between this message and its follow-up.

System action:

The system backs out the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action, if any, to protect data integrity until the remote and the local data can be synchronized.

Destination:

CSMT

Modules:

DFHRMLSO

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0106
date time applid Intersystem communication failure. Resource updates will not be committed or backed out until session recovery. Failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been interrupted. The remote system that contains the coordinator of this unit of work failed and the notification of the outcome of the distributed unit of work has not been received. The definition if the locally executing transaction specifies WAIT(YES) so the local resource updates are being held locked. When communication with the remote system is re-established, the resource updates will be committed or backed out, according to the actions of the other system, and one of the following messages is issued:

If the time specified by the WAITTIME in the transaction definition of the locally executing transaction expires before communication is re-established then the resource updates are committed or backed out in accordance with the ACTION attribute and one of the following messages is issued:

If a decision to preempt resynchronization activity is taken at the local system by either:

then again the resource updates are committed or backed out accordingly and one of the following messages is issued:

System action:

Processing continues. Locks associated with the resource updates are preserved.

User response:

Re-establish communication with the remote system as soon as possible.

Destination:

CSMT

Modules:

DFHRMLSS

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0107
date time applid Intersystem communication failure. Resource updates may be out of sync. Failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with a remote system has been interrupted. This may be due to the failure of a session to a remote system or the failure of a CFDT server system. The resource updates in the local system are committing or backing out. The notification of the outcome of the distributed unit of work might not reach the remote system or server. One system might commit its resource updates while the other backs them out leaving updates out of synchronization. This is checked for at session or server recovery, and one of the following messages is issued:

If a decision to preempt resynchronization activity is taken at the local system by either:

then again the resource updates are committed or backed out accordingly and DFHRM0127 is issued.

System action:

The system commits or backs out the local resource updates and releases the locks associated with those updates. Information is retained to enable resynchronization with the remote system.

User response:

Re-establish communication with the remote system as soon as possible.

Destination:

CSMT

Modules:

DFHRMLSO

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0108
date time applid Intersystem communication recovery. Suspended resource updates now being committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

This message is issued during intersystem communication recovery as a follow up to message DFHRM0106. Communication with the remote system that is the coordinator of this unit of work has been re-established and resynchronization is taking place. It has now been established that the remote system completed the synchronization point. The local resource updates are being committed accordingly.

System action:

The system commits the local resource updates and releases the locks associated with those updates.

User response:

None.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0109
date time applid Intersystem communication recovery. Suspended resource updates now being backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

This is an informatory message issued during intersystem communication recovery as a follow up to message DFHRM0106. Communication with the remote system that is the coordinator of this unit of work has been re-established and resynchronization is taking place. It has now been established that the remote system did not complete the synchronization point. The local resource updates are being backed out accordingly.

System action:

The system backs out the local resource updates and releases the locks associated with those updates.

User response:

If required, restart the interrupted transaction.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0110
date time applid Intersystem communication recovery. Unit of work found to be synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Resynchronization with the remote system which is a subordinate in the unit of work has occurred following the resumption of communication, or the unshunting of the unit of work on the local system. It was found either the local or remote system (or both) had already taken a decision for their parts of the distributed unit of work. It has now been established that the decisions in the local and remote systems are synchronized.

System action:

Processing continues.

User response:

None

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0111
date time applid Intersystem communication recovery. Distributed unit of work found to be not synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Resynchronization with the remote system which is a subordinate in the unit of work has occurred following the resumption of communication, or the unshunting of the unit of work on the local system. It was found either the local or remote system (or both) had already taken a decision for their part of the distributed unit of work. It has now been established that the decisions of the local and remote systems are out of synchronization.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0112
date time applid Intersystem communication recovery. The remote system has reinitialized. The local unit of work is committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. It was found that the remote system has reinitialized and now has no knowledge of the unit of work. The resource updates of the distributed unit of work in the remote system might have committed or backed out.

If the session is an MRO session to a pre-CICS Transaction Server system, this message may be issued even if the remote system was not reinitialized. This can only occur if the session failed during its first unit of work since connection.

The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. This will never be received.

The local unit of work is committed in accordance with the ACTION attribute in the transaction definition.

System action:

The system commits the unit of work and releases the locks associated with any resource updates.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0113
date time applid Intersystem communication recovery. The remote system has reinitialized. The local unit of work is backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. It was found that the remote system has reinitialized and now has no knowledge of the unit of work. The resource updates of the distributed unit of work in the remote system might have committed or backed out.

If the session is an MRO session to a pre-CICS Transaction Server system, this message may be issued even if the remote system was not reinitialized. This can only occur if the session failed during its first unit of work since connection.

The unit of work in the local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. This will never be received.

The local unit of work is backed out in accordance with the ACTION attribute in the transaction definition.

System action:

The system backs out the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0114
date time applid Intersystem communication recovery. The remote system has reinitialized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. It was found that the remote system has reinitialized and now has no knowledge of the unit of work. The resource updates of the distributed unit of work in the remote system might have committed or backed out. The unit of work in the local system had previously committed or backed out.

System action:

Processing continues.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0115
date time applid Intersystem communication recovery. The remote system sent mixed heuristic outcome. Resource updates will be committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. It was found that some resource updates in the distributed unit of work committed and some backed out. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The notification received does not determine whether to commit or back out the local resource updates. The definition of the locally executing transaction will be used to decide whether to commit or back out the local resource updates. The local resource updates are committed in accordance with the ACTION attribute in the transaction definition.

System action:

The system commits the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0116
date time applid Intersystem communication recovery. The remote system sent mixed heuristic outcome. The unit of work will be backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. It was found that some resource updates in the distributed unit of work committed and some backed out. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The notification received does not determine whether to commit or back out the resource updates. The local unit of work is backed out in accordance with the ACTION attribute in the transaction definition.

System action:

The system backs out the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined actions to resynchronize resources in local and remote systems, if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0117
date time applid Intersystem communication recovery. The remote system sent mixed heuristic outcome. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. It was found that some resource updates in the distributed unit of work committed and some backed out. The resource updates in the local system had previously committed or backed out.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0118
date time applid Intersystem communication recovery. Resynchronization information from the remote system was not sufficient to determine the outcome of the unit of work. Resource updates will be committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW uowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Information received from the remote system did not determine whether to commit or back out the local resource updates.

The definition of the locally executing transaction is used to decide whether to commit or back out the local resource updates. The local resource updates are committed in accordance with the ACTION attribute in the transaction definition.

System action:

The system commits the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined actions to resynchronize resources in local and remote systems, if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, uowid,X'localuowid'

DFHRM0119
date time applid Intersystem communication recovery. Resynchronization information from the remote system was not sufficient to determine the outcome of the unit of work. Resource updates will be backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Information received from the remote system did not determine whether to commit or back out the resource updates.

The definition of the locally executing transaction is used to decide whether to commit or back out the local resource updates. The local resource updates are backed out in accordance with the ACTION attribute in the transaction definition.

System action:

The system backs out the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action to resynchronize resources in local and remote systems, if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0120
date time applid Intersystem communication recovery. Resynchronization information from the remote system was not sufficient to determine the outcome of the unit of work. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. Information received from the remote system did not determine whether resource updates in the distributed unit of work committed or backed out. The resource updates in the local system had previously committed or backed out. Start of changeWhen the remote system is a CFDT server, resource updates will have been consistent although the remote system no longer records which action was taken. The CFDT resource may have been subsequently deleted.End of change

System action:

Processing continues.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems. Start of changeWhen the remote system is a CFDT server, no further action is required.End of change

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0121
date time applid Intersystem communication recovery. A protocol violation was detected during resynchronization with the remote system. Resource updates will be committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. The local system detected a protocol violation during resynchronization. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The local system cannot determine whether to commit or back out the resource updates to be consistent other resource changes in the distributed unit of work. The definition of the locally executing transaction will be used to decide whether to commit or back out the local resource updates. The local resource updates are committed in accordance with the ACTION attribute in the transaction definition.

System action:

The system commits the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0122
date time applid Intersystem communication recovery. A protocol violation was detected during resynchronization with the remote system. Resource updates will be backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. The local system detected a protocol violation during resynchronization. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The local system cannot determine whether to commit or back out the resource updates to be consistent other resource changes in the distributed unit of work. The definition of the locally executing transaction is used to decide whether to commit or back out the local resource updates. The local resource updates are backed out in accordance with the ACTION attribute in the transaction definition.

System action:

The system backs out the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0123
date time applid Intersystem communication recovery. A protocol violation was detected during resynchronization with the remote system. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been resumed. Resynchronization with the remote system was attempted. The local system detected a protocol violation during resynchronization. The resource updates in the local system had previously committed or backed out.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0124
date time applid Intersystem communication recovery. Resource updates are out of sync. network UOW netuowid remote system name.
Explanation:

Intersystem communication recovery is in progress. The remote system has attempted to resynchronize a unit of work but the local system no longer has any knowledge of that unit of work. This is because the last agent or the presumed abort protocol is being used and the local system backed out the resource updates associated with the unit of work. The remote system has sent notification that the resource updates in the remote system did not back out.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, netuowid, name

DFHRM0125
date time applid Clear pending issued. The connection to the remote system has been set NOTPENDING. Resource updates will be committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

The connection with the remote system has been set NOTPENDING or NORECOVDATA, or the connection is defined with XLNACTION(FORCE). The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Setting the connection with the remote system NOTPENDING or NORECOVDATA preempts the notification of the outcome from the remote system. The definition of the locally executing transaction is used to decide whether to commit or back out the local resource updates. The local resource updates are committed in accordance with the ACTION attribute in the transaction definition.

System action:

The system commits the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN,DFHRMLK4,DFHRMLSO,DFHRMLSS

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0126
date time applid Clear pending issued. The connection to the remote system has been set NOTPENDING. Resource updates will be backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

The connection with the remote system has been set NOTPENDING or NORECOVDATA, or the connection is defined with XLNACTION(FORCE). The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Setting the connection with the remote system NOTPENDING or NORECOVDATA preempts the notification of the outcome from the remote system. The definition of the locally executing transaction is used to decide whether to commit or back out the local resource updates. The local resource updates are backed out in accordance with the ACTION attribute in the transaction definition.

System action:

The system backs out the local resource updates and releases the locks associated with those updates.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN,DFHRMLK4,DFHRMLSO,DFHRMLSS

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0127
date time applid Clear pending issued. The connection to the remote system has been set NOTPENDING. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication between the systems had previously failed during a syncpoint. Resynchronization between the systems has been preempted. The connection with the remote system has been:

If the unit of work in the local system was in-doubt about the outcome of the distributed unit of work, local resource updates are committed or backed out in accordance with the ACTION attribute in the transaction definition.

Since no resynchronization with the remote system is attempted, the resource updates in the local and remote systems might be out of synchronization.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems.

Destination:

CSMT

Modules:

DFHRMLN,DFHRMLK4,DFHRMLSO,DFHRMLSS

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

Start of changeDFHRM0128End of change
Start of changedate time applid Intersystem communication failure. Resource updates are being committed. Local resources may be out of sync with those on the remote system. Failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.End of change
Start of change
Explanation:

Communication with the remote system has failed. The resource updates in the local system are committing. The notification of the outcome of the distributed unit of work might not reach the remote system. One system might commit its resource updates while the other backs them out leaving updates out of synchronization. There will be no resolution message when the local and remote systems resynchronize, because the remote system does not provide the local system with resynchronization information.

End of change
Start of change
System action:

The system commits the local resource updates and releases the locks associated with those updates. Information is retained to enable resynchronization with the remote system.

End of change
Start of change
User response:

Reestablish communication with the remote system as soon as possible. The local system is the coordinator, and will provide indoubt resolution information for the remote system when communication is reestablished. If the remote system has taken a heuristic decision regarding the unit of work, then it should have provided diagnostic information to indicate this.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHRMLSOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changemm/dd/yy, End of changeStart of changehh:mm:ss, End of changeStart of changename, End of changeStart of changetranid, End of changeStart of changetrannum, End of changeStart of changetermid, End of changeStart of changeuserid, End of changeStart of changenetuowid,End of changeStart of changeX'End of changeStart of changelocaluowidEnd of changeStart of change'End of change

Start of changeDFHRM0129End of change
Start of changedate time applid Intersystem communication failure. Resource updates are being backed out. Local resources may be out of sync with those on the remote system. Failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.End of change
Start of change
Explanation:

Communication with the remote system has failed. The resource updates in the local system are backing out. The notification of the outcome of the distributed unit of work might not reach the remote system. One system might commit its resource updates while the other backs them out leaving updates out of synchronization. There will be no resolution message when the local and remote systems resynchronize, because the remote system does not provide the local system with resynchronization information.

End of change
Start of change
System action:

The system backs out the local resource updates and releases the locks associated with those updates. Information is retained to enable resynchronization with the remote system.

End of change
Start of change
User response:

Reestablish communication with the remote system as soon as possible. The local system is the coordinator, and will provide indoubt resolution information for the remote system when communication is reestablished. If the remote system has taken a heuristic decision regarding the unit of work, then it should have provided diagnostic information to indicate this.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHRMLSOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changemm/dd/yy, End of changeStart of changehh:mm:ss, End of changeStart of changename, End of changeStart of changetranid, End of changeStart of changetrannum, End of changeStart of changetermid, End of changeStart of changeuserid, End of changeStart of changenetuowid,End of changeStart of changeX'End of changeStart of changelocaluowidEnd of changeStart of change'End of change

DFHRM0130
applid Recovery manager has successfully quiesced.
Explanation:

The recovery manager has quiesced.

The warm keypoint has been taken.

System action:

Shutdown continues.

User response:

None.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0131
applid Resynchronization required with protocol resources.
Explanation:

This system contained unquiesed state when shutdown was performed. The state may consist of units of work or lognames (lognames can exist for communications protocols IRC and APPC only). This system may need to perform resynchronization with other systems to resolve the outcome of any distributed units of work. This can be done as part of the work of a subsequent CICS system.

The systems with which resynchronization is necessary are reported in messages DFHRM0132 or DFHRM0133.

A subsequent CICS start which reinitializes the catalog and system log data would discard the units of work and/or lognames and cause a possible loss of data integrity.

System action:

Shutdown continues.

User response:

To maintain data integrity, perform an AUTO start and enable resynchronization with the appropriate systems.

Destination:

Console

Modules:

DFHRMNS2

XMEOUT Parameters: applid, protocol

DFHRM0132
date time applid Resynchronization is required with protocol system system.
Explanation:

A unit of work active in the system at shutdown requires resynchronization with the named system. The unit of work was part of a distributed unit of work and resynchronization is necessary to resolve the outcome.

Resynchronization occurs after a subsequent start unless catalog and system log information is reinitialized.

System action:

Shutdown continues.

User response:

If necessary, take user-defined action to protect data integrity until the remote and the local data can be synchronized.

Destination:

CSMT

Modules:

DFHRMLKQ, DFHRMNS2

XMEOUT Parameters: date, time,applid, protocol, system

DFHRM0133
date time applid Resynchronization may be required with protocol system system.
Explanation:

This system exchanged lognames with the remote system and so may require resynchronization with that system.

Resynchronization occurs after a subsequent CICS start unless catalog or system log information is reinitialized.

System action:

Shutdown continues.

User response:

If necessary, take user-defined action to protect data integrity until resynchronization takes place.

Destination:

CSMT

Modules:

DFHRMNS2

XMEOUT Parameters: date, time,applid, protocol, system

DFHRM0134
applid Recovery manager domain failed reading the global catalog, or did not find its control record.
Explanation:

The recovery manager domain has failed while reading the global catalog. Either it was trying to establish the status of the system at the termination of the last execution of CICS and the control record was missing or invalid, or else it could not read the catalog successfully.

System action:

CICS terminates abnormally with a dump.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Investigate the cause of the error using the dump or other diagnostic messages which have been issued (for example, from VSAM or MVS).

If the problem has been caused by an I/O error, see the description of the CICS message already issued from the catalog for guidance.

If the problem has been caused by an invalid data length, see the exception trace entry in the trace table.

If the problem has been caused by a missing control record, the catalog is not suitable for a recoverable start and you should perform an initial start.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0135
date time applid Intersystem communication recovery. Resource updates found to be synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Resynchronization with the remote system which is a subordinate in the unit of work has occurred following the resumption of communication, or the unshunting of the unit of work on the local system. Either the remote system had already taken a decision for its local resource updates in the distributed unit of work, or the remote system was waiting for the decision from this system. In either case, it has now been established that the resource updates in the local and remote systems are synchronized.

System action:

Processing continues.

User response:

None

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0136
applid The applid has changed from old_applid to new_applid. Recovery cannot continue.
Explanation:

Recovery is requested, but the applid recovered by the recovery manager domain from the CICS catalog is different from that specified for the system. This implies that the identity of the system on the network has changed. The system must maintain the same identity on the network for resynchronization to be performed with other systems.

System action:

The system is terminated.

User response:

If recovery and resynchronization is required, correct the applid in the SIT and restart the system. Do not reinitialize catalog or system log information unless you wish to change the identity of the CICS system.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameters: applid, old_applid, new_applid

Start of changeDFHRM0137End of change
Start of changeapplid Recovery of local logname failed. Recovery cannot continue.End of change
Start of change
Explanation:

Recovery is requested, but the local logname could not be recovered by the Recovery Manager domain from the CICS catalog.

End of change
Start of change
System action:

The system is terminated.

End of change
Start of change
User response:

Investigate the possible causes of the failure to read the required data from the CICS catalog. Was the correct Catalog dataset being used? Could the Catalog dataset have been corrupted?

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRMDMEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

DFHRM0139
date time applid UOWLINK deleted by user action. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

This message is issued to confirm the deletion of a UOW-link (UOWLINK) by a CEMT or EXEC CICS SET UOWLINK ACTION(DELETE) command. This command is used to delete links that were created by connections that have since been discarded.

System action:

The system continues normally.

User response:

None.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0140
applid Recovery manager autostart override found with value: 'autofield'.
Explanation:

Recovery manager has located an autostart override record in the global catalog data set which has one of the values AUTOINIT, AUTOCOLD, or AUTOASIS.

System action:

The system continues. If this is an AUTO start, the autostart override value in the message is used to determine the type of start to be performed.

User response:

No action is necessary.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameters: applid, autofield

DFHRM0141
applid Recovery manager autostart override record is not present. Normal processing continues.
Explanation:

There is no autostart override record in the global catalog data set. If you have not used the utility DFHRMUTL this message is normal for an AUTO start and does not represent a problem.

System action:

The default auto start processing continues. This is equivalent to an AUTOASIS value in an autostart override record.

User response:

No action is necessary.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0142
applid Recovery manager autostart override record found to be: 'autofield', and this is not a valid value. AUTOASIS is assumed instead.
Explanation:

Recovery manager has located an autostart override record in the global catalog data set which does not have one of the values: AUTOINIT, AUTOCOLD, or AUTOASIS.

System action:

AUTOASIS is assumed, a dump is taken, and the system continues. The override record will be removed at startup as usual.

User response:

No action is necessary. To correctly set the autostart override record the utility DFHRMUTL should be used prior to starting CICS.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameters: applid, autofield

DFHRM0143
applid Recovery manager autostart override record is invalid. 'AUTOASIS' is assumed.
Explanation:

Recovery manager has found an autostart override record in the global catalog data set, but it has an invalid length or is in the wrong format.

System action:

A dump is taken and the system continues. The autostart override value is assumed to be AUTOASIS. The autostart override record is removed from the catalog at startup as usual.

User response:

Investigate why the global catalog data set should have been incorrectly modified. The DFHRMUTL utility is used to correctly set the autostart override record prior to starting CICS.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0144
applid Recovery manager catalog record indicates that no recovery is possible. An initial start is required.
Explanation:

Recovery manager has read its catalog record from the global catalog data set and this indicates that no recovery is possible. The most likely reason is that CICS detected a corrupted log before the last CICS shutdown. Startup cannot continue with these start parameters.

System action:

CICS terminates abnormally with a dump.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Determine whether the CICS startup job correctly identifies the global catalog data set. If it does, the system log may be unusable and you must perform an initial start of CICS.

If the global catalog data set was incorrectly identified, retry the job with the correct global catalog data set.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0145
applid Recovery manager does not recognize the form of start requested by SIT parameters and overrides.
Explanation:

Recovery manager cannot determine what sort of CICS start to perform. The parameters on the SIT and any settings read from the catalog data set are inconsistent with a valid start type.

System action:

CICS terminates abnormally with a dump.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

This failure is caused by an internal CICS inconsistency. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0146D
applid Global catalog data set recovery data not found. System log data will be lost. Reply 'GO' or 'CANCEL'.
Explanation:

A cold start has been requested, and no recovery control record information was found in the global catalog data set. Either this is the first execution of CICS with this global catalog data set, the wrong global catalog data set is being used, or the global catalog data set has been initialized without information necessary for recovery.

System action:

The system waits for a response.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

If this is the first time CICS has been run with this global catalog data set, or if it is intended to delete all recovery information from the system log, reply ‘GO’. This forces an initial start with no system log information retained from previous CICS executions. In particular, information used to resynchronize with remote CICS systems is cleared as well as all local recovery information.

If this is not the first time, or if you wish to retain system log information and try with another global catalog data set, reply ‘CANCEL’ to terminate this CICS execution. Nothing is discarded in this case. Check the global catalog data set and try again.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0147
applid Reply CANCEL was received.
Explanation:

A reply of ‘CANCEL’ was received in response to message DFHRM0146.

System action:

CICS terminates.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

None.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

DFHRM0148
date time applid Intersystem communication recovery. Resource updates are in sync. network UOW id netuowid remote system name.
Explanation:

Intersystem communication recovery is in progress. The remote system has attempted to resynchronize a unit of work and the local system no longer has any knowledge of that unit of work. This is because the local system was the coordinator, and the last agent or presumed abort protocols were being used. Any local resource updates associated with the unit of work were backed out. The remote system has sent notification that the resource updates in the remote system are still indoubt (and will be backed out following resynchronization) or have already been backed out.

System action:

Processing continues.

User response:

None.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, netuowid, name

DFHRM0149I
applid Recovery manager autostart override record will be deleted.
Explanation:

Recovery manager has found an autostart override record in the global catalog data set. Start of changeIt is deleted after the correct startup type is determined unless this is a diagnostic run. If this is a diagnostic run the recovery manager global catalog records are not altered.End of change

Start of change
System action:

Unless this is a diagnostic run the record is removed from the global catalog data set and will not influence subsequent starts.

End of change
User response:

None.

Destination:

Console

Modules:

DFHRMDM

XMEOUT Parameter: applid

Start of changeDFHRM0150End of change
Start of changeapplid Diagnostic run due to AUTODIAG override is finished. CICS will now terminate.End of change
Start of change
Explanation:

Recovery manager has performed a diagnostic run and now terminates with a dump. This is a result of an AUTODIAG override in the auto override record.

End of change
Start of change
System action:

The system terminates. A dump is taken.

End of change
Start of change
User response:

No further action is necessary.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRMDMEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHRM0151End of change
Start of changeapplid Diagnostic run is initiated. A simulated AUTO start is performed for diagnostic purposes only.End of change
Start of change
Explanation:

Recovery manager has detected a diagnostic run override (AUTODIAG) on the global catalog. This run of CICS will not perform any application processing and is for diagnostic purposes only.

End of change
Start of change
System action:

The system continues. A dump is taken later prior to terminating.

End of change
Start of change
User response:

No further action is necessary at this time. See the CICS Problem Determination Guide for details of the reasons you might want to perform a diagnostic run, and for other diagnostics you may wish to preserve at the same time.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRMDMEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHRM0152End of change
Start of changeapplid Recovery manager autostart override record is set to AUTODIAG.End of change
Start of change
Explanation:

The recovery manager auto override record on the global catalog has been set to AUTODIAG to allow a diagnostic run before the next initial start.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

No action is necessary. See the CICS Problem Determination Guide for information about how to perform a diagnostic run.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRMDMEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHRM0154End of change
Start of changeapplid Uncommitted local resource updates found on the System Log. COLD start is NOT preserving data integrity.End of change
Start of change
Explanation:

A cold start has been requested, but units of work containing uncommitted local resource updates have been found on the system log. The cold start will ignore this information and so data integrity will not be preserved for the affected resources.

End of change
Start of change
System action:

The cold start continues.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRMU1EEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHRM0156End of change
Start of changeapplid This COLD start will NOT cause any damage to local resources.End of change
Start of change
Explanation:

The recovery manager established that there were no uncommitted resource updates recorded on the system log from a previous execution of CICS. Thus there is no local recovery necessary.

End of change
Start of change
System action:

System initialization continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRMU1EEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

DFHRM0200
applid indoubt_uows indoubt UOWs were reconstructed.
Explanation:

This message displays the number of indoubt units of work (UOWs), indoubt_uows, which were reconstructed on a warm or emergency restart.

It is issued only if there is at least one UOW which is indoubt. It is issued before any of the reconstructed UOWs are unshunted and processed in parallel.

System action:

The system has performed the backwards scan of the system log and is about to start unshunting UOWs which need further processing.

The system commits or backs out UOWs which were indoubt and for which either of the following conditions apply:

Where communications with the coordinator systems is possible, UOWs are unshunted and updates are committed or backed out on the local system. These updates are synchronized with the updates made on the coordinator system.

Where communications with the coordinator systems is not immediately possible, UOWs are preserved until resynchronization with the coordinator system is possible or until the WAITTIME expires. The suspension of these indoubt UOWs causes updated recoverable resources to remain locked against subsequent updates.

User response:

None.

If further investigation is required, use the CEMT INQUIRE UOW INDOUBT and CEMT INQUIRE UOWENQ RETAINED commands once CICS has initialized. These commands detail the indoubt UOWs and the associated retained enqueues.

Destination:

Console

Modules:

DFHRMU1E.

XMEOUT Parameters: applid, indoubt_uows

DFHRM0201
date time applid bfail_uows backout-failed and cfail_uows commit-failed UOWs were reconstructed.
Explanation:

This message displays the number of backout-failed units of work (UOWs), bfail_uows, and the number of commit-failed UOWs, cfail_uows, which were reconstructed on a warm or emergency restart.

This message is issued only if there is at least one such UOW. It is issued before any of the reconstructed UOWs are unshunted and processed in parallel.

Note:
This message is issued before the commit-failed and backout-failed UOWs are processed. Many of these UOWs are likely to be resolved during CICS initialization. Any true commit-failed or backout-failed UOWs are highlighted by further messages issued during CICS initialization. Also, once CICS is fully initialized, the master terminal transaction (CEMT) can be used to determine whether there are any outstanding commit-failed or backout-failed UOWs.
System action:

The system has performed the backwards scan of the system log and is about to start unshunting UOWs which need further processing.

UOWs which have failed to back out locally or commit locally are retried.

User response:

None.

Destination:

CSMT

Modules:

DFHRMU1E

XMEOUT Parameters: date, time,applid, bfail_uows, cfail_uows

DFHRM0202
date time applid inflight_uows inflight UOWs were reconstructed.
Explanation:

This message displays the number of inflight units of work (UOWs), inflight_uows, which were reconstructed on an emergency restart.

It is issued only if there is at least one UOW which is inflight. It is issued before any of the reconstructed UOWs are unshunted and processed in parallel.

System action:

The system has performed the backwards scan of the system log and is about to start unshunting UOWs which need further processing.

User response:

None.

Destination:

CSMT

Modules:

DFHRMU1E.

XMEOUT Parameters: date, time,applid, inflight_uows

DFHRM0203
applid There are indoubt_uows indoubt, cfail_uows commit-failed and bfail_uows backout-failed UOWs.
Explanation:

This message displays the numbers of indoubt units of work (UOWs) indoubt_uows, backout-failed UOWs bfail_uows, and commit-failed UOWs cfail_uows in the CICS system at the time of the normal shutdown.

It is issued only if there is at least one such UOW. If there are none, message DFHRM0204 is issued instead.

Messages DFHRM0203 and DFHRM0204 can be used to determine whether or not it is safe to cold start CICS following a normal shutdown without losing resynchronization information. See DFHRM0204 for more information.

System action:

Shutdown processing continues.

User response:

None.

Destination:

Console

Modules:

DFHRMU1K

XMEOUT Parameters: applid, indoubt_uows, cfail_uows, bfail_uows

DFHRM0204
applid There are no indoubt, commit-failed or backout-failed UOWs.
Explanation:

There are no indoubt, commit-failed, or backout-failed units of work (UOWs) in the CICS system at the time of the normal shutdown.

If there are any such units of work, message DFHRM0203 is issued.

This message indicates that it safe to do a cold start of CICS without losing any resynchronization information.

System action:

Shutdown processing continues.

User response:

None.

Destination:

Console

Modules:

DFHRMU1K

XMEOUT Parameter: applid

DFHRM0205
date time applid An activity keypoint has been successfully taken.
Explanation:

CICS has successfully taken an activity keypoint. This message is also issued for the shutdown keypoint.

System action:

Normal processing continues..

User response:

None.

Destination:

CSMT

Modules:

DFHRMR1K

XMEOUT Parameters: date, time,applid

DFHRM0208
date time applid Intersystem communication recovery. A unit of work recovered only for remote resynchronization is now being committed. Local resources are not synchronized with the unit of work. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

This message is issued during intersystem communication recovery as a follow up to message DFHRM0106. Communication with the remote system that is the coordinator of this unit of work has been re-established and resynchronization is taking place. It has now been established that the remote system completed the synchronization point. Since this unit of work was recovered as part of a cold start, no local resources were locked pending this resynchronization and local resources are not synchronized with this decision.

System action:

The system allows the unit of work to commit for the purposes of resynchronization with remote systems. No local resources are changed.

User response:

None.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0209
date time applid Intersystem communication recovery. A unit of work recovered only for remote resynchronization is now being backed out. Local resources are not synchronized with the unit of work. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

This message is issued during intersystem communication recovery as a follow up to message DFHRM0106. Communication with the remote system that is the coordinator of this unit of work has been re-established and resynchronization is taking place. It has now been established that the remote system did not complete the synchronization point. Since this unit of work was recovered as part of a cold start, no local resources were locked pending this resynchronization and local resources are not synchronized with this decision.

System action:

The system allows the unit of work to back out for resynchronization with remote systems. No local resources are changed.

User response:

None.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0212
date time applid Intersystem communication recovery. The remote system has reinitialized. The unit of work is treated as committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. It was found that the remote system has restarted and has no knowledge of the unit of work. The distributed unit of work in the remote system might have committed or backed out.

The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. This will never be received.

Since this unit of work was recovered only for remote resynchronization, no local resources were locked pending this decision and local resources are not synchronized with the distributed unit of work. The unit of work is treated as committed in accordance with the ACTION attribute in the transaction definition.

If communication was via an MRO session to a pre-CICS Transaction Server system, this message may be issued even if the remote system was not restarted. This can only occur if the session failed during its first unit of work since connection.

System action:

The system continues. Further remote resynchronization treats this unit of work as committed.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0213
date time applid Intersystem communication recovery. The remote system has reinitialized. The unit of work is treated as backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. It was found that the remote system has restarted and has no knowledge of the unit of work. The distributed unit of work in the remote system might have committed or backed out. The unit of work in the local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. This will never be received.

Since the unit of work was recovered only for remote resynchronization no local resources were locked pending this outcome and local resources are not synchronized with the distributed unit of work.

The local unit of work is treated as backed out in accordance with the ACTION attribute in the local transaction definition.

If communication was via an MRO session to a pre-CICS Transaction Server system, this message may be issued even if the remote system was not reinitialized. This can only occur if the session failed during its first UOW since connection.

System action:

The system continues. Further remote resynchronization treats this unit of work as backed out.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0214
date time applid Intersystem communication recovery. The remote system has reinitialized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. It was found that the remote system has restarted and has no knowledge of the unit of work. The distributed unit of work in the remote system might have committed or backed out.

Since this unit of work was recovered only for remote resynchronization, no local resources were locked pending a decision and so local resources are not synchronized with the distributed unit of work.

System action:

Processing continues.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0215
date time applid Intersystem communication recovery. The remote system sent mixed heuristic outcome. The unit of work is treated as committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. It was found that some resource updates in the distributed unit of work committed and some backed out. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The notification received does not determine whether the unit of work should be committed or backed out. The unit of work is treated as committed in accordance with the ACTION attribute in the transaction definition.

Since this unit of work was recovered only for remote resynchronization, no local resources were locked pending this outcome and local resources are not synchronized with this decision.

System action:

The system continues. Further remote resynchronization treats this unit of work as committed.

User response:

Take user-defined action to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0216
date time applid Intersystem communication recovery. The remote system sent mixed heuristic outcome. The unit of work is treated as backed out. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. It was found that some resource updates in the distributed unit of work committed and some backed out. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The notification received does not determine whether to commit or back out the resource updates. The local unit of work is treated as backed out in accordance with the ACTION attribute in the transaction definition.

Since this unit of work was recovered only for remote resynchronization, no local resources were locked pending this decision and local resources are not synchronized with the distributed unit of work.

System action:

The system continues. Further remote resynchronization treats this unit of work as backed out.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0218
date time applid Intersystem communication recovery. Resynchronization information from the remote system was not sufficient to determine the outcome of the unit of work. Local resources are not synchronized. The distributed unit of work is committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW uowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Information received from the remote system did not determine whether to commit or back out the unit of work.

The unit of work is committed in accordance with the ACTION attribute in the local transaction definition.

Because this unit of work was recovered only for remote resynchronization, no local resources were locked pending resolution of the unit of work, and local resources are not synchronized with this commit.

Any further remote resynchronization treats this unit of work as committed.

System action:

The system commits the unit of work for the purposes of remote resynchronization.

User response:

Take user-defined actions to resynchronize resources in local and remote systems, if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, uowid,X'localuowid'

DFHRM0219
date time applid Intersystem communication recovery. Resynchronization information from the remote system was not sufficient to determine the outcome of the unit of work. The distributed unit of work is backed out. Local resources are not synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Information received from the remote system did not determine whether to commit or back out the unit of work.

The unit of work is backed out in accordance with the ACTION attribute in the local transaction definition.

Because this unit of work was recovered only for remote resynchronization, no local resources were locked pending resolution of the unit of work, and local resources are not synchronized with this back out.

Any further remote resynchronization treats this unit of work as backed out.

System action:

The system backs out the unit of work for the purposes of remote resynchronization.

User response:

Take user-defined action to resynchronize resources in local and remote systems, if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0220
date time applid Intersystem communication recovery. Resynchronization information from the remote system was not sufficient to determine the outcome of the unit of work. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. Information received from the remote system did not determine whether the distributed unit of work committed or backed out.

Since this unit of work was recovered only for remote resynchronization, no locks on local resources were held pending resolution of this unit of work, and the local resources are not synchronized with the distributed unit of work.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0221
date time applid Intersystem communication recovery. A protocol violation was detected during resynchronization with the remote system. The distributed unit of work is treated as committed. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. The local system detected a protocol violation during resynchronization. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The local system cannot determine whether the distributed unit of work was committed or backed out.

The distributed unit of work is treated as committed in accordance with the ACTION attribute in the local transaction definition.

Since this unit of work was recovered only for remote resynchronization, no local resources were locked pending resolution and no local resources are synchronized with this decision.

Any further remote resynchronization treats this unit of work as committed.

System action:

The system continues.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0222
date time applid Intersystem communication recovery. A protocol violation was detected during resynchronization with the remote system. The distributed unit of work is treated as backed out. Local resources are not synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. The local system detected a protocol violation during resynchronization. The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. The local system cannot determine whether the distributed unit of work committed or backed out.

The distributed unit of work is treated as backed out in accordance with the ACTION attribute in the transaction definition.

System action:

The system continues. Any further remote resynchronization treats this unit of work as backed out.

User response:

Take user-defined action to resynchronize the resources in the local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0223
date time applid Intersystem communication recovery. A protocol violation was detected during resynchronization with the remote system. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system has been re-established. Resynchronization with the remote system was attempted. The local system detected a protocol violation during resynchronization.

Since this unit of work was recovered only for remote resynchronization, local resources are not synchronized and in this case the outcome of the distributed unit of work cannot be determined.

System action:

Processing continues.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0225
date time applid Clear pending issued. The connection to the remote system has been set NOTPENDING. The distributed unit of work is treated as committed. Local resources are not synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

The connection with the remote system has been set NOTPENDING or NORECOVDATA, or the connection is defined with XLNACTION(FORCE). The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Setting the connection with the remote system NOTPENDING or NORECOVDATA preempts the notification of the outcome from the remote system.

Since this unit of work was recovered only for remote resynchronization, no local resources were locked pending resolution, and local resources are not synchronized with this decision.

The distributed unit of work is treated as committed in accordance with the ACTION attribute in the local transaction definition.

System action:

The system continues. Further remote resynchronization treats the unit of work as committed.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLK4

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0226
date time applid Clear pending issued. The connection to the remote system has been set NOTPENDING. The distributed unit of work is treated as backed out. Local resources are not synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

The connection with the remote system has been set NOTPENDING or NORECOVDATA, or the connection is defined with XLNACTION(FORCE). The local system was in-doubt about the outcome of the distributed unit of work and expected to receive notification of the outcome from the remote system. Setting the connection with the remote system NOTPENDING or NORECOVDATA preempts the notification of the outcome from the remote system.

Since this unit of work was recovered only for remote resynchronization, no local resources were locked pending resolution, and local resources are not synchronized with this decision.

The distributed unit of work is treated as backed out in accordance with the ACTION attribute in the local transaction definition.

System action:

The system continues. Further remote resynchronization treats this unit of work as backed out.

User response:

Take user-defined actions to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLK4

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0227
date time applid Clear pending issued. The connection to the remote system has been set NOTPENDING. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

The connection with the remote system has been set NOTPENDING. The unit of work is recorded as committed or backed out, but since this unit of work was recovered only for remote resynchronization, local resources might not be synchronized with this decision.

The local system did not receive acknowledgment that the remote system had received notification of the outcome of the unit of work.

No further resynchronization with this remote system is attempted and the distributed unit of work in the local and remote systems may not be synchronized.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize resources in local and remote systems if necessary.

Destination:

CSMT

Modules:

DFHRMLK4

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0228
applid indoubt_uows indoubt UOWs have been recovered for the purpose of remote resynchronization. Local resources are not synchronized with these UOWs.
Explanation:

This message displays the number of indoubt units of work (UOWs), indoubt_uows, which have been recovered for resynchronization with remote systems. This message is only issued on cold starts. Local resources may not be kept synchronized with remote resources because CICS is cold starting.

It is issued only if there is at least one UOW which is indoubt. It is issued before any of the reconstructed UOWs are unshunted and processed in parallel.

System action:

The system has performed the backwards scan of the system log and is about to start unshunting UOWs where resynchronization is possible.

Where communications with the remote system or systems is not immediately possible, UOWs are preserved until resynchronization is possible or until WAITTIME (defined on the transaction definition) expires.

This message is followed by message DFHRM0208 if the UOW has been committed, or by DFHRM0209 if the UOW has been backed out on the remote system or systems.

User response:

None.

Destination:

Console

Modules:

DFHRMU1E.

XMEOUT Parameters: applid, indoubt_uows

DFHRM0229
date time applid bfail_uows backout-failed and cfail_uows commit-failed UOWs have been recovered for the purpose of remote resynchronization. Local resources are not synchro nized with these UOWs.
Explanation:

This message displays the number of backout-failed units of work (UOWs), bfail_uows, and the number of commit-failed UOWs, cfail_uows, which have been recovered for resynchronization with remote systems. These UOWs may now be in backout-waiting or commit-waiting states after cold start recovery processing. This message is only issued on cold starts. Local resources may not be kept synchronized with remote resources because CICS is cold starting.

This message is issued only if there is at least one such UOW. It is issued before any of the reconstructed UOWs are processed.

System action:

The system has performed the backwards scan of the system log and is about to start resynchronization for UOWs that require this.

Where communications with the remote system or systems is not immediately possible, UOWs are preserved until resynchronization is possible or until WAITTIME (defined on the transaction definition) expires.

This message is followed by message DFHRM0208 if the UOW has been committed, or by DFHRM0209 if the UOW has been backed out on the remote system or systems.

User response:

None.

Destination:

CSMT

Modules:

DFHRMU1E

XMEOUT Parameters: date, time,applid, bfail_uows, cfail_uows

DFHRM0230
date time applid inflight_uows inflight UOWs have been recovered for the purpose of remote resynchronization. Local resources are not synchronized with these UOWs.
Explanation:

This message displays the number of inflight units of work (UOWs), inflight_uows, which have been recovered for resynchronization with remote systems. This message is issued only on cold starts. Local resources may not be kept synchronized with remote resources because CICS is cold starting.

It is issued only if there is at least one UOW which is inflight. It is issued before any of the reconstructed UOWs are unshunted and processed in parallel.

System action:

The system has performed the backwards scan of the system log and is about to start unshunting UOWs where resynchronization is possible.

Where communications with the remote system or systems is not immediately possible, UOWs are preserved until resynchronization is possible or until WAITTIME (defined on the transaction definition) expires.

This message is followed by message DFHRM0208 if the UOW has been committed, or by DFHRM0209 if the UOW has been backed out on the remote system or systems.

User response:

None.

Destination:

CSMT

Modules:

DFHRMU1E.

XMEOUT Parameters: date, time,applid, inflight_uows

DFHRM0235
date time applid Intersystem communication recovery. Local resources are not synchronized. Original failure date mm/dd/yy failure time hh:mm:ss remote system name transaction tranid task number trannum terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

Communication with the remote system that is a subordinate of this unit of work failed and has been re-established. Resynchronization with the remote system has occurred. Either the remote system has already taken a decision for its local resource updates in the distributed unit of work, or the remote system was waiting for the decision from this system. In either case, since this unit of work was recovered only for remote resynchronization, the local resources are not synchronized.

System action:

Processing continues.

User response:

Take action to resynchronize resources in the local and remote systems, if necessary.

Destination:

CSMT

Modules:

DFHRMLN

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, name, tranid, trannum, termid, userid, netuowid,X'localuowid'

DFHRM0300
KEYWORD 'keyword' IS INVALID OR MISUSED.
Explanation:

The SYSIN data set for DFHRMUTL contains an unrecognized keyword or a keyword which is used incorrectly.

System action:

The DFHRMUTL job terminates.

User response:

Correct the invalid keyword and retry.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0301
applid Force purge of transaction ID tranid task number taskno has been deferred because unit of work X'uowid' is in post commit syncpoint processing.
Explanation:

CICS has received a request to force purge task taskno. The unit of work, uowid, associated with the target of the force purge request is in a critical phase of syncpoint processing. The target task cannot be purged while it is in this state.

System action:

CICS attempts to defer the purge until the target task is no longer protected against purge.

If the syncpoint occurs at the end of the task, the task is permanently protected against purge.

User response:

Normally the task should remain in this critical phase of syncpoint for only a short time. If the target task still has not ended, investigate why unit of work uowid has still to complete syncpoint processing.

See the CICS Problem Determination Guide for guidance about diagnosing task waits.

Note:
Because of the circumstances under which this message is issued, it can only be issued to the console. It should not be rerouted to a transient data queue.
Destination:

Console

Modules:

DFHRMU1N

XMEOUT Parameters: applid, tranid,taskno, X'uowid'

DFHRM0302
ERROR {OPENING | READING | WRITING | CLOSING} THE {DFHGCD |NEWGCD} DATA SET RETURN CODE: X'vsam_retcode', REASON: X'vsam_reason'.
Explanation:

An error occurred when processing a VSAM data set. The VSAM return and reason codes are X'vsam_retcode' and X'vsam_reason'.

System action:

The DFHRMUTL job terminates.

User response:

See the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets manual for the meaning of the return and reason codes. Check the syslog for associated data services messages.

If the error is in opening the NEWGCD data set, ensure that the VSAM cluster:

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0303
ERROR {OPENING | READING | WRITING} THE {SYSIN | SYSPRINT} DATA SET.
Explanation:

An error occurred when processing a QSAM data set.

System action:

The DFHRMUTL job terminates.

User response:

Ensure that the data set DD card is properly defined. Look for associated syslog messages to identify the source of the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0304
INVALID OR MISSING SET_AUTO_START PARAMETER.
Explanation:

The SET_AUTO_START parameter in the SYSIN data set for DFHRMUTL is missing or incorrectly specified.

System action:

The DFHRMUTL job terminates.

User response:

Ensure that the parameter is in the first line of SYSIN, and the keywords are separated by commas without intervening blanks.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0305
SYSIN DATA SET CAN HAVE AT MOST ONE RECORD.
Explanation:

The SYSIN data set should contain either no records or else a single record specifying the parameters for DFHRMUTL.

System action:

The DFHRMUTL job terminates.

User response:

Correct the records in the SYSIN data set and retry.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0306
CANNOT COPY A GCD WITH NO CONTROL INFORMATION.
Explanation:

The COLD_COPY keyword has been specified for a global catalog data set which has no recovery manager control information in it. It is not possible to create a reduced new catalog from an empty catalog.

System action:

The DFHRMUTL job terminates.

User response:

You should use COLD_COPY only to copy a catalog that has been used by CICS. To initialize a catalog for an initial start, use DFHRMUTL with the SET_AUTO_START=AUTOINIT parameter without attempting to copy it with COLD_COPY.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0307
KEYWORD 'keyword' IS REPEATED IN THE SYSIN DATA SET.
Explanation:

Keyword keyword has been repeated in the first line of the SYSIN data set for DFHRMUTL.

System action:

The DFHRMUTL job terminates.

User response:

Remove the duplicate keyword and retry.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0308
SET_AUTO_START=AUTOASIS INVALID. GCD IS A COLD_COPY AND HAS NOT BEEN USED BY CICS.
Explanation:

The keyword SET_AUTO_START specified AUTOASIS, but the global catalog supplied in data set DFHGCD has been copied with the DFHRMUTL COLD_COPY function and has not yet been used by CICS. This change is not allowed because the catalog no longer has the necessary records to allow an emergency or warm start.

System action:

The DFHRMUTL job terminates.

User response:

If you need to perform an emergency or warm start, use a restored copy of the global catalog taken before the run of DFHRMUTL which performed the COLD_COPY. If you do not need an emergency or warm start, change the parameter to AUTOINIT or AUTOCOLD and retry.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0309
GCD HAS NOT BEEN USED BY CICS. YOU MUST SPECIFY SET_AUTO_S TART=AUTOINIT
Explanation:

The keyword SET_AUTO_START specified AUTOCOLD or AUTOINIT, but the global catalog supplied in data set DFHGCD has never been used by CICS.

System action:

The DFHRMUTL job terminates.

User response:

Change the SET_AUTO_START parameter to AUTOINIT and retry.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

DFHRM0311
COLD_COPY KEYWORD INVALID WITH SET_AUTO_START=AUTOASIS.
Explanation:

The input parameters specified keyword COLD_COPY, but also contained SET_AUTO_START=AUTOASIS. This combination is not supported because CICS can only perform a COLD or INITIAL start using a catalog data set that has been cold-copied, because all definitional records have been removed.

System action:

The DFHRMUTL job terminates.

User response:

Either specify AUTOCOLD or AUTOINIT as the SET_AUTO_START value, or remove the COLD_COPY keyword and retry.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHRMUTL

Start of changeDFHRM0312End of change
Start of changeAUTODIAG WITH COLD_COPY NOT ALLOWED.End of change
Start of change
Explanation:

In the parameters for the DFHRMUTL job the option COLD_COPY was specified with SET_AUTO_START=AUTODIAG. This is not allowed.

End of change
Start of change
System action:

The DFHRMUTL job terminates.

End of change
Start of change
User response:

Resubmit the job with the correct parameters.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHRMUTLEnd of change

Start of changeDFHRM0313End of change
Start of changeAUTODIAG CANNOT BE USED.End of change
Start of change
Explanation:

The keyword SET_AUTO_START specified AUTODIAG, but the global catalog supplied in data set DFHGCD has been copied with the DFHRMUTL COLD_COPY function and has not yet been used by CICS. This change is not allowed because the catalog no longer has the necessary records to allow a diagnostic run.

End of change
Start of change
System action:

The DFHRMUTL job terminates.

End of change
Start of change
User response:

If you need to perform a diagnostic run, use a restored copy of the global catalog taken before the run of DFHRMUTL which performed the COLD_COPY. If you do not need a diagnostic run then change the parameter to AUTOINIT or AUTOCOLD and retry.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHRMUTLEnd of change

Start of changeDFHRM0315IEnd of change
Start of changeAUTOCOLD OR AUTOINIT SHOULD NOT BE USED.End of change
Start of change
Explanation:

This is an informational message.

The global catalog indicates that the previous shutdown of CICS was not controlled (i.e. not a Warm shutdown), or that log information that pertains to shunted Units Of Work (UOWs) is present on the system log. In either case, CICS should not be restarted Cold or Initial, since to do so would threaten data integrity. As such, AUTOCOLD or AUTOINIT should not be specified by the use of the SET_AUTO_START keyword.

End of change
Start of change
System action:

The DFHRMUTL job continues.

End of change
Start of change
User response:

None.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHRMUTLEnd of change

DFHRM0400
applid A unit of work was incompletely reconstructed from the system log.
Explanation:

A unit of work has been only partially reconstructed from the log records on the system log.

The first log record that the unit of work wrote to the system log was not browsed during CICS restart although processing of the unit of work has not completed its syncpoint processing.

The probable cause is that the primary system log stream has been truncated incorrectly or that the secondary system log stream has been truncated or deleted incorrectly. Alternatively, the data on either log stream may have been corrupted so that the chain representing the unit of work was not completely processed during CICS restart.

These effects may be due to the log stream being modified between CICS runs, problems in the MVS logger, or problems in CICS itself. The most likely cause is that the logstream was deleted or modified between CICS runs. If it was deleted, the CICS logger will have issued a message during the CICS restart reporting that it was creating the logstream.

System action:

CICS makes an exception trace entry including the unit of work in which the problem was detected, issues this message, takes a dump, and then terminates abnormally.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Ensure that the primary and secondary system logstreams are valid. If a problem can be rectified, auto-start CICS again.

If the problem cannot be rectified, you should perform an initial start of CICS.

If you are certain that the system log streams have not been deleted or modified between CICS runs, there may be an error in the MVS logger or in CICS. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed. It would be helpful to keep the failing logstream or a report of its contents.

Destination:

Console

Modules:

DFHRMU1E.

XMEOUT Parameter: applid

DFHRM0401
applid There is no system log or an empty system log has been detected.
Explanation:

An empty system log has been detected on a CICS restart which requires the log for recovery processing. This is unexpected because there should always be one or more log records on the system log when CICS has started previously. Alternatively, there is no CICS system log because DUMMY has been specified in the definition of the log stream, and a start that requires a valid system log has been requested.

The probable cause is that the primary system log stream has been destroyed or cleared incorrectly. The data on the primary log stream may have been corrupted so that the CICS logger could not find any valid records on it. Alternatively, the system log has been defined as a DUMMY log inappropriately.

These effects may be due to the log stream being modified between CICS runs, problems in the MVS logger, or problems in CICS itself. The most likely cause is that the logstream was deleted or emptied between CICS runs. If it was deleted, the CICS logger will have issued a message during the CICS restart reporting that it was creating the logstream.

System action:

CICS makes an exception trace entry including the unit of work in which the problem was detected, issues this message, takes a dump, and then terminates abnormally.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Ensure that the primary system logstream is valid, and that it is not defined as DUMMY. If the problem can be rectified, start CICS again in the same way.

If the problem cannot be rectified, perform an initial start of CICS.

If you are certain that the system log streams have not been deleted or modified between CICS runs, there may be an error in the MVS logger or in CICS. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed. It would be helpful to keep the failing logstream or a report of its contents.

Destination:

Console

Modules:

DFHRMSL5

XMEOUT Parameter: applid

[[ Contents Previous Page | Next Page Index ]]