Re: Default REGION Size
In f393f47ecbe9fc4aa71b2a242c0b689512f3880...@hfdpmsgcms01.aeth.aetna.com, on 02/09/2011 at 09:46 AM, Veilleux, Jon L veilleu...@aetna.com said: The only problem with not limiting the region below is if you have a job that does a variable length getmain to take all available storage and then opens a lot of datasets you can get errors due to not enough below the line space for LSQA for the dataset control blocks. DEB's, yes, but IOB's et al don't go in LSQA. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
We ignore it entirely by overriding via the IEFUSI exit. REGION is basically useless in this day and age, especially for batch. For UNIX work, it may be needed. And for some types of started tasks, such as DB2 (which we don't have), it can still be very necessary. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Haynes, Stan Sent: Wednesday, February 09, 2011 8:04 AM To: IBM-MAIN@bama.ua.edu Subject: Default REGION Size We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! Haven't assessed how many of our jobs simply accept the default, but I'm thinking of changing the default region size for all jobclasses to a more current value of 32M. In this day and age, not sure how many programmers have a handle on used virtual storage, and not sure it should still matter! Jobs simply shouldn't fail because of region size in this day and age IMHO. I don't know how other shops handle this, and would like to read your comments/thoughts/opinions on my suggested new default region size. Cheers, Stan Haynes z/OS Systems Analyst Canada Revenue Agency -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
On Wed, 9 Feb 2011 09:04:27 -0500, Haynes, Stan stan.hay...@cra-arc.gc.ca wrote: We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! Haven't assessed how many of our jobs simply accept the default, but I'm thinking of changing the default region size for all jobclasses to a more current value of 32M. In this day and age, not sure how many programmers have a handle on used virtual storage, and not sure it should still matter! Jobs simply shouldn't fail because of region size in this day and age IMHO. I don't know how other shops handle this, and would like to read your comments/thoughts/opinions on my suggested new default region size. Assuming you don't have an IEFUSI exit in place, you wouldn't be gaining much by changing the default to 32M. The default above the line region is already 32M. You would probably gain 2M below the line, maybe 3M and that could help some batch jobs that aren't using REGION greater than 7M today and would abend if they needed more. See the MVS JCL Reference for more detail and you may want to read this article I wrote for TSO times about 7 years ago: Region Size: What You See is Not What You Get http://www.tsotimes.com/articles/archive/spring04/TSO-Times-Spring04.pdf The best thing to do would be to implement an IEFUSI and just ignore what is set in JES2 or (most) JCL for the defaults. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
What about region=0m?? From what I remember it will take what is needed, the down side is if you have something run away(loop) you might be in trouble. Mace -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
I worked at a place that had a similar setup with 8M. It was set artificially low because there were a bunch of assembler programs in the shop that did a variable getmains to give them everything below the line. By setting it to 8M, it meant that they couldn't get everything below the line and thus the jobs would tend not to abend for exhausted storage below the line. Not a brilliant way to do things.. but it worked. Cheers, Rob -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
The only problem with not limiting the region below is if you have a job that does a variable length getmain to take all available storage and then opens a lot of datasets you can get errors due to not enough below the line space for LSQA for the dataset control blocks. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Larry Macioce Sent: Wednesday, February 09, 2011 9:27 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size What about region=0m?? From what I remember it will take what is needed, the down side is if you have something run away(loop) you might be in trouble. Mace -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
Yes. And no issue these days on probably 95% + of all systems with above the line either. 2G ain't what it used to be and with the size of today's systems and paging subsystems, even if more than a few of these ill-behaved programs all did the variable length getmains at the same time you probably wouldn't notice.Even my smallest system has 1.5G of real storage and my smallest sandbox LPAR has 1G. I still have my IEFUSI set with a default of 256M above, but anytime someone asks for more, they can have it. If they asks for 1G or more, they get everything above the line (which ends up being about 1700M-1800M on most of my systems). My last real update was in 2005 for MEMLIMIT (other than a slight change in 2007 for OA14391). The next time I do something with it, I'll probably just let all jobs/tasks get everything above the line and remove the 256M default. -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Wed, 9 Feb 2011 09:46:49 -0500, Veilleux, Jon L veilleu...@aetna.com wrote: The only problem with not limiting the region below is if you have a job that does a variable length getmain to take all available storage and then opens a lot of datasets you can get errors due to not enough below the line space for LSQA for the dataset control blocks. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Larry Macioce Sent: Wednesday, February 09, 2011 9:27 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size What about region=0m?? From what I remember it will take what is needed, the down side is if you have something run away(loop) you might be in trouble. Mace -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Haynes, Stan We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! . . . When we went to z/OS 1.11, we finally raised our default region size from 1M all the way up to 4M! :-) TSO size was increased from 4096K to 131072K when Java entered the picture. -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
On Wed, Feb 9, 2011 at 8:46 AM, Veilleux, Jon L veilleu...@aetna.com wrote: The only problem with not limiting the region below is if you have a job that does a variable length getmain to take all available storage and then opens a lot of datasets you can get errors due to not enough below the line space for LSQA for the dataset control blocks. During a DR test our shop got S806s on DB2 jobs that don't specify a region and the program is too large to load. -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
How was the S822 corrected? We get this occasionally and just drain and restart the failing initiator... Our JOBCLASS is set to 4M... John Donnelly National Semiconductor Corporation 2900 Semiconductor Drive Santa Clara, CA 95051 408-721-5640 408-470-8364 Cell cjp...@nsc.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Haynes, Stan Sent: Wednesday, February 09, 2011 6:04 AM To: IBM-MAIN@bama.ua.edu Subject: Default REGION Size We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! Haven't assessed how many of our jobs simply accept the default, but I'm thinking of changing the default region size for all jobclasses to a more current value of 32M. In this day and age, not sure how many programmers have a handle on used virtual storage, and not sure it should still matter! Jobs simply shouldn't fail because of region size in this day and age IMHO. I don't know how other shops handle this, and would like to read your comments/thoughts/opinions on my suggested new default region size. Cheers, Stan Haynes z/OS Systems Analyst Canada Revenue Agency -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
On Wed, 9 Feb 2011 09:04:27 -0500, Haynes, Stan wrote: As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! S822 is not because the region specified is too small. It is because the region specified was not available, possible due to fragmentation of LSQA. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
Is there any reason why you're not using the VSM CHECKREGIONLOSS parameter in your DIAGxx member Mark Jacobs On 02/09/11 11:26, Donnelly, John P wrote: How was the S822 corrected? We get this occasionally and just drain and restart the failing initiator... Our JOBCLASS is set to 4M... John Donnelly National Semiconductor Corporation 2900 Semiconductor Drive Santa Clara, CA 95051 408-721-5640 408-470-8364 Cell cjp...@nsc.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Haynes, Stan Sent: Wednesday, February 09, 2011 6:04 AM To: IBM-MAIN@bama.ua.edu Subject: Default REGION Size We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! Haven't assessed how many of our jobs simply accept the default, but I'm thinking of changing the default region size for all jobclasses to a more current value of 32M. In this day and age, not sure how many programmers have a handle on used virtual storage, and not sure it should still matter! Jobs simply shouldn't fail because of region size in this day and age IMHO. I don't know how other shops handle this, and would like to read your comments/thoughts/opinions on my suggested new default region size. Cheers, Stan Haynes z/OS Systems Analyst Canada Revenue Agency -- Mark Jacobs Time Customer Service Tampa, FL Surrounding yourself with dwarfs does not make you a giant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
Do you have CHECKREGIONLOSS set in your DIAG member? It will automatically bounce your initiators when they get fragmented. VSM CHECKREGIONLOSS(500K,5M) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Donnelly, John P Sent: Wednesday, February 09, 2011 11:26 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size How was the S822 corrected? We get this occasionally and just drain and restart the failing initiator... Our JOBCLASS is set to 4M... John Donnelly National Semiconductor Corporation 2900 Semiconductor Drive Santa Clara, CA 95051 408-721-5640 408-470-8364 Cell cjp...@nsc.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Haynes, Stan Sent: Wednesday, February 09, 2011 6:04 AM To: IBM-MAIN@bama.ua.edu Subject: Default REGION Size We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! Haven't assessed how many of our jobs simply accept the default, but I'm thinking of changing the default region size for all jobclasses to a more current value of 32M. In this day and age, not sure how many programmers have a handle on used virtual storage, and not sure it should still matter! Jobs simply shouldn't fail because of region size in this day and age IMHO. I don't know how other shops handle this, and would like to read your comments/thoughts/opinions on my suggested new default region size. Cheers, Stan Haynes z/OS Systems Analyst Canada Revenue Agency -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
As Tom Marchant pointed out, it's likely LSQA fragmentation. And the S822 was misleading: the step requested 8M but turns out only needed 2M. So getting everything avail in 16M private on the job rerun worked. We (the small z/OS sysprog group) missed CHECKREGIONLOSS. Plain and simple. That will be addressed. Restarting an initiator is easy enough to do, but while fragmentation can happen (and you take a hit to find out), you want to avoid the easy S822's like the one we had. The issue with how much *low* private to allow is ensuring RTM can successfully GETMAIN, so I'm wondering: if we change the default to 128M, or 192M, etc, do we need to subtract some vstor for the low private ? Stan mailto:stan.hay...@cra-arc.gc.ca (613) 941-8091 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mark Jacobs Sent: February 9, 2011 11:41 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size Is there any reason why you're not using the VSM CHECKREGIONLOSS parameter in your DIAGxx member Mark Jacobs On 02/09/11 11:26, Donnelly, John P wrote: How was the S822 corrected? We get this occasionally and just drain and restart the failing initiator... Our JOBCLASS is set to 4M... John Donnelly National Semiconductor Corporation 2900 Semiconductor Drive Santa Clara, CA 95051 408-721-5640 408-470-8364 Cell cjp...@nsc.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Haynes, Stan Sent: Wednesday, February 09, 2011 6:04 AM To: IBM-MAIN@bama.ua.edu Subject: Default REGION Size We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! Haven't assessed how many of our jobs simply accept the default, but I'm thinking of changing the default region size for all jobclasses to a more current value of 32M. In this day and age, not sure how many programmers have a handle on used virtual storage, and not sure it should still matter! Jobs simply shouldn't fail because of region size in this day and age IMHO. I don't know how other shops handle this, and would like to read your comments/thoughts/opinions on my suggested new default region size. Cheers, Stan Haynes z/OS Systems Analyst Canada Revenue Agency -- Mark Jacobs Time Customer Service Tampa, FL Surrounding yourself with dwarfs does not make you a giant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
snip-- We run a 4-system production sysplex using z/OS/JES2 1.11 augmented by Thruput Manager. As a result of an application area reporting one of their critical jobs abending S822 (issue since corrected), we found ourselves noticing a very old parm value: default REGION size for all classes via the JOBCLASS statement. It's still set to an 'ancient' value of 7M! Haven't assessed how many of our jobs simply accept the default, but I'm thinking of changing the default region size for all jobclasses to a more current value of 32M. In this day and age, not sure how many programmers have a handle on used virtual storage, and not sure it should still matter! Jobs simply shouldn't fail because of region size in this day and age IMHO. I don't know how other shops handle this, and would like to read your comments/thoughts/opinions on my suggested new default region size. unsnip--- I've always used a custom-built IEFACTRT exit. Free upon request via private E-Mail. Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
On Wed, 9 Feb 2011 12:28:36 -0500, Haynes, Stan stan.hay...@cra-arc.gc.ca wrote: The issue with how much *low* private to allow is ensuring RTM can successfully GETMAIN, so I'm wondering: if we change the default to 128M, or 192M, etc, do we need to subtract some vstor for the low private ? That is why you need an IEFUSI (or IEALIMIT) exit. I really wish MVS would externalize LSQA reservation, above and below the line region size defaults etc.. in a parmlib member. But of course an exit is much more flexible since you may need more than a one size fits all specification. (not that jobnames etc. couldn't be added to some parmlib member to override the defaults) Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
It would be great if IEFUSI limits could be externalized into PARMLIB. It is a pain to have to recode an assembler exit whenever we need to change how we handle these limits. Not to mention that there are not a lot of us left who know how to code in assembler. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mark Zelden Sent: Wednesday, February 09, 2011 12:57 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size On Wed, 9 Feb 2011 12:28:36 -0500, Haynes, Stan stan.hay...@cra-arc.gc.ca wrote: The issue with how much *low* private to allow is ensuring RTM can successfully GETMAIN, so I'm wondering: if we change the default to 128M, or 192M, etc, do we need to subtract some vstor for the low private ? That is why you need an IEFUSI (or IEALIMIT) exit. I really wish MVS would externalize LSQA reservation, above and below the line region size defaults etc.. in a parmlib member. But of course an exit is much more flexible since you may need more than a one size fits all specification. (not that jobnames etc. couldn't be added to some parmlib member to override the defaults) Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
I think there is a product to do this kind of stuff. OESM or something along those lines. I did a quick web search and obviously I don't have the right name. Rob On Wed, Feb 9, 2011 at 1:02 PM, Veilleux, Jon L veilleu...@aetna.comwrote: It would be great if IEFUSI limits could be externalized into PARMLIB. It is a pain to have to recode an assembler exit whenever we need to change how we handle these limits. Not to mention that there are not a lot of us left who know how to code in assembler. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mark Zelden Sent: Wednesday, February 09, 2011 12:57 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size On Wed, 9 Feb 2011 12:28:36 -0500, Haynes, Stan stan.hay...@cra-arc.gc.ca wrote: The issue with how much *low* private to allow is ensuring RTM can successfully GETMAIN, so I'm wondering: if we change the default to 128M, or 192M, etc, do we need to subtract some vstor for the low private ? That is why you need an IEFUSI (or IEALIMIT) exit. I really wish MVS would externalize LSQA reservation, above and below the line region size defaults etc.. in a parmlib member. But of course an exit is much more flexible since you may need more than a one size fits all specification. (not that jobnames etc. couldn't be added to some parmlib member to override the defaults) Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Rob Schramm Senior Systems Engineer w: 513.305.6224 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Default REGION Size
OSEM - from Trident Services Jerry Whitteridge Design Engineer Safeway Inc. 925 951 4184 If you feel in control you just aren't going fast enough. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Rob Schramm Sent: Wednesday, February 09, 2011 10:08 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size I think there is a product to do this kind of stuff. OESM or something along those lines. I did a quick web search and obviously I don't have the right name. Rob On Wed, Feb 9, 2011 at 1:02 PM, Veilleux, Jon L veilleu...@aetna.comwrote: It would be great if IEFUSI limits could be externalized into PARMLIB. It is a pain to have to recode an assembler exit whenever we need to change how we handle these limits. Not to mention that there are not a lot of us left who know how to code in assembler. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mark Zelden Sent: Wednesday, February 09, 2011 12:57 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Default REGION Size On Wed, 9 Feb 2011 12:28:36 -0500, Haynes, Stan Stan.Haynes@CRA- ARC.GC.CA wrote: The issue with how much *low* private to allow is ensuring RTM can successfully GETMAIN, so I'm wondering: if we change the default to 128M, or 192M, etc, do we need to subtract some vstor for the low private ? That is why you need an IEFUSI (or IEALIMIT) exit. I really wish MVS would externalize LSQA reservation, above and below the line region size defaults etc.. in a parmlib member. But of course an exit is much more flexible since you may need more than a one size fits all specification. (not that jobnames etc. couldn't be added to some parmlib member to override the defaults) Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Rob Schramm Senior Systems Engineer w: 513.305.6224 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Email Firewall made the following annotations. -- Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. == -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
