Automating Processor Operations-Controlled Resources

This information describes how to customize your SA z/OS installation to enable the automation of messages coming from target systems that are controlled by processor operations.

These target systems or resources are referred to as processor operations resources in the following.

Processor Operations, which is a focal point type function, allows you to monitor and control processor hardware including Coupling Facility images, from a single NetView, the processor operations focal point.
Notes:
  1. VM guest systems are treated the same as any other target systems that are controlled by ProcOps (see IBM Z® System Automation Operator's Commands for details).
  2. PSMs are "virtual" hardware and therefore not all target hardware commands apply (see IBM Z System Automation Operator's Commands for details).

With the method described in this chapter, you can use SA z/OS system operations to react on these messages. This information is contained in Automating Processor Operations Resources of z/OS Target Systems Using Proxy Definitions, which introduces the general process to achieve such message automation.

Note:
The capability described in this section is a low-fidelity means to manage hardware resources from System Automation's system operations panels, like INGLIST or INGREQ. However, the use of this capability is discouraged due to certain limitations in this approach:
  • Every target system is presented as an application resource missing the granularity of hardware statuses that you would get, if you use existing processor operations panels, today.
  • The message automation capabilities that this function gives you are focusing around automation of the typical messages on the course of an IPL. Messages that are not already handled by the System Automation product code require the implementation of custom message rules (either a user-defined automation table or using automation table overrides out of the customization dialog).