Invoking Control-M/Analyzer Using Balancing Missions

Balancing missions can be used to invoke Control‑M/Analyzer from one of the following:

application program
Name of the mission to invoke is specified by a program call to Control‑M/Analyzer in the application program. For additional information, see the section about calling user routines in the Control‑M/Analyzer User Guide.

Example

CALL CONTROLB(<mission>, ...);
job step
Name of the mission to be invoked is specified in the JCL statements of the job step that invokes the Control‑M/Analyzer Runtime environment.

Example

// EXEC CONTROLB,
// MISSION=DAILYBAL,GROUP=group,ARG=(arg1,...,argn)

Note: The GROUP argument is mandatory only if the rule definition does not contain a value for the GROUP parameter. If the GROUP parameter is specified in the rule definition, the GROUP argument is optional.

The ARG specification allows up to 50 arguments. For more information see Passing Arguments While Invoking Control-M/Analyzer.

When the call or step that invokes Control‑M/Analyzer is invoked, Control‑M/Analyzer first checks each entry in the Active Balancing file to locate the appropriate balancing mission. the following table describes the phases of the Active Balancing file search method.

Table 214 Active Balancing File Search Method Phases

Phase	Description
Phase 1	All mission entries with corresponding mission names are checked to see if their runtime scheduling criteria are met. Missions whose runtime scheduling criteria are met advance to the second phase for further checking.
Phase 2	Missions that have passed the first phase are checked to see if the values specified by parameters JOB and STEP match the job name and (optional) step name of the current call or step.

Note: The * mask character can be specified at the end of JOB and STEP names.

The SCOPE parameter of each eligible mission entry in the Active Balancing file is checked to determine a JOB-STEP match. The SCOPE parameter specifies one of the following options:

Table 215 Values for Parameter SCOPE

Option	Description
SINGLE	If JOB and STEP values match, the mission entry is eligible for further checking only if it has not been invoked before. the SINGLE option guarantees that this mission entry is only invoked once – by a single Control‑M/Analyzer invocation.
STEP	If JOB and STEP values match, the mission entry is eligible for further checking if it has not been invoked before or if it was previously invoked by the current STEP in the current JOB. The STEP option enables the mission entry to be invoked repeatedly, provided that the mission entry is invoked from the same job step each time (for example, from an application program that invokes Control‑M/Analyzer from within a loop).
JOB	If the JOB value matches, the mission entry is eligible for further checking if it has not been invoked before or if it was previously invoked by the current JOB. The JOB option enables the mission entry to be invoked by several Control‑M/Analyzer invocations, provided that the invocations all originated from the same job.
ALL	The mission entry is always eligible for further checking. The ALL option enables the mission entry to be invoked regardless of the JOB and STEP that previously invoked the mission entry.

The first mission that matches the above criteria is selected for execution. If no matching mission is found, a runtime error occurs.

Parent Topic

Invoking Control-M/Analyzer (Runtime Environment)