I think the other thing that should be said, is that it is a LIMIT, not an allocation. And then it's worth mentioning that an application that run authorized can bypass the limit(like DB2).
_________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of J O Skip Robinson Sent: Tuesday, March 31, 2015 11:20 AM To: [email protected] Subject: Re: SDSF ISF121I message This thread motivated me to check my SMFPRMxx. On most systems we do not specify MEMLIMIT. Turns out that the default is 2G. (Sorry if someone else pointed that out.) Should cover most cases. ;-) . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Neal Eckhardt Sent: Tuesday, March 31, 2015 6:36 AM To: [email protected] Subject: Re: SDSF ISF121I message Just to close this out for anybody searching for this message, increasing MEMLIMIT in SMFPRMxx solved the problem. The fact that you can change it with a SET command is a plus. Thanks for pointing me in the right direction. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
