DFHRS2138    date time applid Invalid exchange log names reply 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 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.

System action

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, which contains the symptom string for this problem, is produced.

User response

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.

Note:

If this command is issued, CICS unilaterally commits any resources which may be waiting for APPC resynchronization. In addition, 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 reply 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.

Module

DFHCRRSY

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. sessid
  5. sysid
  6. netname
  7. protocol

Destination

CSMT and Console



DFHRS2138.html | Timestamp icon Last updated: Sunday, 4 June 2017