Overruling a Suspended Resource

The most prominent use case, when overruling a suspended resource becomes necessary, is when you want to perform a system shutdown. In this situation, you do not want the shutdown process to be delayed just because the suspended resource cannot be shut down.

To enable SA z/OS to shut down such a suspended resource, it provides a new override flag, called SUS, which you can specify with the INGREQ and INGRUN commands. The mechanism works for all start and shutdown requests, not just the system shutdown. For a system shutdown, when INGREQ *ALL is specified, or when SYG is in the scope of a stop request (for example using wildcards or selecting SYG directly), the override flag is provided automatically.

The effect of using OVERRIDE=SUS is that SA z/OS sends an order regardless of the value of the suspend flag to bring the resource into its desired status. It means that the conditions to start or stop other resources can become satisfied and hence ultimately can successfully complete the original request. Note that on the automation agent side, the OVERRIDE=SUS option is handled as if OVERRIDE=FLG is given, that is, commands defined in the policy are issued, even though the resource is suspended.