Maybe Jobs in SMART Tables

The above implementation for handling unscheduled conditions of Maybe jobs can be applied to jobs and conditions.

However, an alternative method is available for conditions and jobs in SMART Tables. Rather than add the unscheduled conditions of Maybe jobs to the IOA Conditions file, the unscheduled conditions can be removed as runtime scheduling criteria for the successor job orders.

The SMART Table Entity definition in SMART Tables contains an ADJUST CONDITIONS field. If a value of Y is specified in the ADJUST CONDITIONS field, Control-M checks the scheduled jobs for unscheduled conditions.

Unscheduled conditions normally added by other jobs in the same SMART Table are removed from the IN statements of the scheduled job orders:

• These conditions do not appear in the Zoom screen. They are not, however, deleted from the original job scheduling definition.
• These conditions also do not appear in the Manual Conditions file. Therefore, there is no real advantage to defining them with a unique prefix, unless they are used as IN conditions for jobs in a different table.

Note the following points

• Unscheduled conditions normally added by jobs in other tables are not removed from the job order. They appear in the Manual Conditions file.
• As indicated above, ADJUST CONDITIONS applies only to jobs in the same SMART Table. By contrast, the IOALDNRS utility detects unscheduled conditions of Maybe jobs across tables, and the ADDMAYBE KSL utility adds these conditions to the IOA Conditions file regardless of table.

For more information, see Job Production Parameters.