re:
http://www.garlic.com/~lynn/2010m.html#16 Region Size - Step or Jobcard
i.e. MVS was still mostly the same address space ... or every MVS
virtual address space was mostly the same (some installations, 13mbytes
threatening to become 14mbytes, of every 16mbyte virtual address
space
Someone asked me the question, and since we are having a good discussion, I
thought I would throw this out to the collective wisdom here.
If there is a job with 200+ steps. Is it better to have region coded at the
JOBCARD level or the STEP Level?
I have heard various thoughts on this over the
In days of yore, long, long ago, and far, far, away, it made sense to code at
the step level.
OS/MVT used a contiguous storage algorithm and reserved that storage for the
life of a job step..
If STEPB required more storage that STEPA, the possibility existed for
significant execution delays
@bama.ua.edu
Subject: Region Size - Step or Jobcard
Someone asked me the question, and since we are having a good discussion, I
thought I would throw this out to the collective wisdom here.
If there is a job with 200+ steps. Is it better to have region coded at the
JOBCARD level or the STEP Level
W dniu 2010-08-04 20:07, Lizette Koehler pisze:
Someone asked me the question, and since we are having a good discussion, I
thought I would throw this out to the collective wisdom here.
If there is a job with 200+ steps. Is it better to have region coded at the
JOBCARD level or the STEP
On Wed, 4 Aug 2010 13:24:02 -0500, Staller, Allan wrote:
In days of yore, long, long ago, and far, far, away, it made sense to code
at the step level.
OS/MVT used a contiguous storage algorithm
More precisely, MVT had a single address space
and reserved that storage for the life of a job
On Wed, 4 Aug 2010 14:07:20 -0400, Lizette Koehler stars...@mindspring.com
wrote:
Someone asked me the question, and since we are having a good discussion, I
thought I would throw this out to the collective wisdom here.
If there is a job with 200+ steps. Is it better to have region coded at
the
Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Lizette Koehler
Sent: Wednesday, August 04, 2010 2:07 PM
To: IBM-MAIN@bama.ua.edu
Subject: Region Size - Step or Jobcard
Someone asked me the question
If you have a problem with the region size, add a REGION parameter to
the jobcard that is equal to or larger than any step, and overrides
all the steps. No need to remove the REGION from the steps or procs,
and any changes to the values could result in typo abends.
On Wed, Aug 4, 2010 at 2:43
m42tom-ibmm...@yahoo.com (Tom Marchant) writes:
More precisely, MVT had a single address space
aka VS2/SVS was minimally modified MVT in a single (16mbyte) virtual
address space; biggest change was borrowing ccwtrans from cp67 for EXCP
... to take the application-passed channel program and make
For new JCL I always recommend just putting an ample region size on the
job card and be done with it. But I would certainly not change running JCL
for no reason.
I always say if it ain't broke don't break it.
I say implement an IEFUSI exit that isn't from the dark ages and not
worry about (or
If there is a job with 200+ steps. Is it better to have region coded at the
JOBCARD level or the STEP Level?
Actually, while I still recommend using region at the job card level, in your
particular case it will narrow the step that caused the fragmentation.
Assuming you use checkregionloss
12 matches
Mail list logo
