It occurred to me after my first response that you may be OK as is. The original x37 abend should have triggered a compress. In the job that failed, look at the CAUSER report. If you see 'NUCLEUS ran out of space', then you have a problem to solve. If that message does not appear, then the problem was solved by SMP/E in the original run.
This situation is not uncommon. NUCLEUS is *not allowed* to have any secondary extent(s), so every now and then it will certainly run out of space and require compressing. If you have your SMP/E options set correctly, compress will be automatic. . . 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
