OSI/MHS SCF Reference Manual

OSI /MHS SCF Reference Manual—424828-001
3-1
3
Formatting Trace Files With PTrace
The PTrace (print trace) program formats data that is stored in unstructured trace files
for output to terminals, printers, and disk files. Trace files contain a record of the
communications between processes. You use PTrace to display and examine trace files
to analyze problems.
You can generate a trace file interactively or programmatically. To start the trace and
capture data interactively, you use the Subsystem Control Facility (SCF) TRACE
command.
To start the trace and capture data programmatically, you use the Subsystem
Programmatic Interface (SPI), which is described in the SPI Programming Manual.
This section describes how to format previously generated trace files for the OSI/MHS
subsystem using PTrace commands. This section presents PTrace information specific
to the OSI/MHS subsystem. For details about PTrace commands and about how PTrace
works, see the PTrace Reference Manual.
Running PTrace
Although the PTrace Reference Manual covers this subject in more detail, here’s
enough information to get you started quickly.
Starting a Noninteractive Session
The syntax of the TACL or SCF RUN command for PTrace is:
run-option-list
is one or more run options, as described in the TACL Reference Manual. Although
other run options are allowed, the options that have special significance for PTrace
are as follows:
IN file-name
designates the initial source for PTrace command input for a session. If the IN
option is omitted, the input source defaults to the input file for the TACL process
through which PTrace is initiated (usually a terminal).
NOWAIT
means that TACL or SCF does not wait while PTrace runs but returns a
command input prompt after sending the start-up message to PTrace. If you
omit this option, TACL or SCF pauses while PTrace runs.
PTRACE [ /run-option-list ] [ ptrace-command ] ...