Automation Manager Considerations

This information presents automation manager considerations relevant to the installation process.

For automation manager concepts that are of interest from an operator's point of view, refer to IBM Z® System Automation User's Guide.

The automation manager is introduced as a separate address space. An installation requires one primary automation manager and may have one or more backups. The automation manager is loaded with a model of the sysplex when it initializes. It then communicates with the automation agents in each system, receiving updates to the status of the resources in its model, and sending orders out to the agents as various conditions in the model become satisfied.

A series of substeps is required to get the automation manager up and running for your SA z/OS installation. These installation steps are described in this documentation, but are not identified as being specific automation manager installation steps.

Only the default installation of UNIX System Services is a prerequisite for the automation manager. No USS file system or UNIX shell is required.

The automation manager must be defined by RACF® (or an equivalent security product) as a super user for UNIX System Services. The user that represents the started tasks in your installation must be authorized for the OMVS segment.

Note: The system on which the automation manager should be started must be defined as policy object System in the policy database that will be used to create the automation manager configuration file that this automation manager uses (see also Step 15A: Build the Control Files).