MONITOR operator command: Difference between revisions
m (Alex moved page MONITOR command to MONITOR operator command: MONITOR command should refer to standard MONITOR command) |
RPuszewski (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
activity (evaluating, compiling, etc.), and the name of the procedure | activity (evaluating, compiling, etc.), and the name of the procedure | ||
that is currently running. | that is currently running. | ||
This information can be used to determine whether a <var>[[BUMP command|BUMP]]</var> or <var>[[RESTART command|RESTART]]</var> command should be issued. | This information can be used to determine whether a <var>[[BUMP command|BUMP]]</var> or <var>[[RESTART operator command|RESTART]]</var> command should be issued. | ||
[[Category: Operator commands]] | [[Category: Operator commands]] | ||
[[Category: Commands]] | [[Category: Commands]] | ||
Latest revision as of 16:43, 19 February 2020
Note: This is a Sirius Mods-only command prior to Version 7.5 of Model 204.
This operator command requests that the utility return information about what is currently happening in Model 204. This command is especially useful if Model 204 appears to be hung or looping, making it impossible to log on to Model 204 in order to determine the cause of the problem.
Information is returned for the main Model 204 task and any subtasks (if the MP/204 feature is being used). The information returned indicates whether each task is running or waiting (corresponding to looping and hung situations, respectively), and where in the Model 204 load module the task is running or waiting. This latter piece of information is most useful to Model 204 internals experts.
If any Model 204 task is indicated as running, information is also provided on the user number and userid of the running user, the current activity (evaluating, compiling, etc.), and the name of the procedure that is currently running. This information can be used to determine whether a BUMP or RESTART command should be issued.