When you copy a PDS with load modules to a PDSE does not IEBCOPY usually invoke the linker/binder under the covers to make the magic happen?
Is there some circumstance where it does not, such as if the first member is plain old data and not a load module? OP: is this supposed to be a load library? A PDS with executable load module programs in it? Gil is right LOL. IBM is offering you the choice of not copying the members or not copying the members. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Friday, February 13, 2015 12:08 PM To: [email protected] Subject: Re: IGW01595E message during PDS to PDSE copy Explanation A PDS is being copied to a PDSE and some of the PDS members or aliases have user TTRS (which are incorrect for a PDSE) indicated by the directory entry. Members that contain User TTRs in the directory entry are not supported for PDSEs. System action Processing of this member is skipped. Processing continues with the next member. Operator response If it is acceptable to not copy the identified members or aliases, then no action is required. Otherwise, run another copy job specifying only those members or aliases which do not have user TTRs. If the same output data set is used again, it will already include successfully copied members and aliases. System programmer response The most likely cause is accidentally copying a load module library to a PDSE. All load modules contain User TTRs in the directory entry. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
