This section contains an alphabetic list of the attributes that can be coded in the customizable Group Sections. The list contains a description of each attribute, its valid values, and the CA Vtape features it supports. Unless specifically noted, each attribute is considered local in scope.
Defines which subgroups are to be automated.
None indicates that all the subgroups for groups using this attribute are not automated. The corresponding Externalization Subgroup Queues will not be automatically released and held by Externalization Automation. None is a stand-alone value that cannot be combined with the other valid settings. If None is combined with the other valid settings an SVTnQQ412E error message will be issued.
Any combination of S,M,L indicates that the subgroup or subgroups coded are automated for the groups using this attribute. The corresponding Externalization Subgroup Queues will be automatically released and held by Externalization Automation. This attribute determines which of the three subgroups in a group are automated. If none of the subgroups in a group are automated, the attribute should be commented out or deleted.
The S, M, L, Short, Medium, and Long values for this attribute can be specified in any order or combination in a comma-separated list or with separate attribute statements.
The following are examples of single attributes with one or more values:
In this example, instead of entering AutomatedSubgroups=Long,M,S as a single attribute statement with multiple values, the same information is entered as separate attribute statements with the following single values:
Subgroups that are automated are automatically released and held by the Externalization Server based on DASD buffer threshold settings and time schedules determined by the following attributes in the Dynamic Options Section:
Note: For more information about Subgroup Automation, see the chapter “Operational Considerations.”
Valid Values:
Default: None | N
Section: Group Sections
Feature: Backstore Engine
Defines the block size used by the Backstore Engine to Externalize Virtual Volumes queued to this group.
You can specify a different block size value for each group.
If 0K is specified CA Vtape will select a block size based on one of the following output device types:
Valid Values:
Default: 16K
Section: Group Sections
Feature: Backstore Engine
Determines the externalization priority assigned to a group. This priority is used by the Externalization Server to determine which group's Backstore Subgroup Queues should be Externalized first. Zero is the lowest priority. Nine is the highest priority.
Several other factors are considered when starting a subgroup:
Valid Values: 0 to 9
Default: 1
Section: Group Sections
Feature: Backstore Engine
Determines the number of seconds that the Backstore Engine will wait for a tape mount before issuing a message to the operator stating that the mount is taking longer than expected.
Valid Values:
Indicates the message should never be issued.
Indicates the number of seconds to wait before issuing the message.
Section: Group Sections
Feature: Backstore Engine
Determines which Backstore Tapes are to be written with CA Tape Encryption.
Valid Values:
Do not encrypt the Backstore Tapes.
Encrypt only the Primary Backstore Tape.
Encrypt only the Duplex Backstore Tape.
Encrypt the Primary and Duplex Backstore Tapes.
Note: When this attribute is set to a value other than NONE, the BrightStorEncryptionDC attribute must specify the SMS DATACLASS defined for CA Tape Encryption services.
Default: NONE
Section: Group Sections
Feature: Backstore Engine
Specifies the SMS DATACLASS name enabling encryption services provided by CA Tape Encryption. Review CA Tape Encryption documentation for instruction on how to setup the DATACLASS to enable encryption.
Note: When this attribute is set to a value other than NONE, the BrightStorEncryption attribute must be set to PRIMARY, DUPLEX, or BOTH.
Valid Values:
Default: NONE
Section: Group Sections
Feature: Backstore Engine
Determines the number of hours that a Virtual Volume will remain resident in DASD cache after externalization. The actual cache expiration date and time is calculated using the Virtual Volume last reference date.
If all of your Virtual Volumes are in the same group or you do not wish to use this feature, leave CacheResidenceHours set to the default value of zero.
Note: Cache utilization may be such that it will be impossible to honor this parameter absolutely. If CA Vtape cannot honor the requested hours, the SVTnVQ432I message will be issued with a date and time higher than the current date and time.
Valid Values: 0 to 999
Default: 0
Section: Group Sections
Feature: Miscellaneous
Determines the subgroup that catalog managed or catalog control date Virtual Volumes will be assigned to. The catalog managed date value used is determined by the CatalogManagedDate attribute in the Dynamic Options Section.
Valid Values:
Indicates that catalog managed date Virtual Volumes should be assigned to the Short Subgroup.
Indicates that catalog managed date Virtual Volumes should be assigned to the Medium Subgroup.
Indicates that catalog managed date Virtual Volumes should be assigned to the Long Subgroup.
Default: L
Section: Group Sections
Feature: Backstore Engine
Determines the title line displayed for the group in the ISPF Interface on the Subgroup Display Panel and the Externalization Queue Display Panel under the Group List option. The value is limited to 30 characters.
Valid Values: 'Any 30 characters'
Section: Group Sections
Feature: Miscellaneous
Determines the unit esoteric or generic that will be used to dynamically allocate a non-CA Vtape tape drive for Externalization or Recycle for the duplex output tape. If a duplex tape should not be written, this attribute should be deleted from the Group Section or commented out by typing a semi-colon (;) at the start of the line.
Note: If the unit esoteric or generic contains special characters, it must be enclosed in single quotes. For example, 3590-1 would be coded as Duplex='3590-1'.
Valid Values: A valid unit esoteric or generic
Section: Group Sections
Feature: Backstore Engine / Recycle
Determines whether the data is transmitted to the remote system when the Virtual Volume is created. This setting is only in effect for scratch mounts.
Note: The local system's attribute is propagated to the remote. The remote's attribute is ignored.
Valid Values:
Virtual volume data is transmitted and written at both sites during volume creation. Virtual drive IO throughput is throttled by the bandwidth and performance of the network.
Only metadata is transmitted during volume creation, minimizing network traffic as the virtual volume is created. Virtual Volume data is never transmitted unless a remote mount request is issued by the remote system. If the local system is not connected, the remote system cannot access the data.
Like (Y)es, only metadata is transmitted during volume creation, minimizing network traffic as the Virtual Volume is created. However, unlike (Y), the virtual volume is queued for Externalization. When Externalization is run at the remote site, the Virtual Volume data will be transmitted. A remote mount request issued by the remote system will also transmit the Virtual Volume data. If the local system is not connected, the remote system cannot access the data.
Note: The HLQ.CCUUJCL(DEFERXMT) job may be used to trigger the transmission of the data prior to Externalization.
Valid Values:
Default: N
Section: Group Sections
Feature: PeerToPeer
Determines the unit esoteric or generic that will be used to dynamically allocate a non-CA Vtape tape drive for Externalization for the export output tape. Blank indicates that an Export tape should not be written. If an export tape should not be written, this attribute should be deleted from the Group Section or commented out by typing a semi-colon (;) at the start of the line.
Note: If the unit esoteric or generic contains special characters, it must be enclosed in single quotes. For example, 3590-1 would be coded as Export='3590-1'.
Note: This attribute is mutually exclusive of the Triplex attribute meaning they cannot both be specified for a Group Section.
Valid Values: A valid unit esoteric or generic
Section: Group Sections
Feature: Backstore Engine
Determines if compression should be performed on data written to Virtual Volumes in the DASD buffer that are assigned to this group.
Note: This attribute is only active if the HardwareCompressionOption attribute in the Dynamic Options Section is set to GROUP.
Valid Values:
Indicates that compression should never be performed.
Indicates that compression should always be performed.
Indicates that compression should be performed if TRTCH=COMP is coded in the JCL or if COMPACT=YES was used when defining the Virtual Devices. If TRTCH=NOCOMP is coded in the JCL, compression will not be performed.
Note: For more information about Virtual Volume Compression, see the chapter “Operational Considerations.”
Default: N
Section: Group Sections
Feature: DASD Buffer Compression
Determines the maximum amount of data in each 50 MB segment of data written to a Virtual Volume that will be compressed. This percentage is directly related to the amount of CPU used by compression. If, for example, this percentage is set to 75, only 75% of the data written will be compressed and only 75% of the CPU that would have been used by compression is actually used.
Note: This attribute is only active if the HardwareCompressionOption attribute in the Dynamic Options Section is set to GROUP.
Valid Values:
Indicates that no data should be compressed. This setting should only be used temporarily. If compression should be turned off permanently, the HardwareCompressionOption attribute should be used.
Indicates the actual percentage of data written that should be compressed. If set to 50, only 50% of each 50 MBs of data written to a Virtual Volume will be compressed.
Indicates compress all the data.
Note: For more information about Virtual Volume Compression, see the chapter “Operational Considerations.”
Default: 100
Section: Group Sections
Feature: DASD Buffer Compression
Determines when additional Externalization subtasks should be started to Externalize the data in the subgroup faster. The amount queued for Externalization in the subgroup queue is divided by the MB_Threshold value and rounded to the next lowest whole number. For example, if 5000 MBs were queued in the subgroup and the threshold is set to the default of 2000 MBs, 5000 divided by 2000 would be 2.5 rounded down to 2. The Backstore Engine will try to start two Externalization subtasks for this subgroup.
Valid Values: 1 to 999999
Default: 2000
Section: Group Sections
Feature: Backstore Engine
Determines the upper limit for the number of days of retention that will cause a Virtual Volume to be assigned to the Medium Subgroup. Zero can only be used when ShortRetention is also set to zero. When a number other than zero is coded, it must be greater than the ShortRetention value.
Valid Values:
Indicates that Virtual Volumes with normal-dated retention should not be assigned to the Medium Subgroup. Virtual Volumes with never-expire (permanent), catalog control, or special retention dates can still be assigned to the Medium Subgroup. If the Medium Subgroup should not be used, you must set the NeverExpireSubgroup, CatalogManagedSubgroup, and SpecialRetentionSubgroup attributes to a value other than “M”.
Indicates the number of days of retention for assignment to the Medium Subgroup. If a Virtual Volume has a number of retention days greater than the ShortRetention value and less than or equal to the MediumRetention value, it will be assigned to the Medium Subgroup.
Section: Group Sections
Feature: Subgroup Assignment
Determines the minimum compression percentage that must be achieved to continue compressing a 50 MB segment of a Virtual Volume being written. Compression is tested every 50 MBs of each Virtual Volume to determine the best compression method to use.
Note: This attribute is only active if the HardwareCompressionOption attribute in the Dynamic Options Section is set to GROUP.
Note: For more information about Virtual Volume Compression, see the chapter “Operational Considerations.”
Valid Values: 1 to 100
Section: Group Sections
Feature: DASD Buffer Compression
Determines the subgroup that never-expire or permanent retention date Virtual Volumes will be assigned to. The never-expire date value used is determined by the NeverExpireDate attribute in the Dynamic Options Section.
Valid Values:
Indicates that never-expire date Virtual Volumes should be assigned to the Short Subgroup.
Indicates that never-expire date Virtual Volumes should be assigned to the Medium Subgroup.
Indicates that never-expire date Virtual Volumes should be assigned to the Long Subgroup.
Default: L
Section: Group Sections
Feature: Backstore Engine
Determines if any copies of the backstore should be excluded from Recall processing. This attribute facilitates sending copies of Virtual Volumes offsite so only the available copy is considered for Recalls.
Valid Values:
Default: None
Section: Group Sections
Feature: Backstore Engine
Determines whether a Primary Backstore Tape Copy of the Virtual Volumes assigned to a group will be created and where to write it. This is a required attribute that must be coded in each Group Section.
Specifying TEMPONLY alters the behavior of the Virtual Volume's retention by immediately placing the volume on the free queue. The volume's retention is then controlled by the CacheResidenceHours attribute.
Note: If the unit esoteric or generic contains special characters, it must be enclosed in single quotes. For example, 3590-1 would be coded as Primary='3590-1'.
Valid Values:
A non-CA Vtape unit esoteric or generic will cause the appropriate device type to be dynamically allocated by Externalization and Recycle. A Primary Backstore Tape Copy will be created for the Virtual Volumes.
Indicates that the Virtual Volumes should not be Externalized. A Primary Backstore Tape Copy will not be created for the Virtual Volumes. These Virtual Volumes will reside in cache until they are scratched.
Indicates that the Virtual Volumes should not be Externalized. A Primary Backstore Tape Copy will not be created for the Virtual Volumes. The Virtual Volumes will reside in cache until their CacheResidenceHours limit is reached and/or space is needed in the DASD cache.
Important! TEMPONLY volumes can be deleted from cache and the data is never Externalized. If the data should be saved, TEMPONLY should not be usedor another system must Externalize them, for example a P2P Remote Server..
Section: Group Sections
Feature: Backstore Engine
Limits the number of times a Recall is attempted from any one backstore copy of a Virtual Volume. Once the threshold is exceeded if another eligible backstore copy is present, Recall will be attempted using that copy. Once all copies have exceeded their threshold, the volume will be mounted as an empty volume. This attribute resets itself for each mount. Specifying or defaulting to zero disables this parameter and Recall always uses the backstore copy after applying the OffsiteBackstoreCopy exclusion rule.
Valid Values: 0 to 15
Default: 0
Section: Group Sections
Feature: Miscellaneous
Determines which remote CA Vtape Subsystem a local CA Vtape Subsystem should communication with first. This is an optional attribute which is only used when the PeerToPeer Option of CA Vtape has been licensed and activated.
The values coded must correspond to a valid RemoteSystem defined in the Peer To Peer Remotes Section of the VTP2PRMT parmlib member. If a RemoteConsoleSuffix is coded, it must be prefaced with a forward slash (/).
Examples:
RemoteSystemPrimary= SYSA.SVT2 ; RemoteSystem RemoteSystemPrimary= /SAV2 ; /RemoteConsoleSuffix
Note: Coding double quotes with no value between the double quotes or coding $Null indicates that the attribute is not in use.
Valid Values:
Default: “”
Section: Group Sections
Feature: Peer To Peer
Determines which remote CA Vtape Subsystem a local CA Vtape Subsystem should communicate with when the subsystem defined by the RemoteSystemPrimary attribute is not responding. This is an optional attribute which is only used when the PeerToPeer Option of CA Vtape has been licensed and activated.
The values coded must correspond to a valid RemoteSystem or RemoteConsoleSuffix defined in the Peer To Peer Remotes Section of the VTP2PRMT parmlib member. If a RemoteConsoleSuffix is coded, it must be prefaced with a forward slash(/).
Examples:
RemoteSystemSecondary= SYSB.SVT3 ; RemoteSystem RemoteSystemSecondary= /SBV3 ; /RemoteConsoleSuffix
Coding double quotes with no value between the double quotes or coding $Null indicates that the attribute is not in use.
Valid Values:
Default: “”
Section: Group Sections
Feature: Peer To Peer
Determines the upper limit for the number of days of retention that will cause a Virtual Volume to be assigned to the Short Subgroup.
Valid Values:
Indicates that Virtual Volumes with normal-dated retention should not be assigned to the Short Subgroup. Virtual Volumes with never-expire (permanent), catalog control, or special retention dates can still be assigned to the Short Subgroup. If the Short Subgroup should not be used, you must set the NeverExpireSubgroup, CatalogManagedSubgroup, and SpecialRetentionSubgroup attributes to a value other than S.
Indicates the number of days of retention for assignment to the Short Subgroup. If a Virtual Volume has less than or equal to this number of days of retention, it will be assigned to the Short Subgroup.
Section: Group Sections
Feature: Subgroup Assignment
Determines the subgroup that special retention or negative retention date Virtual Volumes will be assigned to. The special retention dates used are determined by the SpecialRetentionDate attribute in the Dynamic Options section.
Valid Values:
Indicates that special retention or negative retention date Virtual Volumes should be assigned to the Short Subgroup.
Indicates that special retention or negative retention date Virtual Volumes should be assigned to the Medium Subgroup.
Indicates that special retention or negative retention date Virtual Volumes should be assigned to the Long Subgroup.
Default: S
Section: Group Sections
Feature: Subgroup Assignment
Determines whether the Virtual Volume record in the CA 1 or CA TLMS tape management systems is updated with the duplex or primary tape VOLSER. The field updated is the ACTVOL field. This attribute is active only when the TapeManagementSystem attribute in the Dynamic Options Section is set to a value other than NONE.
Valid Values:
Indicates that the tape management system volume records for Virtual Volumes in this group should be updated with the duplex backstore tape VOLSER. If the group does not have the Duplex attribute specified, then a duplex tape is not being written, the update will be done with the primary backstore tape VOLSER.
Indicates that the tape management system volume records for Virtual Volumes in this group should be updated with the primary backstore tape VOLSER.
Default: DUPLEX
Section: Group Sections
Feature: Tape Management
When USS Backstore is active, this attribute determines if externalization writes a triplex copy of the virtual volume to the USS file system. If a triplex copy shall not be written, this attribute can be commented out of the Group Section by typing a semi-colon (;) at the start of the line.
Note: This attribute is mutually exclusive of the Export= attribute, meaning they cannot both be specified in a Group Section.
Valid Value: USS
Section: Group Sections
Feature: Backstore Engine / UNIX System Services
Specifies the name of the Virtual Volume pool used to obtain the volser for new scratch mount requests.
Virtual Volume pools are defined in the Volume Pool Definitions section of the VTPOOLS member.
Valid Values: POOL1 or any valid virtual volume pool defined under the Volume Pool Definitions Section.
Default: POOL1
Section: Group Sections
Feature: Miscellaneous
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|