On Fri, 29 Mar 2019 12:56:59 -0400, Jeremy Nicoll wrote: > >In the calling exec the rc from the (ispf) edit would be checked, because >invoking edit might have failed, eg because of spfdsn enqueues on the >target file. In the 'production' systems I wrote the execs usually then >slept for a few seconds, then tried again (when they were part of the >batch jobs). If the edit was something invoked from an ispf dialog run >in the foreground, the dialog might have told the user to try again (as >they'd probably already have seen a line-mode dataset contention >message). > I have, on occasion, added a final step, IEFBR14,COND=(0,LE) with a DD DISP=SHR for any such data set so my job would be held by the initiator until the data sets were available.
(Always JES2) In one instance the effect was disastrous -- it created an uncatalogued instance of the DSN on every storage volume. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
