Using INGREQ
As described in Automation Concepts, commands issued with INGREQ and a high priority are the most powerful automation commands to make applications available or unavailable. They supersede all other desired status requests that exist against a resource at that time. Suspend requests against a resource can only be overruled with an INGREQ command and OVERRIDE=SUS.
You can use this command to:
- Initiate the start process of one or more specified application resources or application group resources
- Initiate the shutdown process of one or more specified application resources or application group resources
A desired status request is persistent until:
- You cancel it using the INGVOTE, INGREQ, or INGSET command
- It expires according to the specified EXPIRE parameter
- It is automatically removed when a specified condition comes true
- You want it to be cancelled after a specified timeout period, if the request has not been satisfied after that time
- It is overwritten by a desired status request from the same source
Even though desired status requests are persistent, it is not guaranteed that they will be satisfied by the automation manager.
With a desired status request you specify two categories of parameters:
- How should the request be executed (for example, with low or high priority)?
- What should happen with the request during its lifetime, for example, should it expire after a certain time anyway, or after a timeout if it has not been successful?
If you specify the command name without any parameters, SA z/OS displays a panel where you can specify, for example, startup or shutdown parameters, a priority, and a timeout for the desired status request.
Use PF11 to see additional parameters.
After pressing Enter to submit the desired status request, you will see a verification panel that lists all resources that are affected either when posting an INGREQ command to the automation manager or when cancelling a previously made desired status request. When making a desired status request, a resource is affected if it is within the dependency graph that the request is propagated along. This will also display resources that are already in the desired state. In this case nothing will happen to the resource.
When cancelling a desired status request, a resource is affected when it holds a vote for the request to be removed. Only resources that are highlighted will be processed by the command. All other resources are already in the state satisfying the appropriate dependencies.