I've looked at a lot of installations using vdisk - I've only once seen
an installation where vdisk "seemed" to be an issue - and that was when
the installation had followed the 2 vdisk for swap guideline, but
reversed the priority on the two disks and the larger one was used
instead of the small one.
So unless you've come up with a new imaginative way to use vdisk, use
"INFINITE" and use the ESAMAP report ESASTR1 to understand the cost.
There are many more important things to work on....
Schuh, Richard wrote:
Is there a formula that can be used to determine what the default SYSLIM
for V-disks would be in the absence of any SYSTEM CONFIG definitions? If
I enter QUERY FRAMES, I get this:
q
frames
All
Frames:
Configured=38273023 Real=38273023 Usable=38273023
Offline=0
Pageable=37871142 NotInitialized=0
GlobalClearedAvail=160
LocalClearedAvail=160
LocalUnclearedAvail=155
Frames <
2G:
GlobalUnclearedAvail=56339 Pageable=513876
LogicalFreeStorage=5602
RealFreeStorage=5 LockedRS=497
LockedCmd=0
MinidiskCache=8 Nucleus/Prefix=2521 Trace=400
Other=1386
Frames >
2G:
GlobalUnclearedAvail=4046728 Pageable=37357266
LogicalFreeStorage=55733
RealFreeStorage=19 LockedRS=15358
LockedCmd=0
MinidiskCache=97600
Other=320360
Assuming that the dasd space is sufficient to not be a limiting factor,
does this give enough information to calculate a default SYSLIM?
Regards,
Richard Schuh
