Knutson, Sam wrote:
snip
People are expensive.
Reruns are expensive.
Paging can be expensive not having enough paging space can be more
expensive don't short yourself.
I/O is expensive and slow.
Real memory is cheap.
I could not agree with this more! To use CPU for lack of real storage,
is
26, 2007 11:41 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: TSO Storage Usage, Limits, etc.
Hi, All,
Just rolling out z/OS 1.7 and are looking to modernize some things,
including TSO storage allocations and limits. Currently using
XA-period limitations like REGION=6144K in the logon proc,
MAXSIZE=6144
Also, our current limitations notwithstanding, a snippet of a TASID
==
Jobname | Procname Stepname CPU Time Storage
--
UTSO001 ... TPROC001 ... EXEC ...21:53.3490.2M
Hi, All,
Just rolling out z/OS 1.7 and are looking to modernize some things,
including TSO storage allocations and limits. Currently using
XA-period limitations like REGION=6144K in the logon proc,
MAXSIZE=6144 in the TSO segment of the users' RACF profiles, etc.
What would be reasonable limits
On Fri, 26 Jan 2007 10:40:55 -0600, Chase, John wrote:
Also, our current limitations notwithstanding, a snippet of a TASID
display of TSO address spaces shows this (jobname and procname have been
anonymized):
==
Jobname | Procname Stepname
On Fri, 26 Jan 2007 13:30:55 -0600, Chase, John wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Tom Schmidt
On Fri, 26 Jan 2007 10:40:55 -0600, Chase, John wrote:
Also, our current limitations notwithstanding, a snippet of a TASID
display of TSO address
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Tom Schmidt
On Fri, 26 Jan 2007 13:30:55 -0600, Chase, John wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Tom
Schmidt On Fri,
26 Jan 2007 10:40:55 -0600, Chase, John
7 matches
Mail list logo
