Linda, thanks, yes, that is more or less what I do for the "can't pre-create" cases. I use an internal copy function. (My bug was in not recognizing certain "can't pre-create" cases.)
I'm curious too. The only answer I could get was that IBM supported this and that's what they wanted to do. They are creating a temporary PDS and member and passing it to a subsequent step. I don't see any reason not to pass a sequential file, but I have not seen all of the job, just failing fragments. Whatever. I had the logic to test for the "can't pre-create" cases. I had the copy function. I fixed the bug. They can do all the FOO(BAR),DISP=NEW/MOD they want now. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Linda Mooney Sent: Sunday, March 06, 2011 11:09 PM To: [email protected] Subject: Re: Difference between DISP=NEW and MOD for a PDS member? Yes, that would be the same. So, how about if you preallocated a sequential file, then used IEBCOPY (with or without replace - as might be appropriate for your product) to copy the new file into the pds or pdse member? I am curious as to why a pds or pds/e is needed . In my shop, we use individual sequential , or GDG for ftp datasets. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
