Linda Golding wrote: >On one of our systems running in z/os 1.13 , we saw S878 abends with JES2 >during initialization . After we made SYSSTC.IEFUJI inactive , JES2 came up >without issues . I've always thought that it is IEFUSI that sets the REGION >LIMIT . Can some one tell me if IEFUJI is capable of overriding the REGION >limit set by IEFUSI . Please share your thoughts .
Disabling UJI to stop S878? Weird. You're correct, it is USI which sets that REGION if that is coded so. I have looked again at 'Common Exit Parameter Area', but don't see anything about memory there. Also IEFUJI receives control before the system selects a job on the input queue for initiation. A return code from IEFUJI indicates whether job processing. Ok, at what stage of JES2 initializing do you get the 878? Show your REGION of that JES2 Proc. Show your SMFPRMxx statements especially statements like MEMLIMIT and SUBSYS(STC,EXITS(??)) Did you change something in JES HASPPARM? Or something with that LPAR memory settings? Any PTFs applied? What else was running while getting those 878 abends? Does that JES2 shares the Spool with other JES2? Can you see the MemLimit for JES2 in SDSF? Did something changed in WLM? Can you see (source code) what are those two exits doing? If you can't get answers here from IBM-MAIN, perhaps a PMR or SLIP is in order? 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
