defined a SMART Table Entity with multiple sets of scheduling criteria and with a dependency on successful completion of a job from another table
used Schedule RBCs to appropriately (according to job) assign sets of scheduling criteria to each job
defined additional criteria for two of the jobs in the SMART Table—using an AND relationship with the additional criteria in one of the jobs, and using an OR relationship in the other job
defined two separate lines of dependency in the jobs in the SMART Table—IDJOB3 dependent on IDJOB2, and IDJOB5 dependent on IDJOB4—but no dependency between IDJOB3 and IDJOB4
ordered the SMART Table Entity with the result that all jobs in the table that should have been scheduled that day were also ordered
observed that the SMART Table Entity ended NOTOK when one of the jobs in the SMART Table ended NOTOK
learned the advantages of using a SMART Table over a table that handles jobs individually
