Most likely something has changed and you are either unaware of it and/or it was unintentional.
Things to look for : (1) Changes to JES2 PARMLIB statements - maybe someone has increased some of the definitions for JES objects (2) System exits (eg IEFUJV) that could be stripping off REGION=0M from JCL (3) System exits that could be restricting private storage limits (eg IEFUSI) (4) Changes to system packs that could lead to unexpected changes to JCL PROCLIBs or PARMLIB statements - maybe you are picking up a different JES2 JCL proc or different versions of system exits? Do you have an alternate JES2 PARM that starts a minimal JES2 environment? (If not maybe this would be a good idea) Rob Scott Lead Developer Rocket Software 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA Tel: +1.781.684.2305 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of RCG Sent: 03 September 2013 14:38 To: [email protected] Subject: JES2 start fail with S878-10 Dear Group, 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.. We are on zOS 1.12 at the moment.. Any expertise inputs would be highly appreciated.. Thanks much in advance ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
