CA1 - scratch pool in a mixed VTL environment

Products

• CA 1 Flexible Storage

Issue/Introduction

Currently using a non-IBM VTL that supports CA1 scratch pools.A migration from a VTL  to an IBM TS77xx  VTL will be done.

Documentation states that CA1 scratch pooling is not supported for an SMS managed IBM VTL.

How the NSM rules should be changed  to specify that all mounts use a scratch pool, except specific datasets.

sample:

DSN=SYSPS.DSNN.STG.LIBVTS.-,JOB=- --> go to IBM VTL
DSN=-,JOB=-,POOL=CSTORGP0                           

Environment

Release : 14.0

Component : CA 1 Tape Management

Resolution

The easiest way to do subpooling without worrying about which datasets are coded would be to assign the CSTORGP0 based on UNIT= instead of the DSN=,JOB= statements,so that ANY output tape allocated to one of the units associated with the older robot would have the CSTORGP0 name in the mount message and any other tapes would NOT. That eliminates having to code the IBMVTL range in the TMOSCRxx member and allows to have greater flexibility in terms of controlling which files go to the TS7760 solely based on the SMS constructs.