Re IEB841I IEBUPDTE puzzle
Hi Paul I am late with this response because I have been away but as far as I can see there are two issues with the sample JCL which contains the //HAMDLE DD statement. That particular DD statement does not contain any DCB information and hence unless a DATACLAS is being automatically allocated via SMS the system will only know what SPACE to allocate, not what the attributes are. This is turn means that even though the SYSUT2 allocation assimilates to the same data set the SYSUT2 OPEN within IEBUPDTE will not know what attributes apply. (Remember that HANDLE is an arbitrary name and that there is no OPEN for it in either IEFBR14 or IEBUPDTE so the system cannot scan control blocks.) As regards the ADD statements. These have no bearing on DISPosition. It does not matter whether the data set is new or already exists, to create a new member the ./ ADD statement is used and to replace an existing member the ./ REPLACE statement is used. There is a functional split here between system responsibility (OPEN/CLOSE) and program logic (ADD/REPLACE). Kind Regards - Terry Director KMS-IT Limited 228 Abbeydale Road South Dore Sheffield S17 3LA UK Reg : 3767263 Outgoing e-mails have been scanned, but it is the recipients responsibility to ensure their anti-virus software is up to date. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Re IEB841I IEBUPDTE puzzle
On Jun 7, 2015, at 10:50 PM, Paul Gilmartin wrote: As regards the ADD statements. These have no bearing on DISPosition. It does not matter whether the data set is new or already exists, to create a new member the ./ ADD statement is used and to replace an existing member the ./ REPLACE statement is used. There is a functional split here between system responsibility (OPEN/CLOSE) and program logic (ADD/REPLACE). Mostly true. It's documented that STOW of a duplicate member name will fail if DISP=MOD but succeed if DISP=OLD. But that does not seem relevant to what I observe. SNIP--- Gil, I used to play around quite a bit with iebupdte. I always used to use PARM=NEW with massive updates. You might want to try that as well. I don't think this will get around your lrecl issue but I think if you try and apar you will get WAD . I *think* PDSE's are slightly different flavor. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
