Barbara Nitz wrote:
No, it's 64K tracks. It is the same "per volume" limit as many other
data set types (non-extended). But PDSes and PDSEs are also limited
to a single volume.
I am surprised. I did not know about *those* limitations. And most certainly,
since they are documented, there will be no way to change things.
But: I seem to remember that PDSEs were touted as the only ones making
sense on an EAV, because of the 'extented' part of the name, and that they
could get bigger (but maybe I misunderstood). Not that I would encourage use
of such a large volume, as it is much too slow, and I still haven't opened an
ETR to address 90s (or more) until ISPF 3.4 gives you the directory view.
(Might end up on an ISPF queue, which would require me to open a complaint
due to incompetence.)
PDSEs have only one advantage: They don't need to get compressed. The
rest us a huge amount of disadvantages.
Regards, Barbara
Well, they do have at least one other advantage: they can store
program objects, which allows entry points with long, case-sensitive
names, which is sometimes handy.
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
* To get a good Return on your Investment, first make an investment!
+ Training your people is an excellent investment
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
