Technical data

3.2.1 Startup Procedure
The CTF SYS$MANAGER:CTF$STARTUP.COM startup procedure is executed
during the NET$STARTUP procedure. The startup procedure installs all the
CTF-related images.
3.2.2 System Resources
CTF requires the following specific system resources on the local VMS system:
• For local tracing:
One process slot for CTF$DCP
One process slot for the trace server process (if detached tracing is to be
used)
• For remote tracing:
One process slot for the trace server process (if detached tracing is to be
used)
Tracing imposes considerable overheads on the local system and, in the case of
remote tracing, on the system being traced, with consequent effects on system
performance. These overheads are due to:
• Collecting and buffering trace records from tracepoints.
• Writing trace records to trace files (in the case of detached tracing).
• Displaying trace records on the screen (in the case of live tracing).
3.3 User Requirements
You use the START and STOP commands to control the collection of trace records.
To use these commands you require the following privileges:
• For local tracing you require:
NET$TraceHeaders
or
NET$TraceAll
• For remote tracing you require:
NET$TraceHeadersRemote
or
NET$TraceAllRemote
The username and password associated with the CTF object on the
remote server. These are required only if the remote CTF object on the
server is protected; however, this will usually be the case.
Other CTF commands require no special privileges.
Note
You must have password protection on all remote servers for security.
3–2 Using CTF