You can view the status of runs of procedures from the Work with Procedure Status display. The term “the last run” of a procedure refers to the most recently started run of a procedure, which may be in progress or may have completed.
To display the status of the most recent run of all procedures, do the following:
From the MIMIX Basic Main Menu, select option
1(Work with application groups).From the Work with Application Groups display, press
F20(Procedure Status). The Work with Procedure Status display appears.The most recent run of all procedures are listed on the Work with Procedure Status display. Procedures of type *NODE are listed for each node in the instance and have a status of *NEW if they have not run. Other procedure types that have never been requested to run are not listed.
Press
F18(Subset) if you want to display only procedures of a specific type.Locate the procedure you want and check the value of the Status column. Possible status values and the actions to take to resolve problems are listed in Table 16.
Figure 13 shows an example of the Work with Procedure Status display subsetted to show only runs of a specific procedure and application group. The list is in reverse chronological order so that the most recently started procedures are at the top.
Figure 13.A subsetted view of the Work with Procedure Status display.
A second view, F11 (Duration), shows columns for the Duration of the procedure and the Node on which the procedure was started. Procedures of type *NODE that have not run are blank for these columns and have a status of *NEW.
From the second view, F11 (Schedule summary) shows columns for the Frequency and Scheduled time for procedures of type *NODE that are data protection reports. The frequency indicates how often the report is automatically submitted to be run by MIMIX. The scheduled time identifies when MIMIX will submit the next scheduled run. Only data protection report procedures can be scheduled.
Timestamps are in the local job time. If you have not already ensured that the systems in your installation use coordinated universal time (UTC), see the Assure MIMIX Administrator Reference book for the setting system time topic.
Table 16 identifies the possible status values that can appear on the Work with Procedure Status display and identifies the action to take to resolve reported problems.
|
Category |
Status Value |
Description and Action Required |
|---|---|---|
|
Note: For problem resolution, a virtual switch procedure differs from
other types of procedures in several ways. For more information
about virtual switches for *NONCLU application group, see the
Assure MIMIX Operations book.
|
||
|
Active |
*ACTIVE |
The procedure is currently running. No steps require attention. |
| *ATTN |
The procedure requires attention. Either there is a step with a status of *MSGW, or there is an active step and one or more steps with step status values of *ATTN, *CANCEL, *FAILED, or *IGNERR. Action Required: Determine the status of each step and the action required to correct that status. See Resolving problems with step status. |
|
|
*MSGW |
A step within the procedure is waiting for a response to an inquiry message. The procedure cannot process the step or any subsequent steps without a reply to the message. Action Required: Display and respond to the inquiry message using Responding to a procedure in *MSGW status. |
|
| *PENDCNL |
A request to cancel the procedure is in progress. When the activity for the steps in progress at the time of the cancel request ends, the procedure status changes to *CANCELED. |
|
|
*QUEUED |
A request to run the procedure is currently waiting on the job queue. When the procedure becomes an active job, the procedure status changes to *ACTIVE. |
|
|
Resumable |
*CANCELED |
Either the procedure was canceled and did not complete, or steps within the procedure were canceled as a response to inquiry messages from the steps. The procedure was partially performed. Action Required: Use Resolving a *FAILED or *CANCELED procedure status to determine the state of your environment and whether to resume the procedure or to acknowledge its status. |
|
*FAILED |
The procedure failed. Jobs for one or more steps had errors. Those steps were configured to end if they failed. The procedure was partially performed. Action Required: Use Resolving a *FAILED or *CANCELED procedure status to determine the state of your environment and whether to resume the procedure or to acknowledge its status. |
|
|
Acknowledged |
*ACKCANCEL |
The procedure was canceled and a user action acknowledged the cancellation so that the procedure can no longer be resumed. |
| *ACKFAILED |
The procedure failed and a user action acknowledged the failure so that the procedure can no longer be resumed. |
|
| *ACKERR | The procedure completed with errors and a user action acknowledged the procedure. It is assumed that the user reviewed the steps with errors. A status of completed with errors is only possible when the steps with errors had been configured (within the procedure) to ignore errors or a user’s response to a step in message wait status was to ignore the error and continue running the procedure. After the step is acknowledged, the procedure status changes to *ACKERR. | |
|
Completed |
*COMPERR |
The procedure completed with errors. One or more steps had errors and were configured to continue processing after an error. Action Recommended: Investigate the cause of the error and assess its implications. |
|
*COMPLETED |
The procedure completed successfully. |
|
|
New |
*NEW |
The *NODE type procedure is new and has not yet been run for that node. Action: Use option 9 (Run) to run the procedure. |