Building Blocks
The building blocks are managed only if the key elements of the processor hardware interfaces are defined in the Automation Control policy. There are four policy entry types important for the hardware interfaces: Processor, System, Enterprise, and if an attached zBX must be managed, zEnterprise Ensemble.
Processor (PRO)
This entry defines the local processor (CPC) that you want to control. The entry includes definitions that are required to access the mainframe and details about each processor partition that you want to manage, such as partition name and the system name that is running in this partition. For example, you define a processor that is called PROC1 with an LPAR of LP1, which has SYS1 as the system defined to run in it. Because you decided to use the Processor Operations interface protocol for PROC1, you can use the Processor Operations policy of your SYS1 system entry to specify basic LOAD information to use when initializing SYS1 under Processor Operations control.
See Usage and Operation, for more information about the different processor hardware interfaces.
To learn more about these policy entries, see "Entry Type Reference", sections "System Entry Type", and "Processor Entry Type" in IBM Tivoli System Automation for z/OS Defining Automation Policy.
System (SYS)
This entry contains all definitions that Automation Control needs to manage a system in the context of application automation. For Processor Operations use, the processor operations definitions are provided. These specific system policy definitions are not required for the LPAR Management interface.
To learn more about the Processor Operations specific system policy definitions, see "Entry Type Reference", sections "System Entry Type", in IBM Tivoli System Automation for z/OS Defining Automation Policy.
zEnterprise Ensemble (ENS)
This entry contains the definitions for the connection to an Ensemble HMC for zBX management purposes. If your local processor is defined as an ensemble member node and has a zEnterprise BladeCenter Extension (zBX) attached, you can manage the virtual servers running in the zBX blades with Processor Operations. The ensemble definitions include the HMC address and login credentials. Processor Operations uses this data to communicate with the HMC using the Web API. For example, processor PROC1 has a zBX attached and you define the connection to its ensemble HMC as MYENS.
To obtain more policy-related information, see "Entry Type Reference", section "zEnterprise Ensemble Entry Type" in IBM Tivoli System Automation for z/OS Defining Automation Policy.
Enterprise (ENT)
For Processor Operations only, the PROCOPS FOCAL POINTS policy of your Enterprise entry must be defined. The minimum required definition is the primary focal point name. This is the NetView domain name of your Automation Control Processor Operations instance. Note, that the backup focal point name specification is not used. It is reserved for future use.
To obtain more policy-related information, see "Entry Type Reference", section "Enterprise Entry Type", sub-section "PROCOPS FOCAL POINTS Policy Items" in IBM Tivoli System Automation for z/OS Defining Automation Policy.