PTrace Reference Manual

PTrace Reference Manual—526393-001

1-1

Introduction to PTrace and Trace

Files

The PTrace (print trace) utility formats data that is stored in unstructured trace files for

output to terminals, printers, and disk files. Trace files contain records of the

communication between processes. You can capture a trace file either interactively or

programmatically.

This section summarizes the steps involved in recording and displaying trace data and

gives an overview of PTrace features. It also includes a comparison of the PTrace

utility and CMI PTrace-mode commands.

Recording and Displaying Trace Data

To capture data interactively, you use the Subsystem Control Facility (SCF) or the

Communications Management Interface (CMI). To capture data programmatically, you

use the Subsystem Programmatic Interface (SPI). You use PTrace to display and

examine trace files to analyze problems.

SCF, CMI, and SPI are interfaces that provide control and inquiry for various data

communications subsystems.

•

SCF provides an interactive interface to allow operators and network managers to

configure and control data communications subsystems using the Subsystem

Control Point (SCP).

•

CMI provides an interactive interface to the Communications Management Process

(CMP), which in turn provides an interface to the various I/O processes performing

data communications operations and services.

•

SPI provides a general mechanism for communication with various HP

subsystems. You can write an SPI trace request and send it to a particular

subsystem through the SCP process.

Figure 1-1 shows the four general steps involved in recording and formatting trace

data.

Note. CMI is only used in systems running D-series RVUs with the Envoy ACP/XF, ATP6100,

CP6100, and AM6520 communications subsystems; all other subsystems use SCF. For

systems running G-series RVUs, all communications subsystems use SCF to generate trace

files.