This command displays and sets tracing options within the Process Engine
and is mainly intended for FileNet engineering staff use. You can trace
server activity including remote procedure calls, DBI timings, DBI database
access, Object
Service usage, network connections, application functions, vwisi processes,
and log manager processes. You can route this trace information to the
stdout device, to a log file, or to memory—if you route the trace information
to memory, you can subsequently save the trace information to a file.
The command displays each tracing option and its current settingT
for true (turned on) and F for false (turned off), then gives you the
option to change the settings.
To turn off tracing, enter the trace command with no parameters, and
enter "n" at the logfile and memory prompts.
For each parameter, enter "y" for yes or "n" for
no.
change_tracing_options
Enter "y" to change any of the displayed settings, or
"n" to leave them as is.
The remaining prompts only appear if you answer 'y' to the change_tracing_options
prompt.
logfile
Save the trace to a log file.
If you enable this option, vwtool outputs the name of the log file
it creates.
memory
Save the trace to memory.
Use the writetrace command to subsequently
save this trace information to a file.
extRPC
Trace external Remote Procedure Calls (RPCs).
The extRPC and intRPC options reflect the number of RPCs going
across the network.
intRPC
Trace internal Remote Procedure Calls (RPCs).
The extRPC and intRPC options reflect the number of RPCs going
across the network.
objsvc
Trace Object Service usage.
dbaccess
Trace database access.
This option outputs the SQL statements used by the Process Engine,
along with the values of the substitution variables. (This information
can be useful for FileNet field personnel.)
dbtiming
Trace database timings.
This prompt only appears if you answer 'n' to the dbaccess prompt.
TIP In
vwtool, you can enter parameters on the command line (following the command
name) or let vwtool prompt you for the information by entering just the
command name. Generally, we recommend prompt mode for all but the simplest
commands. Entering the parameters on the command line is intended primarily
for script-driven input.