Hello,
We have an old ACS routine that directs datasets to
3 specific stogroups based on the ds size.
The stogroups are for small, medium and large
datasets.
There are 10 volumes currently in the small stogroup, (PDPPS90),
and 10 volumes in the medium stogroup, (PDPPM90).
There are DB2 vsam datasets, defined as multi-volume, on all.
What we wish to do is consolidate all 3 stogroups into one, so that we only
have the one large stogroup, (PDPPL90), and eventually, via
DB2 reorgs, have the DB2 vsam datasets that are in
the small and medium stogroup move naturally into the large
stogroup.
We have DISNEWed the 10 vols in both the small and
medium pools and our storage guy has changed the ACS routine
from this:
WHEN (&STORCLAS = 'PDPPA')
SELECT
WHEN (&SIZE > 406MB)
SET &STORGRP = 'PDPPL90'
WHEN (&SIZE > 82MB)
SET &STORGRP = 'PDPPM90'
OTHERWISE
SET &STORGRP = 'PDPPS90'
to now look like this:
WHEN (&STORCLAS = 'PDPPA')
SELECT
SET &STORGRP = 'PDPPL90'
So, going forward all will go to the
large stogroup (PDPPL90).
My fear is that, while waiting for the DB2
reorgs to occur and move the dsns, a DB2 dataset on one of the DISNEWed
volumes may need to extend to want to go onto a 2nd volume.
Question: Given a db2 dataset on a DISNEWed volume
that is in the small or medium stogroup, and needs to extend to another volume,
Will it extend without issue to one of the large stogroup's volumes??
Or will it fall on its sword with some type of "candidate
volume unavailable error"?
My rookie idea is to allow those small and medium
stogroup volumes to remain DISNEWed, but to change
the ACS to be:
WHEN (&STORCLAS = 'PDPPA')
SELECT
WHEN (&SIZE > 406MB)
SET &STORGRP = 'PDPPL90'
WHEN (&SIZE > 82MB)
SET &STORGRP = 'PDPPM90','PDPPL90'
OTHERWISE
SET &STORGRP = 'PDPPS90','PDPPL90'
and thus, with PDPPM90 and PDPPS90 disnewed,
any DB2 datasets that go to another volume will
go to PDPPL90 automatically without issue???
IBM provided some feedback....Re-enable the volumes, and with the ACS storgroup change we made, no more NEW datasets will go to the S90 or M90. Allow the db2 reorgs to naturally move the existing volumes off to the L90 pool and to address the issue of should any of the existing db2 multi-volume eligible datasets need to extend to an extra volume,
go into the ACS panels and amend the S90 and M90 storgroups by adding
the L90 storgroup to them in the Extend SG Name field.
Thus...all new datasets go to L90 thanks to the ACS storgroup routine and
any extensions of the datasets still on S90 or M90 volumes will likewise go to an L90 volume thanks to the Extend SG Name setting.
Once those existing dsn's on S90 and M90 move off via the DB2 reorgs, and they empty out, we can then disnew them, re-init them to our spare pool and blow away the then obsolete S90 and M90 storgroups
