Automation in Different Environments

Control-O can interact with the various products in use at your site to provide a wide variety of solutions to common problems and to automate many routine tasks at your site. Some components with which Control-O interacts are

• CICS Automation
• JES2 and JES3
• IMS
• Control-O Extended Automation Mechanism (XAM)
• OMEGAMON products
• SMS
• job SYSOUT processing

CICS Automation

Control-O can automate the operation of CICS, controlling multiple CICS regions from one terminal. About 50% of all CICS messages are routed to CICS transient queues and not to the MVS console. These messages can be automated in the same way as messages routed to MVS consoles.

Control-O CICS automation can

• manage all CICS messages
• manage the availability, serviceability, and recoverability of CICS
• start and stop CICS regions and change startup parameters
• inform Control-M of CICS status
• instruct Control-M to submit a job that processes a file that was closed under CICS

JES2 and JES3

Control-O can automate JES2 and JES3 operations. JES2 and JES3 messages and commands are automated in the same way as messages and commands routed to MVS consoles.

IMS

Control-O can automate the operation of IMS. Messages routed to the IMS Master terminal can be managed in the same way as messages routed to MVS consoles.

The automation of IMS by Control-O can

• manage IMS error and warning messages
• manage the availability, serviceability and recoverability of IMS
• start and stop IMS/DC, and change startup parameters
• inform Control-M of IMS/DC status
• trigger Control-M to submit an IMS recovery job
• receive performance data through a KOA Script, and act accordingly

SMS

SMS includes definitions referenced by the SMS ACS routines. When SMS is implemented, any change to a definition may affect any or all of the Control-O rules at your site. To prevent this, the SMS administrator can configure Control-O rules to override SMS ACS routines, thereby forcing storage methods as defined by Control-O.

The SMS administrator can create and test SMS definitions without influencing other SMS definitions. To determine the behavior of SMS definitions, Control-O users can inspect the trace of the SMS rules in the Automation Log.

In addition, Control-O can add automation to SMS processing that is not available through SMS ACS routines.

Job SYSOUT Processing

Many applications write messages to a Job SYSOUT data set and use it as their internal log. Control-O can intercept messages that are written to Job SYSOUT data sets.