z/OS Communications Server: IP Programmer's Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Segmented records

z/OS Communications Server: IP Programmer's Guide and Reference
SC27-3659-02

For packet trace and data trace, the NMI might create segmented records to represent one packet or one set of data for a socket request. Segmented records are created when the resulting trace record is larger than 65534 bytes. Each segmented record has the same format as regular trace records: a cte, a real-time data portion, and a cteeplg. See Segmented trace records for more information. You can recognize the set of segmented records by checking the following packet trace header (PTH) fields in the records:
  • PTH_Tlen - The value is the same in each record of the set of segmented records. The value is the total length of all trace data in the complete set of segmented records.
  • PTH_Time - The value is the same in all the records.
  • PTH_SeqNum - The PTH_SeqNum starts at 0 in the first segmented record and increases by 1 in the subsequent records. If there are more than 256 records, the value wraps back to 1.
The information in the segmented records can be reassembled into the original complete packet or complete data for the socket request. The PTH_Tlen field value can be used to determine when all the trace data has been reassembled. The first record of the set of segmented records contains the following information based on the trace record type:
  • Packet trace

    The IP and transport headers

  • Data trace

    Any ancillary data that was included on the socket request.

The remaining records of the set of segmented records contain data only from the packet or socket request.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014