How to control DFSMSdss through PARM information in the EXEC statement

The EXEC statement for DFSMSdss can contain PARM information that is used by the program. You can use the following keyword parameters:

ABEND=nnn

nnn is a 3-digit decimal message number (ADRnnnx). If this is specified and this message is to be issued, DFSMSdss performs a user 0001 ABEND dump after issuing the message, the task stops and the return code is set to 8. To get a dump, include a DD statement for SYSABEND, SYSMDUMP, or SYSUDUMP. This keyword is provided for diagnostic purposes only.

AMSGCNT=nnnn

The abend message occurrence count that tells DFSMSdss to end abnormally on the nth occurrence of the message specified in ABEND=nnn. nnnn for AMSGCNT can be a number between 1 and 9999. The default is 1 (first occurrence). This keyword is provided for diagnostic purposes only.

DEBUG=FRMSG

This parameter causes DFSMSdss to issue an informational message during copy or defrag operations for which fast replication methods, such as SnapShot and FlashCopy®, cannot be used. The informational message indicates why DFSMSdss could not use fast replication. This keyword is provided for diagnostic purposes only.

Guidelines:

When you specify this parameter, DFSMSdss interprets it as though you have specified the DEBUG(FRMSG(SUMMARIZED)) keyword.
You can use the DEBUG(FRMSG(MIN | SUM | DTL)) keyword with the COPY and DEFRAG commands. It is used when designating the use of fast replication methods. It is recommended that you convert your DEBUG=FRMSG parameter to this new keyword specification in your JCL jobs.

LINECNT=nnnn

nnnn is a 1-digit to 4-digit number indicating the number of lines to be printed per page for the SYSPRINT data set. The default is 60. Specify LINECNT=9999 to prevent a page ejection.

PAGENO=nnnn

nnnn is a 1-digit to 4-digit number indicating the starting page number to be used for the SYSPRINT data set. The default is 1.

SDUMP=nnn

nnn is a 3-digit decimal message number (ADRnnnx). If this is specified, DFSMSdss requests an SVC dump after issuing the message, and the task continues processing. The SVC dump is directed to a system defined data set (SYS1.DUMPnn) for later analysis. This keyword is provided for diagnostic purposes only.

SIZE=nnnnK

nnnn is a 1-digit to 4-digit number indicating the number of KB (1KB equals 1024 bytes) of main storage to be used by DFSMSdss. This amount must be less than or equal to that specified by the REGION keyword. The default value is the region size.

SMSGCNT=nnnn

The sdump message occurrence count that tells DFSMSdss to request an SVC DUMP on the nth occurrence of the message specified in SDUMP=nnnn. nnnn for SMSGCNT can be a number between 1 and 9999. The default is 1 (first occurrence). This keyword is provided for diagnostic purposes only.

TMPMSGDS=YES|NO

This parameter indicates whether or not a temporary SYSPRINT message data set is to be allocated. When NO, SYSPRINT messages are buffered in an ESA Hiperspace™ and performance is improved. The default is NO.

TRACE=YES

When used during DEFRAG or CONSOLIDATE operation, this prints messages that indicate the relocated extents. This is a diagnostic tool.

TYPRUN=NORUN

For copy, dump, restore, compress, and release operations, only input data set selection is done without actually processing data sets. Printed output for the run indicates the data sets selected. For a defragmentation operation, the initial volume statistics are printed without actually relocating any extents. For a CONVERTV operation, a full report is produced, but no volumes or data sets are actually converted. For CGCREATED operation, only control card syntax checking is done. The task is not processed.

TYPRUN=SCAN

Only control card syntax checking is done. No tasks are processed.

USEEXCP=YES|NO

Specifies whether the access method used by DFSMSdss for DUMP output, RESTORE input and COPYDUMP operations is to be EXCP. If the backup is to or from tape, the default is NO. If the backup is to or from DASD, the default is YES, unless the backup data set is in the extended format. For COPYDUMP and RESTORE operations that specify USEEXCP=YES, if the backup is from a non-label tape or a standard label tape with a block size of zero in its tape header, the dump data set block size must be specified on the input tape's DD in order for EXCP processing to be used. If the block size is not specified, BSAM processing is used instead.

UTILMSG=YES|NO|ERROR

This parameter controls the output of messages from auxiliary programs invoked by DFSMSdss (including ICKDSF, IDCAMS, IEBCOPY, IEBISAM, and IEHMOVE) to the DFSMSdss SYSPRINT output. When YES, informational, warning, and error messages from these auxiliary programs are copied to the DFSMSdss SYSPRINT output. When NO, messages are not copied to the output. When ERROR, messages are copied only if the auxiliary return program returns an error code to DFSMSdss. The default is ERROR.

WORKUNIT=workunit

You can supply an esoteric DASD unit name (for example, SYSDA), a generic DASD unit name (for example, 3380), or a specific DASD address. DFSMSdss passes this unit to dynamic allocation when temporary data sets are allocated. When WORKUNIT is specified by itself, the volumes to be processed by DFSMSdss should not fall within the esoteric group passed as the WORKUNIT name. If the esoteric name applies to the volumes to be processed by DFSMSdss, specify WORKVOL.

WORKVOL=volser

You can supply a volume serial number on which DFSMSdss should allocate temporary data sets. DFSMSdss passes the volume serial number to dynamic allocation. The volume serial number passed as a WORKVOL should not be the same as any volume being processed by DFSMSdss under the current task.

Note:

WORKUNIT, WORKVOL, or both parameters can be specified when invoking DFSMSdss.
When DFSMSdss invokes the IDCAMS utility to copy an ICF user catalog, the export data set is allocated as a permanent data set. The permanent data set cannot be placed on the volume specified by WORKUNIT or WORKVOL.
An esoteric unit name that requests virtual I/O can be used in the WORKUNIT parameter, but when DFSMSdss invokes the IEHMOVE utility during data set copy, the default dynamic allocation unit name is used (SYSALLDA).

XABUFF=ABOVE16|BELOW16

The I/O buffers used by DFSMSdss for COPY, COPYDUMP, DEFRAG, DUMP, PRINT, and RESTORE operations are to be above or below 16 megabytes virtual storage. The default is ABOVE16.

ZBUFF64R=YES|NO

The I/O buffers that DFSMSdss uses for COPY, COPYDUMP, DEFRAG, DUMP, PRINT, and RESTORE operations can be backed by real storage that is anywhere in 64-bit addressing, or below the 2-gigabyte bar. The ZBUFF64R EXEC parameter allows a user to indicate to DFSMSdss where the I/O buffers should be located.

DFSMSdss obtains I/O buffers that are backed by real storage anywhere in 64-bit addressing when you specify EXEC PARM='ZBUFF64R=YES'. The default is ZBUFF64R=YES, which results in all I/O buffers being obtained such that they can be backed above the 2–gigabyte bar.

DFSMSdss determines whether a tape device used in a job supports buffers above the 2-gigabyte bar, and uses buffers above the 2-gigabyte bar when all tape devices in the job support buffers above the 2-gigabyte bar. If any tape device in a job does not support buffers above the 2 gigabyte bar, DFSMSdss uses buffers below the 2-gigabyte bar for the entire job.

Examples of PARM information are:

//  EXEC  PGM=ADRDSSU,
//    PARM='PAGENO=8,LINECNT=57,SIZE=500K,UTILMSG=YES'

//  EXEC  PGM=ADRDSSU,
//    PARM='TYPRUN=SCAN,DEBUG=FRMSG,XABUFF=ABOVE16,UTILMSG=YES'

//  EXEC  PGM=ADRDSSU,
//    PARM='ZBUFF64R=NO,UTILMSG=YES'

Related reading: For additional information about the PARM parameter of an EXEC statement, see the z/OS MVS JCL Reference.

Related reading: For additional information about the ADRUFO parameter list and the ADRUIXIT exit, see the z/OS DFSMS Installation Exits.