Don't try to IPL yet. First run an IEBCOPY COMPRESS on SYS1.NUCLEUS. Then resubmit your most recent APPLY; if you have SDSF, bring up the output job, type SJ to reconstruct the original jobstream, and type SUB on the command line.
Make sure that the job completes without an x37. If that should happen again, repeat the COMPRESS/APPLY process repeatedly until no x37 occurs. At that point it should be safe to IPL. I hate to ask this question, but inquiring minds want to know: are you APPLYing maintenance to a running system? . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] Howard Rifkind <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List <IBM-MAIN@BAMA.UA.EDU> 06/15/2006 03:59 PM Please respond to IBM Mainframe Discussion List <IBM-MAIN@BAMA.UA.EDU> To IBM-MAIN@BAMA.UA.EDU cc Subject Need Urgent Help, Please Hi all, I did a huge apply for FMID HBB7707 and all seemed to go well until I got the message below, now I'm afraid to IPL. The sys1.nucleus file has room in it so I don't know why I'm getting this message. Thanks IEC031I D37-04,IFG0554P,SHUUSR3X,STEP01,NUCLEUS,0A20,ZOSRS1,SYS1.NUCLEUS BPXP018I THREAD 0B5DA5F000000001, IN PROCESS 50332105, ENDED 432 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 84D37000, AND REASON CODE 00000004. ---------------------------------------------------------------------- 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
