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
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
&
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
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
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 t
-
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
r 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 re
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
On Wed, Feb 9, 2011 at 8:46 AM, Veilleux, Jon L 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
-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
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 sta
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 ver
, 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
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 S8
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 jobc
On Wed, 9 Feb 2011 12:28:36 -0500, Haynes, Stan
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 IE
: 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
wrote:
>The issue with how much *low* private to allow
o: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 >
> wrote:
>
>
> >The issue with how much *low* priva
; 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
In
,
on 02/09/2011
at 09:46 AM, "Veilleux, Jon L" 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
20 matches
Mail list logo
