When ACF/TAP processes trace data files, it sequentially
numbers the records in several different ways. The numbering makes
it easy to cross-reference the same record in different types of reports.
Figure 1 shows an example
of a VTAM® trace file with different
types of trace records on it.
Notes: - ACF/TAP sequentially numbers every record on a trace file, even
if the record is a type that ACF/TAP does not process. This absolute
sequence number appears only on the SYSPRINT log.
- ACF/TAP sequentially numbers every record that it processes (SUMMARY=EVERY)
or can process (SUMMARY=YES or ALL) when it scans the file (INPUT=SCAN).
ACF/TAP tests the count select limits (START=count; END=count) against
this process number. See START and END parameters for more
information.
- ACF/TAP sequentially numbers each PIU and buffer trace record
that it can process. ACF/TAP tests the count select limits against
the host trace record number. Every PIU that ACF/TAP analyzes is called
a message and is assigned a message number.
- A line trace record consists of multiple NCP line trace events
of variable length, depending on the type of communication scanner.
ACF/TAP sequentially numbers each NCP line trace event and refers
to it by an element number. A GPT record can consist of multiple events
of variable length. ACF/TAP sequentially numbers each GPT event and
refers to it by an element number.
- A line trace message can consist of multiple elements that can
span one or more records. Each message that is assembled from the
line trace data is assigned a message number. A line trace record
can contain more than one message.
Figure 1. ACF/TAP method for numbering
trace file input data (VTAM Trace File, Recorded by GTF on MVS only)
|
|_____________________ Trace File ____________________________________________________________________________>
| SOURCE=GTF
___________ ___________ ___________ ___________ ___________ ___________ ___________ ___________ _____________>
| Absolute | Absolute | Absolute | Absolute | Absolute | Absolute | Absolute | Absolute | Absolute
1 | Sequence | Sequence | Sequence | Sequence | Sequence | Sequence | Sequence | Sequence | Sequence
| #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | #9
|___________|___________|___________|___________|___________|___________|___________|___________|_____________>
| TYPE= | TYPE= | TYPE= | TYPE= | TYPE= | TYPE= | TYPE= | TYPE= | TYPE=
| GTF | RNIO | NCP Line | User Trace| VTAM | RNIO | NCP Line | GPT | GPT
2 | Header | Trace | Trace | (Not | Buffer | Trace | Trace | Trace | Trace
| | #1 | #1 | Processed)| Trace | #2 | #2 | #1 | #2
| | | | #1 | #1 | | | |
|___________|___________|___________|___________|___________|___________|___________|___________|_____________>
| | RNIO | | | VTAM | RNIO | | |
3 | | Message | | | Buffer | Message | | |
| | #1 | | | Message | #2 | | |
| | | | | #1 | | | |
|___________|___________|___________|___________|___________|___________|___________|___________|_____________>
| | | Multiple | | | | Multiple | Multiple | Multiple
4 | | | Line Trace| | | | Line Trace| GPT Trace | GPT Trace
| | | Elements | | | | Elements | Elements | Elements
|___________|___________|__ _ _ _ __|___________|___________|___________|__ _ _ _ __|__ _ _ _ __|_____________>
| | | #|#|#|#|# | | | | #|#|#| |# | #|#|#|#|# |
| | | 1|2|3|4|5 | | | | 6|7|8| |n | 1|2|3|4|5 |
4 | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | | |
| | | S| | | | | | | | | |E| | | | | | | |
|___________|___________|__|_|_|_|__|___________|___________|___________|__|_|_|_|__|__|_|_|_|__|_____________>
| A | A|
Start of ______|_| | End of Message (E) __||
Message (S) | Line Trace| |
| Elements | |
| #1 to #5 | |
|___________| |
|________________ Line Trace Message #1 _______________|
5