DFHRS2145 date time applid Invalid exchange log names data has been received on session sessid from remote system sysid, netname netname, protocol protocol.
Explanation
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.
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.
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.
User response
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.
If this command is issued, CICS unilaterally commits any resources waiting for APPC resynchronization. Also CICS does not carry out any APPC 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.)
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 z/OS Communications Server: SNA Data Areas Volume 2 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.
Module
XMEOUT parameters/Message inserts
- date
- time
- applid
- sessid
- sysid
- netname
- protocol
Destination
CSMT and Console