Hi,

Users are getting following error messages when running IEBCOPY:

+IEB1021E 0AAD,D,INPDS1 ,00- OP,OUT OF EXTENT ,0000222E000001,EXCP LEN=X'0000' SENSE=0000-41
+IEB1022I I/O ERROR ON PDS DDN=INPDS1 VOL=DG2004 DSN=NPRVTE.COMM.TX.MG.CPY.COBOL
+IEB1023I DURING READ MEMBER=PPB016 TTR=X'10B301' MBBCCHHR=X'010000222E000001' TAPE BLOCK=0

I believe there is an open APAR OA40379, but no fix yet. Any other suggestions?

We are running RD&T 8.5 and z/OS 1.13.

Thanks,
Krystyna

You'll need to open a PMR with your mainframe support contract to try and get resolution of this problem. We don't provide support for the z/OS software stack through this forum.

RDzJohn

Thanks,

I had a PMR open, but this is the reply I got from IBM:

"Regarding to your RDTEz inquiry PMR 44594,130,616 - I/O on PDS in RDTEz environment,
based on IBM support policy we don't provide PMR support to clients for
this product.

Regarding any inquiries for Rational Development and Test Environment
for System Z,
please use IBM DeveloperWorks forum as below.
http://www.ibm.com/developerworks/forums/forum.jspa?forumID=2283
(RDzUTforum)

Our support engineer Tom has already sent you below email about the
process and links for your reference.
Also a similar defect would be related to your issue and if you have
more concerns, please use above forum to help.

We will proceed to close this PMR. Thanks for your cooperation."
Not sure how to proceed from here.

Krystyna

I have raised a second PMR with z/OS team. Better luck this time?

Krystyna

So the story on this is we sell RD&T with no warranty on the z/OS stack. The way you get support is you have a mainframe support contract for your System z hardware and you use that contract to report problems with z/OS on RD&T. Since we don't sell S&S for the z/OS portions of RD&T, I would expect the answer you got if you try to report the problem using your RD&T license.

RDzJohn

The APAR is now available and it is recommended to apply. However, if you find that you are in need of an interim work around, changing the PDS attributes for the input DD will get you around the problem. We noticed that the input DD had several extents. We copied the members of that PDS into a new dataset without extents. The IEBCOPY in the SMP/E RECIEVE (RTC install, in our case) then ran successfully.