VSE 2.6.2:
SPACE AREA V-SIZE GETVIS V-ADDR UNUSED NAME
S SUP 712K 0 $$A$SUPI
S SVA-24 2400K 3032K B2000 0K
0 BG V 2048K 6144K 600000 73728K
:
:
S SVA-31 17428K 17388K 5600000
DYN-PA 471040K
DSPACE 296544K
SYSTEM 8128K
AVAIL 1105888K
TOTAL 2080256K <----'
Frank M. Ramaekers Jr.
Systems Programmer
American Income Life Insurance Company
Phone: (254) 761-6649
-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf
Of Steve Mondy
Sent: Tuesday, September 21, 2004 2:14 PM
To: VSE Discussion List
Subject: Re: Virtual Storage reporting differences
Hi Dave,
A bit late but here is some addition break down of the 24-bit SVA.
MAP
AR 0015 SPACE AREA V-SIZE GETVIS V-ADDR UNUSED NAME
AR 0015 S SUP 900K 0 $$A$SUPI
AR 0015 S SVA-24 2248K 3956K E1000 64K
....
AR 0015 S SVA-31 7196K 11236K 3900000
AR 0015 DYN-PA 342016K
AR 0015 DSPACE 174432K
AR 0015 SYSTEM 4416K
AR 0015 AVAIL 225568K
AR 0015 TOTAL 1117056K <----'
AR 0015 1I40I READY
GETVIS SVA
AR 0015 GETVIS USAGE SVA-24 SVA-ANY SVA-24
SVA-ANY
AR 0015 AREA SIZE: 3,784K 15,016K
AR 0015 USED AREA: 3,008K 10,496K MAX. EVER USED: 3,100K
11,192K
AR 0015 FREE AREA: 776K 4,520K LARGEST FREE: 692K
3,740K
AR 0015 1I40I READY
CA-EXPLORE 'DISPLAY STORAGE MAP'
Space Virtual-------- Total Pfix Area
Id Begin End V-Size Limit--Used Description
_ S 00000000 000D0FFF 836k 0k 0k $$A$SUPI
_ S 000D1000 000E0FFF 64k 0k 0k SDAID AREA
_ S 000E1000 000EAFFF 40k 0k 0k SVA-SDL
_ S 000EB000 00312FFF 2208k 0k 0k 24-BIT VIRTUAL LIBRARY
_ S 00313000 006C4FFF 3784k 8932k 1480k 24-BIT SYSTEM GETVIS AREA
_ S 006C5000 006DFFFF 108k 0k 0k LABEL WORK AREA
_ S 006E0000 006EFFFF 64k 0k 0k VPOOL FOR VIO
_ S 006F0000 006FFFFF 64k 0k 0k UNALLOCATED
....
_ S 03900000 04006FFF 7196k 0k 0k 31-BIT VIRTUAL LIBRARY
_ S 04007000 04039FFF 204k 0k 0k SYSTEM GETVIS CONTROL AREA
_ S 0403A000 04AFFFFF 11032k 1097kk 8168k 31-BIT SYSTEM GETVIS AREA
As you can see the GETVIS SVA command displays the actual 24/31-bit
system getvis. For GETVIS the MAP command includes the LABEL WORK AREA
& VPOOL area. For V-SIZE (PSIZE) the MAP includes the 24-bit virtual
library (SVA) & the SVA-SDL. This can be confirmed by the output from a
LIBR LD SDL report. By the way I have found that the SVA SDL= is
allocated in 4K amounts that equal 56 entries (72 bytes/entry). Let us
know when you release an updated version of VIRTSIZE.
STATUS DISPLAY SDL AND SVA DATE: 2004-09-21
TIME: 13:53
--------------------------------------------------------------------
SDL TOTAL ENTRIES : 566 (100%)
USED ENTRIES : 511 ( 90%)
FREE ENTRIES : 55 ( 10%)
SVA(24) TOTAL SPACE : 2208K (100%)
USED SPACE : 2189K ( 99%)
- PFIXED AREA: 164K ( 7%) START AT: 002E9FB0
FREE SPACE : 19K ( 1%)
SVA(31) TOTAL SPACE : 7196K (100%)
USED SPACE : 2759K ( 38%)
- PFIXED AREA: 560K ( 8%) START AT: 03F7AD98
FREE SPACE : 4437K ( 62%)
--------------------------------------------------------------------
Steve
>>> ***@dapsco.com 9/17/04 1:20:08 PM >>>
I was preparing yet another enhancement to my VIRTSIZE REXX
procedure, when I ran into a discrepancy between two VSE commands as to
the actual amount of virtual storage allocated/reported. Presumably,
someone here can explain this.
I previously had added a breakdown of GETVIS for each active
partition and I just realized I should have done this for System GETVIS
as well. (I'm sorry, but I don't get my ideas all in one big lump --
they come piecemeal.) At any rate... I made the change and ran the
procedure and found this reported for my 31-bit GETVIS:
VIRTSIZE VSE Virtual Size Analysis ...
Mode: LPAR (15010D4D) ...
Area Description K-bytes M-bytes ...
---------------------------------- --------- --------- ... Shared
Virtual Area (31-bit):
Virtual Library Area . . . . . : 3944 3.85
(current 31-bit VLA remaining : 1066 1.04 )
System GETVIS Area . . . . . . : 6296 6.15
(max. 31-bit GETVIS allocable : 8932 8.72 )
(min. 31-bit GETVIS remaining : 772 0.75 )
(curr. 31-bit GETVIS remaining: 1960 1.91 )
Normally, I wouldn't have noticed this because, with DETAILS=NO, the
max. and min. values shown above wouldn't even appear in the report.
However, notice what it says for the max. value as compared to the
previous line. That previous line comes from the MAP VIRTUAL command and
the next three lines come from the GETVIS SVA command. Can anybody
explain the difference?
Note: I also checked the 24-bit GETVIS and found this:
Shared Virtual Area (24-bit):
Virtual Library Area . . . . . : 1612 1.57
(current 24-bit VLA remaining : 14 0.01 )
System GETVIS Area . . . . . . : 2744 2.68
(max. 24-bit GETVIS allocable : 2636 2.57 )
(min. 24-bit GETVIS remaining : 0 0.00 )
(curr. 24-bit GETVIS remaining: 648 0.63 )
Unused Area . . . . . . . . . . : 64 0.06
Now, in this case, I chalked the discrepancy up to some portion of the
24-bit GETVIS area that is reserved by the system at IPL time and that
this amount is not included in the GETVIS SVA command output. This, of
course, is merely supposition on my part. However, lest you suggest it,
none of these numbers matches my user allocations for those areas:
SVA SDL=300,GETVIS=(1920K,5M),PSIZE=(320K,3M)
Lastly, please note that I have manually verified this information at
the console -- so this is not a program logic error. Thanks.
Sincerely,
Dave Clark
DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
(937) 294-5331
----------------------------------------
This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at ***@ailife.com.