Control-M/Analyzer Database variables

Usually, jobs that perform similar functions need access to the same type of information. For example, quality control jobs need to access different Control-M/Analyzer Database variables than payroll jobs.

Control-M/Analyzer assumes that the Database variable being referenced belongs to the current group. There is no need to specify the group name. However, it is possible to define a rule that accesses Database variables of other groups.

Rule Activity screen

Control-M/Analyzer rule invocations can be listed by group. Only relevant rule invocations are shown, providing quick access to needed information (for example, their invocation reports).

IOA Log file

The audit trail in the IOA Log file may be listed by group, providing a meaningful list of audit trail entries.

Implementation modes

Rules can be tested and implemented by group by specifying an implementation mode. The following modes are provided by Control-M/Analyzer:

• Define mode - Rules and variables of a group under Define mode are not processed by Control-M/Analyzer. Control-M/Analyzer automatically returns an OK result. This mode is especially useful when initially developing and inputting new rules and variables.
• Simulate mode - Simulate mode instructs Control-M/Analyzer to process rules and report on balancing results without taking action. This mode enables the testing of rules without impacting the production environment. Online and batch action reports are produced detailing the outcome of the evaluation, but actual reaction processing (for example, committing Control-M/Analyzer variables, adding new prerequisite conditions) is suppressed. This mode is especially helpful during system testing and rule debugging.
• Active Mode - Active mode is the production mode for Control-M/Analyzer rules. In Active mode, data are evaluated and all actions defined by the user are taken.