Previous Topic

Next Topic

Book Contents

Book Index

General Information

Each ON statement starts an ON block that extends to the next ON statement. An ON block is comprised of an ON Statement, ON Statement Defaults and one or more WHEN statements paired with DO statements. For a discussion of the ON Statement Defaults, see ON Statement Defaults: Decollating Parameter (decollating mission).

Multiple ON statements can be specified in order to define different decollation instructions for different parts of the report (for example, report output in Class A is handled differently from report output in Class B).

When Control-V decollates a non-held spool SYSOUT, the SYSOUT is removed from the spool to the compressed SYSOUT dataset.

When Control-V decollates a held spool SYSOUT, the SYSOUT is copied from the spool to the compressed SYSOUT dataset. The original SYSOUT remains on a JES2 spool but is deleted from a JES3 spool.

Note: When Control-V decollates a generic job, the SYSOUT is always deleted from the spool.

Control-V decollates only sysouts or compressed datasets of the job that are defined by ON statements. Any reports of the job that are not included in the ON statements (for example, certain classes) are not decollated. Therefore, they are not available for online viewing, printing or backup.

ON CLASS decollates all the sysouts of the specified class (held and non-held). (For generic decollating missions, only the non-held sysouts are processed.) It is possible to specify multiple ON statements for the same class, each one containing a different set of decollating criteria. It is also possible to apply a different set of decollating criteria for the same report. This option is used only for special cases, examples of which can be found later in this chapter. Normally, it is recommended to avoid multiple ON statements for the same class.

At least one ON CLASS statement must be specified for a generic decollating mission. This class must be defined as a generic class in the Control-V installation parameters. All other classes are rejected (for a generic job). A generic decollating mission can contain only ON CLASS statements for generic classes.

Note: For further information, see Generic Job Considerations (JES2 only).

ON DSN decollates all compressed sysouts that meet the selection criteria specified in the ON DSN field. The selection criteria specified must be valid Compressed Dataset Access Method (CDAM) control parameters (such as PREFIX, PGMSTEP or PROCSTEP) that can be used for retrieval. For more information, see Compressed Dataset Access Method (CDAM) for a list of CDAM control parameters that can be used for retrieval. The CDAM parameters specified in the ON DSN statement are merged with the parameters specified in the DSN field of the Runtime Scheduling parameters. In the case of duplicate parameters, the parameter specified in the ON DSN statement overrides the parameter specified in the DSN field.

Statement ON SYSOUT specifies selection criteria, depending on the type of output, as follows:

Parent Topic

ON Statement: Decollating Parameter (decollating mission)