Re: MEMLIMIT best practice

2014-04-22 Thread Vernooij, CP (SPLXM) - KLM
I don't know. Regards, Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Scott Ford Sent: Friday, April 18, 2014 16:07 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: MEMLIMIT best practice Kees: is there any way programmatically

Re: MEMLIMIT best practice

2014-04-19 Thread Martin Packer
+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: 19/04/2014 00:59 Subject:Re: MEMLIMIT

Re: MEMLIMIT best practice

2014-04-18 Thread Martin Packer
/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

Re: MEMLIMIT best practice

2014-04-18 Thread R.S.
W dniu 2014-04-18 01:25, Ed Jaffe pisze: 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

Re: MEMLIMIT best practice

2014-04-18 Thread Vernooij, CP (SPLXM) - KLM
We have 4G, not from recommendations, but from experience. CICS 5.x required this. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Friday, April 18, 2014 11:49 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: MEMLIMIT best

Re: MEMLIMIT best practice

2014-04-18 Thread Chase, John
Of Vernooij, CP (SPLXM) - KLM Sent: Friday, April 18, 2014 4:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: MEMLIMIT best practice We have 4G, not from recommendations, but from experience. CICS 5.x required this. Kees. -Original Message- From: IBM Mainframe Discussion List

Re: MEMLIMIT best practice

2014-04-18 Thread Vernooij, CP (SPLXM) - KLM
Correct, CICS 4.1 requires 4G. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Chase, John Sent: Friday, April 18, 2014 13:49 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: MEMLIMIT best practice CICS TS 5.1 requires MEMLIMIT=6G

Re: MEMLIMIT best practice

2014-04-18 Thread Scott Ford
. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Chase, John Sent: Friday, April 18, 2014 13:49 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: MEMLIMIT best practice CICS TS 5.1 requires MEMLIMIT=6G, according to the doc: http://pic.dhe.ibm.com

Re: MEMLIMIT best practice

2014-04-18 Thread John Gilmore
I do not remember that IBM has ever characterized its defaults as 'optimal', whatever that may mean without context. What it does try to do---with, I think, reasonable success---is to provide defaults that are innocuous in the sense that they do not give trouble for most jobs most of the time.

Re: MEMLIMIT best practice

2014-04-18 Thread Mark Zelden
My IEFUSI still prevents REGION=0M for all but STCs. Sort of worthless these days on 95% of the systems, but I actually still have some small monoplex LPARs that only have 1.2G - 2G, so the old region=0M and variable length getmain issue is still a valid concern for those LPARs. Actually,

Re: MEMLIMIT best practice

2014-04-18 Thread Ed Jaffe
On 4/18/2014 7:07 AM, Scott Ford wrote: is there any way programmatically that MEMLIMIT can be queried to determine the value ? 6 RAXLVMemLim Bit(64) RXZ,/* Address Space Memory limit in MB@P8C*/ -- Edward E Jaffe Phoenix Software

Re: MEMLIMIT best practice

2014-04-18 Thread Scott Ford
Ed, Thank you, just what I needed. Much appreciated Scott ford www.identityforge.com from my IPAD On Apr 18, 2014, at 2:18 PM, Ed Jaffe edja...@phoenixsoftware.com wrote: On 4/18/2014 7:07 AM, Scott Ford wrote: is there any way programmatically that MEMLIMIT can be queried to determine

Re: MEMLIMIT best practice

2014-04-18 Thread Martin Packer
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 19:18 Subject:Re: MEMLIMIT best practice Sent by:IBM Mainframe

Re: MEMLIMIT best practice

2014-04-18 Thread Ed Jaffe
On 4/18/2014 12:02 PM, Martin Packer wrote: BTW SMF 30 also has the limit and how obtained in it. So you can see what an individual job / address space can get at and why. As one might imagine, the system control block also contains the source of the MEMLIMIT: 6 RAXLVMemLimS FIXED(8) RXZ,

Re: MEMLIMIT best practice

2014-04-17 Thread Ed Jaffe
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:

Re: MEMLIMIT best practice

2014-04-04 Thread Chase, John
-Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. 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