Overview

When defining job scheduling definitions, it is good practice to group together related job scheduling definitions. This is not a requirement—related jobs can belong to different groups, or not belong to any group—but it can be useful. For example, if related jobs belong to the same group, you can use the group name to filter the Active Environment screen so that only the jobs in that group are displayed. But greater functionality than just ease of filtering a display can be provided by assigning a set of jobs to a SMART Table.

The major advantage of defining SMART Tables is that they enable you to define basic scheduling criteria, runtime scheduling criteria and post processing criteria that apply to the jobs in the SMART Table as a whole.