DFHRS2147    date time applid Unrecognized data was received following transmission of an exchange log names reply on session sessid to remote system sysid, netname netname, protocol protocol.

Explanation

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:

  • The remote system has detected a protocol violation in the local system's exchange log names reply GDS variable.

  • There has been an internal error in CICS processing.

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.

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.

User response

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.

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 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 Troubleshooting and support section.)

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 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



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