This section contains an alphabetic list of the Dynamic Options attributes. The list includes a description of each attribute, its valid values, and the CA Vtape features it supports.
While active, the CA Vtape subsystem can dynamically reload the Dynamic Options attributes by using the following operator command:
SVTn REFRESH=OPTION
The following is an alphabetic list of the Dynamic Options attributes:
Determines when Virtual Volumes are eligible for encryption by CA Tape Encryption.
Valid Values:
Virtual Volumes are not eligible for encryption.
Virtual Volumes are eligible for encryption.
Make Virtual Volumes eligible for encryption based on the associated group definition. Instead of globally applying encryption options to all Virtual Volumes in your environment, you can selectively influence encryption by specific groups. If this parameter is set to GROUPS, CA Vtape will interrogate the group definitions in the VTGROUP member of parmlib to determine the setting of the BrightStorEncryption attribute. If the physical tapes are set for encryption, then CA Vtape will make the Virtual Volume ineligible for encryption. If its value is NONE, the physical tapes will not be encrypted and the Virtual Volumes will be eligible for encryption.
Default: Y
Feature: Virtual Device Engine
Determines the number of Externalization attempts that will be made before a Virtual Volume is dequeued from the subgroup queues without being Externalized.
Valid Values:
Indicates that the last value stored in the Local VCAT for this attribute should be used. To determine what the current setting is, issue the SVTn Display Groups console command.
Indicates the number of retries that should be attempted before the Virtual Volume is dequeued. The Externalization Server will wait one minute between attempts.
Note: We recommend a setting of 20, which will allow 20 attempts over a 20-minute period before a Virtual Volume is dequeued. Since the primary reason for an Externalization failure is the Virtual Volume being remounted by an application, a 20-minute delay will allow most applications enough time to complete their processing and release the Virtual Volume. If applications exist that continuously remount a Virtual Volume, then a higher BackstoreRetryCount value is needed.
Default: -1
Feature: Backstore Engine
Determines if Run Length Limited (RLL) compression, accessed through the IBM CSRCESRV service, should be bypassed.
Valid Values:
Indicates that RLL compression should not be performed (bypassed).
Indicates that RLL compression should be performed (not bypassed).
Default: Y
Feature: DASD Buffer Compression
Determines at what percentage of Cache-In-Use Subgroup Automation should hold automated subgroup queues. Manual subgroup queues are not affected.
If the CacheWarningThreshold or the CacheAutoHighReleaseThreshold attributes are set to zero, this attribute is not active.
This attribute's value must be less than the CacheAutoHighReleaseThreshold value unless both are set to zero.
Note: For more information about Subgroup Automation, see the chapter “Operational Considerations.”
Valid Values: 0 to 100
Default: 0
Feature: Backstore Engine
Determines the time periods when Subgroup Automation is allowed to release the subgroup queues for automated subgroups. Manual subgroup queues are not affected.
If the CacheWarningThreshold or the CacheAutoHighReleaseThreshold attributes are set to zero, this attribute is not active.
Up to four time periods separated by commas can be coded. For example:
CacheAutomationSchedule = (00:00-03:00,06:00-09:00,12:00-15:00,18:00-21:00)
The time periods coded must not overlap.
Outside of the time periods coded, the subgroup queues for automated subgroups will be held. When a time period ends, any automated subgroup queue that is released or active will be held. The hold will occur within one minute of the ending time period. For example, if a time period ends at 03:00 all automated subgroup queues will be held and any active Externalization tasks for those queues will be gracefully stopped between 03:00 and 03:01.
Note: For more information about Subgroup Automation, see the chapter “Operational Considerations.”
Valid Values:
Default: (00:00-23:59)
Feature: Backstore Engine
Determines at what percentage of Cache-In-Use Subgroup Automation should release automated subgroup queues. Manual subgroup queues are not affected.
Valid Values:
Indicates that Subgroup Automation is not active.
Indicates that automated subgroups are eligible for release when the percentage coded is reached or exceeded.
If the CacheWarningThreshold is set to zero, this attribute is not active.
This attribute's value must be greater than the CacheAutoHoldLowThreshold value unless both are set to zero.
Note: For more information about Subgroup Automation, see the chapter “Operational Considerations.”
Default: 0
Feature: Backstore Engine
Determines at what percentage of physical allocations in cache CA Vtape will start deleting Externalized Virtual Volumes from cache. A setting of 90 indicates that when the physical allocations in cache reach 90%, Externalized Virtual Volumes should be deleted from cache. CA Vtape will attempt to maintain 10% of the cache free at all times to support scratch mounts and recalls.
Maintaining this free space eliminates the need to free up space during mount processing. By eliminating space management actions from mount processing, the mount can proceed without delay.
Lowering the setting has the following positive effects:
Lowering the setting has the following negative effects:
The setting is typically lowered when you have a number of jobs being submitted at the same time that require large amounts of cache space. For example, if you have multiple backup jobs being submitted at the same time that will write large amounts of data to Virtual Volumes, lowering the setting or increasing the cache size will be necessary to prevent slower mounts and warning messages about momentary cache shortages while CA Vtape is deleting Virtual Volumes from cache.
The 90% setting has been found to be satisfactory at the majority of customer sites.
Observe the following:
Valid Values: 0 to 100
Default: 90
Feature: Miscellaneous
Specifies the Primary space allocation, in MB, used for dynamically allocated Virtual Volume data sets.
The recommended value for this attribute is 1/10th of the Virtual Volume size, for example: 40, 80, or 200.
Valid Values: 24 to 2000
Default: 200
Section: <DynamicOptions>
Feature: Miscellaneous
Specifies the Secondary space allocation, in MB, used for dynamically allocated Virtual Volume data sets.
The recommended value for this attribute is 1/10th of the Virtual Volume size, for example: 40, 80, or 200.
Valid Values: 24 to 2000
Default: 200
Feature: Miscellaneous
Determines the percentage of Cache-In-Use at which the SVTnD0908I message is issued to warn of a potential cache shortage.
Valid Values:
Indicates that the last value stored (0 - 100) in the Local VCAT for this attribute should be used. To determine what the current setting is, issue the SVTn Display Groups console command.
Indicates the following:
Indicates the following:
Note: For more information about Subgroup Automation, see the chapter “Operational Considerations.”
Default: -1
Feature: Backstore Engine
Identifies the date value used to place a tape under catalog management or catalog retention control in the tape management system. This value is used by the Backstore Engine and Recycle to determine which Virtual Volumes will be assigned to the subgroup defined by the group CatalogManagedSubgroup attribute. It is also used by the Backstore Engine and Recycle to place the Backstore Physical Tapes under catalog retention control.
Valid Values:
Indicates that the value last stored in the Local VCAT for this attribute should be used. The value stored during installation is 99000.
Indicates the date value to use. The value used must not match the values coded for the ForeignTapesExpdt, NeverExpireDate, and SpecialRetentionDate attributes.
Default: -1
Features: Subgroup Assignment and Tape Management
Controls the number of seconds before console commands timeout and WTOR SVTnD9920I is issued.
Note: We recommend a setting of 60, which will allow 60 seconds for the CA Vtape console command to be executed before the WTOR is issued.
Valid Values: 30 to 600
Default: 300
Feature: Miscellaneous
Controls the group number assigned to a Virtual Volume when the data set cannot be identified based on data class or data set name filter. One example of this is when a Virtual Volume is mounted on Virtual Device by a specific unit allocation, that is:
//DD1 DD UNIT=/3455,DISP=(NEW,KEEP),..
Valid Values: GROUP01, GROUP02, GROUP03,… to GROUP74
Default: GROUP01
Feature: Backstore Engine / Recycle
Determines the expiration date value that will cause CA Vtape to bypass a mount request for a VOLSER that matches a CA Vtape Virtual Volume, but is not a CA Vtape Virtual Volume. For example, assume your Virtual Volume range is V00000-V99999 and a vendor ships you a tape with a VOLSER of V15000. If a job is run to read the tape using an esoteric that includes the CA Vtape virtual devices, CA Vtape will try to intercept the mount. Adding LABEL=EXPDT=value, where value is that of the ForeignTapesExpdt attribute, to the DD statement in the JCL will cause CA Vtape to bypass or ignore the mount request.
Note: Changing the DD statement UNIT parameter to an esoteric or generic that does not include the CA Vtape virtual devices will also cause CA Vtape to bypass or ignore the mount request.
Valid Values:
Indicates that the feature is turned off or disabled.
Indicates the date value to use. 99365, 99366, '1999/365', and '1999/366' (never-expire dates) are all reserved values that will generate a validation error if used for this attribute.
Default: 00000 or '1900/000'
Feature: Miscellaneous
Determines if physical tape drives used by Recall tasks should be counted when enforcing the MAXDRIVES setting.
Note: If MAXDRIVES is set to zero and FullMaxdrivesEnforcement is set to Y(es), no Externalization or Recall tasks will be started. FullMaxdrivesEnforcement=Y and MAXDRIVES=0 are the requirements to designate a CA Vtape subsystem as a Failover Backstore Engine Server.
When enforcing the MAXDRIVES setting the Backstore Engine will stop Externalization tasks to free physical tape drives, but will not stop Recall tasks.
Valid Values:
Indicates that Recall task physical tape drives should be counted. Use this setting when limiting total physical tape drive usage by the Backstore Engine. Recall physical drive usage will cause active Externalization tasks to stop. Recall physical drive usage itself will not be limited by the MAXDRIVES setting to prevent job delays.
Note: Recall tasks will always be started without regard to the MAXDRIVES setting to prevent job delays, but Externalization tasks, if active, will be stopped to reduce usage back down to the limit.
Indicates that Recall task physical tape drives should not be counted. Use this setting when limiting only the physical tape drives used by the Backstore Engine for Externalization tasks. Recall physical drive usage will not cause Externalization tasks to stop.
Default: Y
Feature: Backstore Engine
Determines whether the Global VCAT reserve is issued with a QNAME.RNAME of “SVTS.GLOBAL” or “SVTS.Global VCAT data set name”.
Valid Values:
Indicates that GLOBAL will be used for the reserve RNAME. This allows backward compatibility with subsystems running at Release 2.0 SP05 or prior maintenance.
Important! The use of this generic enqueue reserve RNAME instead of the actual Global VCAT name, will cause contention and a performance penalty between CA Vtape complexes. When one complex issues the generic reserve to update its Global VCAT, other complexes will have to wait to issue the reserve to update their Global VCAT. Even though the different complexes are using different Global VCATs, updates will be serialized across all complexes.
Indicates that the Global VCAT name will be used for the reserve RNAME. This will prevent contention between multiple CA Vtape Complexes, by issuing the Global VCAT reserve with a reserve name unique to the Global VCAT. In this mode all subsystems in all CA Vtape Complexes must be running in enhanced mode. If a back-leveled or compatibility mode subsystem is detected, enhanced mode subsystems will issue messages and change to compatibility mode.
Default: Compatibility
Feature: Miscellaneous
Determines which compression methods can be employed when compression is active and compression is to be used for data written onto a Virtual Volume in the DASD buffer.
Valid Values:
The default value of $NULL causes this attribute to be ignored. If compression is activated and this attribute is set to $NULL, CA Vtape utilizes RLL and CMPSC compression. LZ78 is not employed.
CMPSC instructs CA Vtape to use the hardware compression call instruction. This method employs several compression dictionaries to achieve moderate compression rates with less CPU overhead than LZ78.
RLL (Run Length Limited) is a software implementation which compresses data by eliminating repeating characters. This method can sometimes achieve good compression with low CPU overhead.
LZ78 (Lepel-Ziv-78) is a software implementation. This method utilizes an adaptive compression algorithm which can achieve higher compression rate but at much higher CPU rates than CMPSC or RLL.
If you have zIIP enabled hardware you can defer the additional CPU requirements of LZ78 by allowing the compression routines to run on the zIIP processor. You can do this by setting additional parmlib attributes (that is, zIIPExploitation=Y and PercentRunOnZIIP=100).
Instructs CA Vtape to employ all of the compression methods mentioned above except $NULL. That is, CMPSC, RLL, and LZ78 are all used. CA Vtape VTA automatically monitors each compression method and chooses the method achieving the highest compression rate for a given Virtual Volume.
Note: More than one compression method can be specified for HardwareCompressionMethod by separating each method using a comma.
For example:
HardwareCompressionMethod= CMPSC,RLL HardwareCompressionMethod= LZ78,RLL
When more than one compression method is employed, CA Vtape automatically monitors each method and chooses the method achieving the highest compression rate for a given virtual volume.
Default: $NULL
Feature: DASD Buffer Compression
Determines if compression should be performed on data written to Virtual Volumes in the DASD buffer.
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, compression will not be performed.
Indicates that the Group Definitions should be checked for one of the above three values.
Note: For more information about Virtual Volume Compression, see the chapter “Operational Considerations.”
Default: N
Feature: DASD Buffer Compression
Determines the number of CPU seconds allowed for each I/O before it is terminated by the operating system with abend code S05B. This prevents the Virtual Device Engine from looping.
Valid Values: 5 to 300
Default: 15
Feature: Virtual Device Engine
Determines the level of detail of internal processes that is recorded by the Logger.
Valid Values:
Indicates that no logging should be done.
Indicates that basic events like messages issued, console commands issued, batch utilities executed, recovery errors, subtask attach/detach, and major routines entered should be logged. This is the recommended setting unless additional log detail is needed to diagnose a problem.
Indicates that in addition to level 1 details, subchannel commands, interrupt commands, and low-level routines entered should be logged.
Indicates that in addition to level 2 details, detailed I/O information should be logged.
LogDetailLevel=2 and 3 may generate a large volume of records on an LPAR with a very active CA Vtape subsystem.
HLQ.CCUUJCL(LOGEVENT) contains complete descriptions of what events are logged and the detail level they are logged at.
Default: 1
Feature: Logger
Determines whether the data generated by the Logger is copied from the CA Vtape log dataspace to an IBM system Log Stream data set. This is referred to as the External Logger.
Valid Values:
Indicates that a Log Stream does not exist so a copy will not be performed. The Logger will overwrite the data generated previously in the log dataspace.
Indicates that a Log Stream does exist. As each block in the log dataspace is filled, a call is made to the System Logger to write the block to the defined Log Stream. If errors are detected, the System Logger and CA Vtape will issue messages and this attribute will be internally changed to a value of NONE.
Note: The only valid Log Stream name is one that was created using the IBM IXCMIAPU utility. You can use the SVTn Display Log console command to determine the status of the logger.
Default: NONE
Feature: Logger
Determines the maximum amount of data that will be compressed in each 50 MB segment of data written to a Virtual Volume. 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.
Valid Values:
Indicates that no data should be compressed. This setting should only be used temporarily. If compression should be turned off permanently, use the HardwareCompressionOption attribute.
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 written.
Note: For more information about Virtual Volume Compression, see the chapter “Operational Considerations.”
Default: 100
Feature: DASD Buffer Compression
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.
Valid Values:
Indicates that this check is disabled. Any achieved percentage compression or no compression will allow compression to continue.
Indicates the percent of compression that must be achieved to continue compressing each 50 MB segment of a Virtual Volume.
Note: For more information about Virtual Volume Compression, see the chapter “Operational Considerations.”
Feature: DASD Buffer Compression
Determines the action taken when the tape management system rejects a scratch mount.
Valid Values:
Indicates that no action will be taken. CA Vtape will continue selecting Virtual VOLSERs from the scratch cell pool until one is accepted by the tape management system or the pool is empty. This could lead to a scratch shortage.
Where nn is between 05 and 99, indicates that after nn VOLSERs are rejected for this mount request a WTOR should be issued. The resulting SVTnV1803W message asks the operator whether the job should be cancelled or whether the Mount Reject Policy should be ignored.
Where nn is between 05 and 99, indicates that after nn VOLSERs are rejected for this mount request the job should be cancelled.
Note: Cancel,10 is the recommended setting.
Default: IGNORE
Feature: Virtual Device Engine
Identifies the date value used to place a tape under never-expire or permanent retention control in the tape management system.
This value is used by the Backstore Engine and Recycle to determine which Virtual Volumes will be assigned to the subgroup defined by the group NeverExpireSubgroup attribute.
Note: The value used must match the tape management system permanent or never-expire date. The value used must not match the values coded for the ForeignTapesExpdt, CatalogManagedDate, and SpecialRetentionDate attributes.
Valid Values: A valid date in yyddd or 'yyyy/ddd' format
Default: 99365 or '1999/365'
Feature: Subgroup Assignment
Specifies the percentage of work to be made eligible for the zIIP processor. In the Startup Options Section, attribute zIIPExploitation= must be set to Y to cause PercentRunOnZIIP to take effect. If PercentRunOnZIIP= is nonzero but zIIPExploitation=N is specified an error message will be issued but CA Vtape will continue to initialize and run without zIIP processing activated.
Valid Values:
Specifies that no work is to be directed to the zIIP processor. It is valid to specify PercentRunOnZIIP=0 and zIIPExploitation=Y at the same time. In this case, CA Vtape will issue warning message SVTnI0009W but will go on to build and maintain the internal resources required to use the zIIP processor but no work will be made zIIP eligible until a nonzero value is specified and the dynamic options are refreshed using the SVTn REFRESH=OPTIONS command.
Specifies the percentage of work that is to be made eligible for the zIIP processor. A value of 100 is recommended to take full advantage of the zIIP processor. You can use WLM to further set priority and eligibility in between other workloads like CA Tape Encryption that are eligible for the zIIP processor.
Default: 0
Feature: Virtual Device Engine
Specifies the percentage which the z/OS available central storage satisfactory threshold should be multiplied by to determine the point at which CA Vtape should defer mount and backstore processing to help z/OS maintain a healthy central storage environment.
z/OS maintains two fields which are used to determine the health of its central or real storage. The fields are RCEAFCLO and RCEAFCOK in the RCE control block. RCEAFCLO is the available central storage low threshold. Reaching this point indicates to z/OS that aggressive actions must be automatically taken to prevent a real storage constraint from impacting the system. RCEAFCOK is the available central storage satisfactory threshold or safety point. Reaching this point indicates to z/OS that aggressive actions are no longer required because the real storage constraint has been relieved.
CA Vtape dynamically acquires real storage for its active virtual devices and for externalization subtasks. As this activity increases, especially in a larger installation with lots of virtual devices being used concurrently, the amount of real storage usage could cause the available real storage to drop below the safety point. The RealStorageSafetyThreshold allows you to tell CA Vtape when to stop acquiring real storage to ensure that the CA Vtape does not cause real storage usage to go lower than the safety point.
For instance, the default of 400% implies that CA Vtape will keep a mount in pending status or defer the Backstore of a subgroup queue if the storage that needs to be acquired will reduce the available real storage to within 400% of the safety point. As other tasks that do not control themselves might be requesting real storage at the same time, the default of 400% is a conservative value to delay CA Vtape real storage requests well before z/OS experiences real storage stress. The default value should be lowered if you see CA Vtape delaying mounts on a system where a storage constrain is not occurring.
If the attribute value is set too high, CA Vtape will issue the SVTnV5008I message delaying new Virtual Mount requests or the SVTnP1708I message delaying new Externalization requests or both and appear to hang. Previous mounts will continue to be processed. Previous Externalization requests will continue to be processed. Only new requests will be delayed. When previous requests complete and free their storage, a new Virtual Mount request or a new Externalization request will be started unless the freed storage is consumed by some other task. Lowering the attribute value and issuing the SVTn REFRESH=OPTIONS console command for each CA Vtape subsystem which needs to pick up the change will eliminate the delays.
To disable this feature, specify a value of 0.
Valid Values: 0 to 900
Default: 400
Feature: Miscellaneous
Determines the mode of communication between a Recall Server and its clients.
Valid Values:
Indicates that the Recall Server and its Virtual Control Unit clients will not immediately post each other when a Recall is needed or a Recall completes. The Recall Server will check every n seconds for new Recall requests. The Virtual Control Units will check every n seconds to see if a requested Recall has completed. The minimum time interval is 30 seconds to minimize Global VCAT overhead.
This mode is required if the Recall Server and its clients are not running on the same LPAR and not running in a sysplex.
Indicates that the ROUTE console command will be used by the Virtual Control Units to immediately notify the Recall Server of a Recall request and by the Recall Server to notify the requesting Virtual Control Unit when the Recall is complete. This is the recommended configuration, but does require that the Recall Server and all its clients be running in a sysplex.
When in Route mode, a TIMED,60 mode is automatically activated as a backup. This ensures that Recall requests and completion notifications are received even if a ROUTE command is not properly processed by the operating system.
Default: TIMED,n
Feature: Backstore Engine
Determines whether the Backstore Engine for a CA Vtape subsystem processes its own Recall requests, processes all Recall requests for its CA Vtape Complex, or notifies another subsystem in the complex so it can perform the Recall requests.
Valid Values:
Indicates that this CA Vtape subsystem will only process Recall requests from its own Virtual Control Units. This mode is provided for backward compatibility with Release 2.0 SP05 and prior maintenance-level subsystems.
Indicates that this CA Vtape subsystem will process the Recall requests from all Virtual Control Units in this CA Vtape Complex.
Indicates that this CA Vtape subsystem will pass its Recall requests to the subsystem defined as the Recall Server in this CA Vtape Complex. If the client subsystem has an active Externalization task using the physical tape required for the Recall request, the request will not be passed to the Recall Server. The request will instead be queued to the active Externalization task.
Note: We recommend that you configure as the Recall Server in a CA Vtape Complex the same subsystem that is configured as the Primary Externalization Server. This will minimize physical tape and drive contention for Externalization and Recall requests.
Default: COMPATIBILITY
Feature: Backstore Engine
Determines the number of seconds a subsystem will wait before issuing a critical alert message that a Recall request is not being processed. The value should be set high enough to not issue unnecessary alert messages when a Recall request is delayed due to contention for physical tape drives.
Valid Values:
Disables the message. The message will never be issued.
Indicates the number of seconds to wait before issuing the waiting message.
Note: Using console automation to intercept the SVTnIR300I alert message and issue the SVTn Display Backstore console command to determine the status of the Recall Server may be desirable.
Feature: Backstore Engine
This attribute Influences the number of days to delay the reuse of a scratched virtual volume. For example, a virtual volume scratched today should not be considered to satisfy a new scratch mount request until (n) days have elapsed.
If the attribute value cannot be honored because there are no n day old scratches available the subsystem will take the following actions:
Note: For a P2P scratch mount, the attribute setting in the remote server determines the reuse delay. Also, the temporary override of the attribute value is not performed.
Valid Values: 0 to 128
Default:5
Feature: VirtualDeviceEngine
Determines whether the SVTnD0928W message is issued every 30 minutes when the number of available scratch Virtual Volumes drops below the specified value.
Valid Values:
Indicates that the available scratch Virtual Volumes are not being monitored. The warning message will never be issued.
Indicates the scratch Virtual Volume threshold value. When the number of scratch Virtual Volumes falls below the specified value, the warning message will be issued. The message is reissued every 30 minutes as long as the number of scratch Virtual Volumes remains below the threshold value.
Default: 0
Feature: Virtual Device Engine
Indentifies a range of date values used to place a tape under special retention control in the tape management system.
These values are used by the Backstore Engine and Recycle to determine which Virtual Volumes will be assigned to the subgroup defined by the group SpecialRetentionSubgroup attribute.
Note: The value used must match the tape management system special retention dates. The values used must not match the values coded for the ForeignTapesExpdt, CatalogManagedDate, and NeverExpireDate attributes.
Valid Values: A valid date range in 'yyddd-yyddd' or 'yyyy/ddd-yyyddd' format
Default: '99001-99001' or '1999/001-1999/001'
Feature: Subgroup Assignment
Determines if the interface to the CA 1 or CA TLMS tape management systems is active. The interface allows CA Vtape to query the tape management system to determine the current expiration date (remaining retention) of a Virtual Volume. This allows Externalization and Recycle to reduce fragmentation on the Backstore Physical Tapes by assigning a Virtual Volume to a subgroup based on its true retention rather than what was specified in the JCL, which wrote the Virtual Volume. The interface also allows CA Vtape to update the Virtual Volume record Container field in the tape management system with the physical tape volser on which the virtual was stacked. The Container field provides a direct link in the tape management system between the application data set on a Virtual Volume and a physical tape for reporting and auditing purposes and for off-site movement.
Valid Values:
Indicates that the interface is not active.
Indicates that CA Vtape should query the Subsystem Interface to determine if CA 1 or CA TLMS is installed and activate the interface with the CA tape management system that is found first.
Indicates that CA Vtape should query the Subsystem Interface to determine if CA 1 is installed and, if installed, activate the interface.
Indicates that CA Vtape should query the Subsystem Interface to determine if CA TLMS is installed and, if installed, activate the interface.
Default: NONE
Feature: Subgroup Assignment and Tape Management
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|