Technical data

All tracing operations of the CTF on DECnet/OSI end nodes or routers require
that the user process hold identifiers in the rights database of the node on which
the user is invoking CTF. These identifiers are:
Table 3–1 Identifiers in the Rights Database
Trace Operation Privilege
NET$TraceHeaders can trace message headers on the local node.
NET$TraceAll can trace entire messages on the local node.
NET$TraceHeadersRemote can trace message headers on remote nodes.
NET$TraceAllRemote can trace entire messages on remote nodes.
These identifiers are created in the rights database during installation. They may
be granted to a user account through the Authorize Utility by a system manager.
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> GRANT/ID NET$TRACEHEADERS user_account
Note
For some tracepoints there is no distinction between tracing a header and
tracing a full message.
3.3.1 Keypad Definitions
When you run the TRACE utility, it reads the default keypad definitions from the
file:
SYS$LIBRARY:CTF$KEY.INIT
The system manager may edit this file to change the default keypad definitions
for all CTF users.
Individual users may override the default keypad definitions by generating their
own copy of CTF$KEY.INIT and equating the logical name CTF$KEY to the copy,
as follows:
$ DEFINE CTF$KEY SYS$LOGIN:CTF_KEYPAD.INIT
The defaults applied to the logical name translation are:
SYS$LIBRARY:.INIT
3.4 Running the TRACE Utility
To run the TRACE utility, enter the following command at the DCL prompt:
$ TRACE
The appearance of the CTF> prompt indicates that TRACE is running and that
you can enter any of the CTF commands described in Chapter 4.
You can include a CTF command in the TRACE command line, as follows:
$ TRACE command-string
Using CTF 3–3