New TRACE option EXEC traces RUN, CHAIN, command line and XCALL AMOS statements. This is particularly useful for tracking user activity. Example trace formats:
|
Context |
Format |
|
RUN PROG1 (from dot prompt or command file) |
<RUN:xxx> Exec(CHAIN): c:\vm\miame\dsk0\007006\prog1.run |
|
CHAIN PROG2 (from PROG1) |
<PROG1:xxx> Exec(CHAIN): c:\vm\miame\dsk0\007006\prog2.run |
|
XCALL AMOS, "RUN PROG3" (from PROG2) |
<PROG2:xxx> Exec(AMOS): Exec(AMOS): RUN PROG3 |
|
LOG DSK0:100,150 (from dot prompt or command file) |
<yyyy:xxx> Exec(CMDLIN) LOG DSK0:100,150 |
So essentially you can search or filter for "Exec(" to easily pick up all the command lines and programs executed.
As with other TRACE options, you can set it from/in various contexts:
|
Context |
Statement |
|
In the MIAME.INI |
TRACE=EXECUTE |
|
From the command prompt |
SET TRACE EXECUTE ON |
|
From within a program |
XCALL MIAMEX, MX_GETTRACE, trflags |
|
From within a program |
XCALL MIAMEX, MX_SETTRACE, trflags OR TROP_EXECUTE |
The symbol TROP_EXECUTE is defined as &h80000000 in ashell.def.