Overview

The heart of the Control-M/Analyzer balancing system is the Control-M/Analyzer Runtime environment (1). The Runtime environment is usually activated by a job step, a subroutine call from an application program, or a call to Control-M/Analyzer from another INCONTROL product.

The Runtime environment is responsible for the execution of balancing procedures (known as rules and balancing missions). Rules contain user-defined instructions for balancing and are stored in the Rule Definition library (2). Missions contain rule scheduling criteria and are stored in the Mission Definition library (3). Both these libraries are standard partitioned data sets and are user-defined.

When the Runtime environment is activated, the name of the mission or rule that should be invoked is specified. The Runtime environment then performs the balancing procedures specified by the mission or rule.

The Repository (4) is accessed by all the components of Control-M/Analyzer. Every action performed by Control-M/Analyzer is recorded in the Repository. The Repository can be scanned and updated using the Online Tracking and Control facility (5), which is a full screen, user-friendly interface that can be activated under TSO, TSO/ISPF, ROSCOE/ETSO, CICS, VTAM, IMS/DC, IDMS/DC, or COMPLETE.

The New Day procedure (6) analyzes the mission scheduling parameters and places missions to be invoked in the Active Balancing file on a daily basis.

The Reporting facility (7) accesses the Repository to produce various reports that are required in an active data center.

Control-M/Analyzer Utilities (8) enhance the operation of Control-M/Analyzer by facilitating maintenance, backup and archiving of the Repository, and by performing other necessary functions. For detailed information about Control-M/Analyzer utilities, see the INCONTROL for z/OS Utilities Guide.