Schedule Generic Decollating Missions to the Active Missions File

Generic Missions must be scheduled to the Active Missions file to execute. The mechanism used to place a copy of the generic decollating mission definitions on the Active Missions file is a special scheduling program called by the New Day procedure (CTDNDAY).

You can schedule generic decollating missions using any of the methods detailed in Phase 3 for regular report decollating missions. We recommend that you use member GENLIST read by the CTDNDAY procedure to schedule generic missions. Control-D will analyze a supplied list of generic missions and determine which ones should be scheduled to the Active Missions file. The reason for this recommendation is that if the CTDNDAY procedure fails to schedule the generic missions, it will automatically deactivate generic processing. The other methods of scheduling will not do this if an error occurs.

MSGCLASS output that is written to a generic class before a generic decollating mission is scheduled, or while generic processing is deactivated, will be processed when the relevant mission is scheduled, or when generic processing is restarted. If generic processing is stopped for any reason, a highlighted message is written to the console every ten minutes. This is to make you aware that the spool might be filling up with MSGCLASS output.