evaction
Abstract
Sets an action for the specified event. The action will occur when the specified event is about to be executed.
Syntax
evaction [<exec_id> | #<sched_id> | +<n> | %<n>] <action>
| Argument | Type | Description |
|---|---|---|
<exec_id> |
integer | numeric index of the event-of-interest in the event execution sequence An execution ID can be estimated, or obtained precisely from an ODB Event Banner of a previous simulation run. |
#<sched_id> |
integer | numeric index of the event-of-interest in the event scheduling sequence A schedule ID can be obtained by using the ODB command evprint, which displays portions of the event list. |
<n> |
integer | numeric index of the event-of-interest, relative to the current event+<n> sets an action on the nth next event;%<n> sets an action for every nth event |
<action> |
string | any ODB command, with any number of arguments. If more than one word, string must be enclosed with double-quotes. |
Details
Events can be specified by their execution ID, schedule ID, or by a relative index. All three ID types are displayed by the evprint command, but only the schedule IDs are fixed at that point. Actions can be suspended by the command suspaction, reactivated by actaction, or deleted by delaction.
Example
ODB> evaction +2 status
Added action 2: action at nth event (1513): status
ODB> evaction +10 "snapshot snap_file"
Added action 3: action at nth event (1521): snapshot snap_file
ODB> status
Breakpoints :
None
Traces :
Full trace is disabled
Encapsulation trace is enabled
Execution trace is disabled
Trace format: indented
No other traces
Actions :
2) action at 2nd event (1513): status
3) action at 10th event (1521): snapshot snap_file
Miscellaneous :
Memory tagging is disabled