|
|
|
|
|
Parameter MAXWAIT is used to overcome the problem of delays in production. A mission that is scheduled for execution on a specific day does not always finish executing that same day. A mission may be delayed due to number of reasons, such as hardware failure, a heavy production workload, or a bug in one of the mission’s predecessors. Therefore, it may be desirable to specify an additional number of days that the mission should remain available for execution.
When a mission is disregarded (that is, Control-V times out), an appropriate message is written to the IOA Log file.
When a mission is scheduled because parameter RETRO is set to Y, the mission always has at least one day to execute. This occurs even if the current working date exceeds the MAXWAIT days after the mission’s last original scheduling date. For additional information, see parameter RETRO later in this chapter.
Emergency missions are also disregarded if their MAXWAIT periods have passed.
An emergency mission that belongs to a specific group (through parameter GROUP) and whose MAXWAIT period has not passed, is not deleted from the Active Missions file until all regular missions belonging to the same group have finished executing. This is desirable because the mission may be needed again at a later stage (due to a job rerun).
Parent Topic |