Re: IEFUJI and REGION LIMIT - S878 abends in JES2
I found this: "We often see abend878’s when starting JES2. This occurs typically when the above the line size is restricted via SMF exits or Region on the jobcard. To avoid this situation REGION=0 should be coded. Changes in definitions could cause storage increases and if the region is too small then suddenly JES2 will not start. Typically for JES2, once it has gone through a peak busy period storage should not increase to much after that due to the use of CPOOL’s." In a PDF document located here: ftp://public.dhe.ibm.com In directory /s390/jes2/Share104/document s2663lp1.pdf -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Linda Golding Sent: Thursday, September 29, 2016 5:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IEFUJI and REGION LIMIT - S878 abends in JES2 Greetings , 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 . TIA , Linda -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN == This email, and any files transmitted with it, is confidential and intended solely for the use of the individual or entity to which it is addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete this e-mail from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
*Of course, all this is easier with an IEFUSI exit routine but I'm just saying that it is possible from within an IEFUJI.* Thanks for clarifying that ...I don't see that being set in IEFUSI and we don't have have support with IBM for the level of OS we are running . This system was built for internal training purpose and I was curious if IEFUJI can interfere with REGION . I replaced IEFUJI module from a fresh system ( w/o any changes) and S878 abends disappeared after that . Thank you everyone for the help ...Have a great weekend :) Regards, Linda On Sun, Oct 2, 2016 at 8:34 AM, linda goldingwrote: > * Are you IPLing the system at the expected z/OS / JES2 levels??* > > > My badthat was a typo...We are on Z/os 1.12 > > > > On Sun, Oct 2, 2016 at 5:14 AM, Dan wrote: > >> Linda, >> >> Most exits can do just about anything. >> An IEFUJI exit can easily locate JCTXRGSZ to simulate REGION=. >> It can also locate JCTXMLSZ to simulate MEMLIMIT=. >> To override anything coded at the step level the exit would also have to >> run the SCT chain and update the SCTX fields. >> Of course, all this is easier with an IEFUSI exit routine but I'm just >> saying that it is possible from within an IEFUJI. >> >> Dan >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
* Are you IPLing the system at the expected z/OS / JES2 levels??* My badthat was a typo...We are on Z/os 1.12 On Sun, Oct 2, 2016 at 5:14 AM, Danwrote: > Linda, > > Most exits can do just about anything. > An IEFUJI exit can easily locate JCTXRGSZ to simulate REGION=. > It can also locate JCTXMLSZ to simulate MEMLIMIT=. > To override anything coded at the step level the exit would also have to > run the SCT chain and update the SCTX fields. > Of course, all this is easier with an IEFUSI exit routine but I'm just > saying that it is possible from within an IEFUJI. > > Dan > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
Linda, Most exits can do just about anything. An IEFUJI exit can easily locate JCTXRGSZ to simulate REGION=. It can also locate JCTXMLSZ to simulate MEMLIMIT=. To override anything coded at the step level the exit would also have to run the SCT chain and update the SCTX fields. Of course, all this is easier with an IEFUSI exit routine but I'm just saying that it is possible from within an IEFUJI. Dan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
In a previous post you stated: On one of our systems running in z/os 1.13 , we saw S878 abends with JES2 during initialization . In the abend messages below, it appears that you ae IPLing into z/OS 1.12: HASP088 FMID = HJE7770LOAD MODULE = HASJES20 $HASP088 SUBSYS = JES2 z/OS1.12 Are you IPLing the system at the expected z/OS / JES2 levels?? From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of linda golding [lindagolding...@gmail.com] Sent: Friday, September 30, 2016 10:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFUJI and REGION LIMIT - S878 abends in JES2 Sorry ..I should have posted the messages earlier . The reason code was 10 R 4,COLD ACF9CCCD USERID JES2MON IS ASSIGNED TO THIS JOB - JES2MON IEF403I IEESYSAS - STARTED - TIME=23.27.59 $HASP9084 JES2 MONITOR ADDRESS SPACE STARTED FOR JES2 $HASP537 THE CURRENT CHECKPOINT USES 243 4K RECORDS *$HASP095 JES2 CATASTROPHIC ABEND. CODE = S878 (RC = 0010) $HASP088 JES2 ABEND ANALYSIS 867 $HASP088 -- $HASP088 FMID = HJE7770LOAD MODULE = HASJES20 $HASP088 SUBSYS = JES2 z/OS1.12 $HASP088 DATE = 2016.270TIME = 23.27.59 $HASP088 MODULE MODULE OFFSET SERVICE ROUTINE EXIT $HASP088 NAME BASE + OF CALL LEVELCALLED ## $HASP088 --- --- -- $HASP088 *HASPIRDA 32869610 + 0055FC OA35942 *ABEND S878 $HASP088 HASPIRDA 32869610 + 00022C OA35942 KBLDCB $HASP088 HASPIRA 32867000 + 0004E4 OA35942 IRDA $HASP088 FAILING INSTR WAS 0A78 $HASP088 PSW = 071C B286EC0C ILC = 2 IC = 78 $HASP088 BEA = IEAVTSFR 00FF3100 + 0003DA $HASP088 ASID = 001E (HOME) 001E (PRIM) 001E (SCND) $HASP088 PCE = INIT (32867FE8) $HASP088 R0 = 12CEB000 32867C34 0009 $HASP088 R4 = 7F831640 009FF890 009DAFC8 12CEB000 $HASP088 R8 = 328BF000 009FF520 327C5D98 7000 $HASP088 R12 = 3286EBC4 32867FE8 B286983C 8476 $HASP088 -- *$HASP198 REPLY TO $HASP098 WITH ONE OF THE FOLLOWING: 868 END- STANDARD ABNORMAL END END,DUMP - END JES2 WITH A DUMP (WITH AN OPTIONAL TITLE) END,NOHOTSTART - ABBREVIATED ABNORMAL END (HOT-START IS AT RISK) SNAP - RE-DISPLAY $HASP088 DUMP - REQUEST SYSTEM DUMP (WITH AN OPTIONAL TITLE) *05 $HASP098 ENTER TERMINATION OPTION R 5,END IEE600I REPLY TO 05 IS;END IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. $HASP9085 JES2 MONITOR ADDRESS SPACE STOPPED FOR JES2 GSDMV20I JOBNAME- --STEP-- -PSTEP-- CCODE ELAPSED-TIME -CPU-TIME- GSDMV21I JES2MON JES2MON IEFPROC 0 00:00:13 0.00S IEF404I IEESYSAS - ENDED - TIME=23.28.12 IEF196I IEF142I IEESYSAS JES2MON - STEP WAS EXECUTED - COND CODE IEF404I IEESYSAS - ENDED - TIME=23.28.12 IEF196I IEF142I IEESYSAS JES2MON - STEP WAS EXECUTED - COND CODE IEF196I IEF373I STEP/IEFPROC /START 2016270.2327 IEF196I IEF032I STEP/IEFPROC /STOP 2016270.2328 IEF196I CPU: 0 HR 00 MIN 00.00 SECSRB: 0 HR 00 IEF196I MIN 00.00 SEC IEF196I VIRT: 4K SYS: 172K EXT: 2408K SYS: IEF196I 8404K IEF196I * ** IEF196I *** IEF196I * z/OS01.12.00 SYSTEM 2097 (2097) :SMF STATISTICS IEF196IDATE=26.09.2016 TIME=23:28:12 * IEF196I * ** * //JES2MON JOB , * * * * STEP TOTAL VIO TCB SRB INIT ELAPSED STORAGE NO.OF NO.OF * * NO. STEPNAME PROCSTEP PROGRAM EXCP'S EXCP'S CPU-TIME CPU-TIME CPU-TIME TIME <16M >16M PAGES SWAPS * * * * 1 JES2MON IEFPROC HASJES2$ 0 00.00S 0.00S0.01S 13.10S 4K2M 0 0 * * --* * JOB SUM (WITH JOB OVERHEAD): 0 00.00S 0.00S0.01S 13.10S 4K2M 0 0 * IEF196I * == IEF196I ==* IEF196I * STORAGE SECTION | USED PRIVATE AREA BELOW 16MB: IEF196I 4K | ALLOWED PRIVATE AREA BELOW 16MB:8192K * IEF196I * | USED PRIVATE AREA ABOVE 16MB: IEF196I 2M | ALLOWED PRIVATE AREA ABOVE 16MB: 256M * I
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
Sorry ..I should have posted the messages earlier . The reason code was 10 R 4,COLD ACF9CCCD USERID JES2MON IS ASSIGNED TO THIS JOB - JES2MON IEF403I IEESYSAS - STARTED - TIME=23.27.59 $HASP9084 JES2 MONITOR ADDRESS SPACE STARTED FOR JES2 $HASP537 THE CURRENT CHECKPOINT USES 243 4K RECORDS *$HASP095 JES2 CATASTROPHIC ABEND. CODE = S878 (RC = 0010) $HASP088 JES2 ABEND ANALYSIS 867 $HASP088 -- $HASP088 FMID = HJE7770LOAD MODULE = HASJES20 $HASP088 SUBSYS = JES2 z/OS1.12 $HASP088 DATE = 2016.270TIME = 23.27.59 $HASP088 MODULE MODULE OFFSET SERVICE ROUTINE EXIT $HASP088 NAME BASE + OF CALL LEVELCALLED ## $HASP088 --- --- -- $HASP088 *HASPIRDA 32869610 + 0055FC OA35942 *ABEND S878 $HASP088 HASPIRDA 32869610 + 00022C OA35942 KBLDCB $HASP088 HASPIRA 32867000 + 0004E4 OA35942 IRDA $HASP088 FAILING INSTR WAS 0A78 $HASP088 PSW = 071C B286EC0C ILC = 2 IC = 78 $HASP088 BEA = IEAVTSFR 00FF3100 + 0003DA $HASP088 ASID = 001E (HOME) 001E (PRIM) 001E (SCND) $HASP088 PCE = INIT (32867FE8) $HASP088 R0 = 12CEB000 32867C34 0009 $HASP088 R4 = 7F831640 009FF890 009DAFC8 12CEB000 $HASP088 R8 = 328BF000 009FF520 327C5D98 7000 $HASP088 R12 = 3286EBC4 32867FE8 B286983C 8476 $HASP088 -- *$HASP198 REPLY TO $HASP098 WITH ONE OF THE FOLLOWING: 868 END- STANDARD ABNORMAL END END,DUMP - END JES2 WITH A DUMP (WITH AN OPTIONAL TITLE) END,NOHOTSTART - ABBREVIATED ABNORMAL END (HOT-START IS AT RISK) SNAP - RE-DISPLAY $HASP088 DUMP - REQUEST SYSTEM DUMP (WITH AN OPTIONAL TITLE) *05 $HASP098 ENTER TERMINATION OPTION R 5,END IEE600I REPLY TO 05 IS;END IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=JES2MON , ASID=001B. $HASP9085 JES2 MONITOR ADDRESS SPACE STOPPED FOR JES2 GSDMV20I JOBNAME- --STEP-- -PSTEP-- CCODE ELAPSED-TIME -CPU-TIME- GSDMV21I JES2MON JES2MON IEFPROC 0 00:00:13 0.00S IEF404I IEESYSAS - ENDED - TIME=23.28.12 IEF196I IEF142I IEESYSAS JES2MON - STEP WAS EXECUTED - COND CODE IEF404I IEESYSAS - ENDED - TIME=23.28.12 IEF196I IEF142I IEESYSAS JES2MON - STEP WAS EXECUTED - COND CODE IEF196I IEF373I STEP/IEFPROC /START 2016270.2327 IEF196I IEF032I STEP/IEFPROC /STOP 2016270.2328 IEF196I CPU: 0 HR 00 MIN 00.00 SECSRB: 0 HR 00 IEF196I MIN 00.00 SEC IEF196I VIRT: 4K SYS: 172K EXT: 2408K SYS: IEF196I 8404K IEF196I * ** IEF196I *** IEF196I * z/OS01.12.00 SYSTEM 2097 (2097) :SMF STATISTICS IEF196IDATE=26.09.2016 TIME=23:28:12 * IEF196I * ** * //JES2MON JOB , * * * * STEP TOTAL VIO TCB SRB INIT ELAPSED STORAGE NO.OF NO.OF * * NO. STEPNAME PROCSTEP PROGRAM EXCP'S EXCP'S CPU-TIME CPU-TIME CPU-TIME TIME <16M >16M PAGES SWAPS * * * * 1 JES2MON IEFPROC HASJES2$ 0 00.00S 0.00S0.01S 13.10S 4K2M 0 0 * * --* * JOB SUM (WITH JOB OVERHEAD): 0 00.00S 0.00S0.01S 13.10S 4K2M 0 0 * IEF196I * == IEF196I ==* IEF196I * STORAGE SECTION | USED PRIVATE AREA BELOW 16MB: IEF196I 4K | ALLOWED PRIVATE AREA BELOW 16MB:8192K * IEF196I * | USED PRIVATE AREA ABOVE 16MB: IEF196I 2M | ALLOWED PRIVATE AREA ABOVE 16MB: 256M * IEF196I * | IEF196I | MAX. ALLOWED MEMLIMIT ABOVE 2GB: NOLIMIT * IEF196I * -- IEF196I --* IEF196I * WLM SECTION | WORKLOAD NAME SYSTEM IEF196I | SERVICE CLASS NAME SYSTEM * IEF196I * | RESOURCE GROUP NAME IEF196I | REPORT CLASS NAME * IEF196I * ** IEF196I *** IEF196I IEF375I JOB/JES2MON /START 2016270.2327 IEF196I IEF033I JOB/JES2MON /STOP 2016270.2328 IEF196I CPU:
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
linda golding wrote: >>*a)Ok, at what stage of JES2 initializing do you get the 878?* >JES2 was getting S878 abends during IPL I forgot to ask: Could you be kind to post the FULL message(s) including the Reason Code and other messages too? You said in subject: 'abends'. Do you get repeately 878 abends or just once? [1] Groete / Greetings Elardus Engelbrecht [1] - I got a case of repeated 878 abends during a RACROUTE macro processing in a STC. Increasing REGION resolved that. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
linda golding wrote: >Apologize for the late response . It is all right with me. ;-) >*a)Ok, at what stage of JES2 initializing do you get the 878?* >JES2 was getting S878 abends during IPL Ok, what replies were given? $WARM? $S or so? Granted if you could go that far. Could you see what automatic JES2 commands were given/handled? Do you see JES2 Monitor starting up? Can you see what last $HASP was shown? >MEMLIMIT(8G) -- PARMLIB Could you try out NOLIMIT to see if that resolves your 878? >This is a newly built system and we are planning to use as sandbox . There is >no maintenance put on these systems No changes made to JES2PARM and nothing >changed with memory settings Ok. >*e)What else was running while getting those 878 abends?* >Probably nothing apart from the system address spaces being a fresh IPL Nothing? What about things like SMF, VLF, LLA, DLF, NET, OMVS, HSM and start/stop things like IRRDPTAB and IFGEDI? Where they also active and running? It could be that one of these is consuming storage or one of them could using UJI eating up memory causing JES2 to die. >*g)Can you see (source code) what are those two exits doing?* >Its vanilla code.no changes to the exits as far as i remember . I'll take a >look again ... Vanilla from where? From IBM or CBT or just setting RC=00 while doing nothing? Check if you have the RIGHT module with the RIGHT name. I see 'vanilla' as something with size of x'20' or something. Perhaps you should compare your system and JES2 and the exits with your other systems? Perhaps you should ask IBM for assistance? Good luck and all of the best for you! 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
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
Hi Elardus , Apologize for the late response . *a)Ok, at what stage of JES2 initializing do you get the 878?* JES2 was getting S878 abends during IPL *b)Show your REGION of that JES2 Proc.* REGION is coded as 0M *c)Show your SMFPRMxx statements especially statements like MEMLIMIT and SUBSYS(STC,EXITS(??))* SUBSYS(TSO,INTERVAL(01)) -- SYS SUBSYS(TSO,NODETAIL) -- SYS SUBSYS(TSO,EXITS(IEFUSI)) -- PARMLIB SUBSYS(TSO,EXITS(IEFUJI)) -- PARMLIB SUBSYS(TSO,EXITS(IEFUTL)) -- PARMLIB SUBSYS(TSO,EXITS(IEFUJV)) -- PARMLIB SUBSYS(TSO,EXITS(IEFACTRT)) -- PARMLIB SUBSYS(TSO,NOTYPE(32,40,60,64,99)) -- PARMLIB SUBSYS(STC,INTERVAL(01)) -- SYS SUBSYS(STC,NODETAIL) -- SYS SUBSYS(STC,EXITS(IEFUSI)) -- PARMLIB SUBSYS(STC,EXITS(IEFUJI)) -- PARMLIB SUBSYS(STC,EXITS(IEFACTRT)) -- PARMLIB SUBSYS(STC,EXITS(IEFUTL)) -- PARMLIB SUBSYS(STC,EXITS(IEFU83)) -- PARMLIB SUBSYS(STC,EXITS(IEFU29)) -- PARMLIB SUBSYS(STC,NOTYPE(32,40,60,64,99)) -- PARMLIB SYS(NODETAIL) -- PARMLIB SYS(INTERVAL(01)) -- PARMLIB SYS(EXITS(IEFUSI)) -- PARMLIB SYS(EXITS(IEFUTL)) -- PARMLIB SYS(EXITS(IEFUJI)) -- PARMLIB SYS(EXITS(IEFUJP)) -- PARMLIB SYS(EXITS(IEFUJV)) -- PARMLIB SYS(EXITS(IEFACTRT)) -- PARMLIB SYS(EXITS(IEFU83)) -- PARMLIB SYS(NOTYPE(32,40,60,99)) -- PARMLIB LISTDSN -- PARMLIB SID(2097) -- DEFAULT JWT(0240) -- PARMLIB EMPTYEXCPSEC(SUPPRESS) -- PARMLIB STATUS(01) -- PARMLIB MEMLIMIT(8G) -- PARMLIB *d) Did you change something in JES HASPPARM? Or something with that LPAR memory settings? Any PTFs applied?* This is a newly built system and we are planning to use as sandbox . There is no maintenance put on these systems No changes made to JES2PARM and nothing changed with memory settings *e)What else was running while getting those 878 abends?* Probably nothing apart from the system address spaces being a fresh IPL *f)Can you see the MemLimit for JES2 in SDSF? Did something changed in WLM?* No changes to WLM *. * *g)Can you see (source code) what are those two exits doing?* Its vanilla code.no changes to the exits as far as i remember . I'll take a look again ... Regards, Linda On Thu, Sep 29, 2016 at 4:25 PM, Elardus Engelbrecht < elardus.engelbre...@sita.co.za> wrote: > 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 > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI and REGION LIMIT - S878 abends in JES2
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