A decollating mission allocates (parts of) reports to users authorized to receive them. A decollating mission also builds one or more predefined indexes for reports so that pages or sections of a report can be selectively retrieved for online viewing, printing, and so on.
The workflow of a decollating mission consists of the following stages:
The New Day procedure analyzes the scheduling parameters of the report decollating mission definitions and decides which decollating missions should be executed on that day. The selected missions are placed in the Active Missions file.
The Control-D monitor analyzes the mission’s runtime scheduling criteria (prerequisite conditions, time constraints, availability of the job on the output queue, and so on). If all scheduling criteria are met, the decollating mission executes.
Generic jobs that appear on a specific output class are automatically decollated. The generic job name can contain mask characters (for example, all jobs starting with NDX).
The monitor reads reports from the spool and writes them to Compressed Dataset Access Method (CDAM) files. Alternatively, reports can be written directly to CDAM files without using the spool.
The indexing process assigns pointers to each page, section or line of a report and identifies beginning and ending pages for each index value. For detailed information about index design and usage, see Report Indexes.
Decollating parameters assign report names and specify migration, printing and backup instructions.
When reports are decollated, prerequisite conditions can be added and/or deleted (thereby triggering other events or missions in the production environment) and messages can be sent to specified destinations via the Shout facility.
Decollation results are stored in the Active User Report List file.
After decollation, reports are available for printing, migration, online viewing, and so on.
