AutoTMF Software User's Guide (Update 14)

Problem Resolution
HP NonStop AutoTMF Software User’s Guide—429952-016
C-8
Tracing

The CI TRACE command.

By setting a tracing process DEFINEs: =_ESCORT_STATEMENT_TRACE,
=_ESCORT_STATEMENT_DATA or =_ESCORT_STATEMENT_KEYS.
You can trace a single process or all instances of a running program. Up to thirty two
such traces, numbered 0 to 31, can be active simultaneously.
To stop tracing, use TRACE STOP.
Static vs. Dynamic Tracing
You can trace a single process or a set of programs. Tracing can be either static or
dynamic:

Static tracing starts at the time the process is launched. Tracing is initiated by the
monitor process through the CI TRACE command.
Tracing can also be started by specifying one of three DEFINES in the program
startup command stream or the Pathway server configuration.

Dynamic tracing can be initiated at any time before or during program execution by
the monitor through the CI TRACE command.
You can enable dynamic tracing on your system with the ALTER GLOBAL
command to set the global DYNAMICTRACE to ON.
The global setting DYNAMICTRACE can be overridden for a single process by
using DEFINEs. See =_ESCORT_DYNAMIC_TRC_OFF and
=_ESCORT_DYNAMIC_TRC_ON for details.
Note that the dynamic tracing global or DEFINE must be specified when a process
is started, which tells the process to check for tracing at various times.
Allowing dynamic tracing increases overhead, so use dynamic tracing judiciously.
Tracing and Debugging
Tracing is often done in conjunction with the debugging of a program using INSPECT.
In addition to the standard TACL and Pathway DEBUG options, you can specify that a
program should be started in INSPECT with the CI TRACE command. Tracing can be
particularly useful when debugging Pathway servers since tracing does not require
modifying the server configuration.
Trace Files
The trace output can be written to a disk file or terminal. If the disk file specified does
not exist, it as created as an entry-sequenced file by the AutoTMF runtime.