Previous Topic

Next Topic

Book Contents

Book Index

Invoking Control-M/Analyzer (Runtime Environment)

Control‑M/Analyzer rules are invoked by the Control‑M/Analyzer Runtime environment. Therefore, the Runtime environment must be invoked in order to invoke a Control‑M/Analyzer rule.

The table describes the methods you can use to invoke the Control‑M/Analyzer Runtime environment.

Table 213 Invoking the Control-M/Analyzer Runtime Environment

Method

Description

Direct call

When the Control‑M/Analyzer Runtime environment is invoked by a direct call, the name of the rule to be invoked by the Runtime environment is one of the parameters passed in the call. The direct call to the Runtime environment can come from an application program, a job step, or another INCONTROL product. A search for the specified rule name is performed in the libraries referenced by DD statement DABRULE. No scheduling criteria are specified. The same rule is always activated.

Balancing mission

A search is performed for the specified balancing mission name in the Active Balancing file. After locating the appropriate mission, the rule specified by the mission is activated. When Control‑M/Analyzer is invoked using this method, scheduling criteria can be specified for date-dependent balancing activities. For example, the same mission can activate different rules according to the day of the week using different categories of the mission.

These methods of rule activation are discussed in the coming topics.

Parent Topic

Control-M/Analyzer