strange, the latest doc I have show's these values for SMF30MES
Value Meaning X'01' MEMLIMIT set by SMF. X'02' MEMLIMIT set explicitly in the JCL with MEMLIMIT parameter on JOB or EXEC statement. X'03' MEMLIMIT is unlimited based on REGION=0 specification. X'04' MEMLIMIT set by IEFUSI (even if IEFUSI did not change the value). X'0A' System provided a default for MEMLIMIT based on REGION=0 specification and a subsequent curtailment of REGION in the IEFUSI exit. Carmen Vitullo ----- Original Message ----- From: "Sean Gleann" <[email protected]> To: [email protected] Sent: Monday, November 19, 2018 10:12:18 AM Subject: Re: Region size for OMVS tasks Interesting stuff, here... Before making any changes, analysis of the type-30 data showed SMF30RGN=56623104 (54M) and SMF30MES - the source of MEMLIT - as '1', which apparently means that MEMLIMIT is set by SMF. Also, SMF30MEM was coming back as 1280M - the same as the MEMLIMIT in SMFPRMxx. So far, so good. So I set the ASSIZEMAX for my own profile to 2G and logged off-n-on. No change in the type-30 values Then I set the associated MEMLIMIT value to 2G & logged off and on again. This time, SMF30MEM is coming back as 2048M. Great! I can modify the MEMLIMIT value and perhaps solve my problem. I'll have to re-engage one of the developers for that, could take a bit of time. But a curiosity has cropped up along the way... Now, my SMF30MES is coming back as '5' - which is undocumented, according to the System Management Facilities manual I'm using (SA22-7630-26 - which I believe is the latest, though I stand to be corrected). Apparently, the values for SMF30MES can be one of 1, 2, 3, 4 or 10 (decimal), so where the '5' is coming from is a mystery. I'm not sure it's important and I shan't chase it up with IBM, but thought it worth mentioning. Sean On Mon, 19 Nov 2018 at 15:38, Elardus Engelbrecht < [email protected]> wrote: > Sean Gleann wrote: > > >None of the suggestions so far check out, unfortunately. > >David: all limits associated with memory come back as 'Unlimited' > >Carmen: Yes, I've got MEMLIMIT(1280M) specified > >Alan: BPXPRMxx MAXASSIZE is set to 2G, and the OMVS segment ASSIZEMAX and > >MEMLIMT values are not specified, so they default to something. > >Hmmm that may be a way forward - play with one or both those settings to > see what happens. > > Check out your OMVS segment in RACF. AFAIK - RACF overrides nearly > everything above. > > Increase these in RACF these parts in the OMVS segment: ASSIZEMAX, > FILEPROCMAX, PROCUSERMAX, THREADSMAX, MMAPAREAMAX > > I know you said ASSIZEMAX, but just set it and increase it (in large > chunks). > > Let us know what your solution is. Good luck! > > Groete / Greetings > Elardus Engelbrecht > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
