|
|
|
|
|
The MAXWAIT parameter is used to overcome the problem of delays in production. A report decollating mission that is scheduled for execution on a specific day does not always finish executing that same day. This is the case when the job that produces the reports has not yet run. A job may be delayed due to a number of reasons, such as hardware failure, a heavy production workload, or a bug in one of the job’s predecessors. Therefore, it may be desirable to specify an additional number of days that the report decollating mission should remain available for execution.
When a report decollating mission cannot be executed within specified time limits, an appropriate message is written to the IOA Log file, and the mission is deleted from the Active Mission file.
When a report decollating mission is scheduled because parameter RETRO is set to Y, the report decollating mission always has given at least one day to execute. This occurs even if the current working date exceeds the MAXWAIT days after the report decollating mission’s last original scheduling date. For additional information, see RETRO: Basic Scheduling Parameter (decollation).
An emergency report decollating mission is also disregarded if its MAXWAIT period has passed.
An emergency report decollating mission that belongs to a specific group (via parameter GROUP) and whose MAXWAIT period has not passed is not deleted from the Active Missions file until all regular report decollating missions belonging to the same group have finished executing. This is desirable because the report decollating mission may be needed again at a later stage (due to a job rerun).
The INCONTROL administrator can implement an option that causes report decollating missions that terminate OK to also remain in the Active Missions file for MAXWAIT days.
Parent Topic |