Operations

SA z/OS uses a Manager/Agent model to automate applications on computer systems. It performs primary start or stop and recover automation for applications, and also performs operating system automation. The Automation Agent has a Processor Operations (ProcOps) focal point function that provides automation for Central Processor Complexes (CPCs), related Logical Partitions (LPARs), and certain operating system operations, especially at times when no system operation is active, for example during the nucleus initialization program (NIP) phase on course of Initial Program Load.

SA z/OS works as follows:

Figure 1. Manager/Agent Overview in SA z/OS
Manager/Agent Overview in System Automation for /OS
  1. Messages get generated from Applications and the Operating System.
  2. The messages get routed into NetView from where they are handled by the Automation Agent.
  3. The Automation Agent then determines the nature of the message and the response appropriate to the message.
  4. Local automation messages trigger an automated response back to the z/OS® system from within the agent itself.
  5. State change messages trigger an update to the Automation Manager.
  6. After the Automation Manager processed the state change and worked out its implications, it sends some orders down to the Automation Agent.
  7. The Automation Agent receives the orders and runs them, possibly resulting in commands that are being issued to the z/OS system.

The user interface for managing applications is a NetView console. However, you must use the operating system consoles to actually stop and restart the Automation Manager and NetView with the Automation Agent.