Do PDSE's have format version numbers? I remember (2015) looking at a
problem where IEBCOPY would not copy what I think IBM called a V3 PDSE
member, and that failure could be predicted by looking at a byte pretty
close to the front of the member data (or maybe it was the dir entry)
that was x'02' (copied ok) or x'03' (wouldn't copy to a standard PDS).
That was right around the time COBOL started requiring PDSE's and I
assumed it was like you say, for long name support.
On 7/29/2021 3:31 PM, Steve Smith wrote:
Where did you get that notion? IEBCOPY can indeed load into a dataset of a
different type than the source. Only exception I know of is from a PDSE
with long aliases.
I'd think your "backup plan" (albeit my first plan), would be to unload the
file into a PDSE and not worry about it until something goes wrong.
sas
On Thu, Jul 29, 2021 at 6:07 PM Billy Ashton <[email protected]> wrote:
These are solution files that the vendor sends to us, so we have no
control of what to do. They tell us that the target is a PDS or PDSE,
but I was just looking for a backup method to try and ensure that what
they say matches the file. As I'm sure you know, if they unloaded a PDS
file with load modules, you can't take the unloaded file and then try to
load it into a PDSE. Likewise, if a PDSE with program objects was
unloaded, you can't load it into a standard PDS.
Billy
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
