Complete the following steps to customize the parmlib that was allocated and populated by running the VTA08NON job in the chapter "System Setup."
Detailed explanations of the parmlib attributes and their values can be found in the chapter "The Parameter Library (PARMLIB)." The attribute settings in the sample parmlib members are generally acceptable at any site, but should be reviewed. Where applicable we will direct your attention to a specific attribute to make a recommended change.
- Edit VTPARMS in PREFIX.PARMLIB.
In the Parmlib Directory Section, uncomment the VolumePoolDefinitions attribute line by deleting the semi-colon at the start of the line.
Follow the comments in the member to set up the attributes in the Startup Options and Dynamic Options sections.
The following parmlib attributes will need to be updated or reviewed:
- Startup Options Section
-
- DsnameBSDS1 should be set to your BSDS1 data set name.
- DsnameGlobalVcat should be set to your Global VCAT data set name.
- DsnameLocalVcat should be set to your Local VCAT data set name.
- Tasklib is set to Automatic which will dynamically allocate and APF authorize a loadlib data set for use when starting and restarting the Virtual Device Controllers and the Backstore Engine address spaces. If you are executing IBM health checks, this may provoke messages. See Library Mode for this attribute in the chapter "The Paramter Library (PARMLIB)" to prevent the health check messages.
- MessagePrefix should be left at the default value of &SVTS.
- Cache Managment = should be set to Dynamic (recommended)
- CacheDefaultDataClass = should be set to your data class name (Dynamic Cache Management only)
- CacheDefaultStorageClass = should be set to your storage class name (Dynamic Cache Management only)
- ZIIPExploitation should be set to Y if you have a zIIP engine installed or want RMF to track potential zIIP usage.
- LicensedLocalVTP should be set to the number of Virtual Devices you are licensed for use in the CA Vtape Complex.
- Dynamic Options Section
-
- GlobalReserve should be set to Enhanced if you intend to set up more than one CA Vtape Complex in a GRSplex or MIMplex.
- CacheWarningThreshold is set to 85. When 85% of the cache is filled with Virtual Volumes that need to be Externalized, start issuing a warning message. If you would like to start receiving those messages sooner, lower the setting.
- CacheAutoHoldLowThreshold is set to 25.When 25% of cache is filled with Virtual Volumes that need to be Externalized, hold the automated queues and stop Externalizing. If you would like to Externalize more Virtual Volumes before stopping, lower the setting.
- CacheAutoReleaseHighThreshold is set to 65. When 65% of the cache is filled with Virtual Volumes that need to be Externalized, release the automated queues and start Externalizing. If you would like to start Externalizing sooner, lower the setting.
- CacheAutomationSchedule should be reviewed and updated to the time frames when the Backstore Engine is allowed to use tape drives to make copies of the Virtual Volumes in cache and mark those Virtual Volumes for deletion.
- ForeignTapesExpdt should be set to the same value used by your Tape Management System Software.
- CatalogManagedDate should be reviewed to ensure you have the correct value for the Tape Management System Software you have installed.
- MountRejectThreshold is set to CANCEL,10. If the scratch tapes mounted by the Subsystem on a Virtual Device are rejected ten times, the job will be cancelled.
- ScratchVolumesThreshold should be reviewed. Setting it to a high value like 6500 to begin with ensures that you are warned of a pending shortage in plenty of time to address it. It also allows you the time to determine the number of Virtual Volumes you will use and scratch daily so you can calculate a better threshold value.
- TapeManagementSystem should be changed to NONE if you do not have CA 1 or CA TLMS Tape management Systems installed.
- PercentRunOnzIIP should be changed to 100 if you are tracking potential zIIP usage or to an appropriate percentage if you have a zIIP engine installed. Discussing this setting with your z/OS or DB2 Performance and Tuning Specialist is recommended.
- RealStorageSafetyThreshold should be reviewed. For execution on a test system with limited memory, a setting of 400 maybe too aggressive. Reducing this to 50 or turning it off with a setting of 0 would be recommended.
- Edit VTPOOLS.
Follow the comments in the member to customize the Volume Pool Definitions Section with your customized volume pool names. Update the Volume Pool Sections with your customized pool names and the unique range of Virtual VOLSERs belonging to each pool defined. One pool must be defined.
Note: If you have a tape management system, the VOLSER range or ranges should first be defined in the tape management system to allow it to track and control the use of the Virtual Volumes just like physical tapes. The range or ranges defined should be reserved solely for the use of CA Vtape.
- Edit VTDRIVE.
Follow the comments in the member to complete the Virtual Device range with the primary set of Virtual Devices.
We recommend that you change the OFFLINE attribute to ONLINE to automatically vary the Virtual Devices online at startup of CA Vtape and split the Virtual Devices between at least two Virtual Control Units. This will cause CA Vtape to start two Virtual Control Unit address spaces, SVTSAS.SVT1V1 and SVTSAS.SVT1V2.
- Create VTDRALT.
Copy VTDRIVE into VTDRALT and change the primary set of Virtual Devices to the alternate set. This member will be used to avoid an IPL if the operating system boxes the current set of Virtual Devices and will not let them be varied back online after they have been restarted in CA Vtape.
- Edit VTGROUP.
Follow the comments in the member to set up the group options.
- Edit VTFILTR.
Follow the comments in the member to add one or more Data Set Name Filters or Data Class Filters.
If Data Class filters are entered, make the corresponding changes in the SMS ACS routines to assign the entered Data Classes to data sets whose tape mounts should be intercepted by CA Vtape.
Note: Do not add the CacheDefaultDataClass value as one of the data class filters.
- Edit VTSCMDS.
Follow the comments in the member to adjust the Maxdrives setting as needed or add additional console commands.
The default setting of Maxdrives is 5. This is the maximum number of physical tape drives that the Backstore Engine is allowed to use at one time to copy Virtual Volumes to physical tape.
- Secure the SUTPARMS member.
Copy the generated SUTPARMS member from the SVTJCL library to the parmlib. This will insure that this member, which contains the internal configuration data needed by CA Vtape to initialize new control data sets, will not be accidentally overlaid or deleted and will be available at your disaster recovery site.
