Using the Suspend File
Resources that are already automated can be suspended and resumed during runtime using the INGSUSPD command. But there might be situations, where it is useful or necessary to "plan" resources in the policy, which are not ready to be used.
For instance, an SA administrator adds an application to the policy and the application is not yet installed. If a policy with such "planned' resources is loaded, they are automated (started and stopped) and may produce error situations until somebody suspends them manually with the INGSUSPD command. To prevent such error situations, it is possible to leverage the planned suspend capabilities of so called suspend file.
This suspend file is processed during a manager COLD/WARM start or an automation configuration REFRESH. A suspend request is generated for all resources listed in the suspend file, so they are not automated after the load of a new or changed policy.