TMS:Engine sense data format

Edit online
This section describes the TMS:Engine sense data format. SNA exception sense codes may appear in some messages. These sense codes have the same meaning as identified in IBM® SNA documentation. Each code consists of a 4-byte fullword field. The first byte is the category, the second the modifier, and the final two bytes are sense code specific information or user-defined data. For more information on interpreting these fields, refer to IBM Systems Network Architecture Format and Protocol Reference Manual: Architectural Logic. The category and modifier bytes hold the sense code defined for the exception condition that occurred. The following categories of messages, as identified by the first two bytes, might display:
00
User Sense Data Only
08
Request Reject
10
Request Error
20
State Error
40
Request Header (RH) Usage Error
80
Path Error
Table 1. TMS:Engine message route codes

This table lists the TMS:Engine message route codes.
Code Description
BYTE 0 BIT 0 - REQSTAT origin flag:
  • 0 if associated with an RPL based request.
  • 1 if associated with a NOTIFY request.
BIT 1 - Sense data flag
  • 0 if system sense, or no sense data available.
  • 1 if user sense data present.
BITS 2-7 - Return code or status information
  • RPL Return code (RPLRTNCD).
  • NOTIFY Notify status code, currently supported values:
    • x'02' Session established.
    • x'03' Procedure error
BYTE 1 Feedback or reason code
  • RPL Feedback code (RPLFDB2).
  • NOTIFY Reason flags, currently valid only for status x’03’. This field refers to the 10th byte of the Third Party Notification NOTIFY vector.
BYTES 2–3 Sense data
  • System sense Refers to the RPLSSEI and RPLSSMI fields, respectively.
  • User sense Refers to the RPLUSNSI field.