A regular report decollating mission differs from a generic decollating mission in the following way:
A regular report decollating mission is associated with a specific job name. It may be triggered for execution by the appearance on the output queue of a job with the same name. It is also possible to send all of the job’s outputs directly to compressed datasets; therefore, no output appears on the spool for such a job. In this case, triggering execution of the report decollating mission is accomplished using prerequisite conditions.
A regular report decollating mission can decollate any output class specified in its ON statements (see "ON Statement" later in this chapter). After decollation, non-held output is deleted from the spool, held output remains on a JES2 but is deleted from a JES3 spool, and the mission status is set to ENDED.
A generic decollating mission can be defined for a specific job name but is usually used in conjunction with a generic job name. A generic job name is specified using mask characters (see "Character Masking" in Chapter 2). Execution of the report decollating mission is triggered by the appearance of a job (whose name matches the job name mask) in specific output classes (in non-held status). These output classes are defined in Control-D installation parameter GENCLAS. The appearance of a matching job name in other output classes (or in held status in the generic classes) does not trigger the execution of a generic decollating mission.
A generic decollating mission can decollate only from the generic classes defined in the Control-D installation parameters. Any output which is decollated by a generic decollating mission is deleted from the spool.
For further information, see the Control-D and Control-V chapter in the INCONTROL for z/OS Administrator Guide.
