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.
Consider the following:
This option is available only on JES2 systems.
Enables concurrent read access to Virtual Volumes that CA Disk created. Also enables multiple, simultaneous read access for CA Disk ARCHVOLS on any LPAR.
Valid values:
Default: NONE
Feature: Virtual Device Engine
Determines if validation is bypassed when updating the Virtual Device UCB's at startup.
Valid Values:
Bypasses validation.
Does not bypass validation.
Default: N
Feature: Virtual Device Engine
Specifies the SMS data class construct name the system uses to define work data sets dynamically.
Multiple CA Vtape Subsystems that share the Global VCAT also automatically share and reference the same SMS construct names.
Valid Values: Valid DFSMS Data Class name
Set this value with the Data Class that CA Vtape uses to allocate temporary work data sets dynamically.
Note: The value set for this attribute is shared with all 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, automatically broadcasts the change to all other Subsystems.
Default: NONE
Feature: Miscellaneous
Specifies the SMS storage class construct name that CA Vtape uses to define work data sets dynamically.
Multiple CA Vtape Subsystems that share the Global VCAT automatically share and reference the same SMS construct names.
Valid Values: A Valid DFSMS Storage Class name
Set this value with the Storage Class that CA Vtapeuses to allocate work data sets dynamically.
Note: The value set for this attribute is being shared with all other 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, automatically broadcasts the change to all other Subsystems.
Default: NONE
Feature: Miscellaneous
Determines if JCL or dynamic allocation is used to allocate the BSDS1.
Valid Values:
Indicates that the BSDS1 DD in the SVTSCE 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 SVTSCE JCL procedure, it must point to the same data set name coded for the attribute. An inconsistency generates a critical error aborting startup. Commenting out or deleting the BSDS1 DD in the SVTSCE 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 SVTSCE 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 SVTSCE JCL procedure, it must point to the same data set name coded for the attribute. An inconsistency generates a critical error aborting startup. Commenting out or deleting the GLOBAL DD in the SVTSCE 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.
Valid Values:
Indicates that the VCAT DD in the SVTSCE 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 generates a critical error aborting startup. Commenting out or deleting the VCAT DD in the SVTSCE 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 SVT1 to CAVTAPE.PD02.SVT1VCAT.
Default: JCL
Feature: Miscellaneous
Specifies the size, in kilobytes, of the ECSA area to store event log records temporarily 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 that the Internal Logger uses for event log records. A typical loaded environment with LogDetailLevel=1 and the default of 8 MBs holds 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 that CA Vtape issues.
Note: Do not change the default value unless there is another application using the same message prefix value as CA Vtape.
Valid Values:
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 start with SVT1 as in SVT1R0200E. All messages issued by Subsystem SVT2 start with SVT2 as in SVT2R0200E.
If you enter four characters (for example SVTS) all messages that the Subsystems using this Parmlib issue, 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. Upon shutdown, the system issues SETIOS commands to set the MIH value to two seconds for the now unusable Virtual Devices.
We recommend a setting of 30 seconds.
Do not set this attribute to a value higher than 60 seconds. Contact CA 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, set this attribute to a value of -1. When MIHTimoutValue is set to a value of -1, CA Vtape does not set the MIH timeout.
Important! If you set this attribute to a value of -1 and you 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 can require an IPL to correct.
Valid Values: -1 to 9999
Default: 15
Feature: Virtual Device Engine
Determines the route code or codes that CA Vtape uses 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 that CA Vtape uses 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 sub address spaces for Virtual Control Units.
Valid Values:
Indicates that the sub address spaces start with a copy of the SVTSCE JCL procedure which has been copied to a member with this name.
Indicates that the sub address spaces start with the same JCL procedure the main task was started with.
Default: &JOBNAME
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 system loads the runtime modules from the STEPLIB DD or a link listed data set and is not 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 a Virtual Control Unit is restarted, the run-time modules are loaded from the STEPLIB DD or a link-listed loadlib. If the modules loaded do not match the maintenance level of the modules the other sub address spaces use, an error report is 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.LIBn where prefix is the CA Vtape data set prefix, xxxxxx is the creation date, yyyyyy is the creation time, and n is the last digit of the Subsystem number (1-8). The temporary loadlib is dynamically APF-authorized and loaded with the modules found in the SVTSCE 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 is then used to start all the CA Vtape started tasks in this Subsystem. If 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 shut down.
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. Stop and start the entire Subsystem so that the changed modules load.
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 SVTSCE JCL procedure. 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.
Start the data set name with the CA Vtape DSN prefix to avoid more security authorizations.
Note: When running in Automatic or Library mode, if a startup error occurs with allocating, accessing, loading, or dynamically APF-authorizing the loadlib, CA Vtape issues error messages and terminates the startup.
Default: Automatic
Feature: Miscellaneous
Determines if CA Vtape updates the Channel Measurement Block (CMB) of the Virtual Devices. This information is collected and reported on by the Resource Measurement Facility (RMF).
Valid Values:
CA Vtape updates the CMB.
CA Vtape does not update the CMB.
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 CPUs 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 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. 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 do not have a zIIP processor installed. When you run in a z9 or later CPUx without a zIIP processor installed, you can specify this value and PercentRunOnZIIP = 100 to simulate zIIP eligibility for capacity planning purposes. For more information about monitoring and performing capacity planning for zIIP processors, see "Performance."
Indicates that CA Vtape does not use the zIIP processor.
Default: N
Feature: Virtual Device Engine
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|