|
|
|
|
|
Balancing missions can invoke Control-M/Analyzer from one of the following:
Table 13 Balancing Mission Invocations
Method |
Description |
|---|---|
Application program |
The name of the mission to invoke is specified by a program call to Control-M/Analyzer in the application program. For additional information see Appendix C, "Calling Control-M/Analyzer User Routines,". Example: CALL CONTROLB(<mission>,...); |
Job step |
The name of the mission to be invoked is specified in the JCL statements of the job step (which invokes the Control-M/Analyzer Runtime Environment). Example: // EXEC CONTROLB,MISSION=msn,GROUP=group, |
Note: The GROUP specification is mandatory only if the GROUP parameter in the rule definition was omitted. Otherwise (the GROUP parameter was specified in the rule definition), the GROUP specification 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 executed, Control-M/Analyzer first checks each entry in the Active Balancing file to locate the appropriate balancing mission. The Active Balancing file search method consists of the phases shown in Table 14.
Table 14 Active Balancing Search 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 the JOB and STEP parameters 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 options shown in Table 15.
Table 15 SCOPE Parameter Options
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 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 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 |