Fields in the buffer contents trace

Table 1 explains the trace fields. In addition to these fields, operating-system-dependent fields may appear. For a description of these fields, see Table 1.

Table 1. Fields in the buffer contents trace
Field header	Meaning
BUFF destname/origname	The destination (destname) and origin (origname) node name. In Figure 1, the destination is APPL12 and the origin is TERM200.
LRC(xxx,yyy)	The number of records lost since the last trace record was written because the trace facility could not get a VTAM® buffer. xxx is the destination's lost record count, and yyy is the source's lost record count.
INBOUND or OUTBOUND	The direction of the traced data (inbound or outbound) with respect to this host subarea. By use of this field and the PIU sequence number in the TH, requests and corresponding responses can be matched.
position SEGMENT (full buffer trace only)	Indicates whether this trace record is FIRST, MIDDLE, or LAST in a series of trace records generated for one trace invocation. If only one trace record is needed, the value is COMPLETE. The segment indicator field appears only when full buffer contents tracing is in effect.
SEQ(xxx) (full buffer trace only)	A sequence number indicating the sequence in which trace records were generated. The sequence number appears only when a series of trace records is generated for a single trace invocation. The sequence number does not appear when one trace record shows a complete buffer. The sequence number starts at 1, and upon reaching 255, wraps to 0. A gap in sequence numbers could indicate lost trace records. The sequence number field applies only when full buffer contents tracing is in effect.
VTAM or USER	Indicates where the message buffers were traced. VTAM means that the buffers were traced in TSC (in which case the TH and the RH are included in the trace record). USER means that the buffers were traced in API (in which case the TH and the RH are not included).
TH	The transmission header portion of the path information unit (PIU).
RH	The request/response header portion of the PIU.
Note: The rest of the trace record shows the contents of the buffer as displayed in Figure 1.

Notes:

If the buffer trace information is out of sequence, your trace could have wrapped.
User entries are not printed by ACF/TAP.
Confidential data is not recorded in trace records. When the trace facility detects confidential data (CONFTXT=YES is specified on the application program's NIB macroinstruction), the user data is replaced with the marker in the trace output.
The marker is CONFIDENTIAL AND SUPPRESSED.

If you are using the VTAM encryption facility, data on a cryptographic session is handled in the same way as confidential data.