CA Vtape supports Virtual Volumes that are 400 MB, 800 MB, or 2000 MB in size. When using CacheManagement=DYNAMIC, 2000 MB Virtual Volumes should be defined to minimize the number of multivolume tape data sets created. Defining 2000 MB Virtual Volumes does not increase DASD space usage because unused DASD space is immediately released when a Virtual Volume is dismounted.
If you have converted all of your SVTS subsystems to dynamic mode, you may want to change your Virtual Volume Size from 400 MB or 800 MB to 2000 MB.
To change your Virtual Volume Size from 400 MB or 800 MB to 2000 MB
Note: Do not run any of the generated jobs.
Run the DEFVCAT job from HLQ.CCUUJCL(DEFVCAT). This will create and initialize a new Local VCAT. You will need to run this job for each SVTS subsystem, making sure that the SVTPARMS DD statement in the job points to the SVTJCL library used for Step 3.
RECOVER=GLOBAL,PREFIX=prefix,DROP_INELIGIBLE
Note: Make sure that the SVTPARMS DD statement in this job points to the SVTJCL library used for Step 3.
Note: If you are running in dynamic mode and you convert your Virtual Volume size to 2000 MB, you can only revert back to a static mode subsystem that supports 2000 MB Virtual Volumes. 2000 MB Virtual volumes cannot be mounted by 400 MB or 800 MB SVTS subsystems.
After the Global VCAT recovery, the number of scratch tapes may increase. This occurs because the recovery will evaluate the status of each Virtual Volume recovered and rebuild the scratch pool with all Virtual Volumes that are in scratch status. The Virtual Volumes which were scratched by the last Scratch Synchronization Job run, but would not be returned to the scratch pool until the next Scratch Synchronization Job run, are being returned early to the pool by the recovery.
Since the Global VCAT recovery was run without the SCRATCH command, the Global VCAT did not scratch additional Virtual Volumes. If the SCRATCH command was accidentally included in the recovery commands, any Virtual Volume scratched by the recovery would be documented with a message in the recovery job output.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|