SMART Table scheduling is not always desired. But in those situations in which SMART Table scheduling is desirable, use of a SMART Table simplifies the process and provides several advantages. Some of these are discussed below:
Once a set of basic scheduling parameters is defined in the SMART Table Entity, all jobs that require that set of scheduling parameters can utilize them simply by specifying the schedule RBC name in the appropriate field. The more complex and detailed the scheduling parameters, the greater the advantage.
Regular job scheduling definitions provide for one set of scheduling criteria. However, in a SMART Table, the SMART Table Entity can include multiple sets of scheduling criteria, and any number of these can be specified in any job scheduling definition in the SMART Table. This enables the job to utilize multiple sets of basic scheduling criteria.
Defining an IN condition in a SMART Table Entity makes all jobs in that table dependent on that condition without defining the IN condition in all the individual job scheduling definitions. The more jobs in the SMART Table that have no predecessor job other than the predecessor of the SMART Table Entity, the greater this advantage.
If you want to define Post-processing that should be performed only if any of the jobs ended NOTOK, it is much easier to define the conditional Post-processing once in the SMART Table Entity, rather than repeatedly in each job scheduling definition.
If you want to define Post-processing that should be defined if all the jobs ended OK, this is also easier to do in SMART Tables if there are jobs not belonging to the same hierarchy of dependence.
If the submission of a job in another table depends on the outcome of all the jobs in the current table, this is easier to define in a SMART Table.
This completes the steps in this chapter of the Control-M for z/OS Getting Started Guide.
Parent Topic |