We were provided 3390-9 volumes to add to our existing databases which use 3390-3 volumes. They are already formatted as device type 8391 which is valid for both kinds, and it has already been confirmed I can add these in with no issues and not even introducing a mixed DS type scenario.
I ran into trouble, though, when I went to format these. We like to do full-pack allocations because adding parts of volumes could lead to some bad results in case we ever needed to reformat the database again before doing a restore. With the 3390-3s, we would format a new container with something like:
//DDASSOR1 DD DSN=hlq.ASSOR1,SPACE=(3338,3338),VOL=SER=(xxxxxx,xxxxxx,xxxxxx,…)
To add space to an existing container, we would do something like:
//DDASSOR1 DD DSN=hlq.ASSOR1,SPACE=(0,3338),VOL=SER=(xxxxxx,xxxxxx,xxxxxx,…)
We would format or add space only in full pack increments.
Now, with the 3390-9s, there are 10016 cylinders available. However, I learned in trying this that this is invalid:
//DDASSOR2 DD DSN=hlq.ASSOR2,SPACE=(10016,10016),VOL=SER=(xxxxxx)
Primary extents are limited to 65,535 blocks which is just a fraction cylinder higher than 3338 cylinders. Ok, so I figured I should be able to revert back to:
//DDASSOR2 DD DSN=hlq.ASSOR2,SPACE=(3338,3338),VOL=SER=(xxxxxx)
3338*3 = 10014, so I would leave 2 cylinders on the table by doing this, but it should take 3 extents on each volume before jumping to the next one, right? Wrong! It formats the first 3338 cyl and then dies with a B37-04!
Is there any way with 3390-9s to make use of full pack allocations like we did before, since that is what I would ideally like to do? If not, how do I format these to make use of the most number of cylinders available on a 3390-9 device?
Thanks in advance!
-Brian