Rick Fochtman wrote:
> In case you forgot: "regular" load modules only contain a note list if
> they are in OVERLAY format, which is both archaic and unnecessarily
> complicated.
OVERLAY format does use a second entry in the NOTE list, but *all*
PDS load modules have at least one entry in the N
Greg Price wrote:
Frank Swarbrick wrote:
Everyone might be interested to know that there are some IMS datasets (I forget which) that *cannot*
be PDSE. They must be PDS.
Yes, PDSEs do not allow NOTE list TTRs in the directory entry.
This is one reason why "regular" load modules cannot
Frank Swarbrick wrote:
> Everyone might be interested to know that there are some IMS datasets (I
> forget which) that *cannot*
be PDSE. They must be PDS.
Yes, PDSEs do not allow NOTE list TTRs in the directory entry.
This is one reason why "regular" load modules cannot be
housed in PDSEs.
Che
Everyone might be interested to know that there are some IMS datasets (I forget
which) that *cannot* be PDSE. They must be PDS. Trust me, I tried them as
PDSE and spend a long time trying to figure out why I couldn't get things
working! :-) So to make life easy on yourselves if you have IMS
Mark Zelden wrote:
One of our small monoplex LPARs (absorbed via consolidation) has their
default set to DSNTYPE(LIBRARY) in IGDSMSxx.This applies to everything,
SMS assigned or not. So even ISPF data sets that are not recommended
to be PDSE are (but I've never seen a problem because of it)
Bob Shannon wrote:
I don't understand why the vendors are populating the libraries in PDSE
If any of the features of Program Objects are required, then PDSEs are
mandatory, i.e., Program Objects cannot reside in PDSs. I suspect the majority
of vendors use PDSs unless their code requires
On Fri, 11 Sep 2009 09:01:02 -0700, Edward Jaffe
wrote:
>In our shop we use SMS to assign default data classes that specify "Data
>Set Name Type . . . . . : LIBRARY". So, if you think you're allocating
>a PDS in batch, it's really a PDSE unless you specify DSNTYPE=PDS to
>explicitly override th
>I don't understand why the vendors are populating the libraries in PDSE
If any of the features of Program Objects are required, then PDSEs are
mandatory, i.e., Program Objects cannot reside in PDSs. I suspect the majority
of vendors use PDSs unless their code requires PDSEs.
Bob Shannon
Rocket
u] On Behalf Of
R.S.
Sent: Monday, September 07, 2009 2:03 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: PDSE HELP Required.
Sivakumar, Manikandan pisze:
> All,
>
>
>
> I would need your assistance to know about PDSE Concepts and
> considerations.
>
>
>
> Currently
Sivakumar, Manikandan pisze:
All,
I would need your assistance to know about PDSE Concepts and
considerations.
Currently the 3rd Party Vendor products were introduced the product
libraries in PDSE format which benefits them in terms of Dynamic Space
allocation with reclaim spaces, 123
All,
I would need your assistance to know about PDSE Concepts and
considerations.
Currently the 3rd Party Vendor products were introduced the product
libraries in PDSE format which benefits them in terms of Dynamic Space
allocation with reclaim spaces, 123 Extent limit, Multiple members ca
11 matches
Mail list logo