This section contains an alphabetic list of the Startup Options attributes. The list includes a description of each attribute, its valid values, and the CA Vtape features it supports.
Observe the following:
This option is available only on JES2 systems and only if CacheManagement=Dynamic is enabled.
Enables concurrent read access to Virtual Volumes that were created by CA Disk and enables multiple, simultaneous read access for CA Disk ARCHVOLS on any LPAR.
Valid values:
Default: NONE
Feature: Virtual Device Engine
Determines whether offline physical devices should be bypassed or considered available during allocation for Externalization and Recall tasks,.
Valid Values:
Will bypass (not include) offline physical tape drives.
Will not bypass (include) offline physical tape drives.
Default: Y
Feature: Backstore Engine
Determines if validation should be bypassed when updating the Virtual Device UCB's at startup.
Valid Values:
Will not bypass validation.
Will bypass validation.
Default: N
Feature: Virtual Device Engine
Valid Values:
A SMS Data Class is not being defined. Set this value only when CacheManagement=STATIC.
Clears the SMS Data Class shared across subsystems from the Global VCAT. Set this value only when converting all the subsystems from DYNAMIC to STATIC.
Set this value with the Data Class to be used by CA Vtape to dynamically allocate Virtual Volumes. A valid Data Class defined with the following attributes is required when CacheManagement=DYNAMIC:
Volume Count . . . . . . : 16 Data Set Name Type . . . : EXTENDED If Extended . . . . . . : REQUIRED Extended Addressability : NO Record Access Bias . . : USER Space Constraint Relief . : YES Reduce Space Up To (%) : 50 Dynamic Volume Count . : 59
Note: The value set for this attribute is being shared with all other CA Vtape subsystems through the Global VCAT. Any subsystem starting with a new setting that is accepted by the operator by replying (Y)es to the SVTnI3301I console message will automatically broadcast the change to all other subsystems.
Default: NONE
Feature: Miscellaneous
Specifies the SMS storage class construct name used to dynamically define VSAM linear data sets used as cache buffers for Virtual Volumes or Virtual Control Units.
Multiple CA Vtape subsystems sharing the same Global VCAT automatically share and reference the same SMS construct names. This is necessary to consistently manage the DASD cache space within the storage class.
Valid Values:
A SMS Storage Class is not being defined. Set this value only when CacheManagement=STATIC.
Clears the SMS Storage Class shared across subsystems from the Global VCAT. Set this value only when converting all the subsystems from DYNAMIC to STATIC.
Set this value with the Storage Class to be used by CA Vtape to dynamically allocate Virtual Volumes. Use of a valid Storage Class associated in your Storage Group ACS with the designated CA Vtape Storage Groups is required when CacheManagement=DYNAMIC is specified.
Note: The value set for this attribute is being shared with all other CA Vtape subsystems from the Global VCAT. Any subsystem starting with a new setting that is accepted by the operator by replying (Y)es to the SVTnI3301I console message will automatically broadcast the change to all other subsystems.
Default: NONE
Feature: Miscellaneous
Determines the type of DASD cache space assigned for new scratch mounts of Virtual Volumes.
Valid Values:
Is based on DIV I/O services, requires 10 pre-allocated VSAM LDS data sets per Virtual Volume, and can be used with or without SMS.
Is based on SMS Media Manager I/O services, requires a single dynamically allocated SMS managed VSAM data set per Virtual Volume, and generates less CPU overhead than STATIC.
Default: STATIC
Feature: Virtual Device Engine
Determines if JCL or dynamic allocation is used to allocate the BSDS1.
Valid Values:
Indicates that the BSDS1 DD in the JCL procedure should be used to allocate the BSDS1 data set.
Indicates that dynamic allocation should be used to allocate the BSDS1 data set. If the BSDS1 DD is coded in the SVTS JCL procedure, it must point to the same data set name coded for the attribute. An inconsistency will generate a critical error aborting the subsystem initialization. Commenting out or deleting the BSDS1 DD in the SVTS JCL procedure would be recommended if the BSDS1 data set name is coded for this attribute.
Default: JCL
Feature: Miscellaneous
Determines if JCL or dynamic allocation is used to allocate the Global VCAT.
Valid Values:
Indicates that the GLOBAL DD in the JCL procedure should be used to allocate the Global VCAT.
Indicates that dynamic allocation should be used to allocate the Global VCAT. If the GLOBAL DD is coded in the SVTS JCL procedure, it must point to the same data set name coded for the attribute. An inconsistency will generate a critical error aborting the subsystem initialization. Commenting out or deleting the GLOBAL DD in the SVTS JCL procedure would be recommended if the Global VCAT data set name is coded for this attribute.
Default: JCL
Feature: Miscellaneous
Determines if JCL allocation or dynamic allocation is used to allocate the Local VCAT. The default value of JCK indicates that the VCAT DD in the JCL procedure should be used to allocate the Local VCAT.
Valid Values:
Indicates that the VCAT DD in the JCL procedure should be used to allocate the Local VCAT.
Indicates that dynamic allocation should be used to allocate the Local VCAT. If the VCAT DD is coded in the SVTS JCL procedure, it must point to the same data set name coded for the attribute. An inconsistency will generate a critical error aborting the subsystem initialization. Commenting out or deleting the VCAT DD in the SVTS JCL procedure would be recommended if the Local VCAT data set name is coded for this attribute.
The Local VCAT name can be coded using variables like &SYSID and &SVST, as in the following example:
DsnameLocalVCAT='CAVTAPE.&SYSID..&SVTS.VCAT'
These variables would be expanded on LPAR PD02 for CA Vtape subsystem 1 to CAVTAPE.PD02.SVT1VCAT.
Default: JCL
Feature: Miscellaneous
Indicates the number of online local virtual devices that your site is licensed to use. In a CA Vtape complex, SVTS will validate that the number of active online local virtual devices in use does not exceed this value. The default value of -1, prevents SVTS from checking the number of online local devices.
If the value is left at -1, an SVT1IR507I message requesting the value be changed will be issued every eight hours by every CA Vtape Subsystem running with the -1 value.
Valid Values: -1 to 32767
Default: -1
Feature: Miscellaneous
Indicates the number of online remote Virtual Devices that your site is licensed to use. Will bypass validation. In a CA Vtape complex, SVTS will validate that the number of active online remote Virtual Devices in use does not exceed this value. The value of -1, prevents SVTS from checking the number of online remote devices. The default value of 0 indicates that there are no licensed remote virtual drives.
If the value is set to -1, an SVT1IR507I message requesting the value be changed will be issued every eight hours by every CA Vtape Subsystem running with the -1 value.
Valid Values: -1 to 32767
Default: 0
Feature: Miscellaneous
Specifies the size, in kilobytes, of the ECSA area to temporarily store event log records when the log dataspace cannot be accessed. This area is acquired during CA Vtape initialization. You do not need to change the size unless the logger files are found to be missing records.
Valid Values: 4 to 16
Default: 8
Feature: Logger
Specifies the size, in megabytes, of the dataspace used by the Internal Logger for event log records. A typical loaded environment with LogDetailLevel=1 and the default of 8 MBs will hold the last 45-60 minutes of event log records.
Valid Values: 1 to 16
Default: 8
Feature: Logger
Determines the four characters used as a message prefix for all messages issued by CA Vtape.
Note: The default value should not be changed unless there is another software product using the same message prefix value as CA Vtape.
Valid Values:
Will be translated to the CA Vtape subsystem number, SVTn, where n is 1-8, depending on which subsystem issues the message. For example, all messages issued by subsystem SVT1 will start with SVT1 as in SVT1R0200E. All messages issued by subsystem SVT2 will start with SVT2 as in SVT2R0200E.
If four characters are entered, for example SVTS, all messages issued by all CA Vtape subsystems using this parmlib will start with SVTS as in SVTSR0200E.
Default: &SVTS
Feature: Miscellaneous
Specifies the Missing Interrupt Handler (MIH) timeout value in seconds. CA Vtape issues SETIOS commands to set the MIH timeout for its Virtual Devices to this value at startup. At shutdown SETIOS commands are issued to set the MIH value to 2 seconds for the now unusable Virtual Devices.
The MIH timeout interval is dependent on environmental conditions like DASD cache volume response times and the number of chained CCW’s in an I/O channel program. If DASD cache volume response times are high or applications like DB2 or Syncsort are writing to Virtual Volumes, a higher value for this attribute will be required. We recommend a setting of 30 seconds.
In general, this attribute should not be set to a value higher than 60 seconds without first discussing the change with CA Technical Support.
If you do not want CA Vtape to set the MIH timeout value for its Virtual Devices and have a process outside of CA Vtape to set the value, you can set this attribute to a value of -1. When MIHTimoutValue is set to a value of -1, CA Vtape will not set the MIH timeout.
Important! If you set this attribute to a value of -1 and do not use a process outside of CA Vtape to set the MIH timeout for the Virtual Devices to an appropriate value or set an inappropriate value, you could provoke mount pending situations and IOS errors. This could result in the Virtual Devices being fenced or boxed which might require an IPL to correct.
Valid Values: -1 to 9999
Default: 15
Feature: Virtual Device Engine
This attribute is used by USS Backstore to describe the directory under which to mount file systems. CA Vtape creates subdirectories under the RootDirectory for the CA Vtape Complex and the USS mount points.
Valid Value: A valid USS directory name that the CA Vtape subsystem is authorized to use and has permissions for read/write access.
Default: /u/users/vtape
Feature: UNIX System Services
Determines the route code or codes to be used by CA Vtape for high priority console messages.
Valid Values:
Indicates that a route code of 1 (master console) should be used.
Indicates the single route code to use for high priority console messages.
Indicates the multiple route codes to use for high priority console messages.
Default: -1
Feature: Miscellaneous
Determines the route code or codes to be used by CA Vtape for normal priority console messages.
Valid Values:
Indicates that the ROUTCODE keyword value on the DEFAULT statement in the CONSOLxx member of SYS1.PARMLIB or SYSn.IPLPARM should be used.
Indicates the single route code to use for normal priority console messages.
Indicates the multiple route codes to use for normal priority console messages.
Default: -1
Feature: Miscellaneous
Specifies the JCL procedure name to use when starting the Backstore Engine, Virtual Controller, and Utility address spaces.
Valid Values: A valid JCL procedure library member
Default: SVTSAS
Feature: Miscellaneous
Determines if Split Maintenance-Level Protection is off or running in Steplib, Automatic, or Library mode. Split Maintenance-Level Protection prevents the CA Vtape address spaces from being started or restarted with different maintenance levels and issues warning messages when mismatched maintenance levels are detected.
Valid Values:
Turns off Split Maintenance-Level Protection. The runtime modules will be loaded from the STEPLIB DD or a link listed data set and will not be validated.
This mode activates Split Maintenance-Level Protection and loads the run-time modules from the STEPLIB DDs in the started task JCL procedures or a link-listed loadlib. If the Backstore Engine or a Virtual Control Unit is restarted, the run-time modules will be loaded from the STEPLIB DD in the SVTSAS JCL procedure or a link-listed loadlib. If the modules loaded do not match the maintenance level of the modules used by the other SVTSAS tasks, an error report will be produced and repeated every 60 seconds.
This mode activates Split Maintenance-Level Protection and is the recommended setting. In this mode a temporary loadlib or Tasklib is dynamically allocated using the name prefix.Dxxxxxx.Tyyyyyy.LOAD where prefix is the CA Vtape data set prefix, xxxxxx is the creation date, and yyyyyy is the creation time. The temporary loadlib will be dynamically APF-authorized and loaded with the modules found in the SVTS JCL procedure STEPLIB DD. Dynamic APF authorization requires that CA Vtape have UPDATE access to the FACILITY class CSVAPF if this is secured. The temporary loadlib will then be used to start all the CA Vtape started tasks in this subsystem. If the Backstore Engine or a Virtual Control Unit is restarted, the temporary loadlib is used. The STEPLIB DD loadlibs and link-listed loadlibs are ignored. The temporary loadlib is deleted when CA Vtape is shutdown.
This mode allows maintenance to be applied to a loadlib referred to by the STEPLIB DD or in the link-list without any impact while CA Vtape is running. The changed modules will not be loaded until the entire subsystem is stopped and started.
Known as library mode, this setting activates Split Maintenance-Level Protection. It is the same as Automatic mode except that the loadlib data set name coded as the attribute value is used in place of a dynamically allocated loadlib. The loadlib data set name must contain at least two nodes and must not be present in the STEPLIB DD in the SVTS and SVTSAS JCL procedures. If the loadlib is not APF authorized, it will be dynamically APF authorized by CA Vtape. Dynamic APF authorization requires that CA Vtape have UPDATE access to the FACILITY class CSVAPF if this is secured.
The data set name used should start with the CA Vtape DSN prefix to avoid additional security authorizations.
Note: When running in Automatic or Library mode, if an error occurs during start up with allocating, accessing, loading, or dynamically APF-authorizing the loadlib, CA Vtape will issue error messages and automatically change to Steplib mode.
Default: Disabled
Feature: Miscellaneous
Enables or disables USS Backstore.
Valid Values:
Enables USS Backstore.
Disables USS Backstore.
Default: N
Feature: UNIX System Services
Determines if CA Vtape will update the Channel Measurement Block (CMB) of the Virtual Devices. This information is collected and reported on by the Resource Measurement Facility (RMF).
Valid Values:
Will cause the CMB to be updated.
Will cause the CMB to not be updated.
Default: Y
Feature: Miscellaneous
Determines if CA Vtape is to use the zIIP processor. This attribute should only be specified if your system supports the zIIP processor (z9 and later systems with the required level of z/OS). A companion parameter in the DynamicOptions Section is required to specify what percentage of CA Vtape work is to be made eligible to run on the zIIP, see the PercentRunOnZIIP= attribute in this chapter.
Valid Values:
Indicates that CA Vtape is to use the zIIP processor. You must also specify a value greater than 0 for the PercentRunOnZIIP attribute in the Dynamic Options member to cause work to be made eligible for the zIIP. You can specify this value even if you don't have a zIIP processor installed; when you run in a z9 system without a zIIP processor installed you can specify this value and PercentRunOnZIIP = 100 to simulate zIIP eligibility for capacity planning purposes. See Operational Considerations to find additional details on how to monitor and perform capacity planning for zIIP processors.
Indicates that CA Vtape will not use the zIIP processor.
Default: N
Feature: Virtual Device Engine
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|