DFHRS2142 date time applid Compare states request data could not be received on session sessid from remote system sysid, netname netname, protocol protocol.
Explanation
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:
-
An error in the remote system
-
A session failure during the resynchronization
-
A CICS logic error.
System action
A system dump is taken unless you have specifically suppressed dumps in the dump table.
Message DFHME0116, which contains the symptom string for this problem, is produced.
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.
User response
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.
If this command is issued, CICS unilaterally commits any resources which may be waiting for resynchronization. In addition, CICS does not carry out any resynchronization activity with the remote system.
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 Troubleshooting and support section.)
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 z/OS Communications Server SNA Programmer's LU 6.2 Reference manual, (SC30-6808). Investigation at the remote system may be necessary.
Module
XMEOUT parameters/Message inserts
- date
- time
- applid
- sessid
- sysid
- netname
- protocol
Destination
CSMT and Console