Create event trace and dump filesint sm_trace(char *commands);
- Commands to execute.
sm_tracecan create trace and dump files containing information about Panther events. The events that are reported in these files can be selected. The
commandsparameter is series of command tokens that control operations. Most tokens can be prefixed with
NOto reverse their effect. The case of tokens is ignored but they will be capitalized in this manual.
sm_tracewas first released in Panther 5.30.
Trace files are written as events occur. The following commands control trace files:
File to write event information to. The file name should be quoted if it contains spaces. Use the null string "" to stop tracing and to close the current
Used to control whether event information is to be written to
TRACEFILE. Default is
TRACE. You can use
NOTRACEto disable tracing to reduce the size of the trace file when nothing of interest is happening.
Dump files are written when the
DUMPcommand is executed. The number of events to store for reporting is controlled by the
FRAMES=command. The following commands control dump files:
File to write information to. The file name should be quoted if it contains spaces.
Used to cause information is to be written to
Specifies how many events are to be stored for writing by the
DUMPcommand. 500 is the default.
The following commands control how files are opened:
Specifies that existing files should be overwritten. It is the default.
Specifies that existing files should be appended to.
The following commands control which events are to be logged:
Control String events.
Field entry, exit and validation events.
Installed function call and return events.
Grid and grid row entry, exit and validation events.
Group entry, exit and validation events.
JPL execution events.
Key being taken off the key queue events.
Local Data Block events.
Report Writer events.
Screen entry, exit and expose events.
Transaction Manager events.
All of the above events. This is the default.
All of the above events except for
The same as
The following command causes parameters to be displayed:
Causes parameters to be displayed for calls to functions, including JPL functions. The default is
To enable tracing to begin at startup, the SMTRACE application variable can be included in a SMVARS or SMSETUP setup file, for example:
SMTRACE=NOJAVA FRAMES=100 TRACEFILE="c:\temp\forex.trc"
SMINITJPL in a setup file can also be used to call
sm_trace, for example:
SMINITJPL=call sm_trace('PARMS TRACEFILE="c:\temp\forex.trc"')
When debugging a program,
sm_tracecan be called from the debugger to produce a dump file. For example, one can call:
to create a dump file named "dump1.dmp" with the most recent trace information.