Since ADSM data base behavior has been brought up... take a gander at one of
mine!
Why do I have 80% free yet only a max reduction of 0.4%
I only have 5 nodes registered here and only keep the act log 5 days and the 5
nodes on this box currently back up to another box... that is, my activity log,
for 5 days is only about 5 screens long showing my standard admin events
running.
Session established with server MVSOSAP: MVS
Server Version 3, Release 1, Level 1.3
Server date/time: 01/05/1999 13:51:19 Last access: 01/04/1999 16:05:49
adsm> q db
Available Assigned Maximum Maximum Page Total Used Pct Max.
Space Capacity Extension Reduction Size Usable Pages Util Pct
(MB) (MB) (MB) (MB) (bytes) Pages Util
--------- -------- --------- --------- ------- --------- --------- ----- -----
9,296 9,196 100 40 4,096 2,354,176 466,067 19.8 20.0
9,296 9,196 100 40 4,096 2,354,176 466,067 19.8 20.0
later,
Dwight
______________________________ Reply Separator _________________________________
Subject: Peculiar ADSM database behavior.
Author: bdc (bdc AT WORLD.STD DOT COM) at unix,mime
Date: 1/5/99 1:33 PM
Perhaps this is normal behavior and I'm just ignorant of some aspect of
ADSM's internals, but I've discovered something which looks rather odd.
What follows is an administrative client session capture which illustrates
this behavior. The server software version is 3.1.1.5.
The following example uses a simple ADSM macro (in.dsm) I wrote for
listing the volumes for a given storage pool which are currently checked
into the the library.
--- in.dsm macro ---
select volume_name from volumes \
select volume_name from volumes \
where stgpool_name = %1 \
and volume_name in \
( select volume_name from libvolumes )
---
Please make special note of the number of megabytes listed under the
Please make special note of the number of megabytes listed under the
Maximum Reduction column heading from the "q db" commands and how it seems
to relate to the correct functioning of the macro.
--- Admin session caputure ---
adsm> q db
adsm> q db
Available Assigned Maximum Maximum Page Total Used Pct Max.
Space Capacity Extension Reduction Size Usable Pages Util Pct
(MB) (MB) (MB) (MB) (bytes) Pages Util
--------- -------- --------- --------- ------- --------- --------- ----- -----
49,152 38,640 10,512 4 4,096 9,891,840 8,043,707 81.3 81.4
49,152 38,640 10,512 4 4,096 9,891,840 8,043,707 81.3 81.4
adsm> macro adsm/in.dsm 'SERVERPOOL'
ANS8000I Server command: 'select volume_name from volumes \
where stgpool_name = 'SERVERPOOL' and volume_name \
in ( select volume_name from libvolumes )'
VOLUME_NAME
------------------
001001
001001
001005
001019
001033
001034
001043
001050
[etc...]
adsm> reduce db 4
ANR2250I Database assigned capacity has been reduced.
adsm> q db
Available Assigned Maximum Maximum Page Total Used Pct Max.
Space Capacity Extension Reduction Size Usable Pages Util Pct
(MB) (MB) (MB) (MB) (bytes) Pages Util
--------- -------- --------- --------- ------- --------- --------- ----- -----
49,152 38,636 10,516 0 4,096 9,890,816 8,043,708 81.3 81.4
49,152 38,636 10,516 0 4,096 9,890,816 8,043,708 81.3 81.4
adsm> macro adsm/in.dsm 'SERVERPOOL'
ANS8000I Server command: 'select volume_name from volumes \
where stgpool_name = 'SERVERPOOL' and volume_name \
in ( select volume_name from libvolumes )'
ANR2034E SELECT: No match found using this criteria.
ANS8001I Return code 11.
ANS8029E Macro processing terminated.
adsm> extend db 4
ANR2248I Database assigned capacity has been extended.
adsm> q db
Available Assigned Maximum Maximum Page Total Used Pct Max.
Space Capacity Extension Reduction Size Usable Pages Util Pct
(MB) (MB) (MB) (MB) (bytes) Pages Util
--------- -------- --------- --------- ------- --------- --------- ----- -----
49,152 38,640 10,512 4 4,096 9,891,840 8,043,710 81.3 81.4
49,152 38,640 10,512 4 4,096 9,891,840 8,043,710 81.3 81.4
adsm> macro adsm/in.dsm 'SERVERPOOL'
ANS8000I Server command: 'select volume_name from volumes \
where stgpool_name = 'SERVERPOOL' and volume_name \
in ( select volume_name from libvolumes )'
VOLUME_NAME
------------------
001001
001001
001005
001019
001033
001034
001043
001050
[etc...]
---
Is a certain amount of "reduceable" overhead required for correctly
Is a certain amount of "reduceable" overhead required for correctly
running select's? Any insight would be appreciated.
-brian.
=========================================================================
|
