How about SPACE=(CYL,(273,273),RLSE) (4095 Tracks per extent, 65520 Tracks per 16 extents) with VOLCNT=10 on the storage group to allow up to 10 volumes). The extents on secondary volumes is the secondary size. Primary extent could be satified in 5 extents, and goes to another volume if the secondary space can't be satisfied (or would exceed the maximum data set size on a volume for that data set organization / type).
Alternatively, SPACE=(CYL,(4369,4369),RLSE) (65535 Tracks per extent, up to 5 extents to satisfy the primary allocation on each volume, with VOLCNT=10 on the storage group to allow up to 10 volumes). Compared to the previous example, some volumes might not qualify due to the larger requirement for the primary extent. The DSORG=PS limits the dataset to the 64K Tracks, and goes to the next volume if the next extent would exceed that value. On Tue, Nov 13, 2012 at 7:38 AM, DEBERT Jean-Louis <[email protected]> wrote: > Vernooij, CP - SPLXM wrote: > <snip> > Another approach: instead of working with multi volume extents of 1 dataset, > why not allocate as many single volume datasets as needed? > <end snip> > > Thanks for the idea, but no ... I am working on an existing application, > where the single-dataset property is important (because the DSN has to be > stored somewhere) and where the multi-volume property is seen as one way to > overcome the 65,535 tracks limit (that is, allowing a bigger file) when > reading the file with BSAM. > -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
