The additional IEBGENER steps (to print the data) all ran OK: for the source members originally containing data, the output was as expected; for the originally empty members, there was no output, naturally.
When I said " Same problem", I meant that the additional IEBGENER's OPEN and CLOSE processing did *not* change the result of the copy operation (IEPCOPY) that followed. The target PDSE is corrupted. Thanks. Karl -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Thomas Berg Sent: Friday, March 20, 2015 5:35 PM To: [email protected] Subject: Re: Intermittent, not consistently reproducible problems with PDSEs on z/OS V2R1 (incl. infrequent S0F4-20 RSN 1C0752EE ABENDs) > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Henn, Karl > Sent: Friday, March 20, 2015 5:02 PM > To: [email protected] > Subject: Re: Intermittent, not consistently reproducible problems with PDSEs > on z/OS V2R1 (incl. > infrequent S0F4-20 RSN 1C0752EE ABENDs) > > > Have you tried with - directly after each IEBGENER step - do an > > IEBGENER from the member > to SYSOUT ? > Yes. Makes no difference. Same problem Just to check: Do you mean that IEBGENER to SYSOUT gives nothing? Best Regards, Thomas Berg ___________________________________________________________________ Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ) ---------------------------------------------------------------------- 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
