An abnormal reply has been received in response to an exchange log name request sent either following a session failure or at first session initiation after system restart. The abnormal reply may indicate that:
For APPC protocol, any synclevel 2 attaches are inhibited. This prevents recoverable activity between the two systems.
For IRC protocol, the message indicates that resynchronization was attempted and failed.
The most likely cause of the message is an initial start (as opposed to emergency restart or its equivalent) of this system when the remote system has resynchronization work outstanding. If it is a cold or warm mismatch or log name mismatch, other diagnostic messages on the local system may indicate the reason for the error. If it is not, examine the log of the remote system which should have generated diagnostic information describing the reason for the abnormal response.
For APPC protocol where a logname mismatch is suspected, override the error situation by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
For IRC, the message may indicate an initial start of one system when the other has resynchronization outstanding; the resynchronization was started before the initial start occurred and becomes invalid. The associated unit of work may need to be committed by using CEMT SET UOW. The message should not recur.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol
A cold start indication was received from the remote system during an exchange log names sequence. However, this system has units of work that need resynchronizing from the previous run. An exchange log names sequence is started either following a session failure or at first session initiation after system restart; both the local and remote systems may initiate the sequence at the same time.
Any synclevel 2 attaches are inhibited. This means that recovery activity between the two systems is prevented.
Override the error by issuing CEMT SET CONN(sysid) NOTPENDING commands for the failing connection.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol
A failure has occurred in the exchange log names process which is carried out either following a session failure or at first session initiation after system restart. This system’s memory of the remote system’s log name conflicts with the log name sent by the remote system.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For APPC protocol, any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocol, resynchronization was attempted and failed.
For APPC, override the error by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
For IRC, the message may indicate the initial start of one system when the other has resynchronization outstanding; the resynchronization was started before the initial start occurred and becomes invalid. The associated unit of work may need to be committed by using CEMT SET UOW. The message should not recur.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol, local_logname, remote_logname
This message is issued when a failure has occurred in the exchange log names process which is carried out prior to resynchronization following an earlier session failure. System sysid has sent an exchange log names request which contains the remote system’s memory (remote_logname) of this system’s log name (local_logname).
This system has detected a log name mismatch. This indicates that system sysid and this system do not have the correct logs for resynchronization.
For APPC protocol, any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocol, the message indicates that resynchronization was attempted and failed.
For APPC, override the error by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection It may be necessary to issue this command (or its equivalent) on both sides of the connection.
For IRC, the message may indicate the initial start of one system when the other has resynchronization outstanding; the resynchronization was started before the initial start occurred and becomes invalid. The associated unit of work may need to be committed by using CEMT SET UOW. The message should not recur.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol, local_logname, remote_logname
This message is issued when an FMH7 has been received in response to an exchange log name reply. An exchange log names sequence is sent either following a session failure or at first session initiation after system restart. The remote system started the sequence, and the FMH7 reply indicates that the remote system failed to interpret the exchange log name reply data sent to it.
For APPC protocol, any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocol, the message indicates that resynchronization was attempted and failed. Communication continues.
Investigate the cause of the error using the system dump. Format the control blocks for the trace domain and the terminal control program. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this exchange log names conversation.
The APPC send and receive buffers for a session are clearly labelled in the dump and are printed below the TCTTE for the session to which they belong. For IRC, the TIOA contains the equivalent data. Check the data against the format of the exchange log names reply GDS variable. The correct format of this SNA defined field can be found in the SNA Formats manual.
Examine the log of the remote system. If a protocol violation was detected, the remote system may have generated diagnostic information itself which may help to diagnose the cause.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol
This system’s memory of the protocols previously negotiated with the remote system conflicts with the indicators sent in an exchange log names variable.
For APPC protocol, any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocols, resynchronization fails. Communications continue normally.
For APPC protocols, the indicators expected from a CICS Transaction Server system are: basic support, X'70'; extended support, X'C000'. For CICS/ESA 4.1 the expected indicators are: basic support, X'40'; extended support, X'0000'. If this combination of the four indicator fields appears in the message, first check that you have Initial started the partner system at the CICS Transaction Server level during a migration from CICS/ESA 4.1, or Cold started a CICS/ESA 4.1 system after running CICS Transaction Server. If this possibility can be ruled out, the message may indicate a logic error in CICS or in the remote system and you may need assistance from IBM to prevent a recurrence. See CICS Problem Determination Guide for guidance on how to proceed.
You can override the error situation by issuing CEMT SET CONN(sysid) NORECOVDATA commands for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
For IRC protocols, you may need to use the CEMT SET UOW command to resolve the state of any units or work which cannot be resolved by the normal resynchronization process.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, protocol, sysid, netname, X'ww', X'xx', X'yyyy',X'zzzz'
An FMH7 has been received in response to an exchange log names reply. An exchange log names sequence is sent either following a session failure or at first session initiation after system startup. This system was either started with the SIT parameter START=INITIAL or CEMT SET CONN(sysid) NORECOVDATA has been issued, both of which reset the state of the connection. This means that no log name is stored for the remote system.
For APPC protocols, the FMH7 reply may indicate one of two causes:
For IRC protocol, the problem is caused by the failure of the remote system to interpret the exchange log names reply data.
For APPC protocol, any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocol, the message indicates that resynchronization was attempted and failed. Communication continues.
The most likely cause of the message is an initial start (as opposed to emergency restart or its equivalent) of this system when the other has resynchronization work outstanding. This can be confirmed by examining the message log of the remote system.
For APPC protocol, the connection on the remote system may need to be reset by issuing the CEMT SET CONN(sysid) NOTPENDING command against the connection entry for this system.
For IRC protocol, a protocol violation or logic error is the only possible cause.
If a cold/warm mismatch is eliminated as the cause of the error, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol
This message is issued when an abnormal reply has been received in response to an exchange log name request. An exchange log names sequence is sent either following a session failure or at first session initiation after system startup. This system was either started with the SIT parameter START=INITIAL, or CEMT SET CONN(sysid) NORECOVDATA has been issued, and no log name is stored for the remote system. The abnormal reply may indicate one of two causes in the case of APPC protocol.
For IRC protocol, the problem is caused by the failure of the remote system to interpret the exchange log name data.
For APPC protocol, any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocol, the message indicates that resynchronization was attempted and failed. Communication continues.
The most likely cause of the message is an intial start (as opposed to emergency restart or its equivalent) of this system when the other has resynchronization work outstanding. This can be confirmed by examining the message log of the remote system.
For APPC protocol, the connection on the remote system may need to be reset by issuing the CEMT SET CONN(sysid) NOTPENDING command against the connection entry for this system.
For IRC protocol, a protocol violation or logic error is the only possible cause.
If a cold/warm mismatch is eliminated as the cause of the error, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol
This message is issued when an FMH7 has been received in response to an exchange log name reply.
An exchange log names sequence is sent either following a session failure or at first session initiation after system startup. Both systems have records of previous contact and have log names stored which were being verified by the exchange log names protocol, which was initiated by the remote system.
The FMH7 may indicate one of two causes:
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For LU6.2 protocol, any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocol, the message indicates that resynchronization was attempted and failed. Communication continues.
For APPC protocol, the connection may need to be reset by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection It may be necessary to issue this command (or its equivalent) on both sides of the connection.
The cause of the error may be indicated by diagnostic information produced by the remote system. The system dump taken by local system can be used to investigate the possibility of an error in the exchange log names reply GDS.
Format the control blocks for the trace domain and the terminal control program. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this exchange log names conversation.
The APPC send and receive buffers for a session are clearly labelled in the dump and are printed below the TCTTE for the session to which they belong. For IRC, the TIOA contains the equivalent data. Check that the data against the format of the exchange log names reply GDS variable. The correct format of this SNA defined field can be found in the SNA Formats manual.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol
An error has occurred during the transmission of an exchange log names request to a remote system. CICS was attempting to establish the connection on first contact with the partner, or to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
This message implies a failure of the session used to carry the transmission.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
In many cases CICS continues to operate normally, and the resynchronization or connection establishment is retried in an attempt to overcome the session failure. However for APPC protocol, a repeated failure may have resulted in exchange log names flows being unsuccessful preventing any synclevel 2 attaches between the local system and the remote system.
For IRC protocol, resynchronization has failed but the connection continues to operate normally.
Issue CEMT INQUIRE CONN(sysid) and look at the XOK field. If exchange log names has not been done, the exchange log names process can be retried by issuing the CEMT SET CONN(sysid) RESYNC command.
Investigate the cause of the error using the system dump and any previously output diagnostic information provided by CICS, the access methods, or the operating system, and examine the log of the remote system. If a protocol violation was detected, the remote system may have generated diagnostic information itself.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this exchange log names conversation.
If the internal trace table is available, use it to track the commands issued against that session and check that the state transitions of the User state machine are correct. If any of the state transitions are not valid, it is possible that there has been a CICS logic error.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
An error has occurred during the transmission of a compare states request to a remote system. CICS was attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
This implies one of the following:
For APPC protocol connections (but not IRC protocol), the failure may have prevented the completion of the exchange log names protocol and this prevents any synclevel 2 attaches between the local system and the remote system.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For APPC protocol, investigate the state of the connection. Issue CEMT INQUIRE CONN(sysid) and look at the XOK field. If exchange log names has not been done, the exchange log names process can be retried by issuing the CEMT SET CONN(sysid) RESYNC command. If there has been previous successful contact between the systems the connection can be reset to its original state and retried. The state can be reset by issuing CEMT SET CONN(sysid) NORECOVDATA. It may be necessary to issue this command on both sides of the connection.
The cause of the error may be indicated by diagnostic information produced by the remote system. Use the system dump taken by the local system to investigate the possibility of an error in the GDS variables.
Format the control blocks for the trace domain and the terminal control program. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this exchange log names conversation.
The APPC send and receive buffers for a session are clearly labelled in the dump and are printed below the TCTTE for the session to which they belong. For IRC, the TIOA contains the equivalent data. Check that the data against the format of the exchange log names and compare states GDS variables. The correct format of this SNA defined field can be found in the SNA Formats manual.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
An error has occurred during an attempt to receive exchange log names reply data from a remote system. CICS was attempting to initialize the connection, or to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
The message means that:
For APPC protocol the failure of exchange log names may mean that any synclevel 2 attaches are inhibited. This means that recoverable activity between the two systems is prevented.
For IRC protocol, the message indicates that resynchronization was attempted and failed. Communication continues.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For APPC protocol, investigate the state of the connection. Issue CEMT INQUIRE CONN(sysid) and look at the XOK field. If exchange log names has not been done, the exchange log names process can be retried by issuing the CEMT SET CONN(sysid) RESYNC command. If there has been previous successful contact between the systems the connection may be reset to its original state and retried. The state can be reset by issuing CEMT SET CONN(sysid) NORECOVDATA. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
The cause of the error may be indicated by diagnostic information produced by the remote system. Use the system dump taken by the local system to investigate the possibility of an error in the GDS variables.
Format the control blocks for the trace domain and the terminal control program. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this exchange log names conversation.
The APPC send and receive buffers for a session are clearly labelled in the dump and are printed below the TCTTE for the session to which they belong. For IRC, the TIOA contains the equivalent data. Check the data against the format of the exchange log names and compare states GDS variables. The correct format of this SNA defined field can be found in the SNA Formats manual.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
An error has occurred during the receipt of a compare states reply from a remote system. CICS was attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
This implies one of the following:
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
CICS continues to operate normally and the resynchronization attempt is retried at the next opportunity.
Investigate the cause of the error first by examining the log of the remote system which may have produced diagnostic information about the data it received. The problem can be investigated locally using the system dump and any previously output diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain and the terminal control program. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this resynchronization conversation.
If the internal trace table is available, use this to track the commands issued against that session and check that the state transitions of the user state machine are correct. If any of the state transitions are not valid, it is possible that there has been a CICS logic error.
The APPC send and receive buffers for a session are clearly labelled in the dump and are printed below the TCTTE for the session to which they belong. Similar information is contained in the TIOA for IRC sessions. Locate the data for the session in question, and check that the contents of the buffer are correct. The buffer contains the compare states GDS variable. The correct format of this SNA defined data can be found in the SNA Formats manual.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system has received data which it attempted to parse using the exchange log names reply GDS format. Either the data could not be parsed, or invalid data was detected.
This system was attempting to initialize the connection for synclevel 2 work, or to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing. Exchange log names was sent and an invalid reply received.
This failure implies an error in the remote system or a CICS logic error.
If resynchronization was being attempted it has failed and is retried at the next opportunity.
For APPC protocol connections (but not IRC protocol) the failure prevents the completion of the exchange log names protocol and this may prevent any synclevel 2 attaches between the local system and the remote system.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For APPC protocol, investigate the state of the connection. Issue CEMT INQUIRE CONN(sysid) and look at the XOK field. If exchange log names has not been done, the exchange log names process can be retried by issuing the CEMT SET CONN(sysid) RESYNC command. If there has been previous successful contact between the systems the connection may be reset to its original state and retried. The state can be reset by issuing CEMT SET CONN(sysid) NORECOVDATA. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
Investigate the cause of the error using the system dump and any previously output diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
An exception trace entry contains the received data, and the reason for the failure is interpreted. Check the format of the exchange log names reply GDS variable. The correct format of this SNA defined field can be found in the SNA Formats manual.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system has received data which it attempted to parse using the compare states reply GDS format. Either the data could not be parsed or invalid data was detected.
The local system was attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing. Data from the remote system received in reply to the compare states was invalid.
This failure implies an error in the remote system or a CICS logic error.
A system dump is taken, unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
The failure prevents the completion of the resynchronization of distributed resources.
Investigate any units of work for which resynchronization is outstanding using the CEMT INQUIRE UOWLINK SYSID(sysid) command. Use the same command on the remote system to determine whether to commit or backout the unit of work. Alternatively, for APPC connections, resynchronization can be overridden by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
Investigate the cause of the error using the system dump. Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
An exception trace entry contains the received data, and the reason for the failure is interpreted. Check the format of the compare states reply GDS variable. The correct format of this SNA defined field can be found in the SNA Formats manual.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system has detected a protocol violation while resynchronizing with the remote system. CICS was attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing. The resynchronization was initiated by the local system.
This implies one of the following:
CICS continues to operate normally and the resynchronization attempt is retried at the next opportunity.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Diagnostics may have been output by the local CICS system, the access methods, or the operating system. Also, investigate the cause of the error in the remote system. It may have produced diagnostic messages indicating why the resynchronization sequence was terminated.
The resynchronization sequence can be analyzed locally by formatting the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this resynchronization conversation.
The trace entries for the DFHCRRSY program show the state of the conversation which was being used and the data received. At the point of failure a confirmation was expected from the remote system as the final flow in the sequence but was not received.
Compare the resynchronization flows with those documented in the SNA LU6.2 Reference: Peer Protocols manual, (SC30-6808). A possible cause of this error is that the remote system did not observe the correct protocols. Investigation at the remote system may be necessary.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol, sessid
The local system has detected a protocol violation while resynchronizing with the remote system. CICS was attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing. The resynchronization was initiated by the remote system.
This implies one of the following:
CICS continues to operate normally and the resynchronization attempt is retried at the next opportunity.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
See any diagnostics output by the local CICS system, the access methods, or the operating system. Also, investigate the cause of the error in the remote system; it may have produced diagnostic messages indicating why the resynchronization sequence was terminated.
The resynchronization sequence can be analyzed locally by formatting the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this resynchronization conversation.
The trace entries for the DFHCRRSY program show the state of the conversation which was being used and the data received. At the point of failure a request confirmation message was expected from the remote system as the third flow in the sequence but was not received.
Compare the resynchronization flows with those documented in the SNA LU6.2 Reference: Peer Protocols manual, (SC30-6808). A possible cause of this error is that the remote system did not observe the correct protocols; investigation at the remote system may be necessary.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol, sessid
The local system has received an exchange log names request from the remote system but failed while attempting to receive subsequent data which was assumed to be a compare states GDS variable. The remote system was probably attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
This implies one of the following:
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
The resynchronization attempt should be retried at the next opportunity by the remote system. However, for APPC protocol connections, the failure may have resulted in exchange log names flows being unsuccessful and this prevents any synclevel 2 attaches between the local system and the remote system.
Issue CEMT INQUIRE CONN(sysid) and look at the XOK field. If exchange log names has not been done, the error situation may be correctable by issuing CEMT SET CONN(sysid) RESYNC. If this fails to cure the problem, resynchronization can be canceled for an APPC connection by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
Investigate the cause of the error using the system dump and any previously output diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Locate the exception trace entries for the DFHCRRSY program and examine any data sent by the remote system. Also examine the state of the conversation at the point of failure. It should have been in receive state.
A possible cause is that the remote system did not send valid data or failed to follow the protocol for compare states. Compare the resynchronization flows with those documented in the SNA LU6.2 Reference: Peer Protocols manual, (SC30-6808). Investigation at the remote system may be necessary.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system sent a Do_know GDS variable to the remote system but did not receive a valid reply. This indicates an earlier failure of a protected conversation during sync point processing and the resolution of the unit of work. This system was using the Do_know GDS variable to cause resynchronization to be started by the remote system.
This implies an error in the remote system or a CICS logic error.
The resynchronization attempt should be retried at the next opportunity by the remote system.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Issue CEMT SET CONN(sysid) RESYNC to cause resynchronization to be retried.
Investigate the cause of the error using the system dump and any previously output diagnostic information provided by CICS, the access methods or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Locate the exception trace entries for the DFHCRRSY program and examine any data sent by the remote system. Also examine the state of the conversation at the point of failure.
A possible cause is that the remote system did not send valid data, or failed to follow the protocol for Do_Know in which case it may be necessary to obtain further diagnostic material from the remote system.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system sent a System_restart GDS variable to the remote system but did not receive a valid reply. This indicates that the local system has restarted and not previously contacted the remote system as part of the initiation of resynchronization protocols.
This indicates an error in the remote system or a CICS logic error.
The transmission of the message is retried the next time the connection is initialized.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Issue CEMT SET CONN(sysid) RESYNC to cause transmission to be retried.
Investigate the cause of the error using the system dump and any diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Locate the exception trace entries for the DFHCRRSY program and examine any data sent by the remote system. Also examine the state of the conversation at the point of failure.
A possible cause is that the remote system did not send valid data or failed to follow the protocol for the System_restart message. In this case it may be necessary to obtain further diagnostic material from the remote system.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system has received data which it attempted to parse using the exchange log names GDS format. Either the data could not be parsed or invalid data was detected.
The remote system was attempting to initialize the connection for synclevel 2 work or to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing. Exchange log names is sent in both of these cases.
This failure indicates either an error in the remote system or a CICS logic error.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If resynchronization was being attempted, it has failed and is retried at the next opportunity.
For APPC protocol connections (but not IRC protocol), the failure prevents the completion of the exchange log names protocol. This prevents any synclevel 2 attaches between the local system and the remote system.
For APPC protocol connections, issue CEMT INQUIRE CONN(sysid) and look at the XOK field. If exchange log names has not been done but there has been previous contact between the systems, the error can be overridden by resetting the state of the connection. To do this, issue CEMT SET CONN(sysid) NORECOVDATA commands for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
Investigate the cause of the error using the system dump and any previously output diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
An exception trace entry contains the received data, and the reason for the failure is interpreted. Check the format of the exchange log names GDS variable. The correct format of this SNA defined field can be found in the SNA Formats manual.
The format of the GDS variable is incorrect and the cause of the error should be located. A likely cause is that the remote system did not send a valid GDS variable in which case it may be necessary to obtain further diagnostic material from the remote system.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system has received data which it attempted to parse using the compare states GDS format. Either the data could not be parsed or invalid data was detected.
The remote system was attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
This failure indicates either an error in the remote system or a CICS logic error.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
The failure prevents the completion of the resynchronization of distributed resources.
Investigate any units of work for which resynchronization is outstanding using the command CEMT INQUIRE UOWLINK SYSID(sysid). Use the same command on the remote system to determine whether to commit or backout the unit of work. Alternatively, resynchronization can be overridden by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
Investigate the cause of the error using the system dump and any diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
An exception trace entry contains the received data, and the reason for the failure is interpreted. Check the format of the compare states GDS variable. The correct format of this SNA defined field can be found in the SNA Formats manual.
The format of the GDS variable is incorrect and the cause of the error should be located. A possible cause is that the remote system did not send a valid GDS variable, in which case it may be necessary to obtain further diagnostic material from the remote system.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
An exchange log names request was received from another system and a reply was sent. More data was expected from the other system but this was not recognized as part of the exchange log names protocol.
This implies one of the following:
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
For APPC protocol, the failure may have resulted in no exchange log name flows being successful preventing any synclevel 2 attaches between the local system and the remote system.
For IRC protocol, resynchronization may fail but communications links remain active.
For links using APPC protocol, issue CEMT INQUIRE CONN(sysid) and look at the XOK field. If exchange log names has not been done, the error situation can be overridden by issuing the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
Investigate the cause of the error using the system dump and any diagnostic information provided by CICS, the access methods, or the operating system. The remote system may also have created diagnostic messages if it detected an error in the data it received.
The data sent by the local system can be investigated by formatting the system dump to show the control blocks belonging to the trace domain and the terminal control program. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this exchange log names conversation.
If the internal trace table is available, use it to track the commands issued against that session and check that the state transitions of the user state machine are correct. If any of the state transitions are not valid, it is possible that there has been a CICS logic error.
The APPC send and receive buffers for a session are clearly labelled in the dump and are printed below the TCTTE for the session to which they belong. The TIOA contains similar information for IRC. Locate the send/receive buffer for the session in question and check that the contents of the buffer are correct. The buffer should contain a valid exchange log names GDS reply variable. The correct format of this SNA defined field can be found in the SNA Formats manual.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
CICS has initiated a resynchronization sequence following the failure of a protected conversation during syncpoint processing. No valid log name was found for the partner system. The resynchronization could not continue.
This message indicates that a CEMT SET CONNECTION NORECOVDATA command was issued before the resynchronization with the partner system could be completed. The UOW and UOWLINK describing the outstanding work have also been deleted.
None
None. This message is issued for information only.
CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, protocol
CICS has initiated a resynchronization sequence following the failure of a protected conversation during syncpoint processing. Data exists describing the conversation but no suitable connection definition was found for the partner system. The resynchronization could not continue because communications could not be established.
Processing continues.
The condition may be due to the discarding of the connection definition or to a cold start which has caused a connection definition to be deleted by CICS; the definition may have been autoinstalled. An autoinstalled definition may be reinstalled by subsequent activity in the system. Alternatively, a suitable definition can be installed manually using CEDA.
CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, netname, protocol
The local system has received data which it attempted to parse as one of the following types of SNA GDS data:
The data could not be recognized.
The remote system was attempting to initialize the connection for synclevel 2 work, or to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
This failure implies one of the following:
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If resynchronization was being attempted, it has failed and is retried at the next opportunity.
For APPC protocol connections (but not IRC protocol), the failure prevents the completion of the exchange log names protocol and this prevents any synclevel 2 attaches between the local system and the remote system.
For APPC protocol connections, issue CEMT INQUIRE CONN(sysid), and examine the XOK field. If exchange log names has not been done but there has been previous contact between the systems, the error can be overridden by resetting the state of the connection. To do this, issue the CEMT SET CONN(sysid) NORECOVDATA command for the failing connection. It may be necessary to issue this command (or its equivalent) on both sides of the connection.
Investigate the cause of the error using the system dump and any diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on this, see the CICS Problem Determination Guide.)
An trace entry contains the received data. Check the format of this data. The correct format of the SNA defined field can be found in the SNA Formats manual.
A possible cause is that the remote system did not send a valid GDS variable. In this case, it may be necessary to obtain further diagnostic material from the remote system.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system was attempting to receive data as part of a resynchronization sequence but the conversation was in the wrong state or an error FMH was received.
The remote system was attempting to initialize the connection for synclevel 2 work or to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
The failure implies one of the following:
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If resynchronization was being attempted, it has failed and will be retried at the next opportunity.
The sequence of resynchronization can be retried by issuing CEMT SET CONN(sysid) RESYNC.
Investigate the cause of the error using the system dump and any diagnostic information already issued by CICS, the access methods or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
The trace entries show the state of the conversation with the remote system and the arrival of any error FMH indicating an error detected in the remote system. If necessary, obtain further diagnostic material from the remote system.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
The local system has initiated a sequence of resynchronization exchanges with the partner system and has completed one or more of them. The conversation is not in the right state to continue the process.
The failure indicates either an error in the remote system or a CICS logic error.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If resynchronization was being attempted, it has failed and is retried at the next opportunity.
The sequence of resynchronization can be retried by issuing CEMT SET CONN(sysid) RESYNC.
Investigate the cause of the error using the system dump and any diagnostic information provided by CICS, the access methods, or the operating system.
Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
The trace entries show the state of the conversation with the remote system. The arrival of any error FMH indicates an error in the remote system. In this case it may be necessary to obtain further diagnostic material from the remote system.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
An error has occurred during the transmission of a System_restart request to a remote system. CICS was attempting to resynchronize distributed resources following an earlier failure of a protected conversation during sync point processing.
This implies one of the following:
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
The cause of the error may be indicated by diagnostic information produced by the remote system. Diagnostics issued by the local system, the access method, or the operating system may indicate a reason for the failure. Format the system dump to show the control blocks belonging to the trace domain. (For guidance on how to do this, see the CICS Problem Determination Guide.)
Determine from the message which session was being used for this exchange log names conversation.
If the internal trace table is available, use it to track the commands issued against the session reported in the message. Check that the state transitions of the user state machine are correct and that the conversation was in send state at the time of the error. If any of the state transitions are not valid, there may have been a CICS logic error.
Console and Transient Data Queue CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sessid, sysid, netname, protocol
A logic error has occurred during resynchronization with the partner system.
The local data associated with the resynchronization was locked at the start of processing but could not be unlocked at the end.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
An ASQL abend is subsequently issued by the transaction processing the resynchronization, and a transaction dump is taken.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname
A change in the generic resource member associated with the partner system has occurred but the local system has resynchronization work to complete.
The local system has previously made contact with the generic resource known as connection sysid (netname netname), and synclevel(2) work has been exchanged with the assigned member, identified by old-luname. Since that time, the affinity with old-luname has been changed to new-luname by action in the remote system. Resynchronization of the synclevel(2) work cannot take place.
No system action is taken, but subsequent messages may indicate an exchange log names failure which could prevent the connection being used for synclevel(2) work. Alternatively, messages may indicate that resynchronization work has subsequently been erased by CICS as a result of the XLNACTION setting on the connection definition.
CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname, old-luname, new-luname
The CLS2 transaction was processing exchange lognames or resynchronization for a connected partner identified by a netname netname. The connection entry associated with this netname is sysid, and was located and locked, but could not be unlocked in subsequent processing. This indicates a CICS internal logic error.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116 is normally produced containing the symptom string for this problem.
An ASQK abend is subsequently issued by the transaction processing the resynchronization, and a transaction dump is taken.
The condition indicates an error in the CICS table manager (which may have produced its own exception trace records), or in the resynchronization program itself. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname
The CLS2 transaction was executing exchange log names and attempted to save a log name received from system sysid (netname netname) by invoking the CICS recovery manager domain. This operation failed because of a CICS internal error in the recovery manager domain or in the resynchronization program.
The transaction is terminated with a transaction dump. A system dump is taken unless you have specifically suppressed dumps in the dump table. Abend ASQI is subsequently issued.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname
The CLS2 transaction was executing exchange log names or resynchronization with system sysid (netname netname). A CICS internal error prevented the successful completion of the operation.
The transaction is terminated with a transaction dump. A system dump is taken unless you have specifically suppressed dumps in the dump table. Abend ASQB may subsequently be issued.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHCRRSY
XMEOUT Parameters: date, time,applid, sysid, netname