|
|
|
|
|
A set of jobs whose processing (for example, scheduling, submission, and post processing) is handled as a unit, is defined in a SMART Table. This table must be created as a SMART Table by selecting Y in the Scheduling Definition facility entry panel.
At the time of creation of a SMART Table, a scheduling definition for the set of jobs, called the SMART Table Entity, is created. The SMART Table Entity is used to define processing criteria for the set of jobs in the SMART Table. These include:
Table 32 Scheduling Criteria
Criterion |
Description |
|---|---|
Basic Scheduling Criteria |
Any number of sets of basic scheduling criteria can be specified in the SMART Table Entity. At least one of these sets must be satisfied before any job in the SMART Table, can be scheduled. Each set of basic scheduling criteria in the SMART Table Entity is assigned a unique name called a Schedule RBC. These Schedule RBC names can be entered in job scheduling definitions in the table. When a set of basic scheduling criteria in the SMART Table Entity is satisfied, job scheduling definitions that specify the corresponding Schedule RBC are scheduled that day. Exclude RBC names can also be entered in job scheduling definitions in the table. These Exclude RBC names start with an "!" prefix and job scheduling definitions that specify the corresponding Exclude RBC are prevented from being scheduled that day. Job scheduling definitions can also contain their own basic scheduling criteria, and be scheduled according to those criteria, provided that the basic scheduling criteria in the SMART Table Entity is satisfied. |
Runtime Scheduling Criteria |
Before any job in a SMART Table can be considered for submission, all SMART Table runtime scheduling criteria specified in the SMART Table Entity must be satisfied. After these are satisfied, a job is submitted only if its own specified runtime scheduling criteria are satisfied. |
Post-processing Actions |
Post-processing actions can be defined for the SMART Table Entity. These are performed after the table has finished processing (that is, all jobs in the table have terminated). These actions can be made conditional upon whether all submitted jobs in the SMART Table ended OK, or whether at least one job did not end OK. |
The SMART Table Entity also contains a field (ADJUST CONDITIONS) that enables job dependencies based on prerequisite conditions to apply only if predecessor jobs in the SMART Table are scheduled.
Control-M internally tracks each SMART Table and the jobs in the SMART Table. Each order of each SMART Table is identified as a unit.
The status of each SMART Table that has been ordered can be viewed using option T (Table) of the Job Status screen (Active Environment screen).
Note: When the IN conditions of the SMART Table Entity, are satisfied (for example, they have been added to the IOA Conditions file), the jobs in the SMART Table begin execution, assuming that their other runtime criteria are satisfied.
By default, if jobs in a SMART Table have already begun execution and an IN condition for the SMART Table is deleted from the IOA Conditions file, this change does not affect the processing of the jobs in the SMART Table; the jobs continue execution as if all the IN conditions were still satisfied. This default is overridden if the TBLRECHK parameter in the CTMPARM member in the IOA PARM library is set to Yes, in which case IN conditions SMART Table Parameters are checked before each job is selected.
Parent Topic |