SET - syncsort_scc_monitor - Latest

Syncsort™ Storage Management SCC DLimit Guide
Product type
Software
Portfolio
Integrate
Product family
Syncsort™ software
Product
Syncsort™ Storage Management > Syncsort™ SCC Monitor
Version
Latest
ft:locale
en-US
Product name
Syncsort Storage Management
ft:title
Syncsort™ Storage Management SCC DLimit Guide
Copyright
2021
First publish date
1991
ft:lastEdition
2025-12-05
ft:lastPublication
2025-12-05T05:06:29.654000

Set values that affect DLMAINT processing.

The SET statement is used to specify values that affect subsequent DLMAINT processing, including the name of the SCC-DLimit database and rule set to be used, the environment names, whether the program is to run in simulation mode, etc.

SET AUDIT( options )

CLEARINCLUDE

DATABASE( type_database( options ) )

DEBUG( options)

ENVIRONMENT( env-name, subenv-name )

MODE( options )

OPTION( options )

RULES( NAME( name PRODUCT )
DDNAME( ddname ) options )

VTOC( options )

AUDIT

Function: This is an optional parameter. The SET AUDIT parameters are used to specify the type of output that should be produced during processing of the DLMAINT statements.

The following AUDIT parameters are available:

  • VOLUME — Indicates that a PROCESSING VOLSER message should be displayed in SYSPRINT prior to the start of processing for each DASD volume.
  • DSNAME — Indicates that the name of each dataset to be processed during DLMAINT operations should be displayed in SYSPRINT prior to the start of processing for the dataset.
  • ACCOUNT — Indicates that the accounts that are being processed should be displayed during SCAN or other processing.
Note: This parameter provides a way to obtain more detailed information about the progress of DLMAINT processing.

Default: DSNAME, ACCOUNT

Format: AUDIT(VOLUME DSNAME)

CLEARINCLUDE

Function: This is an optional parameter. This statement nullifies any previous INCLUDE criteria. Note that if no additional INCLUDE statements fol- low SET CLEARINCLUDE, then the next statement to be executed will use the default selection criteria, that is, all accounts or datasets are selected.

Default: None

Format: SET CLEARINCLUDE

DATABASE( type )

Function: This is an optional parameter. The SET DATABASE statement indi- cates what SCC-DLimit database is to be processed during the DLMAINT run. The default, if no SET DATABASE statement is pres- ent, is to use the active SCC-DLimit database.

SYSTEM: Indicates that the active SCC-DLimit database is to be used.

VSAM( ddname option ): Indicates that the VSAM cluster allocated to the specified DD name is to be used as the SCC-DLimit database.

RACF( options ): Indicates that the RACF database is to be used as the SCC-DLimit database.

BDAM( ddname option ): Indicates that the BDAM file allocated to the specified DD name is to be used as the SCC-DLimit database.

Default: DATABASE(SYSTEM)

Format: DATABASE( SYSTEM | VSAM( ddname ) | BDAM( ddname) | RACF(options) )

DATABASE( VSAM ( ddname options ) )

Function: This is an optional parameter. The SET DATABASE statement indi- cates what SCC-DLimit database is to be processed during the DLMAINT run and the options that pertain to the database.

VSAM( ddname option ): Indicates that the VSAM cluster allocated to the specified DD name is to be used as the SCC-DLimit database. Valid options include FORMAT and NOFORMAT. FORMAT indi- cates that the database is new and must be formatted with the $CON- TROL record and database records initialized.

Default: NOFORMAT

Format: DATABASE( VSAM( ddname FORMAT ) )

DATABASE( RACF (options ) )

Function: This is an optional parameter. The SET DATABASE statement indi- cates what SCC-DLimit database is to be processed during the DLMAINT run and the options that pertain to the database.

RACF( options ): Indicates that the RACF database is to be used as the SCC-DLimit database. Valid options include classname, userid, group.

Default: None

Format: DATABASE( RACF( classname userid group ) )

DATABASE( BDAM ( ddname option ) )

Function: This is an optional parameter. The SET DATABASE statement indi- cates what SCC-DLimit database is to be processed during the DLMAINT run and the options that pertain to the database.

BDAM( ddname option ): Indicates that the BDAM file allocated to the specified DD name is to be used as the SCC-DLimit database. Valid options include FORMAT and NOFORMAT. FORMAT indicates that the database is new and must be formatted with the $CONTROL record and database records initialized.

Default: NOFORMAT

Format: DATABASE( BDAM( ddname FORMAT ) )

DEBUG

Function: This is an optional parameter. This statement is used to enable various diagnostics for the DLMAINT utility. DEBUG options can activate var- ious levels of CSR logging and module tracing.

If CSRLOG( num ) has been specified, log messages are created for the OS interface requests made by DLimit. These messages are written to the SYSPRINT DD statement. The numeric value represented by num specifies the level and type of logging.

If MODTRACE has been specified, trace messages are created to aid in debugging DLimit. The messages show the program flow through DLimit modules, and the messages are written via the WTO SVC to the job log.

Both the CSRLOG and MODTRACE options should only be used when requested by a technical support representative.

Default: None

Format: SET DEBUG(CSRLOG(8) MODTRACE))

Function: This is an optional parameter. The SET ENVIRONMENT parameters are used to specify the SCC-DLimit environment name to be used when the SCC-DLimit rules are invoked. The values specified are placed in the &ENVIRON and &ENVIRONS variables. These variables can be used in the SCC-DLimit rules to assign an account to a dataset. The default values are &ENVIRON = ‘ALLOCATE’ and &ENVIRONS = ‘DADSM_PRE’. If the active SCC-DLimit database and active SCC- DLimit rules are being used during RESYNC processing, it may be desirable to set &ENVIRON to ‘ALLOCATE’ and &ENVIRONS to ‘DADSM_PRE’. These are the values used when a dataset is created by system allocation routines

Valid environments are: ALLOCATE, EXTEND, SCRATCH, RELEASE, RENAME, PARTREL, VSAMEXT

Valid sub-environments are: DADSM_PRE, DADSM_POST

Default: None

Format: ENVIRONMENT( envir-name, sub-env-name )

MODE

Function: This is an optional parameter. The SET MODE statement specifies whether the BACKUP, RESTORE, RESET, RESYNC, or ERASE pro- cessing specified in subsequent statements is actually to be performed or only to be simulated. If SET MODE(SIMULATE) is specified, all sub- sequent operations are simulated and no changes are actually made to the SCC-DLimit database. If NOSIMULATE, which is the default, is specified, then any changes which result from subsequent processing are immediately applied to the database.

Default: NOSIMULATE

Format: MODE(SIMULATE)

OPTION

Function: This is an optional parameter. The SET OPTION statement specifies whether warning messages will be issued when a request for space causes the limit for an account to be exceeded when a RESYNC is per- formed. The values for option are WARN or NOWARN.

Default: NOWARN

Format: OPTION(WARN)

RULES(NAME( prd PRODUCT ))

Function: This is an optional parameter. The SET RULES statement specifies the SCC-DLimit Rule Set to be used during DLMAINT processing. The Rule Set provides the policies for assigning an account name to each dataset to be processed. The default is to use the rules currently active for the product (DSL PRODUCT). Alternatively, the name of a member contained in the DIF PARMLIB dataset may be used.

PRODUCT: the prd field contains the DIF product name (DSL) and specifies that the rules currently active for the SCC-DLimit system are to be used. These are the rules which were loaded when the most recent START or REFRESH command was issued to the DIF started task.

Default: None

Format: NAME(DSL PRODUCT)

RULES(NAME(name) DDNAME(PARMLIB))

Function:

This is an optional parameter. The SET RULES statement specifies the SCC-DLimit Rule Set to be used during DLMAINT processing. The Rule Set provides the policies for assigning an account name to each dataset to be processed. The default is to use the rules currently active for the product (DSL PRODUCT). Alternatively, the name of a member contained in the DIF PARMLIB dataset may be used.

NAME: Specifies that the member name of the rules to be used are a member in the //PARMLIB dataset allocated to the DLMAINT job. This dataset may be the same one as the PARMLIB DD in the DIF started task.

DDNAME: Specifies the name of a DD statement allocated to the DLMAINT job, which contains the rules that are to be used. The DDname must be PARMLIB.

Default: None

Format: NAME( name ) DDNAME(PARMLIB))

RULES( ... options )

Function:

This is an optional parameter. The SET RULES statement specifies the SCC-DLimit Rule Set to be used during DLMAINT processing. The Rule Set provides the policies for assigning an account name to each dataset to be processed.

LIST | NOLIST: Specifies whether the contents of the rule set are to be displayed in SYSPRINT immediately following the SET RULES state- ment. The default is not to display the content of the rule set.

TRACE | NOTRACE: Indicates whether SCC-DLimit rule tracing is to be performed. This is equivalent to specifying the //DSLTRACE DD DUMMY statement in the JCL. If TRACE is specified, messages describing the processing of each rule statement are written to SYS- PRINT as the rules are encountered.

TEST | NOTEST: Indicates whether rules which have a TEST operand on the DEFRULE statement are to be honored. This is equivalent to specifying //DSLTEST DD DUMMY in the JCL. If TEST is specified, SCC-DLimit rules which do specify TEST are included in processing and not ignored.

MESSAGE | NOMESSAGE: Indicates whether messages issued from the rules are to be written to the SYSPRINT job output.

Default: NOLIST, NOTRACE, NOTEST, NOMESSAGE

Format:

LIST or NOLIST

TRACE or NOTRACE

TEST or NOTEST

MESSAGE or NOMESSAGE

VTOC( options )

Function: This is an optional parameter. SET VTOC statement specifies the access method used to read the VTOC. DLimit can perform EXCP pro- cessing, use the CVAF interface provided by the operating system, or use the SMS Fast VTOC interface.

The SMS Fast VTOC interface is used by default. Volumes do not have to be SMS managed to use the SMS Fast VTOC interface, and the VTOC access is actually much faster than the EXCP method. This inter- face also obtains additional information that is not available from the VTOC. Note: For non-SMS managed systems, the VTOC read routine will fall back to EXCP processing.

If SMS has been requested, the VVDS subparameter can also be speci- fied: VTOC(SMS(VVDS)). In this case, the SMS Fast VTOC interface will sequentially process the VVDS on the volume and then process any VTOC entries that were not encountered on the VVDS read loop.

Default: VTOC( SMS (VVDS) )

Format: EXCP, CVAF, SMS or SMS(VVDS)