DLMAINT JCL - syncsort_scc_monitor

Sample JCL The following example shows the basic JCL required to run DLMAINT. Additional DD statements may be required, depending upon the function being performed.


        //JOBNAME JOB ...
        //MAINT EXEC PGM=DLMAINT
        //STEPLIB DD DISP=SHR,DSN=DTS.R71.LOADLIB
        //SYSPRINT DD SYSOUT=*
        //SYSIN DD *
        dlmaint control
        statements
        /*

Figure 7-1. DLMAINT sample JCL

DLMAINT JCL statement definitions

This section describes the execution JCL used by the DLimit maintenance program. The following definitions describe the job control statements necessary for using DLMAINT.

Statement		Use
`JOB`		Job statement for the DLMAINT job.
`EXEC`		Specifies the program name for the DLimit Maintenance program: `PGM=DLMAINT`
`STEPLIB`	`DD`	This is a required file if DLMAINT is not in the system linklist concatenation. Defines the load library containing the DLMAINT program; by default, `DTS.R71.LOADLIB`. Note: All libraries allocated to `STEPLIB` must be authorized.
`SYSPRINT`	`DD`	Defines a sequential output data set or SYSOUT file used for listing actions taken by the DLMAINT program.
`SYSIN`	`DD`	The `SYSIN` dataset contains the DLMAINT statements to be executed. The DCB information is: `DCB=(LRECL=80,RECFM=FB)`.

Figure 7-2. DLMAINT JCL statement definitions

Additional JCL statements may be required for some DLMAINT functions. These additional statements are described below:

`SYSUTx`	`DD`	The `SYSUT1` and `SYSUT2` DD statements are required during execution of a `RESYNC` function. These datasets are used to hold intermediate information during RESYNC processing. They should be sequential DASD datasets of sufficient size to hold one DLimit database record for each dataset processed during RESYNC. Specifying `SPACE=(CYL,(5,1),RLSE)` is usually sufficient. These datasets may be temporary or permanent. The use of permanent datasets allows RESYNC to be restarted after a failure if necessary. Note: SYSUT1 is required for a `REORG`.
`Bkup/Rest`	`DD`	During BACKUP or RESTORE of a DLimit database, a DD statement is required which references the sequential copy of the database which is the target of the backup or the source of the restore. The DDNAME for the sequential file is specified by the `TODD` or `FROMDD` operands of the BACKUP or RESTORE statements, respectively. There is no default DDNAME.
`PARMLIB`	`DD`	If an SCC-DLimit rule set other than the ACTIVE rule set is to be used during DLMAINT operations, the sequential file which contains the rules may be specified on the `SET RULES` statement. The DDNAME specified on the DDNAME operand of the `SET RULES` statement must be `PARMLIB`.
`RRDSdb`	`DD`	Specifies the location of the BDAM file used as the database when specified by the `SET DATABASE` statement. The `BDAM(ddname)` operand of `SET DATABASE` indicates the DDNAME of the BDAM file. There is no default DDNAME.
`VSAMdb`	`DD`	If an SCC-DLimit database other than the ACTIVE database is to be used during DLMAINT operations, the location of the ICF VSAM key-sequenced cluster used as the database may be specified by the `SET DATABASE` statement. The `VSAM(ddname)` operand of `SET DATABASE` indicates the DDNAME of the KSDS cluster. There is no default DDNAME.
`MCDS`	`DD`	If the DFSMShsm MCDS is to be scanned to obtain space information about migrated datasets, the DDNAME operand of the DLMAINT`HSM` statement is used to specify the DDNAME to which the MCDS is allocated. The default DDNAME is `MCDS`.
`SORTWKxx`	`DD`	During RESYNC processing, work space is required for the system sort. `SORTWK` files should be temporary datasets at least as large as the `SYSUT1` or `SYSUT2` files allocated for RESYNC. Depending upon the system sort defaults, SORTWK files may be automatically provided by the sort.
`SYSOUT`	`DD`	May be required for SORT messages during RESYNC processing. This file should be allocated to SYSOUT.

DLMAINT control statements

DLMAINT is run as a batch job, with the control statements supplied in the SYSIN stream.

Comments

DLMAINT treats any statement having an asterisk in column 1 as a comment statement. Comment statements are echoed to the SYSPRINT dataset but are otherwise ignored.

Comments cannot be continued onto another statement, but multiple comment statements may be specified.

Continuing DLMAINT control statements: DLMAINT control statements may be continued from one line to another by placing a dash (-) as the last character on the line following a parameter or subparameter. Statements may be continued onto as many lines as necessary.

DLMAINTControl statement filtering

The INCLUDE and EXCLUDE control statements allow selection criteria for DLMAINT processing to be partially qualified. The following filtering characters may be used:

asterisk (*) — the asterisk can be used as a 'wildcard' to indicate any number of arbitrary characters. An asterisk may be placed at the beginning of a string, at the end of a string, or embedded in the middle of a string. For example, the filter criteria ABC*DEF will match any string beginning with the characters ABC and ending with the characters DEF, with any number of characters (zero or more) in between. The filter criteria *XYZ will match any string which ends with the characters XYZ.
question mark (?) — the question mark can be used as a 'wildcard' to indicate any single character. For example, the filter criteria AB?DEF will match any string of exactly six characters, beginning with the characters AB and ending with the characters DEF, and with any character in the third position.
The asterisk and question mark characters can be used in combination to specify any desired filter criteria. For example, the filter criteria *PAY??JAN*98 can be used to select strings containing the characters PAY, preceded by any number of characters and followed by any two characters, then followed by the characters JAN, and ending with the characters 98.

DLMAINT syntax quick reference

The chart below provides an overview of the DLMAINT control statement syntax. For further details on each statement, refer to the section which describes the statement.


BACKUP
  TODD(ddname) LIST

CONVERTDB
  INDD(ddname) OUTDD(ddname) DEBUG
  DETAIL COPYMODEL

ERASE
  ALL/EMPTY LIST

EXCLUDE
  VOLUME(name1,name2,...,namen)
  DSNAME(name1,name2,...,namen)
  ACCOUNT(name1,name2,...,namen)

HSM
  DDNAME(ddname) DEFVOLSER(volser)
  LEVEL1/NOLEVEL1 LEVEL2/NOLEVEL2 TAPE/NOTAPE DISK/NODISK

INCLUDE
  VOLUME(name1,name2,...,namen)
  DSNAME(name1,name2,...,namen)
  ACCOUNT(name1,name2,...,namen)

REORG
  REORG FROMDD(indd) TODD(outdd) LIST ACTIVE
  SIZE(recs)

REPORT
  ACCOUNT(DETAIL) DSNAME(SORT(DSNAME/VOLSER/ACCOUNT/SPACE))

RESET
  CLEAR(CUR/HWM/ALL) LIST

RESTORE
  FROMDD(ddname) ALL/CONTROL LIST

RESYNC
  DETAIL

SCAN
  UPDATE LIST

SET
  AUDIT(VOLUME/NOVOLUME DATASET/NODATASET ACCOUNT/NOACCOUNT) CLEARINCLUDE
  DATABASE(SYSTEM
    VSAM(ddname FORMAT/NOFORMAT))
    RACF(class userid group)
    BDAM(ddname FORMAT/NOFORMAT)
  DEBUG(CSRLOG(num) MODTRACE)
  ENVIRONMENT(environmentname,sub-environmentname) MODE(SIMULATE/NOSIMULATE)
  OPTION(WARN/NOWARN)
  RULES(NAME(rulename/prdname PRODUCT) DDNAME(PARMLIB) LIST/NOLIST TRACE/NOTRACE TEST/NOTEST MESSAGE/NOMESSAGE)
  VTOC(EXCP/CVAF/SMS(SORT VVDS))

SHOW
  LIST

VOLUME
  LIST LOCK/UNLOCK RESERVE/RELEASE

Figure 7-3. DLMAINT syntax quick reference

DLMAINT JCL - syncsort_scc_monitor - Latest

Syncsort™ Storage Management SCC DLimit Guide

DLMAINT syntax quick reference