DISPINFO display
Current status
The Current status section shows the resource's current agent status, when it was last updated, and the message that is associated with that status change.
There are many agent statuses, but the primary flows that are listed are:
- A normal flow for a resource that is being started:
AUTODOWN -> RESTART -> STARTED -> ACTIVE -> UP - A normal flow for a resource that is being stopped:
UP -> AUTOTERM -> AUTODOWN
Table 1 shows the statuses indicating the automated recovery is impending.
| Status | Description |
|---|---|
| STOPPING | The resource is being shut down outside of automation. Depending on your automation policy settings, SA z/OS might try to restart it. |
| ABENDING | The resource failed and is shutting down. Again, SA z/OS might try to restart it. |
| INACTIVE | When SA z/OS ran a monitor to check the resource automation status and detected that it wasn't running, the monitor reported that the resource was not active. SA z/OS tries to restart it. |
Table 2 shows the statuses indicating there is a problem that automation cannot fix on its own. The operators should examine the resource and get it to a state from which it can be restarted. They might have to call in support.
| Status | Description |
|---|---|
| STARTED2 | The resource is started, but it did not issue the message indicating that it is up yet. If the resource is just running slow, verify it is really active and manually set its status to UP using SETSTATE. |
| HALTED | The resource is still running, but it has encountered a problem that impacts its functionality. This might fix itself. |
| BREAKING | The resource failed and is shut down. The nature of the failure indicates that SA z/OS might not automatically restart it. |
| BROKEN | Similar to BREAKING, but the resource is down. |
| ZOMBIE | The resource’s final termination message is received by SA z/OS, but the address space is not terminated within a reasonable time frame. |
| STUCK | SA z/OS issues all the shutdown commands that it has for the resource, but it has not shut down. |
| STOPPED | The resource is shut down outside of automation and SA z/OS is instructed not to automatically restart it. |
| CTLDOWN | The resource is down and SA z/OS is instructed not to start it. The agent does not treat this situation as an error. |
| DENIED | The agent automation flag for the resource is turned off, preventing SA z/OS from acting for the resource. You can use the INGAUTO or INGSUSPD command to re-enable automation for the resource after you determine that it is appropriate to do so. |
Flags
Flags show the current, effective setting of the Automation Agent flags for this resource.
Flags - Automation : Yes
Init Start : Yes
Start : Yes
Recovery : Yes
Terminate : Yes
Restart : Yes Each flag controls a different aspect of automation (Start After IPL, Start from Down, Recovery, Shutdown, Restart). If the AUTOMATION flag is turned off, no automation is allowed, regardless of how the other flags are set. You can use the INGSUSPD command to suspend the automation of a resource completely. On the Automation Agent side, the AUTOMATION flag is effectively set off. Manipulating the AUTOMATION flag using INGAUTO or DISPFLGS is possible for compatibility reasons, but not recommended due to possible side-effects.
Thresholds
There are some thresholds that are defined in the automation policy for the resource.
Thresholds - SUBSYSTEM
Critical : 02 in 00:05:00
Frequent : 02 in 00:30:00
Infrequent : 02 in 01:00:00 These definitions are counted in terms of application failures (unsolicited shutdowns or recoverable abends) within the time specified. If the Critical threshold for a resource is exceeded (in this case, if the abend occurs more than twice within 5 minutes), then the automated recovery is suspended and the resource’s state is changed to BROKEN to await operator assessment.
Startup and Shutdown Details
This section gives the details of how SA z/OS is instructed to start and stop the resource. In addition to checking that the instructions are correct, it can also act as a reference if you want to perform a startup or a shutdown manually. Use INGSUSPD to suspend all automation for the resource during this process.
Active Startup : None
Active Shutdown : None
Start Up Mechanism -
Scheduling Subsystem : JES2
External startup : NEVER
Start Up Process -
Prestart :
None
Startup :
Start command to be used :
MVS S RMF
User Start Up Commands :
None specified
Poststart :
None
Refreshstart :
None
Anystart :
None
Start Delay : 00:02:00
Start Cycles : 1
Shutdown Mechanism -
External shutdown : NEVER
Captured Messages
The Captured Messages section shows the last few messages that the agent is processing for the resource:
Captured Messages for RMF (maximum is 20) -
2018-09-03 11:14:48 :
AOF571I 11:14:48 : RMF SUBSYSTEM STATUS FOR JOB RMF IS UP -
CHANGED FROM DOWN AT SYS-OPS REFRESH
The colors of the messages indicate their severity - Green (Normal), Yellow (Unusual), and Red (Critical).
If the resource ends with an abend, you can use this section to see the captured messages. Use the timestamp to find correlated messages in the Syslog and Netlog.
Policy definitions
The Policy definition section shows automated actions that SA z/OS is instructed to perform beyond a simple automated restart.
This example tells SA z/OS that when the ERB603D WTOR is issued during a normal RMF start, it automatically responds GO to it.
Policy Definitions for RMF -
ERB306D :
REPLY=(NORM,,'GO') These actions are mostly controlled by the Recovery automation flag. If you do not want SA z/OS to act, use the INGSUSPD command to suspend the resource.