SMMSYSxx PARMLIB parameter explanations

ACS_GDG_DSN

The ACS_GDG_DSN global parameter specifies whether a generation date set qualifier (G nnnn V nn ) is added to data set names for the SMSACSDC, SMSACSMC, SMSACSSC, SMSACSSG, and SMSACSTE functions for use in Filter List and Rule List processing.During ACS processing, IBM provides the data set name with the final qualifier removed. While it is known that this is a generation data set, the actual generation might not be known. When the specific generation is unknown, a value of G0000V00 is appended if this parameter is in effect.

ADDV_CANDP

The ADDV_CANDP global parameter specifies the name of a MainView SRM defined pool that is to be used by the Automation AUTOADDV command as a pool of candidate volumes for adding to other storage groups.This keyword is optional. If it is not specified, the AUTOADDV command and associated function will ignore requests to add a volume to a storage group.

ALLSTORTAB#

The ALLSTORTAB# global parameter controls the number of entries that can be contained in a buffer before information is written to activity logs on the rare occasions when MainView SRM Allocation is unable to obtain storage during initial processing under a batch job or Started Task.
Setting ALLSTORTAB#=0, causes messages to be written to the joblog or SYSLOG, rather than sending the information to the activity logs.

AOO_SUBSYS

The AOO_SUBSYS global parameter indicates the subsystem IDs of automation operations packages.External events are sent to the specified subsystems by issuing a PUT to a DD statement with the SUBSYS parameter.MainView AutoOPERATOR subsystems IDs can be specified in this parameter. Other automation operations packages subsystem IDs can be specified in this parameter if they accept external events in this manner.

AUTO_MXTSK

AUTO_XCFCOM

AUTOJ_OINDX

The AUTOJ_OINDX global parameter specifies the prefix to be used on data set names that were created by MainView SRM and are used to save tailored skeleton JCL.The function name, solution name, date, and time are appended to this prefix to complete the full data set names. This parameter is required for the automation component to be able to save skeleton JCL to a data set when JOB_DEST=SAVE is specified in an AUTO function RLST.You must manage these data sets manually. The Automation component never deletes these files. Migration and other data set management attributes should be assigned to these data sets as needed.

AUTOJ_OPR

The AUTOJ_OPRI global parameter specifies the primary allocation size in tracks for the save JCL data sets.

AUTOJ_OSEC

The AUTOJ_OSEC global parameter specifies the secondary allocation size in tracks for the saved JCL data sets.

AUTOJ_OVOL

The AUTOJ_OVOL global parameter specifies the volume serial number of the saved JCL data sets.

AUTOJ_OUNIT

The AUTOJ_OUNIT global parameter specifies the device type of the saved JCL data sets.The AUTOJ_OUNIT parameter must specify a direct access device type. If it does not, an error message displays when the solution is encountered. This parameter is required for the automation component to be able to save skeleton JCL to a data set when JOB_DEST=SAVE is specified in an AUTO function RLST.

BBI3_SSID

The BBI3_SSID global parameter specifies the CAS subsystem name to which the SVOS PAS should connect. Because the MainView infrastructure (MVI) connection occurs during SVOS startup, SVOS will not start if BBI3_SSID is not specified. To update the value of BBI3_SSID, SVOS must be stopped and restarted; it cannot be refreshed.The CAS subsystem name is specified in the SSID= parameter on the PARM= keyword for the CAS JCL EXEC statement.

BCDSn

The BCDSn global parameter specifies HSM CDS database files to be used by the MainView SRM Reporting component. You can supply up to four BCDSn names, replacing n with a value of 1 through 4. You must specify the BCDS names in numerical order, beginning with number 1. For example, supplying a BCDS2 and BCDS3 global name without specifying BCDS1 would cause MainView SRM to ignore all BCDS entries.Under special circumstances it is desired to not allocate any of the HSM CDS data sets. When this is the situation, any one of the CDS files must be specified as 'NONE'. All of the CDS data sets (BCDS1, MCDS1, and OCDS) can be specified as 'NONE' but it is only necessary to specify one for this feature to take place. 

BLKINPUT

The BLKINPUT global parameter, when set to Y, causes function OPTBLKSZ to change the block size in the program DCB if the program DCB contains a nonzero block size. If a block size was either not specified or specified as 0 in the program DCB, no change is made.This feature is for older programs that open data sets for input processing and were coded with hard coded block size values where those values are different from what is found in the F1DSCB. This option is not normally required.

BLKOLDSR

The BLKOLDSR global parameter, when set to Y, causes function OPTBLKSZ to change the block size in the program DCB to the value that is specified in the OPTBLKSZ RLST SET statement when a data set is opened for output processing and either DISP=SHR or DISP=OLD has been specified.This option is for older programs that have hardcoded block size values specified. This option is not normally used because hardcoded block size values are usually only specified when a data set is created by using DISP=NEW.

BSCAN_DCLAS

The BSCAN_DCLAS global parameter specifies data class name to assign to the BCDS scan temporary data set.

Note: SMS data compaction can be used on the temporary data set by setting DSNTYPE=EXTENDED and COMPACTION=YES in the assigned data class. When a data class is specified, BCDS scan generates a permanent data set name for the temporary data set. This combination of parameters is required for data compaction to be allowed. The temporary data set is still deleted at the end of the BCDS scan.

BSCAN_OEAS

The BSCAN_OEAS global parameter indicates whether the BSCAN output collection data set can reside in the extended address space (EAS) on an extended address volume (EAV) or not.

BSCAN_OPRI

The BSCAN_OPRI global parameter specifies the primary allocation size in cylinders for the BCDS scan collection data set.

BSCAN_OSEC

The BSCAN_OSEC global parameter specifies the secondary allocation size in cylinders for the BCDS scan collection data set.

BSCAN_OUNIT

The BSCAN_OUNIT global parameter specifies the unit name for the BCDS scan collection data set.

BSCAN_OVOL

The BSCAN_OVOL global parameter specifies the volume name for the BCDS scan collection data set.

BSCAN_POST

The BSCAN_POST global parameter specifies that the BSCAN process should be initiated on completion of either HSM primary space management (PRI) or HSM secondary space management (SEC). BMC recommends running the BSCAN process after the completion of either primary or secondary space management (whichever comes last). This parameter can be used to issue a BSCAN command automatically when one of those processes is completed.If MSCAN is also setup to run (via the MSCAN_POST parameter), the BSCAN process will not begin until the MSCAN process has completed.If this parameter is not specified, the BSCAN process is not initiated automatically at the end of either HSM process. In this case, BSCAN can be initiated manually through the console, or by using the MainView SRM Scheduled Services facility.This keyword requires the HSM Collector to be active, and the MainView SRM ARCINEXT exit to be installed in the DFSMShsm address space.

BSCAN_SCLAS

The BSCAN_SCLAS global parameter specifies the storage class name to assign to the BCDS scan temporary data set.If BSCAN_SCLAS is specified, BSCAN_TUNIT and BSCAN_TVOL are ignored.

BSCAN_SGCIN

The BSCAN_SGCIN global parameter specifies whether to include Application Collector data in the BCDS scan collection data set when SVSGC is active.

BSCAN_TPRI

The BSCAN_TPRI global parameter specifies the primary allocation size in cylinders for the BCDS scan temporary data set.

BSCAN_TEAS

The BSCAN_TEAS global parameter indicates whether the BSCAN temporary data set can reside in the extended address space (EAS) on an extended address volume (EAV).

BSCAN_TSEC

The BSCAN_TSEC global parameter specifies the secondary allocation size in cylinders for the BCDS scan temporary data set.

BSCAN_TUNIT

The BSCAN_TUNIT global parameter specifies the unit name for the BCDS scan temporary data set.

BSCAN_TUNIT is ignored when BSCAN_SCLAS is specified.

BSCAN_TVOL

The BSCAN_TVOL global parameter specifies the volume name for the BCDS scan temporary data set.

BSCAN_TVOL is ignored when BSCAN_SCLAS is specified.

CAL

The CAL global parameter specifies the suffix of the SMCALS xx member. SMCALS xx contains calendar parameters used to specify nonworking days for the DFSMShsm-related functions.

CAPPLN_APPL

The CAPPLN_APPL global parameter specifies whether box and physical disk summaries should be included in the capacity planning database. This parameter can be used when these summaries are not necessary to reduce the amount of data that is logged to the capacity planning database and, thereby, increase the retention period of the data that is logged.

CAPPLN_DAPP

The CAPPLN_DAPP global parameter specifies whether to include data set application summaries in the capacity planning database.

CAPPLN_DGRP

The CAPPLN_DGRP global parameter specifies whether to include data set group and pool summaries in the capacity planning database.

CAPPLN_DHGP

The CAPPLN_DHGP global parameter specifies whether to include data set high-level qualifier and group and pool summaries in the capacity planning database.

CAPPLN_DHLQ

The CAPPLN_DHLQ global parameter specifies whether to include data set high-level qualifier summaries in the capacity planning database.

CAPPLN_DHMC

The CAPPLN_DHMC global parameter specifies whether to include the data set high-level qualifier and management class summaries in the capacity planning database.

CAPPLN_DMCG

The CAPPLN_DMCG global parameter specifies whether include management class and group summaries in the capacity planning database.

CAPPLN_DMGT

The CAPPLN_DMGT global parameter specifies whether to include data set SMS management summaries in the capacity planning database.

CAPPLN_DVOL

The CAPPLN_DVOL global parameter specifies whether to include data set volume summaries in the capacity planning database.

CAPPLN_PHYS

The CAPPLN_PHYS global parameter specifies whether box and physical disk summaries should be included in the capacity planning database. This parameter can be used when these summaries are not necessary to reduce the amount of data that is logged to the capacity planning database and, thereby, increase the retention period of the data that is logged.

CDS_DCLAS

The CDS_DCLAS global parameter specifies SMS data class name for the CDS collection data set that is used when allocating this data set.

CDS_EAS

The CDS_EAS global parameter indicates whether the CDS collection data set can reside in the extended address space (EAS) on an extended address volume (EAV) or not.

CDS_MCLAS

The CDS_MCLAS global parameter specifies the SMS management class name for the CDS collection data set that is used when allocating this data set.

CDS_PRI

The CDS_PRI global parameter specifies the primary allocation size in cylinders for the CDS collection data set.

CDS_PRFX

The CDS_PRFX global parameter specifies the prefix data set name to be used for the CDS collection data set name that is used when allocating this data set.

• BKD for backups
• BKV for backup versions
• MIG for migrates

CDS_SCLAS

The CDS_SCLAS global parameter specifies SMS storage class name for the CDS collection data set that is used when allocating this data set.

CDS_SEC

The CDS_SEC global parameter specifies the secondary allocation size in cylinders for the CDS collection data set.

CDS_UNIT

The CDS_UNIT global parameter specifies the direct access device type of the CDS collection data set.

CDS_VOL

The CDS_VOL global parameter specifies the volume serial number of the CDS collection data set.

CHECK

The CHECK global parameter controls whether the first volume or all volumes are immediately assigned from the assigned pool if multiple volumes are requested for a data set, VSAM or non-VSAM.

CNFG_MXTSK

The CNFG_MXTSK global parameter value indicates the maximum number of tasks to be used by the configuration component to collect configuration data. This value can be lowered to reduce the CPU and virtual storage consumption of the SVOS address space during a configuration collection, at the cost of increased response time to complete the collection process. This value can be increased to reduce the response time of a configuration collection, at the expense of CPU consumption and virtual storage utilization during a configuration collection. Increasing this value past a certain point could cause storage-related errors during configuration collection. The point at which this error occurs is dependent on the private-area size of the z/OS system as well as the REGION= parameter of the SVOS Started Task JCL.

CONFIG_INV=nnnn (PTF BPG7945 applied) 

The CONFIG_INV global parameter specifies the interval (in minutes) that the configuration manager waits for before it checks for a missed SMS status change of an SMS Managed volume. The configuration manager database is updated as volumes change online and offline. If a volume is reserved while a change occurs, there is a possibility to miss the change in status. The CONFIG_INV value determines how often the configuration manager checks for a missed SMS status change.

CRITLIST

The CRITLIST global parameter specifies the suffix of the SMCRIT xx member. SMCRIT xx members contain lists of critical data set names to be used by the VOLSEL option of CRITDSN.

CSCAN_DSN

The CSCAN_DSN global parameter specifies the data set name that will contain the catalog information gathered through the SVOS CSCAN command.

CSCAN_EAS

The CSCAN_EAS global parameter indicates whether the CSCAN output data set can reside in the extended address space (EAS) on an extended address volume (EAV) or not.

CSCAN_PERFI

CSCAN_PERFS

The CSCAN_PERFS global parameter specifies whether the Catalog Performance collector should write performance statistics being actively collected when the SVCPF component is stopped. This keyword can be used to capture any data that has been collected since the last time the performance statistics were offloaded to the CSCAN data set. You might determine that the data lost at component stop does not skew the statistics one way or the other, and might not be necessary.Performance statistics are offloaded to the data set for any CSCAN command that specifies PERF=YES (the default), PERF=ONLY, or PERF=INTEND.

CSCAN_PRI

The CSCAN_PRI global parameter specifies the primary allocation size in cylinders for the SVOS CSCAN output data set.

CSCAN_SEC

The CSCAN_SEC global parameter specifies the secondary allocation size in cylinders for the SVOS CSCAN output data set.

CSCAN_UNIT

The CSCAN_UNIT global parameter specifies the device type of the SVOS CSCAN output data set.

CSCAN_VOL

The CSCAN_VOL global parameter specifies the volume serial (VOLSER) number of the SVOS CSCAN output data set.

DADSMEX

The DADSMEX global parameter determines if the DADSM preprocessing exit (IGGPRE00) is called. If it is called and the exit returns a zero, the volume is used for a volume switch. If the exit returns a four, scanning continues for an acceptable volume. If the exit returns an eight, no volume switch occurs.

DASDGENR

The DASDGENR global parameter specifies the only generic DASD names that are to be processed for specific functions if space requirements are not specified. Standard pooling functionality allows the JCL UNIT parameter to specify a pool name. To avoid this specification use DASDGENR to intercept data set allocations without space information. Such allocations will only be considered for subsequent processing if the unit is found in an internal table (3380, 3350, and so on) or if the unit is found in the DASDGENR list. DASDGENR affects functions DASDPOOL, DSNCHECK, SETEXPDT, and FORCECAT. If no DASDGENR table is coded, all DASD allocations will be processed.

DATEFMT

The DATEFMT global parameter specifies the format of calendar dates in MainView SRM reports and display screens.This parameter does not apply to the format of input dates for SMCALS xx parameters.

DBAS

The DBAS global parameter specifies the suffix of database data set list SMDBAS xx member. This member is where the data sets that make up the capacity planning database are specified.

DCTYPE

The DCTYPE global parameter specifies which device characteristics are to be maintained across volumes during a volume switch. For example, if your site wants to segregate data sets residing on cached and noncached devices, the DCTYPE=(CACHE) operand can be used to ensure that the cache property is maintained during a volume switch. Data sets residing on a cached device only switch to volumes that are also cached. Likewise, data sets on noncached devices switch to only noncached volumes.

DFREORGPRC

The DFREORGPRC global parameter defines default SPACVOLA reorganize procedure name of the procedure that is started if SPACVOLA reorganize processing is requested.

DIAG

The DIAG global parameter specifies the suffix of parameter member SMDIAGxx.

DIAGMSDD

The DIAGMSDD global parameter establishes WTO message tracing.

DISPLAY

The DISPLAY global parameter determines which functions are displayed in the ISPF interface functions panel.

DMYUNIT

The DMYUNIT global parameter specifies to convert a nonexistent UNIT parameter to a valid UNIT parameter only if JCLEXT=YES.

The DASDPOOL function must be active in order for the DMYUNIT parameter to work.

DP_RENAME

The DP_RENAME global parameter specifies that during DADSM RENAME, DASDPOOL will be driven to verify that the POOL containing the volume on which the data set currently resides is also a POOL that would be assigned to the renamed data set.When DP_RENAME=Y, if the first POOL in which the current volume is found does not match a POOL that would be assigned to the renamed data set, the RENAME will be denied.When DP_RENAME=A, if any POOL in which the current volume is found does not match a POOL that would be assigned to the renamed data set, the RENAME will be denied.

DPO_COLLECT (PTF BPG7719 applied)

DPO data collection occurs:

• Y activates data collection.
• N deactivates data collection, and certain aspects of functions that use DPO-related parameters will not

operate.

For example, DASDPOOL is a function that can use DPO-related parameters. If DPO data collection is deactivated, DASDPOOL processing will ignore any DPO-related parameters that DASDPOOL uses.

Similarly, some views display DPO data. If data collection is deactivated, those views will not contain any data.

For more information, see DPO-startup-DASDPOOL.

DS_ASST_DB

The DS_ASST_DB global parameter specifies the data set name of the DS Size Assist DB file. DS_ASST_DB=NONE prevents the DS Size Assist feature from starting.

DS_ASST_CNT

The DS_ASST_CNT global parameter specifies the number of DB updates to occur before issuing ENDREQ to flush the buffers to DASD.

DS_ASST_RLS

DS_ASST_SLO

The DS_ASST_SLO global parameter specifies the number of slots to maintain in each tracked data set record. Each slot records the allocation amounts of a data set, which when combined, provide an allocation history of the data set.

When changing this value after records exist in the DS Size Assist DB, the DS Size Assist feature automatically adjusts a data set record in the DB, but only when a data set goes through one of the collection points (allocation, extend, partial release, uncatalog, migrate and GDG roll-off).

If you want to change all data set records at once, you can run the Data Set Size Assist Maintenance Utility. Refer to the distributed JCLDSAAS sample member in BBSAMP for instructions on performing this utility.

Note: Raising the DS_ASST_SLO value causes record length increases for any pre-existing data set record when the record is next updated, can cause CI/CA splits to occur in the DB. A better solution might be to run sample JCLDSAAS, followed by a reorganization (see sample JCLDSARO).

DUMPDD

The DUMPDD global parameter produces SYS1.DUMP xx dump if MainView SRM abends.

ECDS_NOAPPL

The ECDS_NOAPPL global parameter specifies whether the acquisition of application data should be suppressed during the creation of an extended CDS query collection data set.

ENCLAVES

The ENCLAVES global parameter specifies whether z/OS enclaves should be used to enable management of resource consumption in the SVOS address space using z/OS Workload Manager (WLM).Normally, enclaves should always be used, even if WLM definitions are not established to assign service classes to the enclaves. This keyword can be used to turn off enclave usage in situations where MainView SRM enclave usage incurs errors.

Note: This keyword cannot be refreshed. Any change to this keyword will not take effect until you cycle the SVOS address space.

ETS_ID

The ETS_ID global parameter is no longer supported. The Ensign Alarm Console is no longer supported in the Automation component. If the keyword is specified, the SVM0766I messages is issued and the value is ignored.

EVNT

The EVNT global parameter specifies the suffix that you assign to the name of the SMEVNT xx event definition member.This value can be overridden after SVOS has started using the SVOS REFRESH command. To determine the currently active SMEVNT xx member, use the ADMEMA view or look in the SVOS job log for the last occurrence of message SVM0731I.

EVNT_MSGCMP

The EVNT_MSGCMP global parameter specifies whether excess spaces should be removed from all event messages issued.

The EVNT_MSGCMP parameter can be overridden for specific events by using the MSGCMP parameter in the event definition, which is coded in the SMEVNTxx member.

EVNT_TENTHS

The EVNT_TENTHS global parameter specifies whether to use decimal points in event message text for FLST/RLST variables with values in tenths. For example: &AV_FULLT (volume percentage full in tenths) used in event text Volume is &AV_FULLT percent full would be displayed in event message as Volume is 55.8 percent full (with EVNT_TENTHS=Y coded).

EXTMSG

The EXTMSG global parameter enables you to turn off the SVM4133W message. When VSAM data sets reach the maximum number of extents allowed, message IEC070I is issued with a reason of 204. The Allocation component (StopX37/II) also issues the SVM4133W message, which describes the error that occurred. In some environments, this additional message is not helpful or desired. Specify SVM4133W=NO to prevent the SVM4133W message from being produced.

FORPLEXNAME

The FORPLEXNAME global parameter specifies one or more user-defined PLEXNAMEs that can be included or excluded in a sysplex environment.

FORSMFID

The FORSMFID global parameter specifies SMF records that can be included or excluded in a sysplex environment.

FORSYSID

The FORSYSID global parameter specifies user-defined system IDs that can be included or excluded in a sysplex environment.

FUNC

The FUNC global parameter specifies the suffix of the SMFUNCxx member. SMFUNC xx contains function definition parameters. A function must be included in the SMFUNCxx member to be available during MainView SRM execution. Each function definition identifies two other members that define:

• The resources affected by the function (SMFLSTxx–the filter list)
• How those resources are affected (SMRLSTxx–the rules list)

Note: Some functions do not use a rules list, but all functions require a filter list.

HISTDAYS

The HISTDAYS global parameter specifies the number of days of data to retrieve from the performance collector and temporarily store in a data space.

HSM_DAY_TOD

The HSM_DAY_TOD global parameter specifies the time of day at which HSM AutoBackup occurs.

MainView SRM inspects every HSM on the system where SVOS is running (the local system) for the SETSYS AUTOBACKUPSTART keyword value. If the AUTOBACKUPSTART keyword is specified in an HSM, the corresponding value is used. The HSM_DAY_TOD keyword can be specified on systems where local DFSMShsms do not have the SETSYS AUTOBACKUPSTART keyword specified in the ARCCMD members.

If HSM_DAY_TOD is specified, it overrides any value found for HSM AUTOBACKUPSTART keyword.This value is used in the HSM views to align reporting to the HSM day. The start of AutoBackup defines the start of the HSM day. The HSM DAY field on the data entry dialogs can be used to cause the reporting time period to align with the HSM day. This is discussed in the online Help for the HSM DAYS field in the data entry dialogs.

HSMACTID

The HSMACTID global parameter specifies the high-level data set name qualifier for the DFSMShsm activity data sets. This name qualifier is used by the output management facility to build the name of the DFSMShsm activity data sets that are used as input.

HSMRQ_SCOPE

The HSMRQ_SCOPE global parameter defines the scope of the HSMRQUE function.

HSMRQ_VSAM

The HSMRQ_VSAM global parameter specifies the VSAM cluster name or a path name of a recall queue file.

IGNOREDD

The IGNOREDD global parameter suppresses all MainView SRM activity for the job step containing the specified DD name. No MainView SRM functions will occur for any data set in the job step.

JCLEXT

The JCLEXT global parameter specifies whether Allocation obtains volume and unit information after the operating system accesses the catalog, which is useful when PROCOLD=YES and/or DISP=MOD is specified.

JCLUREQ

When the PROCOLD parameter is set to YES and Allocation is analyzing a DD statement for an existing data set, the JCLUREQ parameter determines whether UNIT information is required.If JCLUREQ=YES is specified, MainView SRM intercepts the DD statement only when the JCL specifies UNIT parameter. This process allows the data center to correct an invalid UNIT parameter without analyzing DD statements that are correctly specified. If you specify JCLUREQ=NO, Allocation examines every DD statement that is associated with an existing data set.

JES3CI

The JES3CI global parameter allows certain activities to be suppressed when they are invoked under the JES3 Converter/Interpreter.

MAXPOOL

The MAXPOOL global parameter specifies the number of pools in which a single volume can be defined. MainView SRM pools are defined in the SMPOOL member. A single volume can be defined in up to eight pool definitions. MAXPOOL can be used to limit the number of pool definitions defined. The value that is specified is used by the Configuration component when reading the SMPOOL member and building internal pool definitions.

MAXVOL

The MAXVOL parameter limits the number of volumes that SPACVOLA allows a data set to use. When additional units are allocated with UNIT=(SYSDAn ), they are counted if space is obtained on a volume. If n is greater than the MAXVOL value, SPACVOLA does not limit the use of the additional volumes, but does not add additional volumes through a volume switch.

MCDSn

The MCDSn global parameter specifies HSM migrated data set file allocated during system startup.If this parameter is not specified, MainView SRM will discover the HSM MCDS data set name when SVOS is started. BMC recommends that you let SVOS discover the data set names; however, discovery requires that the DFSMShsm address space be active prior to SVOS being started. If this requirement cannot be met, this keyword should be used to specify the name.You can supply up to four MCDSn names, replacing n with a value of 1 through 4. You must specify the MCDS names in numerical order, beginning with number 1. For example, supplying a MCDS2 and MCDS3 global name without specifying MCDS1 would cause MainView SRM to ignore all MCDS entries.In certain situations, it is better to not allocate any of the HSM CDS data sets. In these situations, any one of the CDS files must be specified as 'NONE.' All of the CDS data sets (BCDS1, MCDS1, and OCDS) may be specified as 'NONE'.

METRIC

The METRIC global parameter specifies the default metric to use when space sizes are displayed in various reporting views. This parameter allows the metric used to calculate size fields that are displayed in the space collector group and pool views to be changed. The fields can be displayed in bytes, tracks, or cylinders depending on the parameter setting. This parameter sets the default for all users; however, each user can change the display by using SETSRM or overtyping the METRIC field in the header section of the display.The default metric is used in conjunction with the SETSRM METRIC command to set the metric for the current view.

MODDELETMIG

The MODDELETMIG global parameter specifies whether the MODDELET function will use the HDELETE command to delete files residing on DFSMShsm migration volumes rather than allow the data set to be recalled and then deleted.

MODTRCDD

The MODTRCDD global parameter establishes module entry and exit tracing.

MREDUCE

The MREDUCE global parameter determines whether secondary space reduction can occur on multivolume data sets that were allocated with JCL.

MSCAN_BCDS

The MSCAN_BCDS global parameter specifies whether to include DFSMShsm backup data in the MCDS scan collection data set. Setting this keyword to YES retrieves of all DFSMShsm backup records for the data sets being scanned. This retrieval can significantly affect the scan's elapsed time and I/O.

MSCAN_OEAS

The MSCAN_OEAS global parameter indicates whether the MSCAN output collection data set can reside in the extended address space (EAS) on an extended address volume (EAV).

MSCAN_MXTSK

The MSCAN_MXTSK global parameter specifies the maximum number of tasks to be used by BSCAN and MSCAN command processing. Each task is used to read sections of the DFSMShsm BCDS/MCDS data sets during their respective processing. Increasing this number will decrease the elapsed time that the process takes at the expense of higher CPU percentage and I/O rates in the SVOS address space. Decreasing this number lengthens the elapsed time of the process, but will cause lower CPU percentages and I/O rates from SVOS.

MSCAN_OPRI

The MSCAN_OPRI global parameter specifies the primary allocation size in cylinders for the MSCAN output collection data set.

MSCAN_OSEC

The MSCAN_OSEC global parameter specifies the secondary allocation size in cylinders for the MSCAN output collection data set.

MSCAN_OUNIT

The MSCAN_OUNIT global parameter specifies the device type of the MSCAN collection data set. The MSCAN_OUNIT parameter must specify a direct access device type. If it does not, when an MSCAN is initiated, an error message is issued and the scan is terminated.

MSCAN_OVOL

The MSCAN_OVOL global parameter specifies the volume serial number of the MSCAN collection data set.

MSCAN_POST

The MSCAN_POST global parameter specifies that the MSCAN process should be initiated on completion of either HSM primary space management (PRI) or HSM secondary space management (SEC). BMC recommends running the MSCAN process after the completion of either primary or secondary space management (whichever comes last). This parameter can be used to issue an MSCAN command automatically when one of those processes is completed.

MSCAN_SGCIN

The MSCAN_SGCIN global parameter specifies whether to include Application Collector data in the MCDS scan collection data set when SVSGC is active.

MSGID

The MSGID global parameter specifies the inclusion of the MainView SRM message identifier in the message text.

MSGLVL

The MSGLVL global parameter specifies the level of messages that will be printed. Messages are inclusive of increasing levels of severity. When a particular level is chosen, messages of that level and greater will be printed. For example, if E is chosen, messages of severity E or S are printed.

MSGPREF

The MSGPREF global parameter specifies the three-character message identifier prefix on MainView SRM messages.

MULTISTRIPE

The MULTISTRIPE global parameter controls the number of volumes that can be added to a multistripe VSAM data set by SPACVOLA.

MVL_LSNAME

The MVL_LSNAME global parameter identifies the MainView Logger logspace name where MainView SRM events and audit log records are to be logged.

MVL_SSID

The MVL_SSID global parameter identifies the MainView Logger subsystem ID of the MainView Logger address space. If this parameter is not specified, MainView SRM will send its events and audit log records to the default MainView Logger address space. This parameter should be used only if more than one MainView Logger address space is running on the system where SVOS is active and you want to direct the events to a specific MainView Logger address space.

NOCATDYN

The NOCATDYN global parameter allows NOCATLG2 to process dynamically allocated data sets.

NOCATPFX

The NOCATPFX global parameter specifies the second-level qualifier to be used by NOCATLG2 when renaming a data set. NOCATLG2 can be directed to rename existing data sets by specifying the NOCATLG2=RENAME operand on the RLST action parameter.

NOCATPRG

The NOCATPRG global parameter specifies whether NOCATLG2 can scratch a data set that has not reached its expiration date when NOCATLG2=SCRATCH is specified in the RLST action parameter.

NOCATSEC

The NOCATSEC global parameter specifies the level of security checking that NOCATLG2 performs before scratching or renaming a data set. If the creator of the new data set does not have the specified level of authority, NOCATLG2 will not scratch or rename the existing data set.

NOCATSMS

The NOCATSMS global parameter specifies whether SMS-managed data sets can be renamed, uncataloged, or scratched by NOCATLG2.

NOCATTIM

The NOCATTIM global parameter specifies the amount of time (in minutes) that StopX37/II will wait while attempting to perform NOCATLG2 processing (DELETE option only) on an SMS managed data set.

NOCATVOL

The NOCATVOL global parameter allows a new data set to be allocated to the same volume to which it was previously cataloged. This can occur when a catalog entry is orphaned because a data set is removed from a volume without the data set being uncataloged or when a catalog entry is added for a data set but the data set is never actually created.

This operand acts differently depending on the NOCATWHEN setting in the NOCATLG2 RLST. If NOCATWHEN=TERM is specified and NOCATLG2=UNCATLG is specified in the relevant RLST action parameter, NOCATVOL=SAME indicates that the data set should be uncataloged and recataloged even if the old and new volumes are the same and NOCATVOL=DIFF means that the old catalog entry is left in the catalog if the old and new volumes are the same.

If the relevant RLST action parameter specifies NOCATLG2=SCRATCH or NOCATLG2=RENAME, NOCATVOL=DIFF is forced and the NOCATLG2 processing will fail with an error message if the old and new volumes are the same.

If NOCATWHEN=ALLOC is specified, NOCATVOL is ignored and NOCATLG2 processing occurs, even if the old and new volumes are the same.

NOCATWHEN

The NOCATWHEN global parameter specifies when NOCATGL2 processing occurs for non-SMS managed data sets. ALLOC indicates that NOCATGL2 processing occurs during data set allocation. TERM indicates that NOCATLG2 processing occurs during step termination. NOCATLG2 processing for SMS-managed data sets must occur during data set allocation.

OCDS

The OCDS global parameter specifies HSM OCDS data sets to be defined and allocated during system startup.

OFFLINEVOLS

MainView SRM can collect information throughout a system for both offline and online volumes. Occasionally, gathering information about offline volumes can be problematic. For problematic situations, you can specify OFFLINEVOLS=NO to instruct MainView SRM not to gather information about offline volumes.

OPMHLQ

The OPMHLQ global parameter specifies the high-level qualifier for the data sets created by the Output Management Facility, which allows selection of DFSMShsm and DFDSS messages for reporting and analysis.

ORIGDATA

During Allocation processing, ORIGDATA specifies whether VOL and UNIT contain the original volser and unit values from the JCL or the current value.

The fields ORIGVOL and ORIGUNIT will always contain the original VOLSER and UNIT that were specified in the JCL.

PASS_DSN

The PASS_DSN global parameter defines a data set name (DSN) that contains the authorization tables that are generated by the Product Authorization Utility.

PDSE_USED

The PDSE_USED global parameter specifies whether to calculate the true PDSE percent used value in views WBSL (Data Set Locate) and WBVTOCD (VTOC SCAN Data Set Level Statistics), in policy interval collections, and in processing of any AUTODS commands. 

PERFRM_PRC

The PERFRM_PRC global parameter specifies the name of the procedure used to start the historical performance collector. The procedure is distributed in ?prefix .BBSAMP as member SGPPROC.

PKG_DSP2

The PKG_DSP2 global parameter indicates whether a second data space will be created and used by VTOC scan collection. When created, the VTOC scan collection process will use a separate data space from all other processes, including VTOC scan retrieval. This process lessens the possibility of out-of-storage conditions.

PKG_RELEASE

The PKG_RELEASE global parameter indicates whether system resources that are used to back virtual storage should be released when data space storage cells are freed. If yes, freed data space storage cells will no longer occupy space in central, expanded, or auxiliary storage.

POL_GROUP

The POL_GROUP global parameter defines the default policy to SVOS for any defined storage group in the SMPOOL xx member that does not have a policy specifically assigned to it. If a default policy is not supplied, any storage group that is defined in the SMPOOL xx member without being specifically defined to a policy will not be managed by policy definitions.

POL_POOL

The POL_POOL global parameter defines the default policy to SVOS for any defined pool in the SMPOOL xx member that does not have a policy specifically assigned to it. If a default policy is not supplied, any pool that is defined in the SMPOOL xx member without being specifically defined to a policy will not be managed by policy definitions.

POL_VOLUME

The POL_VOLUME global parameter defines the default policy to SVOS for any defined volume in the SMPOOL xx member that does not have a policy specifically assigned to it. If a default policy is not supplied, any volume that is defined in the SMPOOL xx member without being specifically defined to a policy will not be managed by policy definitions.

POLI

The POLI global parameter defines which SMPOLI xx policy member SVOS will use at startup. If this parameter is not defined, SVOS will start and display a notification message in the log. Data collection will not occur, nor will subsequent data logging or automation by policy definitions.

POOL

The POOL global parameter specifies the suffix of an SMPOOL xx member. SMPOOL xx contains non-SMS managed device pool definition parameters. It names pools and assigns volumes to pools.

PROCOLD

The PROCOLD global parameter specifies whether Allocation will intercept DD statements that specify OLD allocations. Allocation processing always intercepts NEW and MOD allocations.Allocation also intercepts DD statements that specify the UNIT parameter when PROCOLD=Y is specified, which is useful for correcting questionable JCL. For example, assume DASDPOOL pools a data set to a TEST volume. If a later step wants to use the data set and specifies UNIT=PROD, the job receives a JCL error. You can correct this situation by specifying PROCOLD=Y.

PROCOLD=Y is useful to override volsers that are hardcoded in JCL for old data sets. PROCOLD=Y will logically remove that hard-coded volume. However, use caution if you also specify JCLEXT=Y, which will assign a unit and volume from the catalog.

REJECT

The REJECT global parameter controls termination of processing at the first or last data set rejected by REJECT=YES in DASDPOOL or DSNCHECK.

REQTYPE

The REQTYPE global parameter specifies whether the MNTYPE statement in SPACVOLA is considered the request type instead of the mount type. For example, VOL=SER=WORK01 can be considered a private request even though the pack was mounted storage. MNTYPE defaults to the request type.

RLS

The RLS global parameter specifies whether the system should determine the VSAM Record Level Sharing environment available for DFSMShsm.

RVACOLL

The RVACOLL global parameter specifies whether to gather RVA data for SVA devices.

SCAT

The SCAT global parameter forces a catalog update to occur during the volume switch. By default, when SPACVOLA performs a volume switch on a permanent data set, the catalog is updated to contain the new volumes at step termination. For SMS-managed data sets, the catalog is always updated immediately.

SCHD

The SCHD global parameter defines which scheduled service (in SMSCHD xx PARMLIB member) SVOS will use at startup.

SGC_ADDEXIT

The SGC_ADDEXIT global parameter defines the name of application Add Exit.

SGC_CHKEXIT

The SGC_CHKEXIT global parameter defines the name of application Check Exit.

SGC_DEFEXIT

The SGC_DEFEXIT global parameter defines the name of application Default Exit.

SGC_KEYEXIT

The SGC_KEYEXIT global parameter defines the name of Account Code Build Exit.

SGC_SECEXIT

The SGC_SECEXIT global parameter defines the name of application Security Exit.

SGC_SELEXIT

The SGC_SELEXIT global parameter defines the name of application Select Exit.

SGC_STOGRP

The SGC_STOGRP global parameter specifies whether to retrieve SMS storage group information. This parameter can only be set to YES if SMS storage group information is required for FLST or RLST processing.

SGC_STORCLS

The SGC_STORCLS global parameter specifies whether to retrieve storage class information. This parameter can only be set to YES if SMS storage class information is required for FLST or RLST processing. SGC_STORCLS includes data class, management class, and storage class information.

SGCDSN

The SGCDSN global parameter specifies the data set name for the dynamic allocation/deallocation of application database DD, namely SGCDB. The dynamic allocation occurs with the start of the SVSGC component and deallocation occurs with the stop of SVSGC. This parameter is used only if the SGCDB DD statement is not present with the SVOS startup JCL.

SGMAXACCTn

The SGMAXACCTn global parameter specifies the maximum number of active accounts in the application database.

SGP_EXITBBS

The SGP_EXITBBS global parameter specifies the number of megabytes to allocate in a scope common data space for the performance exit buffer block.

SGP_EXITLIB

The SGP_EXITLIB global parameter specifies the default library where the performance collector SMF exits reside.

Note: EXITLIB in SGPPROC should point to the library that contains the exit load modules: SGPERU83 and SGPERU84. If EXITLIB is not coded or is left as a null in the Started Task, it will assume the default that is coded in SGP_EXITLIB (usually SYS1.LINKLIB). Change SGP_EXITLIB= to the appropriate load library.

SGP_MAXCCUS

The SGP_MAXCCUS global parameter defines the maximum number of control units that are in use during a single collection interval.

SGP_MAXDIRS

The SGP_MAXDIRS global parameter defines the maximum number of directors that are in use during a single collection interval.

SGP_MAXDSNS

The SGP_MAXDSNS global parameter defines the maximum number of data set names that are in use during a single collection interval.

SGP_MAXJOBS

The SGP_MAXJOBS global parameter defines the maximum number of jobs (batch, TSO, and Started Tasks) that are in use during a single collection interval.

SGP_MAXLCUS

The SGP_MAXLCUS global parameter defines the maximum number of logical control unit/CHIP combinations in use during an interval. This value is the maximum number of actual LCUs in use multiplied by the average number of CHPs carrying data traffic to the LCU.

SGP_MAXPOLS

The SGP_MAXPOLS global parameter defines the maximum number of pools that are in use during a single collection interval.

SGP_MAXPTHS

The SGP_MAXPTHS global parameter defines the maximum number of CHPIDs that are in use during a single collection interval. The minimum value is 1; the maximum value is 267000.

SGP_MAXPVLS

The SGP_MAXPVLS global parameter defines the maximum number of physical volumes that are in use during a single collection interval.

SGP_MAXRRKS

The SGP_MAX RRKS global parameter defines the maximum number of RAID ranks that are in use during a single collection interval.

SGP_MAXRSFS

The SGP_MAXRSFS global parameter defines the maximum number of RVA frames that are in use during a single collection interval.

SGP_MAXSCLS

The SGP_MAXSCLS global parameter defines the maximum number of storage classes that are in use during a single collection interval.

SGP_MAXVOLS

The SGP_MAXVOLS global parameter defines the total number of online DASD volumes on the z/OS image being monitored. Note that this parameter is the only SGP_MAX xxxx parameter that depends on neither the interval length nor the amount of activity on the system.

SGP_RDFCOMP

The SGP_RDFCOMP global parameter specifies whether data compression is in effect for records being written to the performance resource data files.

SGP_SIBSTK

The SGP_SIBSTK global parameter identifies the IXFP SIBBATCH parameter member to be used by the MainView SRM IXFP services for communications with the IXFP address space. The presence of this system parameter value indicates RVA collection is to be activated. This parameter must be specified to activate RVA collection in the performance collector. Without this parameter, the performance collector views will have a physical disk ID and box serial number of question marks. 

SGP_SMF42

The SGP_SMF42 global parameter determines if the SMF 42 record is written to the SMF data set. If set to NO, the historical performance data collector does not allow the record to be written.

SGP_TRACE

The SGP_TRACE global parameter specifies the trace default for the performance collector.

SHARED_VSAM

The SHARED_VSAM global parameter specifies whether SPACVOLA can bypass the check for shared enqueue on a VSAM data set when it is determining if the data set is allocated to another task. If more than one task holds the SYSDSN (major name) enqueue on a data set, a SPACVOLA recovery is not allowed and a SVM4463I DATA SET IS ALLOCATED TO ANOTHER JOB message is issued.

SIZEISPRIM

The SIZEISPRIM global parameter determines if the SIZE FLST/RLST parameter includes only the size of the primary extent or the size of the primary and one secondary extent.

SKIP

SMFID

The SMFID global parameter specifies the SMF record number for MainView SRM audit records written to the SMF data set.

Note: SMF message generation is also controlled by the SMF parameter on individual MainView SRM functions in member SMFUNCxx and by the SMF parameter on filter list specifications.

SMFRECOV

The SMFRECOV global parameter specifies whether MainView SRM recovery records should be written to the SMF data set. Recovery records are written on behalf of STOPX37 functions for both successful and failed recovery attempts.

SMS_ALLOC

The SMS_ALLOC global parameter specifies that SMSSELCT will be driven during DADSM ALLOCATE. If a POOL is coded in SMSPOOL, the current volume will be compared to the volumes in the POOL. If the current volume is not in a POOL assigned to the data set, the volume will be rejected with a DADSM return code of 4.

Note: The FLST/RLST parameter DADSM_FUNC should be used to limit the data sets that are processed by enabling this option.

SMS_EXTENDSM

The SMS_EXTEND global parameter specifies that SMSSELCT will be driven during DADSM EXTENDNV (new volume). If a POOL is coded in SMSPOOL_EXT, the current volume will be compared to the volumes in the POOL. If the current volume is not in a POOL assigned to the data set, the volume will be rejected with a DAD.

Note: The FLST/RLST parameter DADSM_FUNC should be used to limit the data sets that are processed by enabling this option.

SMSPOOL

The SMSPOOL global parameter specifies the suffix of the SMS pool member. An SMSPOLxx member contains device pool definition parameters. It names SMS subpools and assigns volumes to them.

SNAPDUMP

The SNAPDUMP global parameter controls whether SNAP dumps are produced for internal errors rather than SVC dumps. SNAPDUMP=YES produces SNAP dumps. BMC recommends the use of the default, SNAPDUMP=NO.

SPACPRIMACS

The SPACPRIMACS global parameter determines if SPACPRIM invokes the DFSMS ACS routines to obtain the list of available storage group(s) for a single-volume SMS allocation.When SPACPRIMACS is set to NO, MainView SRM uses the SPACPRIM RLST reduction percentage to lower the primary amount before making another attempt to satisfy the allocation request.

Depending on the available space in the storage group(s) and the original primary request, SPACPRIM can make multiple attempts to recover the allocation.

When SPACPRIMACS is set to YES, MainView SRM calls the DFSMS ACS routines to obtain the list of available storage groups for a single-volume allocation and determines available space before making another attempt to satisfy the allocation request. This typically leads to much better allocation performance, since SPACPRIM adjusts the primary to the available space and only makes one attempt to recover the allocation.

If you find SPACPRIM is causing your SMS allocations to select a volume from the wrong DFSMS storage pool, then your ACS routines could be using read-only ACS variables not supplied by MainView SRM during SPACPRIM recovery. MainView SRM supplies many of the DFSMS read-only ACS variables typically used to assign DASD storage group(s).

You might want to set SPACPRIMACS=NO if your ACS routines are using any of the following read-only ACS variables to assign DASD storage pools:

• &EXPDT
• &FILENUM
• &LABEL
• &LIBNAME
• &MEMHLQ
• &MEMLLQ
• &MEMN
• &MEMNQUAL
• &MSPARM
• &MSPDEST
• &MSPOLICY

Note: MainView SRM only invokes the DFSMS ACS routines for new data set allocations (&ACSENVIR=ALLOC). MainView SRM will not invoke the DFSMS ACS routines when a data set is being recalled by HSM.

START_ALL

The START_ALL global parameter specifies whether all components should be started. You can set this keyword to N to prevent all components from starting and to start only SVOS.

Note: You must set START_ALL=YES before the system will read any other START parameter.

START_ALLOC

The START_ALLOC global parameter specifies whether the Allocation component should be started. You can set this keyword to N to keep the Allocation component from starting in the event of a problem.

Note: You must set START_ALL=YES before the system will read any other START parameter.

START_AUTO

The START_AUTO global parameter specifies whether the automation component should be started. You can set this keyword to N to keep the automation component from starting in the event of a problem.

Note: You must set START_ALL=YES before the system will read any other START parameter.

START_CPF

The START_CPF global parameter specifies whether the catalog performance manager should be started. You can set this keyword to N to keep the catalog performance manager from starting.

START_EHSM

The START_EHSM global parameter specifies whether the HSM collector should be started. You can set this keyword to N to keep the HSM collector from starting in the event of a problem.

Note: You must set START_ALL=YES before the system will read any other START parameter.

START_RPRT

The START_RPRT global parameter specifies whether the Reporting component should be started. You can set this keyword to N to keep the Reporting component from starting in the event of a problem.

Note: You must set START_ALL=YES before the system will read any other START parameter.

START_SGC

The START_SGC global parameter specifies whether the application collector should be started. You can set this keyword to N to keep the application collector from starting in the event of a problem.

Note: You must set START_ALL=YES before the system will read any other START parameter.

START_SGD

The START_SGD global parameter specifies whether the space collector should be started. You can set this keyword to N to keep the space collector from starting in the event of a problem.

Note: You must set START_ALL=YES before the system will read any other START parameter.

START_SGP

The START_SGP global parameter specifies whether the performance collector should be started. You can set this keyword to N to keep the performance collector from starting in the event of a problem.

Note: You must set START_ALL=YES before the system will read any other START parameter.

STKSCR

The STKSCR global parameter specifies the default location of scratch tapes for the STKSUPP function.

STOPX37II

The STOPX37II global parameter specifies whether the Allocation or StopX37/II product will be started at system start-up.

STOR64B

The STOR64B global parameter sets the amount of 64-bit storage that will be allocated in Megabytes. MainView utilizes 64-bit storage. This parameter overrides the default value that is used by MVI for MainView SRM view processing.

SVALLOCWAIT

The SVALLOCWAIT global parameter specifies the number of minutes that SVALLOC waits for the ETILOAD ENQ to be released after a reply of WAIT to the SVO0623I message. If the ENQ has not been released after the specified time limit, SVOS issues the SVO0623I message again.

SYSLIB

TAPE_ATLLIB

The TAPE_ATLLIB global parameter specifies one or more automated tape library (ATL) library names. The TSCAN command obtains data for tape volumes located in these libraries. To prevent TSCAN from attempting to read ATL libraries, specify NONE as the first ATL library name.

TAPE_CA1DSN

The TAPE_CA1DSN global parameter specifies the data set name of the CA1 data set.

TAPE_CAT

The TAPE_CAT global parameter specifies the tape management systems available for report generation.

TAPE_CCTLTH

The TAPE_CCTLTH global parameter specifies the high-level qualifier for the Control-T data sets.

TAPE_CEAS

The TAPE_CEAS global parameter indicates whether the TSCAN output collection data set can reside in the extended address space (EAS) on an extended address volume (EAV) or not.

TAPE_CHLQ

The TAPE_CHLQ global parameter specifies the high-level qualifier for the TSCAN data sets.

Note: RELEASE cannot be turned on for TSCAN data sets.

TAPE_COLHSM

The TAPE_COLHSM global parameter specifies whether to collect DFSMShsm information.

TAPE_CPRI

The TAPE_CPRI global parameter specifies the number of cylinders for the primary allocation.

TAPE_CSEC

The TAPE_CSEC global parameter specifies the number of cylinders for the secondary allocation.

TAPE_CTLTRL

The TAPE_CTLTRL global parameter specifies the release number for Control-T.

TAPE_CVOL

The TAPE_CVOL global parameter specifies the volume serial numbers of the volumes to be used for the linear data sets, with a maximum of six volsers.

TAPE_DLMDEV

TAPE_RMMDSN

The TAPE_RMMDSN global parameter specifies the data set name for the RMM control data set.

TAPE_RMMEAS

The TAPE_RMMEAS global parameter indicates whether the TSCAN RMM extract data set can reside in the extended address space (EAS) on an extended address volume (EAV).

TAPE_RMMHLQ

The TAPE_RMMHLQ global parameter specifies the high-level qualifier for the TSCAN RMM Extract data sets.

Note: Use the TAPE_RMMHLQ parameter only at the request of BMC Software Customer Support. The extract files must be preallocated.

TAPE_RMMPRI

The TAPE_RMMPRI global parameter specifies the number of cylinders for the primary allocation for the TSCAN RMM extract file.

Note: Use the TAPE_RMMPRI parameter only at the request of BMC Customer Support.

TAPE_RMMSEC

The TAPE_RMMSEC global parameter specifies the number of cylinders for the secondary allocation for the TSCAN RMM extract file.

Note: Use the TAPE_RMMPRI parameter only at the request of BMC Customer Support.

TAPE_SGCIN

The TAPE_SGCIN global parameter specifies whether to include Application Collector data in the TAPE scan collection data set when SVSGC is active. Setting this keyword to YES causes the scan to determine the application names of all tape data sets being scanned. Determining these names significantly affects the scan's elapsed time and I/O. The default is NO (which does not determine application names).

TAPE_SMFDSn

The TAPE_SMFDSn global parameter specifies up to nine SMF data set names. If you skip a name in the order (for example, specifying SMFDS4 and SMFDS6 but not SMFDS5), processing stops at the first gap. In the preceding example, SMFDS6 would not be allocated. The SVOS TSCAN processes files that were created by IFSMFDP, not live VSAM files. If you do not want SMF data, do not specify the data set name.

Note: The SMF data set must be a copy of the active SMF data set. The active SMF data set cannot be used for this parameter. The SMF data set is required for collection of historical information only; otherwise, it is not necessary to include this parameter in the SMMSYSxx member.

TAPE_STCLAS

The TAPE_STCLAS global parameter specifies 1 to 4 mainframe storage classes to connect a virtual tape to an IBM TS7700 Series distributed library. The tape scan uses the virtual tape to collect IBM physical tape information from the distributed library.TAPE_STCLAS will work with TAPE_VTUNIT. Use NONE when a mainframe storage class or unit name is not needed to establish the connection. The following example shows the equivalent JCL statements for the TAPE_STCLAS and TAPE_VTUNIT parameters

TAPE_STCLAS=(STC1,NONE,STC3)
TAPE_VTUNIT=(NONE,UNIT2,UNIT3) //VirtualTape1 DD STORCLAS=STC1
//VirtualTape2 DD UNIT=UNIT2
//VirtualTape3 DD STORCLAS=STC3,UNIT=UNIT3

Note: Tape scan will only collect TS7700 Series physical tape information on JES2 systems.The distributed libraries associated with this parameter must be defined to the SMS configuration.

TAPE_VTSLIB

The TAPE_VTSLIB global parameter specifies one or more virtual tape server (VTS) library names. The TSCAN command obtains data for tape volumes located in these libraries. To prevent TSCAN from attempting to read VTS libraries, specify NONE as the first VTS library name.

TAPE_VTUNIT

The TAPE_VTUNIT global parameter specifies 1 to 4 unit names to connect a virtual tape to an IBM TS7700 Series distributed library. Tape scan will use the virtual tape to collect IBM physical tape information from the distributed library.TAPE_ VTUNIT will work with TAPE_STCLAS. Use NONE when a mainframe storage class or unit name is not needed to establish the connection.In the following example, the JCL shows the equivalent JCL statements for the TAPE_ parameters:TAPE_VTUNIT=(NONE,UNIT2,UNIT3) TAPE_STCLAS=(STC1,NONE,STC3) //VirtualTape1 DD STORCLAS=STC1 //VirtualTape2 DD UNIT=UNIT2 //VirtualTape3 DD STORCLAS=STC3,UNIT=UNIT3

Note: Tape scan will collect only TS7700 Series physical tape information on JES2 systems.The distributed libraries associated with this parameter must be defined to the SMS configuration.

TAPEGENR

The TAPEGENR global parameter specifies tape device generic names that some Allocation functions will intercept.If you want to intercept all tape requests, specify ALLTAPE as the first generic name. (However, you cannot use ALLTAPE when JCLEXT=N.) TAPEGENR affects functions DSNCHECK and SETEXPDT.

TRACEDD

The TRACEDD global parameter traces all MainView SRM functions for the job step containing the specified DD name. This is the same type of filter or rule list trace as produced by the TRACE parameter for the SMFUNCxx function definition; however, using TRACEDD, all MainView SRM functions will be traced for a single job step, based on the presence of a JCL DD name.

TRACEPAGES

The TRACEPAGES global parameter determines the number of virtual storage pages that are used for debugging s by MainView SRM Allocation. Because the number of storage pages affects CPU performance, the default should only be increased if you are instructed by BMC Software Customer Support. You can lower this number to 0 to turn off the tracing feature.

TRKCYL

The TRKCYL global parameter specifies the number of tracks per cylinder for the default device type. The value is used only if no default device geometry exists in the DFSMS SCDS base configuration.The default device geometry is used to convert space allocations to various metrics. The geometry is used by various functions and reporting views.

TRKLEN

The TRKLEN global parameter specifies the track length for the default device type. The value is used only if no default device geometry exists in the DFSMS SCDS base configuration.The default device geometry is used to convert space allocations to various metrics. The geometry is used by various functions and reporting views.

TSCAN_UNIT

The TSCAN_UNIT global parameter specifies the unit name of the output collection data set allocated during TSCAN operation.

USE_EMCAPI

The USE_EMCAPI global parameter is used to turn off the usage EMCSAI process.MainView SRM uses EMC services to gather data about EMC devices during SVOS initialization and refresh processing. Errors can be encountered during this process that might not be critical to users.

USE_NONBFIT

The USE_NONBFIT global parameter specifies whether MainView SRM should bypass the DFSMS non-best fit volume selection process when the IBM IDCAMS utility is used to define a SMS-managed data set in MVS releases after z/OS 1.7.

Note: The USE_NONBFIT parameter can be used on all MVS images. The parameter is ignored on systems running z/OS 1.7 (or below) and has no impact on DFSMS performance.

USECAT

The USECAT global parameter specifies whether the catalog name is used as a selection criteria in any MainView SRM ACS replacement function (SMSACSDC, SMSACSMC, SMSACSSC, SMSACSSG). USECAT can cause an embrace with catalog functions.

USEMVI

The USEMVI global parameter supports users who install and run only the StopX37/II Stand-Alone product.

VAR

The VAR global parameter specifies the suffix of the SMVARS xx member. SMVARS xx contains variables definition parameters. The values of defined variables are substituted in MainView SRM selection statements to simplify the specification of large selection criteria used in multiple statements.

VSAM_ADJ4GB

The VSAM_ADJ4GB global parameter controls StopX37/II recovery for non-extended VSAM data sets when new extent will exceed the 4GB limit. VSAM_ADJ4GB=YES allows StopX37/II to adjust the requested allocation amount to fit within the 4GB maximum limit.

VSAMJCL

The VSAMJCL global parameter controls the level of processing of VSAM data sets by Allocation.

VSAMLIMWARN

The VSAMLIMWARN global parameter specifies the percentage value to be used before issuing the MainView SRM 4GB limit message. This informational message shows how close a nonextended format VSAM file is to the 4-GB limit.

VSAMPRIM

The VSAMPRIM global parameter specifies that volume additions to a VSAM file (by SPACVOLA) will use the primary allocation size instead of the secondary. VSAMPRIM does not apply to multistripe VSAM and IBM DB2 VSAM data sets.

VSAMZSEC

The VSAMZSEC global parameter specifies which StopX37/II function controls recoveries for VSAM out-of-space conditions if no secondary allocation amount was specified when the data set was defined.

VSCAN_AGER1

The VSCAN_AGER1 global parameter specifies the high-end of age range one. Data sets that have not been used between zero days and this value fall into AGER1. The value is optional and is a one- to five-digit number. The number must be less than the remaining ranges.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER2

The VSCAN_AGER2 global parameter specifies the high end of age range two. Data sets that have not been used between AGER1 and this value fall into AGER2. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER3

The VSCAN_AGER3 global parameter specifies the high end of age range three. Data sets that have not been used between AGER2 and this value fall into AGER3. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER4

The VSCAN_AGER4 global parameter specifies the high end of age range four. Data sets that have not been used between AGER3 and this value fall into AGER4. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER5

The VSCAN_AGER5 global parameter specifies the high end of age range five. Data sets that have not been used between AGER4 and this value fall into AGER5. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER6

The VSCAN_AGER6 global parameter specifies the high end of age range six. Data sets that have not been used between AGER5 and this value fall into AGER6. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER7

The VSCAN_AGER7 global parameter specifies the high end of age range seven. Data sets that have not been used between AGER6 and this value fall into AGER7. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER8

The VSCAN_AGER8 global parameter specifies the high end of age range eight. Data sets that have not been used between AGER7 and this value fall into AGER8. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

VSCAN_AGER9

The VSCAN_AGER9 global parameter specifies the high end of age range nine. Data sets that have not been used between AGER8 and this value fall into AGER9. The value is optional and is a zero- to five-digit number. The number if specified, must be higher than the preceding ranges and less than the remaining ranges. When set to zero, the range is ignored. However, all remaining ranges must also be set to zero.If this parameter is updated, you must issue a VSCAN command, TSCAN command, and an MSCAN command before you can see the change in the related views.

Note: All data sets that exceed range nine fall into the tenth range. The tenth range is automatically set; it cannot be set by a user.

VSCAN_DCLAS

The VSCAN_DCLAS global parameter assigns the specified data class name to the VTOC scan temporary data set.

If VSCAN_DCLAS is specified, VSCAN_SCLAS is required.

Note: SMS data compaction can be used by the temporary data set by setting DSNTYPE=EXTENDED and COMPACTION=YES in the assigned data class. When a data class is specified, VTOC scan generates a permanent data set name for the temporary data set. This combination of parameters is required for data compaction to be allowed. The temporary data set is still deleted at the end of the scan.

VSCAN_DEAS

The VSCAN_DEAS global parameter indicates whether the VSCAN output collection data set can reside in the extended address space (EAS) on an extended address volume (EAV).

VSCAN_DIR

The VSCAN_DIR parameter indicates whether the VTOC scan collection data set directory should be maintained.

VSCAN_DPRI

The VSCAN_DPRI parameter indicates the primary allocation size of the VTOC scan collection data set directory.

VSCAN_DSEC

The VSCAN_DSEC parameter indicates the secondary allocation size of the VTOC scan collection data set directory.

VSCAN_DUNIT

The VSCAN_DUNIT parameter indicates the unit name of the VTOC scan collection data set directory.

VSCAN_DVOL

The VSCAN_DVOL parameter indicates the volume name of the VTOC scan collection data set directory.

VSCAN_MNTSK

The VSCAN_MNTSK global parameter specifies the minimum number of tasks (TCBs) used by the VTOC scan to perform the collection.

VSCAN_MXTSK

The VSCAN_MXTSK global parameter controls the number of tasks (TCBs) involved in scanning VTOCs for VTOC reporting and automation requests. It can also be used to affect the response given to automation requests.It can be used to affect the response given to automation and VSCAN command requests.

VSCAN_OEAS

The VSCAN_OEAS global parameter indicates whether the VSCAN output collection data set can reside in the extended address space (EAS) on an extended address volume (EAV) or not.

VSCAN_OCOMP

The VSCAN_OCOMP global parameter indicates whether to use compression on the VTOC scan collection data sets.

VSCAN_OINDX

The VSCAN_OINDX global parameter specifies the data set name prefix that is used when allocating VTOC scan collection data set. Dyymmdd.Thhmmss is appended to the prefix to complete the full data set name for other than the master file. This keyword value is also used for the MSCAN collection data set name. The format of the MSCAN collection data set is: oindx .MSCAN.MASTER

VSCAN_OPRI

The VSCAN_OPRI global parameter specifies the primary allocation size in cylinders for the VTOC scan collection data set.

VSCAN_OSEC

The VSCAN_OSEC global parameter specifies the secondary allocation size in cylinders for the VTOC scan collection data set.

VSCAN_OUNIT

The VSCAN_OUNIT global parameter specifies the device type of the VTOC scan collection data set. The VSCAN_OUNIT parameter must specify a direct access device type. If it does not, when a VTOC scan is initiated, message SVO5009E is issued and the scan is terminated.

VSCAN_OVOL

The VSCAN_OVOL global parameter specifies the volume serial number of the VTOC scan collection data set.

VSCAN_PCTR1

The VSCAN_PCTR1 global parameter specifies the high end of percentage used range one. Data sets that are between zero and this value fall into PCTR1. The value is optional and is a one- to three-digit number. Percent used refers to how full the data set is. The value must be less than the remaining percentage used values.

VSCAN_PCTR2

The VSCAN_PCTR2 global parameter specifies the high end of percentage used range two. Data sets that are between PCTR1 and this value fall into PCTR2. The value is optional and is a zero- to three-digit number. The number if specified, must be higher than the preceding values and less than the remaining values. When set to zero, the value is ignored. However, all remaining values must also be set to zero.

VSCAN_PCTR3

The VSCAN_PCTR3 global parameter specifies the high end of percentage used range three. Data sets that are between PCTR2 and this value fall into PCTR3. The value is optional and is a zero- to three-digit number. The number if specified, must be higher than the preceding values and less than the remaining values. When set to zero, the value is ignored. However, all remaining values must also be set to zero.

VSCAN_PCTR4

The VSCAN_PCTR4 global parameter specifies the high end of percentage used range four. Data sets that are between PCTR3 and this value fall into PCTR4. The value is optional and is a zero- to three-digit number. The number if specified, must be higher than the preceding values and less than the remaining values. When set to zero, the value is ignored. However, all remaining values must also be set to zero.