|
|
|
|
|
The MAXWAIT parameter is used to overcome the problem of delays in production. A job that is scheduled for execution on a specific day does not always get executed that same day. This can be due to a number of reasons, such as hardware failure or a heavy production workload. Therefore, it may be desirable to specify an additional number of days that the job must remain in the Active Jobs file awaiting execution.
When a job cannot be submitted for execution within the specified time limits, an appropriate message is written to the IOA Log file, and the job is deleted from the Active Jobs file.
Jobs scheduled as a result of a Y value in the RETRO parameter are always given at least one day within which to execute, even if the MAXWAIT parameter indicates that they must no longer be in the Active Jobs file. This occurs when the current working date exceeds the original scheduling date (ODATE) by more than the number of days specified in the MAXWAIT parameter on the day the job is scheduled by RETRO=Y. For more information, see RETRO: Basic Scheduling Parameter.
Emergency jobs not belonging to a group (parameter) are discarded if their specified MAXWAIT periods have passed. An emergency job that belongs to a specific group (specified in the GROUP parameter) and whose MAXWAIT period has not passed is not deleted from the Active Jobs file until all of the regular jobs that belong to the same group have finished executing. This is in case the job is needed at a later stage.
When a job is not ENDED OK, the MAXWAIT of a job is affected by the FROM DAYS and UNTIL DAYS parameters. The job remains in the AJF until the end of the logical UNTIL DAY. The job is only deleted from the AJF on MAXWAIT days after the job's ODATE (provide that the Control-M logical date is later than the job's ODATE plus MAXWAIT).
For jobs containing a time zone later than the local Control-M time, one day is added to MAXWAIT so that the job will stay one additional day on the Active Jobs file.
For ON SPOOL jobs in WAIT SCHEDULE status, the MAXWAIT parameter is ignored. Jobs in this status are not removed from the AJF even after the MAXWAIT value is exceeded, but remain in the AJF until their status is changed to ENDED OK or ENDED NOTOK.
Parent Topic |