No, I got that wrong. I should have read the manual instead of relying on memory, or maybe assumptions. I do cross-load/unloads from time-to-time, but they must all be non-executables.
Still, it seems like an odd hole in IEBCOPY's functionality. sas On Thu, Jul 29, 2021 at 8:37 PM Billy Ashton <[email protected]> wrote: > Steve, this is from the IEBCOPY doc: > A load module from an unload data set cannot be reloaded into a PDSE as > a program object. The load modules should be reloaded into a partitioned > data set and then the partitioned data set should be copied to a PDSE to > convert the unloaded load module into a program object. > > This means if a loadlib PDS is unloaded by IEBCOPY, it cannot be loaded > directly back into a PDSE as executable modules. I haven't found the doc > on it, but it is my understanding that a PDS cannot contain program > objects, so if a PDSE is unloaded by IEBCOPY, it cannot be loaded > directly back into a PDS. > > Or am I misreading something here? Don't forget that I am working only > with the unloaded file sent to me via FTP, and I do not have the > original PDS or PDSE available to me to do things like a 3.3 copy. > B > > Steve Smith wrote on 7/29/2021 18:31: > > 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 > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
