But if everybody upped and grabbed all 2GB and touched each page... :-( :-)
Which is why I recommend a good regime in place. I haven't yet said what that regime would be nor how to code it. Perhaps I should. :-) Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Banking Center of Excellence, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Ed Jaffe <edja...@phoenixsoftware.com> To: IBM-MAIN@listserv.ua.edu Date: 18/04/2014 00:34 Subject: Re: MEMLIMIT best practice Sent by: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> On 4/4/2014 12:47 PM, R.S. wrote: > I'm looking for some ROT (rule of thumb) for MEMLIMIT. > What I learnt: > - default limit is set in SMFPRMxx > - the limit can be affected by IEFUSI or other exit (this is not my case) > - REGION=0 implies default MEMLIMIT ignore (MEMLIMIT=inifinity) > - gotcha: MEMLIMIT=0 does not mean infinity, it really means zero. > > However I'm looking for a clue what to put into SMFPRM. What value is OK? If you specify absolutely nothing about MEMLIMIT anywhere, the system-provided default is 2G so obviously you can't go wrong with that in SMFPRMxx. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
