The VPE service trace must be activated before any logging occurs. The service trace can be activated for an entire session or any part of a session. Entries are logged until an @I$TRACE OFF or @I$TRACE PRINT command is issued.
A DIAL trace with output directed to the VPE trace file (described in the next section) must also activate the VPE service trace first.
The following command activates or deactivates a VPE service trace.
This command has the following format:
{ON } [LOCAL ]
@I$TRACE {OFF} [GLOBAL]
Activates the VPE trace and begins logging entries to a sequential file (installed as ADRTRC).
Terminates a VPE trace.
Logs only those entries for the CA Ideal user requesting the trace. The user is identified with a particular terminal online or with a particular batch job.
Online, logs entries for all users. Use caution with GLOBAL because the trace file can quickly reach its capacity. In batch, this option has the same effect as Local.
Online asynchronous tasks (network prints and compiles) require a global trace. Compiles can be traced locally if they are run synchronously or in batch. For more information, see the “Application Debugging Tools” chapter.
Example
@I$TRACE ON
Activates a VPE trace for the current user only.
@I$TRACE ON GLOBAL
Online only, activates a VPE trace for all users.
@I$TRACE OFF
Deactivates a VPE trace for the current user.
@I$TRACE OFF GLOBAL
Deactivates a VPE trace for all users.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|