No errors at all in the job log. And, not really GIYF as it was obvious that the directory needed expansion from the message. There may have been a faster path, but this PTF failed in the first run where 500 succeeded. I am sure I could have found this message in that run, but I certainly would have seen the x37 had it been there. Instead, I did another APPLY run for one PTF to just get the error. Then I expanded the directory. And then made my final run. This one and it's 31 dependents went on clean.
Friday whining :) Really just killing time until migrating my final Lpar from 1.13 to z/OS 2.1 at 00:15 Sunday. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Paul Gilmartin > Sent: Friday, September 23, 2016 4:28 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Binder: What happened to nice simple x37 abend > > On Fri, 23 Sep 2016 23:03:26 +0000, Gibney, Dave wrote: > > >IEW2736S DA10 THERE IS NO SPACE LEFT IN THE DIRECTORY FOR DDNAME > SISFLOAD. STOW OF THE DIRECTORY ENTRY MEMBER NAME > > HSFKYWDU FAILED. > > > >With an SMP/E APPLY. Easy to fix, but harder to spot the error :( > > > Did the job log show "x37"? > > But, generally I agree. Show the damn SYNADAF line or RC/RSN in > SYSTERM/SYSPRINT, *Followed by* Binder's interpretation if the developer > believes that helps. > > OTOH, in this case GIYF. IEW2736S takes me promptly to the M&C page. > Sometimes dumbing diagnostics down is harmful. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
