|
|
|
|
|
Standard report decollating missions can handle output from the spool or from CDAM datasets. They are executed once to handle the output produced by a specific job name (unless defined as cyclic report decollating missions, with a task type of CRP).
The generic decollating missions monitor specific JES classes (assigned in member CTDPARM in the IOA PARM library) for the appearance of Non-Held output. When an output appears, Control-D looks for a generic mission to process the output.
The table below compares the differences between standard and generic decollating missions:
Table 36 Differences Between Standard and Generic Report Decollating Missions
Standard Report Decollating Mission |
Generic Report Decollating Mission |
|---|---|
Decollates from the spool or CDAM. |
Decollates from spool only. |
Decollates from any specified class. |
Decollates only from the defined generic classes. |
Decollates Held and Non-Held output. |
Decollates Non-Held output only. |
Handles specific job names only. |
Can use job name masks. |
Executes once (unless the task type is set to CRP). |
Executes every time a job name match is found. |
Parent Topic |