Step 2
The second step is used to degrade the operational state if the SA z/OS compound
state reports a problem. The degradation is done in combination with
the desired and observed status according to Table 1.
| SA z/OS compound status | SMU desired status | SMU observed status | Operational state | |
|---|---|---|---|---|
| Degraded | * | * | ⇒ | Degraded |
| Awaiting | Available | Unavailable | ⇒ | StartReqPending |
| Awaiting | Unavailable | Available | ⇒ | StopReqPending |
| Denied | Available | Unavailable | ⇒ | StartInhibited |
| Denied | Unavailable | Available | ⇒ | StopInhibited |
| Inhibited | Available | Unavailable | Stopping | ⇒ | StartInhibited |
| Inhibited | Unavailable | Available | Starting | ⇒ | StopInhibited |
| Inhibited | Available | Available | ⇒ | StopInhibited |
| Inhibited | Unavailable | Unavailable | ⇒ | StartInhibited |
| Problem | * | * | ⇒ | Error |
| * indicates that this can be any valid value. | ||||
For example, the operational state will be degraded in this second step, if the health status is degraded, which impacts the compound status of SA z/OS. Another reason for a degraded compound status of SA z/OS might be an automation flag that is switched off.