W dniu 05.09.2024 o 16:06, Lennie Bradshaw pisze:
A few questions for the VSAM experts here.
From memory, for a non-vsam data set the primary space request can be split
into up to 5 physical extents. This can be avoided by specifying CONTIG on the
SPACE keyword.
There is no CONTIG equivalent for VSAM data sets.
Can the primary space allocation be split as well?
If so, is there some way to avoid it? (use an empty volume 😊).
Does the SMS storage class option Guaranteed_Space affect things?
Yes, there is no CONTIG option for VSAM. Yes, VSAM can be allocated with
more extents.
No, it cannot be avoided.
Yes, it is some pain i.e. for IODF allocation.
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
