Default availability
In your automation policy, each resource has a Default Desired Status setting.
The possible values for the setting are as follows:
| Default Desired Status setting | Description |
|---|---|
| Always | The resource is always up. In the absence of any other instruction, the resource is started and is recovered if it fails. This is usually the most common setting. |
| On Demand | The resource is up if it is needed and it is
down otherwise. If the resource is needed to support a resource that you must start, then this resource is started and recovered if it fails. If the demand for it goes away, it is shut down. |
| As Is | Automation does not start or stop the resource
unless instructed to do so. If the resource is running, it is left alone, but it is not recovered if it fails. If it is down, it is also left alone. Use this status setting for resources that you do not want automation to take action. |
There is some inference of these settings through the parent-child tree, with the Automation Manager working out an effective Default Desired State for each resource. The INGINFO panel shows the value:
Desired Available : Always The Default Desired Status provides the background availability goals that you are working with as an operator. It explains that the automation with the on demand setting can take your commands and amplify them, if, for example, you ask SA z/OS to stop the only resource that is providing demand for a chain of on demand resources. Then SA z/OS shuts down all the resources in the chain in response to your request to stop the one resource at the bottom. SA z/OS is working to minimize the dependencies in running your system. If it causes operational problems, then discuss the matter with your automation administrator.