The TRACE utility provides the Common Trace Facility command interface
that allows you to collect and display information that passes between
protocol layers in a network. CTF commands allow you to start tracing
data, stop tracing, and display an analysis of the traced information.
The following process privileges are required to use CTF:
ALTPRI, BYPASS, CMKRNL, NETMBX, PRMGBL, PRMMBX, PSWAPM, SYSGBL, SYSLCK,
SYSNAM, TMPMBX, WORLD
To run the TRACE utility, enter the command:
TRACE
The prompt CTF> will appear, indicating that you may enter CTF commands.
Alternatively, you can enter a CTF command directly from DCL:
TRACE command-string
1 – About CTF
CTF provides user commands that allow you to:
o Start and stop the collection of protocol information from specified
points within networking software, called tracepoints. Each time
data is collected at a tracepoint, it is stored in a trace record.
o Display the collected trace information on your terminal, or save
it in a trace file for later analysis.
You can collect protocol data from networking software running on the
local VMS system or on remote servers. Note, however, that you cannot
collect protocol data from remote VMS systems.
2 – Rights Identifiers
To trace data on a local system or a remote server, you must hold
specific rights identifiers in the rights database of the node you
are invoking CTF from. These rights identifers are:
NET$TraceHeaders - trace protocol header information on local node
NET$TraceAll - trace protocol header and data on local node
NET$TraceHeadersRemote - trace protocol header info on remote server
NET$TraceAllRemote - trace protocol header and data on remote server
The difference between NET$TraceHeaders and NET$TraceAll is that
NET$TraceAll will allow you to see the user data portion of the
protocol data unit, which may contain sensitive or private information.
These rights identifiers must be granted through the Authorize utility:
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
$ GRANT/ID <rights_id> <username>