Using INGSUSPD
As described in Automation Concepts, commands issued with INGSUSPD can not be overruled by a command issued with INGREQ. They can only be overwritten with the OVERRIDE parameter of INGREQ.
- Suspend automation of one or more specified application resources or application group resources
- Resume automation of one or more specified application resources or application group resources
- You cancel it using the INGVOTE, INGSUSPD, or INGSET command.
- It expires according to the specified EXPIRE parameter.
- You want it to be canceled after a specified timeout period, if the request has not been satisfied after that time.
- It is overwritten by a suspend request from the same source.
Even though suspend requests are persistent, it is not guaranteed that they will be satisfied by the automation manager.
- How should the request be executed (for example, with a scope only or a scope all)?
- 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, suspend parameters, a scope, and a timeout for request.
After pressing Enter to submit a suspend request, you will see a verification panel that lists all resources that are affected either when posting an INGSUSPD command to the automation manager or when canceling a previously made suspend request. When making a suspend 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 suspended. In this case nothing will happen to the resource.
When canceling a suspend 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.