Spooler FASTP Network Print Processes Manual

Troubleshooting and Using the Trace Facility
Spooler FASTP Network Print Processes Manual — 427528-007
8 - 7
Reading Trace Output
Reading Trace Output
Reading trace output varies based on whether the shadow trace file is in the original
entry-sequenced format or in the new unstructured format.
Reading an Entry-Sequenced Shadow Trace File
An entry-sequenced shadow trace file is the only format supported by FASTPSMB,
FASTPNOV, FASTPX25, and FASTPXNS. This format can also be produced by
FASTPTCP if the shadow trace file was manually created as an entry-sequenced file.
No special tools are provided to view an entry-sequenced shadow trace file. However,
because the trace file is an entry-sequenced Enscribe file, you should use the FUP
COPY command with the H option to list the trace information. For example:
TACL 1>FUP COPY trace-file-name,$S.#location,H
The H option is required to format the binary data into displayable hexadecimal and
displayable ascii (in which control characters are suppressed.) Note that the trace file
might contain non-printable data.
Entry-Sequenced Trace File Format
When the entry-sequenced file format is used, each trace event causes two or more
records to be written to the trace file. The first record (the identifier record) identifies:
•
The type of event
•
The time at which the event occurred
•
An abbreviated stack trace for the procedure that produced the event
The second record (the data record) contains data related to the event. If the amount
of data exceeds the trace file record size, the data is written as two or more records.
For example, the following example shows two records related to one trace event:
$DATA4.BGXEROX.SHADA RECORD 0 KEY 0 (%0) LEN 30 7/13/99 9:22
000: 3036 204A . . . 3920 2D20 06 Jul 99 12:25:05:39 -
00C 4F75 7470 . . . 3736 2C30 Output - 171623,130476,0
018 3037 3336 . . . 07364,156635
$DATA4.BGXEROX.SHADA RECORD 1 KEY 1 (%1) LEN 74
000: 004A 027A . . . AA33 11E0 .J.zC............:...3..
00C: 0000 0000 . . . AA33 11E0 .........H.*.....d...3..
018: 0005 0000 . . . 0000 0000 .....d......(....`......
024: 0002 ..
Note. The example above has been reformatted to fit this page.