How do I make sure all allocated S2KPADnn file space is used by SYSTEM 2000 software?
For Version 1, all S2KPADnn files are now VSAM. SYSTEM 2000 uses the maximum space
available (up to 123 extents per volume). All calculations are done by SYSTEM 2000,
so even if you specify number of allocation units and number of blocks
per allocation unit, the numbers are ignored and SYSTEM 2000 assumes PADnn=YES.
For V1, if you specify multiple S2KPADnn files, they all must be the same CISIZE.
Here are a few automatic features added in V1:
-
S2KPAD00 sets the CISIZE that all other S2KPADnn files must follow. The first
S2KPADnn not matching S2KPAD00 causes SYSTEM 2000 to assume PADnn=NO for that S2KPADnn
and subsequent S2KPADnn files.
-
If S2KPAD00 does not match the CISIZE specified for POOL7, POOL7 is automatically
reset to match S2KPAD00.
Prior to V1, BDAM S2KPADnn files could be reformatted to match the scratch file
buffer pools. With V1 and the VSAM file format, VSAM files cannot be dynamically
reformatted after they have been defined.