Exchange/RJE Manual

TRACE Command
Exchange/RJE Commands
104698 Tandem Computers Incorporated 3–77
C[YCLES] cycles
specifies the maximum number of cycles that you want to allow. The trace is
stopped automatically when the writing of blocks has cycled through the trace
file cycles times. For example, if you specify one cycle, the trace stops as
soon as the trace file fills up. If you specify six cycles, the trace stops after the
writing of blocks has cycled through the trace file six times. Regardless of
how many cycles you specify, only maximum of the most recent blocks are in
the trace file; the older blocks have been written over as the writing cycled
through the trace file.
If you omit this parameter, there is no limit to the number of times the writing
cycles through the trace file. In this case, you must stop the trace with either
the TRACE STOP command, the DISCONNECT command, or the EXIT
command.
E[XTENT] size
specifies the size of the primary extent and the secondary extents. This
number determines the size of the trace file, which is 16 (the maximum
number of extents) times the extent size. The extent size is in units of one page
(2048 bytes). For files on disks running under DP2, the extent size must be an
even number of pages, and size is rounded up to an even number if needed.
The maximum extent size is 65,535 (65,534 for DP2). If you omit this
parameter, the default extent size is 2 (for a trace file size of 2 X 16 X 2K or 64K
bytes).
S[TOP]
stops the trace operation and the trace server.
Line Activity None.
Considerations The TRACE command starts and stops the Exchange/RJE trace server, which logs the
activity on the data communications line. Before you can use the TRACE command,
you must first have established a connection between Exchange/RJE and the data
communications line using the CONNECT command. For information on establishing
a connection, see the CONNECT command earlier in this section.
To list the contents of the trace file, use the DUMP command. For more information,
see the DUMP command earlier in this section.
Examples 1. This example shows how to use the TRACE command to start the trace server.
>TRACE TO trace
RJCI32 TRACE INITIATED IN CPU 9, PIN 27, PROCESS NAME IS '$Y875'
2. This example shows how to use the TRACE command to stop the trace server.
>TRACE stop
RJCI35 TRACE PROCESS '$Y875' HAS BEEN STOPPED