DFHZC4948 E    date time applid An error has been detected when processing an{ unknown | inbound | outbound} { request. | Persistent Verify Signoff request. | Persistent Verify Timeout request.} Transaction tranid is{ continuing. | terminating. | terminating abnormally.} Error code: X'xxxxx' Connection: yyyy

Explanation

An error has been detected during the execution of transaction CLS3. The error code indicates the nature of the error:

X'01'

Transaction CLS3 issued an unsuccessful communications request on an APPC session.

X'02'

Transaction CLS3 was started by a START command with data, but the format of the data was incorrect.

X'04'

Transaction CLS3 is attempting to send a signoff request to a remote system, but the connection to the remote system is not an APPC connection.

X'06'

Transaction CLS3 was not started by terminal input, nor by a START command.

X'09'

Transaction CLS3 was started by a START command with data, but the data could not be retrieved.

X'0A'

Transaction CLS3 is attempting to send a signoff request to a remote system, but there is no connection to the remote system.

X'0B'

Transaction CLS3 unsuccessfully attempted to allocate an APPC session to a remote system.

System action

Depending upon the nature of the event that gave rise to the message, the transaction continues execution, terminates normally, or terminates abnormally. The message text indicates which action is being taken.

User response

This depends upon the error code:

X'01'

Determine why the communications request on the APPC session failed. Possible reasons are:

  • There has been a session failure.

  • The connected transaction has abended.

:pc.This error produces an exception trace, which helps to determine the cause of the problem.

X'02'

Ensure that transaction CLS3 was started by CICS-supplied code, and not by application code. If it was started by CICS-supplied code, contact your IBM Support Center.

X'04'

Check the connection definition for the remote system. It should be an APPC connection.

X'06'

Ensure that transaction CLS3 was started by CICS-supplied code, and not by application code. If it was started by CICS-supplied code, contact your IBM Support Center.

X'09'

Determine why the data could not be retrieved. If you are unable to do so, contact your IBM Support Center

X'0A'

Ensure that the connection has been correctly defined

X'0B'

Ensure that the connection is acquired and in service

Module

DFHCLS3

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. Value chosen from the following options:
  5. Value chosen from the following options:
  6. tranid
  7. Value chosen from the following options:
  8. X'xxxxx'
  9. yyyy

Destination

CSNE



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