Thanks Jim. That's exactly what I needed to know. Hey, why isn't that in the documentation? Why do I have to learn this stuff on the street?
Anne R. Adams, CISSP DTI, Systems Engineering Sr. Mainframe Services Analyst 302.298.3196 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jim Mulder Sent: Tuesday, August 29, 2017 3:20 PM To: [email protected] Subject: Re: SMFLIMxx parameter REGIONABOVE controls 31-bit addressable storage. You cannot address more than 2G with only 31 bits. MEMLIMIT controls 64-bit addressable virtual storage. It has nothing to do with the amount of real memory you have installed. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY IBM Mainframe Discussion List <[email protected]> wrote on 08/29/2017 12:12:37 PM: > From: "Adams, Anne (DTI)" <[email protected]> > To: [email protected] > Date: 08/29/2017 03:15 PM > Subject: Re: SMFLIMxx parameter > Sent by: IBM Mainframe Discussion List <[email protected]> > > Hey Carmen! > Yep, and things still don't work. However, if I change REGIONABOVE to > 2G (or whatever I have in SMFPRMxx) then It works just fine ... > except for the fact that the region size is only 2G ... and I want it all. > > Anne R. Adams, CISSP > DTI, Systems Engineering > Sr. Mainframe Services Analyst > 302.298.3196 > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected] ] > On Behalf Of Carmen Vitullo > Sent: Tuesday, August 29, 2017 11:57 AM > To: [email protected] > Subject: Re: SMFLIMxx parameter > > Hi Anne, tell Everyone I said YO! > all the example I've seen show > REGION JOBNAME(*) SUBSYS(JES*,STC) > REGIONABOVE(NOLIMIT) REGIONBELOW(NOLIMIT) > SYSRESVABOVE(50M) SYSRESVBELOW(512K) looks like the error is > pointing to the SYSRESVBELOW posssibly did you try reversing the order > and try again? > > > Carmen > > ----- Original Message ----- > > From: "Anne Adams (DTI)" <[email protected]> > To: [email protected] > Sent: Tuesday, August 29, 2017 10:47:04 AM > Subject: Re: SMFLIMxx parameter > > Hey Steve - > > Here's how we set up SMFLIMxx > > REGION JOBNAME(*) SUBSYS(STC,JES2) > REGIONABOVE(NOLIMIT) REGIONBELOW(NOLIMIT) > SYSRESVBELOW(512K) SYSRESVABOVE(100M) > MEMLIMIT(10P) > > If we left SMFPRMxx MEMLIMIT(2G) then the maximum region size > remained, 2G. Likewise if we put 4G or 6G that was the maximum. > However if we put NOLIMIT, then it appeared to default to 2G. We tried > setting REGIONABOVE(4G) in SMFLIMxx and would get and error. > T SMFLIM=00 > IEE252I MEMBER SMFLIM00 FOUND IN SYS1.PARMLIB ASA008I ERROR IN PARMLIB > MEMBER=SMFLIM00 ON LINE 3, POSITION 14: 362 VALUE IS NOT VALID - OUT > OF RANGE. > > What I want to have happen is when we put NOLIMIT, the default is > however much memory I have installed. Maybe I don't fully understand > how this works. > > > Anne R. Adams, CISSP > DTI, Systems Engineering > Sr. Mainframe Services Analyst > 302.298.3196 > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected] ] > On Behalf Of Steve > Sent: Friday, August 18, 2017 9:20 AM > To: [email protected] > Subject: Re: SMFLIMxx parameter > > Do you have the IEF043I joblog message and the SMFLIMxx rules that you > could post? Along with whatever messages you get for the refusalto run... > > - Steve > > > > On 8/17/2017 1:03 PM, Adams, Anne , DTI wrote: > > Hello Friends, > > > > Has anyone had any success using (or diagnosing failures) when > using the SMFLIMxx parameter? We have a few CICS and database regions > and one unrepentant job that refuse to run. > > > > Anne R. Adams, CISSP > > DTI, Systems Engineering > > Sr. Mainframe Services Analyst > > 302.298.3196 > > ---------------------------------------------------------------------- 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
