Using the Schedule table

If there is no entry for an object in the Schedule table, the object can run at any time.

BMC AMI Utility Managerchecks the include records before the exclude records and honors the first record found for an object. Therefore, to exclude objects from processing within all but specific time frames, add an exclude record that covers all time and then add include records for time frames for which you want to allow processing. 

BMC AMI Utility Managerchecks records from most specific to least specific. For example, MEDRECS is more specific than MEDR%.

When there is a conflict between the time frames in the Schedule table and a job schedule, the time frame specified in the Schedule table prevails. For example, if a job schedule specifies that an object should run at a time excluded in the Schedule table, the object will never run.  

When you establish the Schedule table records, consider both the table spaces and their indexes. During RTS criteria processing, the BMC AMI Reorg job can skip the table space processing and process only its indexes. When this is done, the job converts a REORG TABLESPACE into a REORG INDEX.

To handle this processing, add records in the Schedule table for index entries as well. If you don't create Schedule table records for indexes, they may run at unexpected times. Add an exclude record to prevent processing of any index selected for reorganization by the Criteria table.

We recommend adding additional IX records to the Schedule table, similar to the table space wildcard records. These index exclude records make sure that reorganization of indexes don't run outside the appropriate time frames.