Setting Automation Agent Flags

You can set automation agent flags for:

System Defaults (using their AUTOMATION FLAGS policy item)
Application Defaults (using their AUTOMATION FLAGS policy item)
MVSCOMP Defaults (using their AUTOMATION FLAGS policy item)
Applications (using their AUTOMATION FLAGS or MINOR RESOURCES policy item)
MVS Components (using their MINOR RESOURCES policy item)

Note: For MVS components, only the Automation and Recovery flags apply.

Because flags have inherited values, it is not necessary to define them all explicitly. Specific resources need only have flags defined if they differ from the values inherited from the defaults.

A common step during automated handling of events is to check the automation flags to determine whether automation is on or off and whether automated handling of an event can continue.

The AOCQRY command performs this automation flag check.

The benefit of this automation hierarchy is that you can customize SA z/OS to automate as many activities and resources as necessary in the z/OS environment. You can choose to have SA z/OS handle all phases of startup, monitoring, recovery, and shutdown for all resources or have a human operator control some phases for some resources. You can control all automation by setting just one flag (the Automation flag) on one panel and then setting exceptions. The simplest way to automate your resources is to use the Automation flag.

Periods that automation is not to apply for can be specified.

There are several commands to display automation flag settings, for example, DISPFLGS. The INGAUTO command dialog can be used to set or override automation flags, if the affected resources are not suspended.

SA z/OS provides an exit capability for automation flag processing. See IBM Z® System Automation Customizing and Programming for more information.