|
|
|
|
|
When Control-M/Analyzer is invoked, the Active Balancing file is scanned for corresponding mission entries, those entries with mission names that match the MISSION parameter. Corresponding mission entries are then checked further to determine which mission to execute. The SCOPE parameter helps determine which entries match the specified JOB and STEP specifications.
Valid SCOPE values are shown in Table 286.
Table 286 SCOPE Parameter Values
Value |
Description |
|---|---|
SINGLE |
If JOB and STEP values match, the mission entry is eligible for further checking only if it has not been executed before. SINGLE guarantees that this mission entry is only executed 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 executed before, or it was previously executed by the current STEP in the current JOB. STEP enables the mission entry to be executed by several Control-M/Analyzer invocations, provided that the invocations all originated from the same job step (for example, from an application program that invokes Control-M/Analyzer from within a loop). |
JOB |
If JOB and STEP values match, the mission entry is eligible for further checking if it has not been executed before, or it was previously executed by the current JOB. JOB enables the mission entry to be executed by several Control-M/Analyzer invocations, provided that the invocations all originated from the same job. |
ALL |
If JOB and STEP values match, the mission entry is eligible for further checking. ALL enables the mission entry to be executed by any or all Control-M/Analyzer invocations regardless of the jobs and steps that previously initiated the entry. |
For additional information on the Active Balancing file search method, see Invoking the Control-M/Analyzer Runtime Environment.
Parent Topic |