While these systems are running on your local processor, you can define them in the Automation Control PDB as Processor Operations target systems. You can then perform base operator tasks, such as console message monitoring, LPAR management, activation, and IPLs for all these systems from a single point of control, the Automation Control Processor Operations focal point. The following operating system environments are supported:
If a z/VM guest system is running in an LPAR of your local processor, Processor Operations can be used to manage guest systems running on this z/VM host. In your automation policy, define a PSM processor and define each guest that you want to manage as a system associated with the PSM processor. You can then use Processor Operations commands to monitor and control these guests.
To learn more about the policy entries, see "Entry Type Reference", section "Processor Entry Type", sub-section "Policy Items for PSM Processors" in IBM Tivoli System Automation for z/OS Defining Automation Policy.
For information on how to prepare and install the PSM support, see to "Installing SA z/OS on Host Systems", section "Preparing the VM PSM" in IBM Tivoli System Automation for z/OS Planning and Installation Guide.
All operator commands of the processor hardware interfaces are implemented as APIs. You can use these APIs to write your own automation REXX scripts, supplementing the existing set of commands with your environment-specific sequence of Processor Operations or LPAR Management commands. For more information refer to "How to Automate Processor Operations-Controlled Resources" in IBM Tivoli System Automation for z/OS Customizing and Programming Guide.
In addition to the product Automation Control entries in the automation table, you can add your own entries with the INGMSGU member. This is also valid for messages that are coming from the processor hardware interface. Messages with the message IDs of ISQ900I, ISQ800I, and ISQ700I might be of special interest. See IBM Tivoli System Automation for z/OS Messages and Codes for more information about these messages.
Processor Operations receives hardware messages and status changes from the target hardware for connected systems. Some hardware messages and status changes might point to severe problems, which might affect the availability of the managed systems. Processor Operations uses the INGALERT Automation Control command to inject alerts into a system and provides built-in alert points for selected hardware problems. The following set of built-in alert points is available for Processor Operations:
| Alert ID | Description | Resource Type |
|---|---|---|
| ISQHWMSG | One of the following important hardware messages
was issued on the target hardware:
|
MVSESA |
| ISQHWST | Target hardware (CPC) status that is changed
to one of the following statuses:
|
MVSESA |
For more information, see "Alert Based Notification" in section "Enable Alerting" in IBM Tivoli System Automation for z/OS Customizing and Programming Guide.
For Hardware Messages details, refer to the Hardware Messages task, which is available on the Hardware Management Console. For a list of the available CPC statuses, use the Acceptable Status tag in the details window that is shown for a selected CPC on your Hardware Management Console.