CLASS

Class names. The letter of the classes must be specified. A maximum of eight held or non-held classes can be specified (for example, ON CLASS ABCD). Only reports from the specified classes are decollated.

To limit the selection of sysouts from the specified classes, values can be specified for the following subparameters:

• EXTWTR–Name of an external writer to which the reports are written. Only reports of the specified CLASS that are written to the specified EXTWTR are decollated. The EXTWTR name has a maximum of eight characters. Character masking (* for any number of alphanumeric characters and ? for one alphanumeric character) is supported. Character mask $* results in decollation of all outputs with a writer name beginning with $.
• DEST–Name of a printing destination for the reports. Only reports of the specified CLASS with the specified DEST are decollated. The DEST name has a maximum of eight characters.
• FORM–Name of a printing FORM for the reports. Only reports of the specified CLASS for the specified FORM are decollated. The FORM name has a maximum of four characters.

DSN

One or more CDAM selection criteria must be specified for the DSN subparameter. The specification can occupy up to two lines. A maximum of 101 characters can be entered: 44 on the first line, and 67 on the continuation line. For an example of how to format the selection criteria, see "Example 2" in Examples.

In the DSN specification, PGMSTEP=pgmstep and/or PROCSTEP=procstep statements are often used as retrieval parameters. However, CDAM control parameter ALLOCOPT cannot be used in an ON DSN statement.

Note: pgmstep is the step name in the job, and procstep is the step name in the JCL procedure.

If a procedure is not nested, the step that calls another procedure is also PGMSTEP for ON DSN. In such a case, PGMSTEP is the same step as specified in the STEPNAME field on the SDSF screen and PROCSTEP is the same step as specified in the PROCSTEP field on the SDSF screen.

MQ

When an IBM WebSphere MQ message is available in the MQ queue defined for the decollation mission, the ON MQ statement is executed.

The following subparameters, corresponding to parameters in the MQ descriptor, can be used as selection criteria:

• USERID – The name of the user who sent the message.
• ACCT – The token or number of the message, determined by the application that sent the message.
• APPLID – Additional information that the application has added about the user.
• APPLT – Additional information about the kind of application that sent the message. For example: CICS, Unix.
• APPNM – Name of the application that sent the message.
• PRIORITY – Number indicating the priority of the message.
• FORMAT – Format of the message.

Note: The MQSTR value in this field indicates that the report is a text report. A blank or any other value in this field indicates that the report is a binary report.

SYSJCL

The expanded JCL system dataset.

SYSLOG

The job log console messages system dataset.

SYSMSG

The runtime execution messages system dataset.

SYSOUT

Step and/or DD statement selection criteria. The following SYSOUT subparameters can be specified:

• PGMSTEP – A specific program step. If blank, or if the reserved word ANYSTEP is specified, all program steps are selected. Length: 1 through 8 characters.

  Note: PGMSTEP is the step name in the EXEC statement that identifies the program to be executed:

  //pgmstep EXEC PGM=pgmname

• PROCSTEP – A specific procedure step. If blank, or if the reserved word ANYSTEP is specified, all procedure steps are selected. Length: 1 through 8 characters.

  Note: PROCSTEP is the step name in the EXEC statement that invokes the procedure:

  //procstep EXEC procname

• DDNAME – A specific DD name. If blank, all DD names are selected. Length: 1 through 8 characters.
• CLASS – A specific class. If blank, all classes are selected.

TRNCLASS

The same class and selection criteria fields as the CLASS subparameter are displayed, with the addition of CLIQUE, which identifies the Report Clique to be used for report transformation.

Instead of writing the original report to a CDAM file as with the CLASS subparameter, Control-D transforms the selected reports into two formats: Normalized and Row Columnized (text). The normalized report is then written to the CDAM file, and the text format is used for the decollation process.

The transformation process is defined using the Report Clique specified in the CLIQUE subparameter. For more information on Report Cliques, see Report Cliques. For information on preparing reports for transformation, see Decollation of Report Types.

Currently, transformation is supported only for full AFPDS, Xerox LCDS, and Xerox MetaCode reports.

Note: Although transformation using the TRNCLASS subparameter is more efficient than using the TRNDSN subparameter, BMC recommends using the TRNDSN subparameter instead of the TRNCLASS subparameter for transformation. When transforming reports using the TRNCLASS subparameter, the original report is not saved. If there is a transformation failure, such as a missing resource or an incorrectly transformed report, the original report cannot be restored.

TRNDSN

Selection criteria for selecting CDAM files must be defined. This selection criteria is defined in the same way as described for the DSN subparameter, with the addition of the CLIQUE subparameter, which identifies the Report Clique to be used for report transformation.

Using the TRNDSN subparameter, a new CDAM file is created. The report from the original CDAM file that is defined by the selection criteria is transformed into two formats: Normalized and Row Columnized (text). The normalized report is saved in the new CDAM, and the text format is used for the decollation process.

The transformation process is defined using the Report Clique specified in the CLIQUE subparameter. For more information on Report Cliques, see Report Cliques. For information on preparing reports for transformation, see Decollation of Report Types.

Note: The original CDAM should be backed up in case the normalization process fails. The normalized CDAM should be processed for viewing, printing, and migration.