Thanks... My mistake - I found my old notes and they mention a Program
Object version number, not PDSE version. So maybe that makes more
sense. During an attempt to IEBCOPY from PDSE to PDS most load members
copied fine, but some newer members failed with:
IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND
CANNOT BE SAVED IN LOAD MODULE FORMAT.
The client wanted to change the ASM code that called IEBCOPY to check
the source module version before the copy attempt, in order to issue a
nicer error message. That's why I went looking for the version number
in the module itself. I do remember finding it pretty easily and asked
IBM if it was the correct byte and they said yes.
On 7/29/2021 9:18 PM, Steve Smith wrote:
There are PDSE V1 and V2. Never was sure why IBM decided to do that.
There's no significant external difference other than only V2 supports
member generations.
IEBCOPY's unload file format is documented fairly well in an appendix of
the Dataset Utilities manual. I think you were looking at flags, not a
number as such.
sas
On Thu, Jul 29, 2021 at 7:00 PM Tom Brennan <[email protected]>
wrote:
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.
----------------------------------------------------------------------
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
