- ACDS(dsname)
- The dsname specifies a data set that has been
defined as an active control data set. The information in the data
set is copied into the SMS address space to create (or replace) the
active configuration. This parameter affects all MVS™ systems
in the SMS complex. The command format is:
SETSMS ACDS(dsname)
- AKP({nnn[,nnn[...,nnn]]
|1000})
- Specifies one or more activity keypoint trigger (AKP) values.
Each AKP value (nnn) is the number of logging operations
between the taking of keypoints. You can specify up to 32 activity
keypoint values. AKP values must be specified in the same order as
DFSMStvs instance names. Valid values are from 200 to 65535. The default
is 1000.
The command format follows:
SETSMS AKP(1000)
- BreakPointValue (0-65520)
- Valid values range from 0 cylinder to 65520 cylinders.
This
value specifies the maximum number of cylinders during allocation
of VSAM data sets by SMS.
This value is used by
SMS in making volume selection decisions and subsequently by DADSM.
If the allocation request is equal to or higher than the BreakPointValue,
the system prefers to satisfy the request from free space available
from the cylinder-managed space. If the preferred area cannot satisfy
the request, both areas become eligible to satisfy the requested space
amount.Note: The BreakPointValue is only used to direct placement
on an Extended Address Volume. Generally, for VSAM data set allocation
requests that are equal to or larger than the BreakPointValue, SMS
prefers Extended Address Volumes; for non-VSAM allocation requests
and VSAM allocation requests that are smaller than the BreakPointValue,
SMS does not have a preference.
The default is 10.
- CA_RECLAIM(NONE|{DATACLAS|DATACLASS})
- Overrides the specifications of the keyword CA_RECLAIM in IGDSMSxx
and data classes. SETSMS CA_RECLAIM has no default. When NONE is specified,
no KSDS will do CA reclaim, regardless of the data classes and SYS1.PARMLIB
specifications. Specifying DATACLAS or DATACLASS enables CA reclaim
for data classes with CA Reclaim=Y.
The SETSMS command takes effect
on SMS-managed and non-SMS-managed KSDSs immediately, regardless of
which system defined the KSDS, though the CA reclaim already in progress
will not be interrupted by the command. Systems earlier than V1R12
will not do CA reclaim, and will reject the new SETSMS options with
an existing message.
If a CA reclaim is interrupted because
of Cancel or ABENDs, the other requests running on z/OS V1R12 systems
might complete the CA reclaim, regardless of the SETSMS command.
For
VSAM and VSAM RLS, the SETSMS command is system-wide. To make the
SETSMS command sysplex-wide, route the command to the other systems
with the ROUTE option RO *ALL, SETSMS.
- COPYSCDS(scds_dsn, acds_dsn)
- Specifies that SMS is to copy an SCDS (specified by scds_dsn)
into an ACDS (specified by acds_dsn). Although
typically the only way to create an ACDS is to activate an SCDS, you
might not want to activate an SCDS for this purpose. For example,
you might have a production system that creates and maintains an SCDS
for a disaster recovery system, and you want the corresponding ACDS
to be available during the IPL of the disaster recovery system. However,
you do not want to activate the SCDS on the production system. Without
using COPYSCDS, activating the SCDS was the only way to create the
disaster recover ACDS. COPYSCDS provides an alternate way to create
a copy of a SCDS as an ACDS without having to activate the SCDS. Do
not specify COPYSCDS in the same command as ACDS, SCDS, SAVESCDS
or SAVEACDS.
- SCDS(dsname)
- SMS is to use the specified source control data set (SCDS) to
activate a new configuration. This parameter affects all MVS systems
in the SMS complex.
If the ACDS is empty or does not contain a
valid configuration (possibly because of a damaged data set), use
the SCDS parameter to specify a source control data set. The command
format is:
SETSMS ACDS(dsname),SCDS(dsname2)
If
the ACDS is empty and no SCDS is specified, SMS issues a message that
identifies the specified control data set as non-valid.
Note: Do
not specify the SCDS parameter if the ACDS does contain a
valid configuration; the SCDS will overlay the ACDS. To recover from
such accidental loss, it is a good idea to maintain a backup copy
of the current ACDS to be activated in case of damage to the main
copy.
- SAVEACDS(dsname)
- Specifies the ACDS that SMS is to use to save to DASD
the active configurat1ion from the SMS address space. SAVEACDS is
one way to create a backup ACDS. Do not specify SAVEACDS in the same
command as ACDS, SCDS, or SAVESCDS.
- SAVESCDS(dsname)
- Specifies the SCDS that SMS is to use to save to DASD the active
configuration from the SMS address space. SAVESCDS is one way to create
a backup SCDS. Do not specify SAVESCDS in the same command as ACDS,
SCDS, or SAVEACDS.
- COMMDS(dsname)
- SMS is to use the named data set as the new communications data
set.
If the replacement COMMDS is empty, SMS primes it with information
from the active configuration. If the data set is not empty, SMS
determines which ACDS was used to prime the new data set. If the
ACDS named on COMMDS is the same as the one that is active, processing
continues with the new COMMDS. Otherwise, SMS prompts the operator
(by message IGD076D) to decide whether SMS should use the ACDS named
on COMMDS or continue to use the current ACDS.
Note: - If SMS cannot re-access the previously active communications data
set, the operator must issue the command to change the COMMDS on each MVS system
in the SMS complex.
- The COMMDS parameter is mutually exclusive with ACDS, SCDS, and
SAVEACDS.
- FAST_VOLSEL(ON|OFF)
- Specifies whether to use the 'fast' approach during SMS volume
selection.
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.
The default is OFF.
- 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
- 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.
This
parameter applies across all systems.
Note: - Lock requests are considered unique if they lock different records
within the base cluster. Repeated requests for the same base cluster
records will not result in the count being incremented.
- 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.
- 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.
- 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.
- 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
The default for both values is 0.
- PDSE1_BUFFER_BEYOND_CLOSE (YES | NO )
- For the SMSPDSE1 address space, specifies whether to keep directory
and member data in memory beyond the last close on this system of
a PDSE data set. For the NO option, a PDSE directory and member data
will be purged from the in-memory cache when the last close of the
data set occurs. If you specify the YES option, the system retains
the PDSE directory and member data in the in-memory cache beyond the
last close of the data set. You must restart the SMSPDSE1 address
space in order for this change to become effective.
- PDSE1_DIRECTORY_STORAGE (nnn)
- The operand size values are defined with nnnM for megabytes, or
nnnG for gigabytes. For example, to request a 500 megabytes size for
the SMSPDSE1 restartable address space 64-bit virtual directory cache,
specify SETSMS PDSE1_DIRECTORY_STORAGE(500M). You must restart the
SMSPDSE1 address space in order for this change to become effective.
Maximum:
16 Gigabytes
Minimum: 64 Megabytes
- PS_EXT_VERSION(1|2)
- Indicates the format in which the system should create sequential
extended format data sets. The default is to make no change to the
current value for PS_EXT_VERSION. A value of 1 denotes the version
1 format. If you specify PS_EXT_VERSION(2), it means that when anyone
creates a sequential extended format data set, it will be version
2.
If DFSMSdss processes an extended format multivolume, non-striped
data set that is version 1, it cannot use FlashCopy. This results
in reduced performance for the copying or the back up. If the data
set is version 2, DFSMSdss can use FlashCopy. That generally results
in improved performance for the operation.
If you do not wish
to exploit this version 2 capability, you do not need to take any
action. The associated 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.
- PDSE1_HSP_SIZE(nnnn)
- Requests up to 2047 megabytes for the PDSE1 hiperspace. You can
also indicate that the hiperspace is not to be created by setting
PDSE1_HSP_SIZE to 0. If the hiperspace is not created, the system
does not cache PDSE member data. You must restart the SMSPDSE1 address
space in order for this change to become effective.
- PDSE_SYSEVENT_DONTSWAP (YES | NO)
- Specifies whether the task that enters the SMSPDSE or SMSPDSE1
address space is placed in DONTSWAP 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. The
default value is NO.
- QTIMEOUT({nnn|300})
- Specifies the quiesce exit timeout value in seconds. The quiesce
timeout value specifies the amount of time the DFSMStvs quiesce exits
will allow to elapse before concluding that a quiesce cannot be completed
successfully. Specify a value between 60 to 3600. Changing the value
of QTIMEOUT affects only those quiesce requests that are submitted
after the change is made; it has no effect on quiesce requests that
are already in progress. The default is 300.
The command format
is:
SETSMS QTIMEOUT(300)
- RLS_MAXCFFEATURELEVEL({A|Z})
- Specifies the method that VSAM RLS uses to determine the size
of the data that 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.
If you do not specify a value, or if you specify Z, then only VSAM
RLS data that have a Control Interval (CI) value of 4K or less are
placed in the CF cache structure. The default is Z.
Restrictions:
- If A is specified for the RLS_MAXCFFEATURELEVEL parameter, systems
lower than V1R3 will not be able to connect to the CF cache structure.
- 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.
- If the SETSMS command is used to change the RLS_MAXCFFEATURELEVEL
value to A on a mixed-level system, the command is rejected and message
IGW500I is issued.
- RLS_MAX_POOL_SIZE
- 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® recommends that you limit the
size of the local buffer pool.
The default is 100.
- RLSINIT({NO|YES})
- Specifies whether you want the SMSVSAM address space started.
Specify YES if you want the SMSVSAM address space started as part
of system initialization or the V SMS,SMSVSAM,ACTIVE command.
- 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 time
out value; the request will wait for as long as necessary to obtain
the required lock.
VSAM RLS detects deadlocks within VSAM and DFSMStvs.
VSAM RLS 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:
- The value specified in the RPL, if any.
- The value specified in the JCL at the step level, if any.
- The value specified in the IGDSMSxx member of SYS1.PARMLIB, if
any.
RLSTMOUT is a valid 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.
The default is 0.
- RLSABOVETHEBARMAXPOOLSIZE(ALL,size )
- RLSABOVETHEBARMAXPOOLSIZE(sysname1,size1;sysname2,size2;... sysname32,size32)
- Specifies the total size of the BMF buffer pool that resides above
the bar for either of the following:
- All systems
- Each system referenced in the parameter
Valid values are between 500MB and 2,000,000MB (2 Terabytes).The
default is 0.
- RLSFIXEDPOOLSIZE(ALL,size )
- RLSFIXEDPOOLSIZE(sysname1,size1;sysname2,size2;...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:
- All systems
- Each system referenced in the parameter
The default is 0.
- SAM_USE_HPF({YES|NO})
- Specifies whether or not you want BAM to use HPF when it is available.
HPF can be enabled by specifying ZHPF=YES on the ZHPF statement in
the IECIOSxx parmlib member.
- YES specifies that you want BAM to use HPF when it is available
and enabled. If you specify or default to SAM_USE_HPF(YES), SMS sets
on a new bit in the DFA, DFASAMHPF.
- NO specifies that BAM should not use HPF. If you specify SAM_USE_HPF(NO),
the DFASAMHPF bit in the DFA control block is set off and BAM does
not use HPF.
Default: YES
- 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.
The default is NO.
- SUPPRESS_SMSMSG({YES|NO,IGD17054I,IGD17227I,IGD17395I})
- Specifies
whether SMS messages, IGD17054I, IGD17227I, and/or IGD17395I are to
be issued or suppressed. If YES is specified, these specific messages
are to be suppressed. If NO is specified, these messages will be
issued. The user may specify one or more of the applicable messages
in this parameter.
Default: NO