One change mentioned was an intervening POR since the last successful IPL. POR reinitializes all LPARs on the box with current Image profiles. This is a rare event in most shops. It may have been a very long time since the sandbox LPAR was last reactivated, leading to the possibility that some long forgotten profile change finally took effect with the POR. If you're not running operlog, JES2 failure means no syslog to peruse. It's vital that you get some kind of dump for the error.
. . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Elardus Engelbrecht <elardus.engelbre...@sita.co.za> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 09/03/2013 08:34 AM Subject: Re: JES2 start fail with S878-10 Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> RCG wrote: >I am looking at a strange issue this morning while I had to IPL my test system.. While I try to start JES2 its failing with S878 rc 10.. knowing its an Private storage shortage, wondering what happened with no changes made to the system at all.. No changes? Really? Check all those replies you got. Nearly all of them said - CHANGES. I think you should talk with all and every persons and check what did they do since last successfull IPL. Check what happened during that POR. Check your configuration on HCD. Where is your ALTPARM? Can you fallback on that one? What JES2 replies, if any at all, you got before that abend? And, please post all messages including that one for S878 - 10 Since you're having problems with a sandbox, I really hope for your part the same is not happening with one of your prod lpars... Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
