So private area below the line is what is left over after the system carves out
everything else.
So CSA, HSA (I think - Hardware area), etc....
I was looking for a graphic that displays this better than I can write it.
So
The portion of the user private area in each virtual address space that is
available to the user's application program is referred to as its region.
Except for the 16 KB system region area, each storage area in the private area
has a counterpart in the extended private area.
The private area contains the following areas:
A local system queue area (LSQA)
A scheduler work area (SWA)
Subpools 229 and 230 (the requestor protect key area)
A 16 KB system region area (used by the initiator)
A private user region for running programs and storing data.
The private area user region can be any size up to the size of the entire
private area (from the top end of the prefixed storage area (PSA) to the
beginning, or bottom end, of the common service area (CSA)) minus the size of
LSQA, SWA, subpools 229 and 230, and the system region: for example, 220 KB. It
is recommended that the region is 420 KB less to allow for recovery termination
management (RTM) processing.
The segment sizes are one megabyte, therefore CSA is rounded up to the nearest
megabyte. The private area is in increments of one megabyte.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of phil yogendran
Sent: Thursday, August 27, 2015 12:43 PM
To: [email protected]
Subject: Re: Smaller Private Area in DR
Thanks all for the responses. I'm referring to private below the line.
Unfortunately, there's no dump or map of storage to do any meaningful
debugging. The obvious reason is that something was added somewhere for private
to drop 1M. I'm aware it changes in 1M chunks. However, 'nothing changed' is
what I'm told.
Mark, can you elaborate please? Would that be in the IODF that was picked up in
DR?
Thanks
On Thu, Aug 27, 2015 at 3:01 PM, Ed Finnell <
[email protected]> wrote:
> Have to examine all the parts. CSA, ECSA, etc that take away from private.
> Something like Mark's IPLINFO is a starter or the PRIVAT mapper in IVP
> lib is another choice.
>
>
> In a message dated 8/27/2015 1:47:44 P.M. Central Daylight Time,
> [email protected] writes:
>
> Might be related to the number of devices defined to the environment.
> Are you talking about above or below private?
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
