|
|
|
|
|
Special scheduling of generic decollating missions ensures that all generic missions are scheduled successfully before the Control‑D monitor starts generic mission processing. If procedure CTDNDAY fails (for example, the system crashes or there are invalid parameters in generic decollating mission definitions) while processing a report decollating mission from member GENLIST, when the Control‑D monitor is started, it does not process generic decollating missions without a manual operator command. If all generic missions are scheduled successfully, decollating of generic missions resumes when the Control‑D monitor is brought up.
If generic mission decollating is not active when the Control‑D monitor shuts down for a new day (for example, because the operator deactivated it manually), it remains inactive when the Control‑D monitor is brought up again.
Generic decollating missions can also be scheduled manually, or by any of the other scheduling methods. However, it is highly recommended not to schedule the missions through the REPLIST member of the New Day procedure with non‑generic decollating missions.
Parent Topic |