Descriptions of Analyzer JCL statements

//CMFRPTS EXEC

//CMFSAVE DD

(optional) specifies the destination of SMF records determined to be bad either by logic within an Analyzer module or because of an ABEND in an Analyzer Poster module

This DD statement is normally allocated as a physical sequential file with the following DCB attributes:

RECFM=VBS, DSORG=PS, LRECL=32760, BLKSIZE=8192

//STEPLIB DD

required if hilevel. BBLINK is not in a LINKLIST data set; specifies a partitioned data set that contains the Analyzer load modules

//DMSSMAIN DD

(optional) when specified, defines a BDAM work file

Allocate a minimum of 5 cylinders, and add 1 cylinder for every 10,000 records of input from EXTDATA. Secondary extents are ignored. The Analyzer issues messages that specify the number of spaces used.

For more information about MEMOBJ JCL Parameter, see Descriptions-of-Analyzer-JCL-PARM-parameters

For more information about DMSS Control Statement , see General-control-statements.

If omitted or specified as DD DUMMY, a Memory Object is used as the work file.

//EXTDATA DD

defines the SMF or CMF data set containing Extractor records from which reports are to be produced

If you want to use data in the XDS data buffer, this statement must be omitted. If you want to use data from an Extractor output data set, this statement is required.

SMF data sets residing on DASD are VSAM data sets and cannot be concatenated.

Records for the same interval must remain in the original order in which they were written. If, for some reason, the records become disordered, their original order can be restored by specifying the following statement, which will reorder the records by SYSID, Date, and Time:

This statement might not work if the records have been sorted without the EQUALS parameter or if record types have been separated and are now being merged. If this SORT statement fails to reorder the records, you must return to the original data if it is available.

//SYSIN DD

defines input for the Analyzer control statements

//CMXREC DD

(optional) defines a sequential output data set where records accepted for analysis are to be written

If you need this statement defined, you must remove the comment (*) character from the CMFJANL member.

//RPTCONTS DD

(optional) defines a print file for the Report Table of Contents

If you use this statement, it should be inserted in front of the //CMFLOG DD and //SYSPRINT DD statements.

//CMFLOG DD

defines an optional print file to direct the Collection Phase Log reports to an alternate data set

These reports are automatically produced by the Analyzer, unless the SHIFT statement is defined with RPTS=INTERVAL or RPTS=DAILY. If the SHIFT statement is defined as described here, the Collection Phase Log reports are automatically suppressed.

If a //CMFLOG DD statement is not defined, the reports are written to a CMFLOG print file dynamically allocated by the system.

By specifying the //CMFLOG DD statement, you can direct the Collection Phase Log reports to a different print file. You can define this print file to a valid data set name, or as DUMMY or NULLFILE.

It can be useful to define a data set on DASD as the //CMFLOG DD print file destination, in case of an Analyzer error. If problems occur while using NLOG, rerun the Analyzer without NLOG defined to obtain the Collection Phase Log. The Extractor characteristics are sometimes helpful in diagnosing problems. Each time the Analyzer is run, this data set is overwritten.

If used, the //CMFLOG DD statement should be inserted after the //RPTCONTS DD statement and before the //SYSPRINT DD statement. In addition, a subset of the Collection Phase Log reports can be suppressed by defining PARM=’NLOG’ on the EXEC statement.

//SYSPRINT DD

defines a print file or an Analyzer output data set for the requested CMF MONITOR reports and graphs

If you define an output data set, it must be allocated with the following characteristics:

The //SYSPRINT DD statement must be inserted after the optional //RPTCONTS DD and //CMFLOG DD statements.

//CMFPRINT DD

(optional) defines an Analyzer output data set for the requested CMF MONITOR reports and graphs

This statement can be used in conjunction with the SYSPRINT DD statement, so that report output can be directed to both SYSOUT and an output data set.

The output data set must be allocated with the following characteristics:

The //CMFPRINT DD statement, if used, should be inserted after the optional //RPTCONTS DD and //CMFLOG DD statements.

//CMXTRACE DD

(optional) defines a print file for the CMF MONITOR Trace Report output

//SNAPS DD

(optional) defines a print file for snap dumps issued by the Analyzer

//SNAPVBS DD

(optional) defines a print file for snap dumps issued by the Analyzer

//SYSUDUMP DD

provides for a dump if a program fails

//CMFSTAGE DD

//CMFSTAGO DD

Obsolete; will be ignored if specified

(optional, unless dynamic allocation fails) defines a temporary staging data set when RPTS=INTERVAL or RPTS=DAILY is defined on the SHIFT general control statement.

//CMFSTAGE DD

//CMFSTAGO DD

(continued)

Obsolete; will be ignored if specified

Occasionally, you might experience problems while trying to allocate the staging data sets on UNITS, either temporarily or dynamically, with error messages such as IEC141I RC013-34. These messages are IEC data set open/close DFP messages and can be dependent on:

• how the units are managed (for example, are the volumes SMS managed?)
• are they mounted PRIVATE or STORAGE?
• other vendor software hooks relating to Open/Close processing
• the DFP maintenance release level in place, and so on

When these problems happen, the best solution is to preallocate the staging data set with the vendor software hooks method (third bullet), and point CMFSTAGE and CMFSTAGO to it in the Analyzer JCL.

// CMFTDUMP DD

allows the Analyzer to take machine readable dumps when it encounters certain errors.

When specified, the data set is the same format as a SYSMDUMP data set (RECFM=FBS,LRECL=4160). The TDUMP parameter in the JCL PARM field can be specified to create TDUMP data sets dynamically.