|
|
|
|
|
Normally, jobs in a table are processed independently of each other—each job is handled only according to the parameters in its own job scheduling definition.
However, you can define a SMART Table in the Scheduling Definition facility which supports handling the set of jobs in the table as a unit. The scheduling definitions of the jobs as a unit are defined in the SMART Table Entity. Each job in the SMART Table is handled according to the relationship between the basic scheduling criteria of the job and the basic scheduling criteria of the SMART Table Entity. These include:
Table 13 SMART Table Handling Criteria
Criteria |
Description |
|---|---|
Basic Scheduling criteria |
Scheduling criteria to be applied to jobs in the SMART Table. |
Runtime Scheduling criteria |
Required runtime criteria for all scheduled jobs in the SMART Table. |
Post Processing actions |
Actions to be performed when all scheduled jobs in the SMART Table have finished executing with the appropriate status. |
When jobs are ordered, you will be able to monitor the status of the jobs in and perform actions on the jobs individually. In addition, when a SMART Table is ordered, you will be able to monitor the status of and perform actions on the table. For example, just as you can define post-processing tasks that Control-M should perform when a job successfully ends, you can define post-processing tasks that Control-M should perform when all the jobs in a SMART Table successfully end.
Note: The tables that appear in the active environment were defined as SMART Tables.
Parent Topic |