Observed Status
This represents the current status of the resource and is provided by the related automation agent.
Possible values are:
- Unknown (Assumed unavailable)
- The automation manager has no observed status information about the resource. To be on the safe side, the automation manager will assume that the resource is unavailable and will try to make it available if this is the desired status. On the other hand, this assumption allows the automation manager to process shutdown requests for supporting resources that can only be made unavailable if this resource is unavailable.
- SysGone (unavailable)
- The system that the resource is defined on is no longer a member of the sysplex.
- SoftDown (unavailable)
- The resource is unavailable and automation may restart it.
- HardDown (unavailable)
- The resource is unavailable and automation will not restart it.
- Starting (available)
- The automation agent is either in the process of making the resource available or has detected actions from some outside command to make the resource available.
- Available
- The resource is ready for use.
- Degraded (available)
- The resource is available but not all required members in the server group are available.
- Standby (unavailable)
- The resource has a primary/secondary system association defined.
The automation agent posts this status to the automation manager when setting the automation agent status
to MOVED or FALLBACK.
Note: The automation manager treats STANDBY like a HARDDOWN status except that it is not considered that this indicates an error condition.
- Problem (available)
- The resource is available but has a serious problem, probably making it unusable.
- Stopping (available)
- Either the automation agent is in the process of stopping the resource, or it has detected that some outside command is doing so.
- WasAvailable (Assumed available)
- The automation manager has lost contact with the automation agent responsible for the resource, however the resource was available when contact was lost and the system it is on still appears to be running. The resource will be treated as being available. This is primarily to prevent inappropriate recovery actions from being initiated whenever an SA z/OS NetView is recycled.