Through the CA OPS/MVS Automated Operations Facility (AOF), you can develop applications to automate responses to system events.
The ability to react to various system events is mandatory when attempting to build effective automated applications. The AOF is a base component of CA OPS/MVS that monitors system events and automatically responds to them. You determine the system events that the AOF recognizes, and how it responds to those events, by defining special OPS/REXX programs called AOF rules.
AOF rules are classified as special OPS/REXX programs because AOF rules have a unique structure, reside in PDS data sets called rule sets, and are triggered by a system event.
The AOF can take action in response to the following types of system events:
An API event occurs when an application program calls the API interface. Typically, the application that calls the API is a system service provider program, such as a tape library manager, or a network control program. When these programs detect an event that needs attention, they can initiate automation rules by calling the API. Applications can also request information from CA OPS/MVS through the API.
An ARM event occurs when the z/OS Automatic Restart Manager tries to restart an ARM-registered job or started task after an unexpected termination. The restart may occur on the same system or on another system in the sysplex if the termination was due to a complete system failure.
A command event occurs when any z/OS or subsystem command is issued on the system.
A DOM event occurs when any z/OS component issues a DOM macro to remove a highlighted message from an MCS console; for example, a tape mount message gets internally DOMed when the mount is satisfied.
EOJ events occur when a task such as a batch job terminates and the INITSMF and EOSRULES parameters of CA OPS/MVS are set to YES.
EOJ rules have these advantages over message rules:
EOM events occur when any address space such as a TSO user or started task terminates.
EOM rules have these advantages over message rules:
An EOS event occurs when a step terminates in a job or started task and the INITSMF and EOSRULES parameters of CA OPS/MVS are set to YES.
A global variable event occurs when the value of an OPS/REXX global variable changes.
A message event occurs when a system component sends a message to a console or to a system log. The AOF recognizes and responds to these types of messages:
An OMG event occurs when an OMEGAMON exception is generated from any of these products:
A request event is triggered on demand by any end user.
A screen event occurs when the screen or state of an EPI virtual terminal changes. Screen event rules allow you to automate any VTAM application.
A security event occurs when you invoke any CA OPS/MVS facility (for example, using the OPSCMD command processor to issue a z/OS command), allowing security for CA OPS/MVS to be performed by coding OPS/REXX programs, rather than by complex assembler exits. Security rules can be used to interface with your security product to provide comprehensive and flexible control of CA OPS/MVS facilities.
A TLM event occurs when a job or task exceeds the processor time limit imposed by the system, either by default or by the TIME JCL parameter on the JOB or execute statement. A TLM event also occurs if a non-exempt job exceeds the maximum continuous wait time specified in the SMF parameters for the system.
A time event occurs at a specified time or date or after a specified time interval.
A USS event occurs when the CA OPS/MVS message exit of CCS for z/OS is driven by one of the following:
|
Copyright © 2011 CA.
All rights reserved.
|
|