Optional keywords for IGDSMSxx

The following keywords are optional; defaults, if any, are noted.

ACSDEFAULTS(YES | NO)

Specifies whether SMS initializes the following automatic class selection (ACS) routine variables from an additional call to RACF®:

• &APPLIC
• &DEF_DATACLAS
• &DEF_MGMTCLAS
• &DEF_STORCLAS

Specify YES to request that RACF or a functional equivalent give SMS the values. Because SMS must set these variables every time a data set is created, specifying NO reduces the overhead of using RACF. If you specify NO, these variables will have no values associated with them.

The ACSDEFAULTS keyword is not applicable for OAM.

Default: NO

AKP({nnn[,nnn[...,nnn]] |1000})

Specifies the activity keypoint trigger value, which is the number of logging operations between keypoints. Up to 32 activity keypoint values can be specified. AKP values must be specified in the same order as DFSMStvs instance names. Specify a value from 200 to 65535.

You can allow some values to default while specifying others. For example, in AKP(800,,3000), the value for the DFSMStvs instance in the second position defaults to 1000, and sets the values for the first and third DFSMStvs instances to 800 and 3000 respectively.

If AKP is specified with only the TVSNAME parameter without an identifier, AKP applies to the system on which the PARMLIB member is being read. TVSNAME must be specified with the AKP parameter.

Activity keypointing is the process of accounting for all the log records in the undo and shunt logs that are involved in active units of recovery. Activity keypointing enables DFSMStvs to delete records that are no longer involved in active units of recovery. It also enables DFSMStvs to update the undo log to optimize its restart performance related to reading the log stream.

Default: 1000

ASID(asid|*[(TRACE|T|VOLSELMSG|V)[,asid|*(TRACE|T|VOLSELMSG|V)]])

Specifies whether SMS is to limit tracing (TRACE(ON)) or issue volume selection messages (VOLSELMSG(ON)) to a specific address space (asid) or all address spaces *.

asid|*

Limit tracing and volume selection analysis messages for a certain address space, or all address spaces (*). You can enter up to 4 digits for the ASID keyword. If you leave off the leading zeros, they are inserted.

[(TRACE|T|VOLSELMSG|V)[,asid|*(TRACE|T|VOLSELMSG|V)]]

These are optional sub-parameters. TRACE|T or VOLSELMSG|V associated with the first sub-parameter specifies whether the required value, asid or *, specified in the first sub-parameter applies to TRACE or VOLSELMSG facility. The second sub-parameter is optional and can be used to specify another value and facility after the first sub-parameter is specified. When none of these optional sub-parameters are specified, the value specified in the first sub-parameter applies to both TRACE and VOLSELMSG. For example, if you want to have ASID 0010 for the SMS TRACE facility, and ASID 0020 for the VOLSELMSG facility, you could code: ASID(10(TRACE),20(VOLSELMSG)).

Default: *

BLOCKTOKENSIZE(REQUIRE|NOREQUIRE)

Requires every open for a large format data set to use BLOCKTOKENSIZE=LARGE on the DCBE macro, indicating that the application has made needed changes to support the data sets. The exception to this is if the data set contains no more than 65535 tracks on each volume and is open for input using EXCP, BSAM or QSAM, or for update using BSAM or QSAM.

In z/OS® V1R8, IBM® changed the default from BLOCKTOKENSIZE(REQUIRE) to (NOREQUIRE). If you want BLOCKTOKENSIZE(REQUIRE), then you must explicitly specify it.

Default: NOREQUIRE

NOREQUIRE

Allows applications to access large format data sets under more conditions without having to specify BLOCKTOKENSIZE=LARGE on the DCBE macro.

When NOREQUIRE is in effect, programs that use the following access methods can open large format data sets without specifying BLOCKTOKENSIZE=LARGE on the DCBE macro:

• QSAM or BSAM without the NOTE or POINT macros.
• BSAM with the NOTE or POINT macros (MACRF=xP) only if the data set has 65535 or fewer tracks on the volume and the OPEN option is INPUT or UPDAT.
• EXCP (MACRF=E) and only when the data set has 65535 or fewer tracks on the volume and the OPEN option is INPUT.

BREAKPOINTVALUE (0-65520)

Specifies the disk space request (primary or secondary), expressed in the number of cylinders (0-65520), where the system should prefer the cylinder-managed space (CMS) on an extended address volume (EAV).

BREAKPOINTVALUE is applicable only to data sets that are eligible for extended addressing space (EAS). Data sets that are not EAS-eligible must reside in the track-managed region of a volume.

When a disk space request is equal to or greater than the value of BREAKPOINTVALUE , the system uses the cylinder-managed space for that extent. If not enough CMS is available, the system uses track-managed space (TMS) or both CMS and TMS. If the requested disk space is less than the BREAKPOINTVALUE, the system uses TMS. If not enough TMS is available, the system uses CMS or both of TMS and CMS.

BREAKPOINTVALUE is an optional field. If it is not specified at the storage group level, the system uses the default value that is specified in the IGDSMSxx member of SYS1.PARMLIB. If BREAKPOINTVALUE is not specified, a value of 10 cylinders is used instead.

CACHETIME({nnnnn}) {3600 }

Specifies the number of seconds between recording SMF records for device cache use. The CACHETIME parameter applies only to the volumes behind an IBM 3990 Storage Control with cache unit. You can specify a value from 1 to 86399 (23 hours, 59 minutes, 59 seconds), and the default is 3600 (one hour). For information about the control unit cache summary recorded in SMF record type 42, see z/OS MVS System Management Facilities (SMF) .

Default: 3600

CA_RECLAIM(NONE|{DATACLAS|DATACLASS})

Specifies whether or not to use CA reclaim for KSDSs according to the CA Reclaim attribute in their data classes.

• NONE indicates that none of the KSDSs will be using CA reclaim, regardless of the data class specification. The default is NONE. If CA_RECLAIM is not specified in SYS1.PARMLIB, the CA_RECLAIM(NONE) default will be in effect, which means the default is CA reclaim disabled.
• DATACLAS|DATACLASS indicates that the SMS-managed KSDSs and non-SMS-managed KSDSs will go by the data class specification of CA Reclaim=Y|N at define time or subsequent ALTER setting. Only the resultant catalog setting of CA Reclaim=Y will do CA reclaim; CA Reclaim=N will not do CA reclaim. It is the way to specify some KSDSs not to use CA reclaim.

Default: NONE

CF_TIME({nnnnn}) {3600}

Specifies the interval (in seconds) for recording SMF record 42 (subtypes 15, 16, 17, 18) for the SMSVSAM address space's use of the coupling facility.

If you record these subtypes, you can use CF_TIME to synchronize SMF type 42 data with SMF and RMF™ data intervals.

Specify a value from 1 to 86399 (23 hours, 59 minutes, 59 seconds). The default is 3600 (one hour).

The SMF_TIME keyword, if set to YES, overrides the CF_TIME keyword.

In a sysplex, the first system that is initialized with an IGDSMSxx member having a valid CF_TIME specification determines the CF_TIME value for the other systems in the sysplex. You can change this value through the SETSMS or SET SMS commands.

Default: 3600

CICSVR_INIT(YES|NO)

This parameter indicates whether the CICSVR server address space should be started during an IPL:

• YES indicates that the CICSVR server address space should be started at system initialization.
• NO indicates that the CICSVR start should be deferred. If you specify CICSVR_INIT(NO) you will have to issue a SETSMS CICSVR_INIT(YES) command before you can activate the CICSVR server.

Note: Every system in a sysplex must have an IGDSMSxx setup for the CICSVR server address space.

Default: NO

CICSVR_BACKOUT_CONTROL(cicsvr_backout_control_string)

Specifies the CICSVR batch backout control string that is used to control CICSVR batch backout. The cicsvr_backout_control_string is up to 17 characters long. The valid characters are alphanumeric (A-Z, 0-9) and national ($, @, #) characters, blanks, and comma.

Default: a blank character string

CICSVR_DSNAME_PREFIX(DWW|dsname prefix)

Defines a prefix for all CICSVR required data sets. This prefix is used for the data sets that must be pre-allocated before you can start the CICSVR server address space (for example, data sets that are allocated to the DD name, DWWMSG).

Note: CICSVR_DSNAME_PREFIX is required if you specify CICSVR_INIT(YES). This defines a prefix for all CICSVR—required data sets excluding RCDS data sets, DWWCON1, DWWCON2, and DWWCON3.

Default: DWW

CICSVR_GENERAL_CONTROL(cicsvr_general_control_string)

Specifies the CICSVR general control string that is used to general control CICSVR. For example, CICSVR general control string and service functions can be used to invoke a CICSVR scavenger or to display the current setting of all CICSVR control strings.

The cicsvr_general_control_string is up to 17 characters long. The valid characters are alphanumeric (A-Z, 0–9) and national ($, @, And #) characters, blanks and comma.

Default: a blank string that is interpreted as SUBMIT NONE

CICSVR_GRPNAME_SUFFIX(cicsvr_grpname_suffix)

Defines the CICSVR XCF group name suffix that the CICSVR server address space will use to create a unique XCF group name for the sysplex and connect to the XCF group. All the systems that share the same suffix and are active will belong to the same CICSVR XCF group. The cicsvr_grpname_suffix is up to four characters long. The valid characters are alphanumeric (A-Z, 0–9) and national ($, @, And #) characters.

Default: PROD

CICSVR_RCDS_PREFIX(cicsvr_rcds_prefix)

Defines a prefix of the CICSVR Recovery Control Data set (RCDS) name that the CICSVR server address space will use to allocate the RCDS to the CICSVR server. The cicsvr_rcds_prefix is up to 17 characters long. It follows the syntax rules for data set names. The prefix can contain up to two qualifiers separated by a period.

Default: DWW

CICSVR_UNDOLOG_CONTROL(cicsvr_undolog_control_string)

Specifies the CICSVR UNDO logging control string. The cicsvr_undolog_control_string is up to 17 characters long. The valid characters are alphanumeric (A-Z, 0–9) and national ($, @, And #) characters, blanks and comma.

Default: a blank string that is interpreted as ENABLE CONT

CICSVR_UNDOLOG_PREFIX(cicsvr_undolog_prefix)

Defines a CICSVR UNDO log name prefix that the CICSVR server address space will use to determine the log stream name that should be written to by CICSVR UNDO logging. The cicsvr_undolog_prefix is up to eight characters long. It follows the syntax rules for data set names.

Default: DWW

CICSVR_ZZVALUE_PARM(zzvalue_parm_string)

Specifies the ZZVALUE parameter string that is used to control CICSVR debugging and diagnostics. The zzvalue_parm_string must be up to 17 characters long, padded on the right with blanks if necessary. The valid characters are alphanumeric (A-Z, 0–9), national ($, @, And #) characters, blank, and comma.

Default: a blank characters string

COMPRESS({TAILORED|GENERIC|ZEDC_R|ZEDC_P})

Specifies the type of compression to be used for the data set.

TAILORED

Specifies that the data set is eligible for compression specifically tailored to the data set. A tailored dictionary is built, using the initial data written to the data set, and imbedded into the data set. The dictionary is issued to compress or expand data written to or read from the data set. This type of compression applies only to sequential data sets, not to VSAM KSDSs.

To convert an existing DBB-based compressed data set to use tailored compressions, you must set the COMPRESS parameter to TAILORED and copy the generic DBB-based data set to a new data set that meets compression requirements.

GENERIC

Specifies that the data set be compressed using generic Dictionary Building Block (DBB) compression. The dictionary is derived from a defined set of compression algorithms in data set SYS1.DBBLIB.

ZEDC_R

Specifies that the data set be compressed using zEnterprise® data compression (zEDC). No separate dictionary is created, as zEDC compression hides the dictionary in the data stream. A new dictionary starts in each compression unit. The system can decompress the segment as is.

With this option (as opposed to ZEDC_P), the system will fail the allocation request if the zEDC function is not supported by the system, or if the minimum allocation amount requirement is not met.

ZEDC_P

Specifies that the data set be compressed using zEDC compression, as with the ZEDC_R option above. But here, the system will not fail the allocation request, but rather create either a tailored compressed data set if the zEDC function is not supported by the system, or create a non-compressed extended format data set if the minimum allocation amount requirement is not met.

Note:

1. Use tailored compression only when all systems in the SMS complex have been converted to DFSMS/MVS 1.4 or later, and when there is no need to revert to a prior release level for local recovery or remote recovery with Aggregate Backup and Recovery Support (ABARS). The date of general availability for DFSMS/MVS 1.4 was in 1997.
2. To convert an existing DBB-based (generic) compressed data set to use tailored compression, or to convert from either generic or tailored to zEDC compression, first set the COMPRESS parameter to TAILORED, ZEDC_R, or ZEDC_P in the IGDSMSxx parmlib member. Use IEBGENER, ICEGENER, REPRO, or any QSAM or BSAM application to copy the data set to a new data set that meets compression requirements.
3. Note that the zEDC feature must be installed on all systems before using zEDC compression. For more information on zEDC compression, see z/OS MVS Programming: Callable Services for High-Level Languages.

Default: GENERIC

DB2SSID(ssid)

Specifies the name of the DB2® subsystem which is used by Object Access Method (OAM) for object storage. ssid can be from one to four characters. There is no default.

If your installation does not use OAM for object storage, do not specify this parameter.

DEADLOCK_DETECTION(nnnn|15,kkkk|4)

This keyword specifies the intervals for local and global deadlock detection.

nnnn specifies the local system's deadlock detection interval (in seconds). Specify nnnn as a one to four digit numeric value in the range 1-9999.

kkkk specifies the number of local deadlock cycles that must expire before the sysplex performs global deadlock detection. Specify kkkk as a one to four digit numeric value in the range 1-9999.

In a sysplex, the first system that is initialized with an IGDSMSxx member having a valid DEADLOCK_DETECTION specification will determine the DEADLOCK_DETECTION value for the other systems in the sysplex. You can change this value through the SETSMS or SET SMS commands.

Default: 15,4

DESELECT({event[,event][,...]|ALL})

Deletes items from the list of events and services to be traced (if SMS tracing is active). DESELECT has no default. If you specify events that conflict in SELECT and DESELECT, the keyword that appears last has final authority. The events that you can specify on SELECT and DESELECT are:

MODULE

SMS module entry or exit

SMSSJF

SMS/SJF interfaces

SMSSSI

SMS/SSI interfaces

ACSINT

ACS services interfaces

OPCMD

Operator commands

CONFC

Configuration changes

CDSC

Control data set changes

CONFS

SMS configuration services

MSG

SMS message services

ERR

SMS error recovery and recording services

CONFR

Return data from an active configuration

CONFA

Activate a new configuration

ACSPRO

Perform ACS processing

IDAX

SMS interpreter/dynamic allocation

DISP

SMS disposition processing exit

CATG

SMS catalog services

VOLREF

SMS VOLREF services

SCHEDP

SMS scheduling services (prelocated catalog orientation)

SCHEDS

SMS scheduling services (system select)

VTOCL

SMS VTOC/data set services (allocate existing data set)

VTOCD

SMS VTOC/data set services (delete existing data set)

VTOCR

SMS VTOC/data set services (rename existing data set)

VTOCC

SMS VTOC/data set services (allocate new data set)

VTOCA

SMS VTOC/data set services (add a volume to a data set)

RCD

SMS recording services or SMS fast VTOC/VVDS access

DCF

SMS device control facility

DPN

SMS device pool name select subsystem interface

TVR

SMS tape volume record update facility

DSTACK

Trace execution of SMS data set stacking

DEBUG

Debug service

ALL

All of the above options

DINTERVAL({nnn}) {150}

Specifies the interval (in seconds) that SMS waits between reading device statistics from the 3990-3 control unit (applicable only if the 3990-3 is installed and has at least one SMS-managed volume). Specify a value from 1 to 999 (16 minutes, 39 seconds).

Default: 150

DSNAME(DSNAME|*)

Limits the number of issued volume selection analysis messages activated by VOLSEGMSG(ON) that are issued to the hardcopy and job logs for a certain data set name or for all data set names. For a VSAM data set, this is the cluster's entry name. Specify "*" to issue volume selection analysis messages for all data set names.

Default: *

DSNTYPE(LIBRARY|PDS|HFS)

Specifies the installation default for data sets allocated with directory space but without a data set type specified. If DSNTYPE is PDS, the default is a partitioned data set format; if DSNTYPE is LIBRARY, the default is a PDSE (partitioned data set extended) format. If DSNTYPE is HFS, the default is a hierarchal file-system format. For more information about data set types, see z/OS DFSMS Using Data Sets.

Default: PDS

DSSTIMEOUT({nnn}) (0)

Specifies the number of seconds that the dss component of DFMSMS waits during backup processing for quiesce data set requests to complete. Specify a value from zero to 65536 seconds (which is more than 18 hours). If you specify a value between 1 and 299 seconds, the system uses a value of 300 seconds (which equals 5 minutes).

The value specified in the DSSTIMEOUT parameter value is activated when the first instance of the SMSVSAM address becomes active in the sysplex. All subsequent SMSVSAM instances will use the same value.

You can alter the DSSTIMEOUT value dynamically in the following ways:

• Using the SETSMS DSSTIMEOUT(nnnn) command
• By adding or updating the DSSTIMEOUT parameter in IGDSMSxx parmlib member and then activating it with the SET SMS=xx command

Default: 0

FAST_VOLSEL(ON|OFF)

Specifies whether to use the "fast" approach during SMS volume selection.

For striping allocations, fast volume selection is automatically activated regardless of the specification of the FAST_VOLSEL parameter.

If you specify ON, SMS first selects volumes typically until DADSM rejects 100 volumes for insufficient free space. SMS issues message IGD17294I to indicate that 'fast' volume selection has been entered and then excludes volumes that do not have sufficient free space in the volume statistics. This 'fast' approach can inadvertently exclude volumes that have sufficient free space but for which SMS volume statistics indicates that they do not. SMS volume statistics can occur for the following events:

• The VTOC index is broken.
• OEM products bypass CVAF processing.
• In an SMSplex when the SMS synchronization time interval has not yet been driven to update the SMS configuration with the most current space statistics. These statistics are based on updates that can occur on another system in the SMSplex

If you specify OFF, SMS uses the 'normal' approach to select volumes.

Default: OFF

GDS_RECLAIM(YES|NO)

Specifies whether the system will reclaim generation data sets. This is an optional keyword.

If you specify YES, the system will reclaim generation data sets.

If you specify NO, GDS reclaim processing will not be done. This means that if a new generation is created by a job but does not get rolled in, then you must manually:

• delete the generation,
• rename it to a different name, or
• roll it in using Access Method Services

If you do not take one of these manual steps, then on a subsequent attempt to create a new generation, SMS will detect the existence of a duplicate data set and will fail the allocation.

For complete information about how reclaim processing works, see Reclaiming Generation Data Sets in z/OS DFSMS Using Data Sets.

Default: YES

HONOR_DSNTYPE_PDSE (YES|NO)

Specifies whether DSNTYPE of LIBRARY or HFS will be honored during the data set creation, regardless of what DSORG is specified and regardless of whether directory blocks have been specified. If YES is specified, then DSNTYPE of LIBRARY or HFS will be honored even if the DSORG is not set to PO and there are no directory blocks specified. If NO is specified, DSNTYPE of LIBRARY or HFS will be honored only when the DSORG is set to PO or directory blocks are specified; otherwise, a physical sequential data set will be created.

Default: NO

INTERVAL({nnn}) {15 }

Specifies the synchronization interval of the system, which is the number of seconds between system checks of the COMMDS for information about SMS configuration changes from other systems in the SMS complex. You can specify a value from 1 to 999 (16 minutes, 39 seconds).

If your installation has multiple systems simultaneously trying to update the SMS configuration and you have your INTERVAL value set too low, you may experience contention. The larger the number of SMSplex members and the larger the configuration, the more contention you may experience. SMS makes several attempts to complete the configuration updates, but after a pre-defined number of attempts have been blocked by contention, the system issues the 6040 configuration services reason code. This is more liked to happen in installations with multiple SMSplex members (8 or more) and large SMS configurations (50,000 or more volumes). To reduce the amount of contention and 6040 reason codes you experience, set your INTERVAL value higher.

Default: 15

JOBNAME(jobname|*[(TRACE|T|VOLSELMSG|V)[,jobname|*(TRACE|T|VOLSELMSG|V)]])

Specifies whether SMS is to limit tracing (TRACE) and volume selection analysis messages (VOLSELMSG(ON)) for a certain job (jobname), or permit tracing and volume selection analysis messages on all jobs. This keyword supports objects or tape libraries.

jobname|*

Limit tracing and volume selection analysis messages for a certain job, or all jobs (*). Specify "*" to issue for all jobs.

[(TRACE|T|VOLSELMSG|V)[,jobname|*(TRACE|T|VOLSELMSG|V)]]

These are optional sub-parameters. TRACE|T or VOLSELMSG|V associated with the first sub-parameter specifies whether the required value, jobname or *, specified in the first sub-parameter applies to TRACE or VOLSELMSG facility. The second sub-parameter is optional and can be used to specify another value and facility after the first sub-parameter is specified. When none of these optional sub-parameters are specified, the value specified in the first sub-parameter applies to both TRACE and VOLSELMSG. For example, if you want to have all jobs for the SMS TRACE facility, and a particular job, JOB111, for the VOLSELMSG facility, you could code: JOBNAME(*(TRACE),JOB111(VOLSELMSG)).

Default: *

LOG_OF_LOGS(logstream)

Specifies the log stream that is to be used as the log of logs. This log contains copies of tie-up and file-close records written to forward recovery logs and is used by forward recovery products. If this parameter is not specified, no log of logs is used. This parameter is unique to each system in the sysplex. As each instance of DFSMStvs starts, it uses the log of logs name that is found in its member of SYS1.PARMLIB. If you run test and production systems within the same sysplex, use a separate PARMLIB member for the test system and specify a different log of logs in it.

If you specify the LOG_OF_LOGS parameter, you must also specify the TVSNAME(nnn) parameter.

Default: There is no default.

MAXGENS_LIMIT(0-2000000000)

Specifies an upper limit for the MAXGENS parameter on the DD statement in JCL. MAXGENS specifies the number of generations for version 2 PDSEs.

For information about the MAXGENS parameter, see z/OS MVS JCL Reference.

Default: The default is 0.

MAXLOCKS({max|0},{incr|0})

Specifies a pair of values in the range of 0 to 999999. The two values are the maximum number of unique lock requests that a single unit of recovery can make and an increment value. Once the maximum number of unique lock requests is reached, warning messages are issued every time the number of unique lock requests over and above the maximum increases by a multiple of the increment. When the maximum number is reached, warning message IGW859I is issued to the system console, and message IGW10074I is issued to the job log. The messages include the name of the job that is holding the locks. This information will help you to determine whether the job should be canceled, in which case the unit of recovery will be backed out, and the locks will remain held until the backout completes. Specifying a value of 0 indicates that warning messages IGW859I and IGW10074I should not be issued.

If you specify the MAXLOCKS parameter, you must also specify the TVSNAME(nnn) parameter. This parameter applies across all systems.

Note:

1. Lock requests are considered unique if they lock different records within the base cluster. Repeated requests for the same base cluster records do not result in the count being increased.
2. Warning messages IGW859I and IGW10074I are not issued for units of recovery that are in backout. This is because a unit of recovery that is in backout cannot obtain locks on any additional records.
3. Messages IGW859I and IGW10074I are issued until the unit of recovery reaches commit. Once the unit of recovery reaches commit, no additional messages will be issued.
4. To avoid flooding the system console with messages, messages IGW859I and IGW10074I are issued by an asynchronous timer driven task that wakes up every 10 seconds. This means that the messages will not necessarily reflect the exact values specified for the maximum and the increment, but rather will reflect the values which represent the state of the unit of recovery at the time the task awakens.
5. MAXLOCKS takes into account the number of unique lock requests. It does not count the actual number of locks obtained. The number of locks requested will differ from the number of locks held when alternate indexes are used. If an update modifies alternate keys, a lock is obtained for the base record, for each old alternate key, and for each new alternate key. Therefore, if n alternate keys are modified, a single lock request can result in obtaining (2n+1) locks.

Some examples of how this parameter can be specified are:

MAXLOCKS(0,0)

Valid - messages IGW859I and IGW10074I will never be issued.

MAXLOCKS(,)

Valid - this is the equivalent of specifying MAXLOCKS(0,0); messages IGW859I and IGW10074I will never be issued.

MAXLOCKS(5000,0)

Valid - messages IGW859I and IGW10074I will be issued when the asynchronous task wakes up and a unit of recovery has made its 5000th lock request.

MAXLOCKS(0,2000)

Not valid

MAXLOCKS(4500,1000)

Valid - messages IGW859I and IGW10074I will be issued when the asynchronous task wakes up and a unit of recovery has made its 4500th lock request and again every 1000 unique lock requests thereafter.

MAXLOCKS(1000,2300)

Valid - messages IGW859I and IGW10074I will be issued when the asynchronous task wakes up and a unit of recovery has made its 1000th lock request and again every 2300 unique lock requests thereafter.

MAXLOCKS(3200,)

Valid - this is the equivalent of specifying MAXLOCKS(3200,0); messages IGW859I and IGW10074I will be issued when the asynchronous task wakes up and a unit of recovery has made its 3200th lock request.

MAXLOCKS(,2000)

Not valid

Default: The default for both values is 0

OAMPROC(procname)

Specifies the name of the procedure that is to start the OAM address space when SMS is initialized. You must specify this keyword if you want the OAM address space to be started during IPL. The procedure name can be from one to eight characters. There is no default.

OAMTASK(taskid)

Specifies the ID of the task that is to be used to start the OAM address space. OAMTASK is optional; if you specify it without an OAMPROC value, it is ignored. If you omit OAMTASK, the task ID defaults to the procedure name specified in OAMPROC. OAM keywords take effect only if you start SMS at IPL; otherwise the system ignores them. The task ID can be from one to eight characters.

OVRD_EXPDT(YES|NO)

Specifies whether the expiration date or retention period for an SMS-managed DASD data set is to be overridden when a user attempts to delete the data set in one of the following ways:

• DISP parameter on the JCL DD statement.
• Dynamic allocation.
• IEHPROGM utility.
• ISPF/PDF D or DEL line commands.

Specify YES to override an expiration date or retention period for an SMS-managed DASD data set. The data set will be deleted regardless of expiration dates or retention period and the system will not prompt for confirmation. Note that this is a system-level parameter that will effect all jobs running on the system. Exercise caution in using it, so that you do not accidentally delete needed data sets.

When you specify YES, ensure that all appropriate personnel at your installation know that specifying an expiration date or retention period for an SMS-managed DASD data set will not prevent the data set from being deleted.

IBM suggests that you specify YES when:

• Expiration dates or retention periods are not used for data sets, or are overridden by appropriate management classes.
• Data sets allocated to tape are redirected using tape mount and the retention periods and expiration dates for these data sets are not overridden by management classes.

Specify NO to honor the expiration date or retention periods.

Default: NO

PDSE_BMFTIME|BMFTIME(nnn)

With the introduction of a second PDSE address space, two sets of PDSE parameters exist depending on the release of the z/OS system. For z/OS 1.8, PDSE_BMFTIME applies. For z/OS 1.8 and later, BMFTIME applies and is associated with the SMSPDSE address space. For information about parameters for z/OS releases earlier than z/OS 1.8, see the appropriate version and release level of this information.

Specifies the number of seconds that SMS is to wait between recording SMF type 42 subtype 1 records for buffer manager facility (BMF) cache use and SMF type 42 subtype 6 interval records. You can specify a value from 1 to 86399 (23 hours, 59 minutes, 59 seconds), and the default is 3600 (one hour).

For information about the buffer management statistics recorded in SMF record type 42, see z/OS MVS System Management Facilities (SMF).

Default: 3600

PDSE_BUFFER_BEYOND_CLOSE (YES|NO)

For the SMSPDSE address space, specifies whether to keep cached directory and member data in storage beyond the last close on this system of a PDSE data set. If the NO option is selected or defaulted, the cached directory and member data of a PDSE is purged from the in-memory cache when the last close of the data set occurs. If you specify the YES option, the cached PDSE directory and member data are retained in the in-memory cache beyond the last close of the data set.

Default: NO

PDSE_DIRECTORY_STORAGE(nnn|2G)

Specifies the size in gigabytes or megabytes of 64-bit virtual storage that is used to cache PDSE directory buffers in the SMSPDSE address space. The size values are defined with nnnM for megabytes, or nnnG for gigabytes. For example, to request a 500 megabytes size for the PDSE server address space directory cache, specify PDSE_DIRECTORY_STORAGE(500M).

Default: 2 Gigabytes

Maximum: 16 Gigabytes

Minimum: 64 Megabytes

PDSE_HSP_SIZE|HSP_SIZE(nnn)

With the introduction of a second PDSE address space, two sets of PDSE parameters exist. For z/OS 1.8 and greater, HSP_SIZE is synonymous with PDSE_HSP_SIZE and is associated with the SMSPDSE address space. For information about parameters for z/OS releases earlier than z/OS 1.8, see the appropriate version and release level of this information.Specifies the size of the hiperspace in megabytes that is used for PDSE member caching for SMSPDSE.

You can use the HSP_SIZE parameter to request up to 2047 megabytes for the PDSE hiperspace. You can indicate that the hiperspace is not to be created by setting HSP_SIZE to 0. If the hiperspace is not created, the system will not cache PDSE members.

On systems that are running in z/Architecture® mode, by default the PDSE hiperspace is not created and PDSE member caching is disabled.

The system uses the valid values for HSP_SIZE to create the PDSE hiperspace at IPL-time. The HSP_SIZE value remains in effect for the duration of the IPL.

If not enough of the appropriate storage is available to satisfy the HSP_SIZE value, the system uses some portion of the available storage (up to the full amount) for the PDSE hiperspace depending on the amount of caching activity in the system. If the available storage becomes full, the system stops caching PDSE members

Use the HSP_SIZE parameter with care. If you specify an HSP_SIZE value that is too low for normal PDSE hiperspace usage, you can degrade PDSE performance. If you specify a value for HSP_SIZE that is too large, and there is contention for storage on the system, you can degrade performance of other components or applications in the system.

To determine the current HSP_SIZE value of the PDSE hiperspace, use the DISPLAY SMS,OPTIONS command, or review the messages that are written to syslog when SMS is started.

You can examine SMF type 42, subtype 1, records to evaluate the effectiveness of a particular HSP_SIZE value.

PDSE Caching statistics at the data set level are available in SMF type 14 and 15 records. You can also display PDSE Caching details using the DISPLAY SMS,PDSE,HSPSTATS command.

Default: 0 for z/Architecture mode, 256 for non-z/Architecture mode

PDSE_LRUCYCLES|LRUCYCLES(nnn)

LRUCYCLES specifies the maximum number of times (5 to 240 cycles ) that the least recently used (LRU) routine passes over inactive buffers before making them available for reuse. While this parameter sets the maximum value, the LRU algorithm dynamically changes the actual number of times it passes over inactive buffers.

LRUCYCLES is related to LRUTIME. A change to the LRUCYCLES value introduced by this parameter takes effect on the next execution of the LRU routine. Use the default value. In some very high data rate situations, you can tune this value. Monitor the SMF 42 type 1 record to determine the amount of caching activity in the BMF data space. See z/OS MVS System Management Facilities (SMF) for information about the buffer management statistics recorded in SMF record type 42.

Note: With the introduction of a second PDSE address space in z/OS 1.6, two sets of PDSE parameters exist. For z/OS 1.6 and greater, LRUCYCLES applies and is associated with the SMSPDSE address space. For information about parameters for z/OS releases earlier than z/OS 1.6, see the appropriate version and release level of this information.

Default: 15 for z/Architecture mode, 240 for non-z/Architecture mode

PDSE_LRUTIME|LRUTIME(nnn)

With the introduction of a second PDSE address space in z/OS 1.6, now two sets of PDSE parameters exist. For information about parameters for z/OS releases earlier than z/OS 1.6, see the appropriate version and release level of this information.

LRUTIME specifies the number of seconds (5 to 60) that the system waits between calls to the LRU (least recently used) routine. The LRU routine releases inactive buffers in the data space that are used to cache PDSE (partitioned data set extended) directory data and in the hiperspace used to cache PDSE member data.

LRUTIME is related to LRUCYCLES. A change to the LRUTIME value takes effect on the next execution of the LRU routine. Use the default value. In some very high data rate situations you can tune this value. Monitor the SMF 42 type 1 record to determine the amount of caching activity in the data space. See z/OS MVS System Management Facilities (SMF) for information about the buffer management statistics recorded in SMF record type 42.

Default: 60 for z/Architecture mode, 15 for non-z/Architecture mode

PDSE_MONITOR({YES|DISPLAY|DUMPNEXT|NO}[,interval[,duration]])

Specifies how the processing for the PDSE monitor should be started or modified for the non-restartable PDSE address space, SMSPDSE.

YES

Turns on monitor processing.

DISPLAY

Turns on monitor processing and causes any possible error messages to be displayed to the console.

DUMPNEXT

Turns on monitor processing and causes a dump to be taken for the next error detected. Only one dump is taken.

NO

Turns off monitor processing.

If the PDSE parameter is omitted, the monitor is started with default values for 60 seconds for interval and 15 seconds for duration.

interval

Specifies the number of seconds between successive scans of the monitor. If the PDSE_MONITOR keyword is specified, but interval is omitted, the interval remains unchanged, except at IPL time when the interval is set to 60.

duration

Specifies the number of seconds a possible error condition must exist before it is treated as an error. If the PDSE_MONITOR keyword is specified, but duration is omitted, the duration remains unchanged, except at IPL time when the duration is set to 15.

Default: YES

PDSE_RESTARTABLE_AS(YES|NO)

Specifies whether PDSE initialization during IPL NIP processing brings up a second restartable PDSE address space.

If you specify PDSE_RESTARTABLE_AS(YES), with PDSESHARING(EXTENDED), and EXTENDED sharing is not used, processing does not allow PDSE initialization to create a second restartable PDSE address space.

The PDSE_RESTARTABLE_AS specification is set in the IGDSMSxx member of SYS1.PARMLIB. This value cannot be changed through an operator command.

Default: NO

Note: The PDSE parameters must be specified in the IEASYSxx SMS=xx rather than in IEFSSNxx.

PDSE_VERSION({1|2})

Specifies the version number to be used as a default for data sets that are allocated with a DSNTYPE of LIBRARY.

The PDSE_VERSION specification is set in the IGDSMSxx member of SYS1.PARMLIB. This value cannot be changed through an operator command.

Default: 1

PDSE1_BMFTIME(nnn)

Specifies the number of seconds that SMS is to wait between recording SMF type 42 subtype 1 records for buffer manager facility (BMF) cache use and SMF type 42 subtype 6 interval records. You can specify a value from 1 to 86399 (23 hours, 59 minutes, 59 seconds). For information about the buffer management statistics recorded in SMF record type 42, see z/OS MVS System Management Facilities (SMF) .

Default: 3600 (one hour)

Note: With the introduction of a second PDSE address space in z/OS 1.6, two sets of PDSE parameters now exist. For z/OS 1.6 and later, PDSE1_BMFTIME is associated with the restartable SMSPDSE1 address space. See the PDSE_RESTARTABLE_AS(YES) parameter for information about the SMSPDSE1 address space.

PDSE1_BUFFER_BEYOND_CLOSE (YES|NO)

For the SMSPDSE1 address space, specifies whether to keep cached directory and member data in storage beyond the last close on this system of a PDSE data set. If the NO option is selected or defaulted, the cached directory and member data of a PDSE is purged from the in-memory cache when the last close of the data set occurs. If you specify the YES option, the cached PDSE directory and member data are retained in the in-memory cache beyond the last close of the data set.

Default: NO

PDSE1_DIRECTORY_STORAGE(nnn|2G)

Specifies the size in gigabytes or megabytes of 64-bit virtual storage that is used to cache PDSE directory buffers in the SMSPDSE1 address space. The size values are defined with nnnM for megabytes, or nnnG for gigabytes. For example, to request a 10 gigabytes size for the PDSE1 server address space directory cache, specify PDSE1_DIRECTORY_STORAGE(10G).

Default: 2 Gigabytes

Maximum: 16 Gigabytes

Minimum: 64 Megabytes

Note: The PDSE1_DIRECTORY_STORAGE amount is not a hard limit. This amount can be exceeded during periods of heavy PDSE processing.

PDSE1_HSP_SIZE(nnn|0)

PDSE1_HSP_SIZE parameter specifies the size of the hiperspace in megabytes that is used for PDSE member caching for SMSPDSE1.

You can use the PDSE1_HSP_SIZE parameter to request up to 2047 megabytes for the PDSE1 hiperspace. Or, you can indicate that the hiperspace is not to be created by setting PDSE1_HSP_SIZE to 0. If the hiperspace is not created, the system will not cache PDSE members.

On systems that are running in z/Architecture mode, by default the PDSE1 hiperspace is not created and PDSE member caching is disabled.

If you specify a valid value for PDSE1_HSP_SIZE, the system uses it to create the PDSE1 hiperspace at IPL-time. The PDSE1_HSP_SIZE value may be changed by a SET SMS=xx command, and then the new value will be used if the SMSPDSE1 address space is restarted.

If not enough of the appropriate storage is available to satisfy the PDSE1_HSP_SIZE value, the system uses some portion of the available storage (up to the full amount) for the PDSE1 hiperspace, depending on the amount of caching activity in the system. The system stops caching PDSE members if the available storage becomes full.

Use the PDSE1_HSP_SIZE parameter with care. If you specify an PDSE1_HSP_SIZE value that is too low for normal PDSE hiperspace usage, you can degrade PDSE performance. If you specify a value for PDSE1_HSP_SIZE that is too large, and there is contention for storage on the system, you can degrade performance of other components or applications in the system.

To determine the current PDSE1_HSP_SIZE value of the PDSE1 hiperspace, use the DISPLAY SMS,OPTIONS command, or review the messages that are written to syslog when SMS is started.

You can examine SMF type 42, subtype 1, records to evaluate the effectiveness of a particular HSP_SIZE value.

PDSE Caching statistics at the data set level are available in SMF type 14 and 15 records. You can also display PDSE Caching details using the DISPLAY SMS,PDSE1,HSPSTATS command.

Note: With the introduction of a second PDSE address space in z/OS 1.6, two sets of PDSE parameters now exist. For z/OS 1.6 and later, PDSE1_HSP_SIZE is associated with the restartable SMSPDSE1 address space. See the PDSE_RESTARTABLE_AS(YES) parameter for information about the SMSPDSE1 address space.

Default: 0

PDSE1_LRUCYCLES(nnn|15)

PDSE1_LRUCYCLES specifies the maximum number of times (5 to 240 cycles ) that the least recently used (LRU) routine will pass over inactive buffers before making them available for reuse. The LRU algorithm will dynamically change the actual number of times it passes over inactive buffers.

PDSE1_LRUCYCLES is related to PDSE_LRUTIME. A change to the PDSE1_LRUCYCLES value takes effect on the next execution of the LRU routine. Use the default value. In some very high data rate situations, you can tune this value. Monitor the SMF 42 type 1 record to determine the amount of caching activity in the BMF data space. See z/OS MVS System Management Facilities (SMF) for information about the buffer management statistics recorded in SMF record type 42.

Note: With the introduction of a second PDSE address space in z/OS 1.6, now two sets of PDSE parameters now exist. For z/OS 1.6 and later, PDSE1_LRUCYCLES is associated with the restartable SMSPDSE1 address space. See the PDSE_RESTARTABLE_AS(YES) parameter for information about the SMSPDSE1 address space.

Default: 15 for z/Architecture mode, 240 for non-z/Architecture mode

PDSE1_LRUTIME(nnn|60)

PDSE1_LRUTIME specifies the number of seconds (5 to 60) that the system waits between calls to the LRU (least recently used) routine. The LRU routine releases inactive buffers in the data space that are used to cache PDSE (partitioned data set extended) directory data and in the hiperspace used to cache PDSE member data.

PDSE1_LRUTIME is related to PDSE1_LRUCYCLES. A change to the PDSE1_LRUTIME value takes effect on the next execution of the LRU routine. Use the default value. In some very high data rate situations, you change this value for tuning purposes. Monitor the SMF type 1 record to determine the amount of caching activity in the data space. See z/OS MVS System Management Facilities (SMF) for information about the buffer management statistics recorded in the SMF type 42 record.

Note: With the introduction of a second PDSE address space in z/OS 1.6, two sets of PDSE parameters now exist. For z/OS 1.6 and later, PDSE1_LRUTIME is associated with the restartable SMSPDSE1 address space. See the RESTARTABLE_PDSE_AS(YES) parameter for information about the SMSPDSE1 address space.

Default: 60

PDSE1_MONITOR({YES|DISPLAY|DUMPNEXT|NO}[,interval[,duration]])

Specifies how the processing for the PDSE1 monitor is to be started or modified for the restartable PDSE address space, SMSPDSE1.

YES

Turns on monitor processing.

DISPLAY

Turns on monitor processing and causes any possible error messages to be displayed to the console.

DUMPNEXT

Turns on monitor processing and causes a dump to be taken for the next error detected. Only one dump is taken.

NO

Turns off monitor processing.

If the PDSE1 parameter is omitted, and the restartable PDSE address space is created, the monitor is started with default values for 60 seconds for interval and 15 seconds for duration.

interval

Specifies the number of seconds between successive scans of the monitor. If the PDSE1_MONITOR keyword is specified, but interval is omitted, the interval remains unchanged, except at IPL time when the interval is set to 60.

duration

Specifies the number of seconds a possible error condition must exist before it is treated as an error. If the PDSE1_MONITOR keyword is specified, but duration is omitted, the duration remains unchanged, except at IPL time when the duration is set to 15.

Default: YES

PDSESHARING(NORMAL|EXTENDED)

Specifies how PDSEs can be shared across systems in a sysplex. NORMAL allows users to share read access to PDSEs across systems in the sysplex. EXTENDED allows users to share read and write access to PDSEs across systems in the sysplex.

All systems that share PDSEs must use the same sharing protocol, either NORMAL or EXTENDED. The first system in the sysplex to IPL will determine which sharing protocol is used. If EXTENDED has been established as the protocol and a system that is not able to run with EXTENDED PDSE sharing joins the sysplex, that system will not be able to use the PDSEs.

For more information about sharing PDSEs across a sysplex, see z/OS MVS Setting Up a Sysplex.

Default: NORMAL

PDSE_SYSEVENT_DONTSWAP(NO|YES)

Specifies if the task that enters the SMSPDSE or SMSPDSE1 address spaces should be placed in run DONTSWAP in order to prevent the task from being swapped out while holding internal PDSE latches or locks. Specifying this parameter can delay the system from being swapped out but prevents PDSE processing from being delayed by a swapped address space. In addition, it causes the SYSEVENT ENQHOLD to be issued against a latch holder to insure that the holder completes its processing and releases the latch.

For more information about sharing PDSEs across a sysplex, see z/OS MVS Setting Up a Sysplex.

Default: NO

PS_EXT_VERSION(1|2)

This parameter indicates the format in which the system should create sequential extended format data sets. The default is PS_EXT_VERSION(1) to denote the version 1 format. That means that if the sequential extended format data set is not striped and has multiple volumes, FlashCopy® cannot process it.

DFSMSdss must use conventional I/O to copy this type of data set. When the option is PS_EXT_VERSION(2), any new sequential extended format data sets created will be in version 2 format. This will allow FlashCopy to copy the data set much more efficiently if it has multiple volumes and is not striped. The system saves this version number in the field DFASEFVR in the DFA, which is mapped by the IHADFA macro as described in z/OS DFSMSdfp Advanced Services.

Each data set's catalog entry will indicate whether the data set is version 1 or version 2. You can display the data set version via IDCAMS LISTCAT and DCOLLECT.

Default: 1

QTIMEOUT({nnn|300})

Specifies the quiesce exit timeout value, in seconds. The quiesce timeout value specifies the amount of time the DFSMStvs quiesce exits allow to elapse before concluding that a quiesce cannot be completed successfully. Only one quiesce timeout value can be specified. The first instance of DFSMStvs that is brought up within the sysplex determines the value. Subsequent SFSMStvs instances use the value established by the first system, regardless of what can be specified in their members of SYS1.PARMLIB. Specify a value between 60 and 3600.

If you specify the QTIMEOUT parameter, you must also specify the TVSNAME(nnn) parameter. This parameter applies across all systems.

Default: 300

REVERIFY(YES|NO)

Specifies whether SMS is to check a user's authority to allocate a new data set and use storage or management class at job interpretation time or at both job interpretation time and execution time. If you want SMS to check the authority at both times, code YES; NO directs SMS to check only at job interpretation time.

Default: NO

RLSINIT({NO|YES})

Specifies whether you want the SMSVSAM address space started as part of system initialization or through the V SMS,SMSVSAM,ACTIVE command.

Specify YES if you want the SMSVSAM address space started as part of system initialization or through the command. This value applies only to the system accessed by the parmlib member and is acted upon when SMSVSAM is next started.

Specify NO if you do not want to start SMSVSAM during system initialization or through the command. If you specify NO, you must take the following steps to start SMSVSAM later:

1. Change RLSINIT to YES
2. Issue the SET SMS=xx command to activate the parmlib member you updated with RLSINIT(YES)
3. IPL or issue the V SMS,SMSVSAM,ACTIVE command to start the SMSVSAM address space

Default: NO

RLS_MAX_POOL_SIZE({nnnn|100})

Specifies the maximum size in megabytes of the SMSVSAM local buffer pool. SMSVSAM attempts to not exceed the buffer pool size you specify, although more storage might be temporarily used. Because SMSVSAM manages buffer pool space dynamically, this value does not set a static size for the buffer pool.

Use SMF 42, subtype 19 records to help you determine the maximum size of the SMSVSAM local buffer pool.

You can specify a two to four-digit numeric value, with 10 as the minimum value. If you specify a value less than 10, the field is set to 10. If you specify a value greater than 1500, SMSVSAM assumes there is no maximum limit. IBM suggests that you limit the size of the local buffer pool.

Default: 100

RLS_MAXCFFEATURELEVEL({Z|A})

Specify the method that VSAM RLS should use to determine the size of the data that is placed in the CF cache structure. You can use the RLS_MAXCFFEATURELEVEL keyword to limit the connect level when the sysplex has a mixed level of releases and maintenance. If you do not specify a value, or if you specify Z, then only VSAM RLS data that has a Control Interval (CI) value of 4K or less is placed in the CF cache structure. If you specify A, caching proceeds using the RLSCFCACHE keyword characteristics that are specified in the SMS data class that is defined for the VSAM sphere.

RLS_MAXCFFEATURELEVEL is a sysplex wide value. The first system activated in the sysplex will set the value; all other systems will use the value set by the first system.

Default: Z

Note:

1. If A is specified for the RLS_MAXCFFEATURELEVEL parameter, systems lower than V1R3 will not be able to connect to the CF cache structure.
2. If a lower-level system is the first system activated in the sysplex, RLS_MaxCfFeatureLevel defaults to Z, and all systems will be able to connect to the CF cache structure.

RLSTMOUT({nnn|0})

Specifies the maximum time, in seconds, that a VSAM RLS or DFSMStvs request is to wait for a required lock before the request is assumed to be in deadlock and ended with VSAM return code 8 and reason code 22(X'16'). Specify a value in seconds between 0 to 9999. A value of 0 means that the VSAM RLS or DFSMStvs request has no timeout value; the request waits for as long as necessary to obtain the required lock.

VSAM RLS detects deadlocks within VSAM and DFSMStvs. It cannot detect deadlocks across other resource managers, and uses the timeout value to determine when such deadlocks might have occurred. You can specify a global timeout value in the IGDSMSxx member of SYS1.PARMLIB, a step level timeout value on the JCL, or a timeout value on the RPL passed for each VSAM request.

For a particular VSAM RLS or DFSMStvs request, the value used for timeout is in the following order:

• The value specified in the RPL, if any
• The value specified in JCL at the step level, if any
• The value specified in the IGDSMSxx member of SYS1.PARMLIB, if any

RLSTMOUT is valid a parameter for either VSAM RLS or DFSMStvs. If you specify RLSTMOUT but do not specify the TVSNAME parameter, the value is used only by RLS. For DFSMStvs, the first instance of DFSMStvs brought up within the sysplex determines the value. Subsequent DFSMStvs instances use the value established by the first system, regardless of what might be specified in their members of SYS1.PARMLIB.

RLSTMOUT can be specified only once in a sysplex and applies across all systems in the sysplex.

Default: 0

RLSABOVETHEBARMAXPOOLSIZE({(ALL,size)})

RLSABOVETHEBARMAXPOOLSIZE({(sysname1,size1[...;sysname32,size32])})

Specifies the total size of the buffer management facility (BMF) buffer pool that resides above the 2-gigabyte bar for either of the following environments:

• All systems
• Each system referenced of the following parameter

Valid values are between 500MB and 2,000,000MB (2 Terabytes).

Default: 0

RLSFIXEDPOOLSIZE({(ALL,size)})

RLSFIXEDPOOLSIZE({(sysname1,size1[...;sysname32,size32])})

Specifies the amount of the total real storage, both above and below the 2 gigabyte bar, that will be permanently fixed (pinned) on either of the following environments:

• All systems
• Each system referenced in the parameter

Default: 0

SAM_USE_HPF({YES|NO})

Specifies whether you want SAM (BSAM and QSAM) and PAM to use HPF when it is available. This has an effect only if you enable HPF by specifying ZHPF=YES on the ZHPF statement in the IECIOSxx parmlib member.

• YES specifies that you want SAM and PAM to use HPF when it is available and enabled. If you specify or default to SAM_USE_HPF(YES) in either IGDSMSxx or on the SET SMS command, SMS sets on a bit in the DFA, DFASAMHPF.

  Note that because YES is the default, you will see SAM_USE_HPF=YES when you display SMS options for the system, even if it is not attached to an HPF-capable device.

• NO specifies that SAM and PAM should not use HPF. If you specify SAM_USE_HPF(NO) in either IGDSMSxx or on the SET SMS command, the DFASAMHPF bit in the DFA control block is set off. SAM and PAM do not use HPF

The following list are cases in which BAM does not use HPF even though IOS allows it:

• In a partitioned concatenation one or more of the data sets is a PDS that resides on a device that does not support HPF.
• An I/O error occurred with HPF. BAM switches to CCW channel programs and does not resume HPF for the currently open DCB.
• Certain temporary conditions cause BAM to switch to CCWs temporarily but resume HPF for later channel programs.

Default: YES

SELECT({event[,event][,...]|ALL})

Specifies one or more events or services that SMS is to trace (if SMS tracing is active). See the description of the DESELECT parameter for a list of valid events.

Default: ALL

Note: DESELECT(ALL) must precede the SELECT parameter if only specific trace options are to be traced.

SIZE(nnnnnnK|nnnM|nnnnnn|128K)

Specifies the size of the SMS trace table in bytes. If you specify a value of 0, no tracing is performed.

nnnnnnK specifies the size in kilobytes; the value can range from 0K to 255000K (255,000 kilobytes), and it is rounded up to the nearest 4K unit.

nnnM specifies the size in megabytes; the value can range from 0M to 255M (255 megabytes).

If you specify nnnnnn without a unit, the system assumes a unit of kilobytes.

Default: 128K

SMF_TIME(YES|NO)

SMF_TIME specifies whether DFSMS is to use SMF timing; that is, whether SMF type 42 records are to be created at the expiration of the SMF interval period, synchronized with SMF and RMF data intervals.

The following SMF record 42 subtypes are affected when you specify SMF_TIME(YES): 1, 2, 15, 16, 17, 18. If you record these subtypes, you can use SMF_TIME(YES) to synchronize SMF type 42 data with SMF and RMF data intervals.

Specifying SMF_TIME(YES) overrides the following IGDSMSxx parameters: CACHETIME, CF_TIME.

Default: YES

STEPNAME(STEPNAME|*)

Limits the number of volume selection analysis messages activated by VOLSEGMSG(ON) for a certain stepname or for all stepnames. Specify asterisk (*) to indicate all stepnames.

Default: *

SUPPRESS_DRMSGS (YES|NO)

Specifies whether SMS suppresses DELETE/RENAME messages issued to the hardcopy log and job log.

• Specifying YES suppresses DELETE/RENAME messages to the hardcopy log and job log.
• Specifying NO does not suppress DELETE/RENAME messages to the hardcopy log and job log.

Note that this parameter does not suppress callers from issuing the DELETE/RENAME messages. Some callers of SMS issue these messages and some do not. The SCOPE of this parameter is the entire system.

Default: NO

SUPPRESS_SMSMSG (YES|NO,IGD17054I,IGD17227I,IGD17395I)

Specifies whether SMS messages, IGD17054I, IGD17227I, and/or IGD17395I are to be issued or suppressed. The user must specify one or more of the applicable messages in this parameter. If YES is specified, the messages specified are suppressed. If NO is specified, the messages specified are issued.

Default: NO

SYSNAME(sysname1[,sysname2[...,sysname32]])

Specifies the name of the system or systems on which DFSMStvs instances are to run. You can specify up to 32 system names, which must be in the same order as the DFSMStvs instance names. SMS examines the specified system names and compares them to the system names in the CVT. When it finds a match, SMS stores the value of the TVSNAME parameter in the matching position as the DFSMStvs instance name for the system.

Use the combination of SYSNAME and TVSNAME when the PARMLIB member is shared between systems. If no SYSNAME parameter is specified, the TVSNAME parameter applies to the system on which the PARMLIB member is read.

If you specify the SYSNAME parameter, you must also specify the TVSNAME(nnn) parameter. If you specify SYSNAME, but the system name is not specified, DFSMStvs is not started on the system.

Default: There is no default.

SYSTEMS({8|32})

This keyword specifies whether the system is running in compatibility mode (8-name limit) or 32-name mode.

SYSTEMS(8) specifies that a maximum of 8 system names, system group names, or both, can be specified for the SMS configuration. This value indicates that the system is running in compatibility mode and can share configurations (SCDSs or ACDSs) and COMMDS with systems that are running down-level releases of z/OS. Essentially, the system continues to operate as before DFSMS/MVS 1.3, whose date of general availability was in 1995.

SYSTEMS(32) specifies that a maximum of 32 system names, system group names, or both, can be specified for the SMS configuration. This value indicates that the system is not running in compatibility mode, and therefore the ACDS, SCDS and COMMDS cannot be shared with any systems that are running in compatibility mode.

Note:

1. When a system in an SMS complex begins running at a level with DFSMS/MVS Version 1.3 or later, the constructs in the SMS configuration are automatically expanded to prepare for the additional system information. This change occurs for all SMS configurations regardless of whether SMS 32-name support is used.
2. When you are using RESERVE or RELEASE on the volumes that contain shared SMS control data sets with other systems, the potential for deadlock increases dramatically. Even if the ACDS and COMMDS are allocated as the only data sets on separate volumes, deadlocks can occur. To avoid contention problems, you can use global resource serialization (GRS) to convert hardware reserves on the ACDS and COMMDS to SYSTEMS scope enqueues. Also, you should place resource name IGDCDSXS in the RESERVE conversion resource name list (RNL) as a generic entry. This can minimize contention delays and prevent deadlocks, which are sometimes associated with the VARY SMS command.
3. When you convert an SMS complex from compatibility mode to 32-name mode, the conversion is permanent. Be sure to copy your current SMS control data sets to data sets with different names before you begin the conversion.
4. You can do the conversion through the operator console or an ISMF panel. When you begin to convert, take the following steps:
   1. Set a date and time for the conversion when the allocation activity on the systems is low.
   2. Create an SCDS, ACDS, and COMMDS by copying existing SMS control data sets. Be sure to use the new formulas for data set space requirements. To provide for emergency fallback, do not convert your existing primary SCDS, ACDS, and COMMDS at the outset.
   3. On each system in the SMS complex, create an IGDSMSxx member in SYS1.PARMLIB that points to the new ACDS and COMMDS and specifies SYSTEMS(32).
   4. Immediately before conversion, issue SETSMS INTERVAL(999) on all systems involved in the conversion. This prevents a system from rereading the COMMDS and attempting to activate the new configuration before you have an opportunity to change the mode of that system.
   5. On each system, issue SET SMS=xx to restart SMS or re-IPL the system using the new IGDSMSxx member of SYS1.PARMLIB. This restarts SMS in 32-name mode using the new ACDS and COMMDS.
   Restarting SMS resets the INTERVAL parameter for the system. If INTERVAL is specified in the IGDSMSxx member of SYS1.PARMLIB, that value is used, otherwise, the default value is 15.

Default: 8

TRACE(ON|OFF)

Specifies whether SMS tracing is to be on or off.

Default: ON

TRACEEXIT(user-trace-exit)

Defines an installation exit for SMS tracing. The name of the exit must be 1 to 8 alphanumeric characters and it must be a valid load module. There is no default. For more information about the SMS tracing exit, see z/OS DFSMS Installation Exits.

TVSNAME(nnn1[,nnn2[...,nnn32]])

Specifies the identifier or identifiers that uniquely identify DFSMStvs instances that run in the sysplex. You can specify up to 32 identifiers, each of which must be a numeric value from 0 to 255. Each identifier must be unique within the sysplex. DFSMStvs uses this identifier as the last byte of its instance name (although it displays as three bytes). If the TVSNAME parameter is specified without the SYSNAME parameter, only a single value can be specified, and the name applies to the system on which the PARMLIB member is read. The numeric digits are appended to the characters IGWTV to form the DFSMStvs instance name.

You can use the TVSNAME parameter without the SYSNAME parameter when the PARMLIB member is not shared between systems. If no TVSNAME parameter is found, DFSMStvs processing is not available on the system.

Default: There is no default.

TV_START_TYPE({WARM|COLD}[,{WARM|COLD}[...,{WARM|COLD}]])

Specifies the type of start that each instance of DFSMStvs is to perform. Up to 32 TV_START_TYPE values can be specified. TV_START_TYPE values must be specified in the same order as DFSMStvs instance names. If WARM is specified, DFSMStvs reads its undo log and processes the information found in accordance with the information that RRS has about any outstanding units of recovery. If COLD is specified, DFSMStvs deletes any information remaining in the undo log and starts as if the log were empty. Use COLD only when the DFSMStvs undo log has been damaged.

Recommendation: Do not cold start DFSMStvs unless the DFSMStvs system logs have been damaged. After a cold start, data sets for which recovery was not completed could be left in a damaged state and must be recovered manually. If the data sets are forward recoverable, their forward recovery logs might also be damaged. IBM suggests that you manually recover the data sets (without using forward recovery), take back ups of them and any other data sets using the forward recovery log, then delete and redefine the forward recovery log.

You can allow some values to default and others to be specified. For example, specifying the keyword in the following way would cause the DFSMStvs instance in the second position to warm start, while the first and third DFSMStvs instances would cold start.

TV_START_TYPE(COLD,,COLD) 

If both TVSNAME and SYSNAME parameters are also specified, TV_START_TYPE applies to the system specified on the SYSNAME parameter preceding or following it. If TV_START_TYPE is found with only the TVSNAME parameter, it applies to only the system on which the PARMLIB member is being read.

Default: The default is WARM.

TYPE(ERROR ALL[(TRACE|T|VOLSELMSG|V)[,ALL|ERROR(TRACE|T|VOLSELMSG|V)]])

Specifies how you want to trace events (TRACE) and issue volume selection analysis messages (VOLSELMSG).

ERROR

Specify ERROR to trace error events and issue volume selection analysis messages (VOLSELMSG(ON)) for allocations that have failed.

ALL

Specify ALL to trace all events and issue volume selection analysis messages (VOLSELMSG(ON)) for all allocations.

[(TRACE|T|VOLSELMSG|V)[,ALL|ERROR(TRACE|T|VOLSELMSG|V)]]

These are optional sub-parameters. TRACE|T or VOLSELMSG|V associated with the first sub-parameter specifies whether the required value, ALL or ERROR, specified in the first sub-parameter applies to the TRACE or VOLSELMSG facility. The second sub-parameter is optional and can be used to specify another value and facility after the first sub-parameter is specified. When none of these optional sub-parameters are specified, the value specified in the first sub-parameter applies to both TRACE and VOLSELMSG. For example, if you want to set a TYPE value of ERROR for the SMS TRACE facility, and a TYPE value of ALL for the VOLSELMSG facility, you could code: TYPE(ERROR(TRACE),ALL(VOLSELMSG)).

If you specify VOLSELMSG(nnnnn), where nnnnn has a value greater than 0, with TYPE(ALL), you must also specify one of the following parameters to limit the number of detailed analysis messages:

• JOBNAME
• ASID
• STEPNAME
• DSNAME

Default: ERROR

USEEAV({YES|NO})

Specifies, at the system level, whether SMS can select an Extended Address Volume during volume selection processing. This check applies to new allocations and when data sets are extended to a new volume.

YES

This means that Extended Address Volumes can be used to allocate new data sets or to extend existing data sets to new volumes.

NO

This is the default and means that SMS does not select any Extended Address Volumes during volume selection. Note that data sets might still exist on Extended Address Volumes in either the track-managed or cylinder-managed space of the volume.

When SMS is not active in the system, USEEAV is not available and the installation must use alternate means to control the usage of Extended Address Volumes.

Default: NO

USE_RESOWNER({YES|NO})

Indicates whether construct authorization checking is done using the RESOWNER value, which is based on the high-level qualifier of the data set name, or using the allocating user ID for the data set. If you specify NO, the RESOWNER value is not extracted and the allocating user ID is used.

Default: YES

VOLSELMSG({ON|OFF|0|nnnnn|ALL})

Allows you to control volume selection analysis messages issued when you create or extend an SMS-managed data set to a new volume. These analysis messages are written to the hardcopy log and the job log.

ON|OFF

Controls whether SMS volume selection analysis messages are to be issued.

Default: OFF

0|nnnnn|ALL

Controls whether SMS volume selection analysis messages are to be issued.

Default: 0

0

Indicates only summarized analysis messages are to be issued.

nnnnn

The number of volumes to be included in the message with a range of 0 to 65535.

ALL

Indicates that all volumes used for volume selection will be included in detailed analysis messages.

If you specify VOLSELMSG(nnnnn), where nnnnn has a value greater than 0, with TYPE(ALL), you must also specify one of the following parameters to limit the number of detailed analysis messages:

• JOBNAME
• ASID
• STEPNAME
• DSNAME

When all volumes are to be included, volumes are listed by storage group. If only a subset of volumes is to be included, volumes are listed in volume selection preference order without an association to storage group. The system can issue an excessive number of analysis messages to the spool for the following conditions:

• The job or address space creates or extends many SMS-managed data sets
• Many volumes are to be included in the analysis messages.