SNA network monitoring NMI response format

All SNA NMI responses flow on the socket from the VTAM® server to the client application. The general format of an NMI response is as follows:

The response header, which includes the response type, the return code and reason code, the request section descriptors (triplets), and the response section descriptors (quadruplets). A quadruplet consists of the offset (in bytes) of the response section relative to the beginning of the response header, a reserved field, the number of elements in the response section, and the total number of elements that passed the request filter checks.
Tip: This last field in the quadruplet is applicable only to responses that have a corresponding request. Initialization and termination records do not have corresponding requests. Therefore, this field is reserved and is set to the value 0 on responses that contain initialization and termination records.
The request sections.
The response sections.
- Response sections of the following solicited response types are returned if data is found that matches the corresponding filtered or unfiltered request (if no matches were found, no response data sections are returned):
  - EE connection information
  - EE summary information
  - HPR connection information
  - CSM statistics information
- An initialization record always contains a single response section.
- A termination record does not contain a response section (all information is contained within the response header).

The NMI response section consists of one or more records that contain information that passed the request filter checks.

The general format of an NMI response section record is as follows:

The record header, which contains the overall length of the record and one or more subrecord descriptors (triplets). The record triplet consists of the offset in bytes, relative to the start of the response section record, for the first instance of a given subrecord; the length in bytes of this particular subrecord; and the total number of instances of this subrecord.
The subrecord sections that are associated with this response section record.

An application that navigates an NMI response must use the overall length value in the response section record to move to the next variable length record. The application should use the response section record triplet data to navigate within the record itself.

The following response section records are returned for the solicited response types:

EE Summary Response
1. One EE Summary Global Data Section record
2. One or more EE Summary IP Address Data Section records
EE Connection Response
1. One or more EE Connection Data Section records
HPR Connection Response
1. One HPR Connection Global Data Section record
2. One or more HPR Connection Specific Data Section records
CSM Statistics Response
1. One CSM Global Pool Output Section record
2. One CSM Summary Output Section record
3. Zero or one CSM Storage Owner Output Section record

Every response record sent by VTAM to the client looks like the format that follows.

Common Request/Response Header

Input Triplet information (copied from corresponding request, if any): a single triplet is defined.

Offset from start of response data to first input record
Length of each input section of this type
Number of input sections of this type

Output Quadruplet information: a single quadruplet is defined.

Offset from start of response data to first output record
0
Number of output records included in this response. If this value is less than the number of records matching the filters supplied on the corresponding request (if any), then some data was not reported as the result of storage constraints.
Number of output records matching the filters supplied on corresponding request, if any

Start of input information (copied from corresponding request, if any — offset from start of response data saved in Input Triplet)

Start of output information (offset from start of response data saved in Output Quadruplet)