Re: Expire Inventory

     there are tons of other things...
     1) once a file is expired, its pointers to the tapes on which it
     resides still exist until tape reclamation clears it
     2) your activity log is stored in the DB, you may use the "set
     actlogretention ###" to adjust the number of days you keep that
     information
     3) you may want to daily run an audit license to update such things as
     the value listed by an "auditocc"
     4)...
     N) all client directory info is kept no matter what files exist or
     don't exist within them

     The DB is just FULL of misc other junk... here is a DB from a MVS adsm
     that I'm getting rid of... I mean there is NOTHING on this system, no
     policies, no clients, no schedules, no storage, just 3 admins and 1
     days worth of activity log...

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,172       124        60   4,096 2,348,032     3,962   0.2   0.2
    9,296    9,172       124        60   4,096 2,348,032     3,962   0.2   0.2




______________________________ Reply Separator _________________________________
Subject: Expire Inventory
Author:  malkit at unix,mime/DD.RFC-822=malkit AT UDI.CO DOT IL
Date:    3/14/99 7:32 AM


Hello !

I have a customer with 6GB of data base. We upgrade to to V3.1.2.1 and
run expire inventory. The output of the process was:

ANR0812I Inventory file expiration process 3 completed:
                          examined 372334 objects, deleting 101915
backup objects,
                          0 archive objects, 0 DB backup volumes, and 0
recovery
                          plan files. 0 errors were encountered.
ANR0987I Process 3 for EXPIRE INVENTORY running in the
                          BACKGROUND processed 101915 items with a
                          complition state  of SUCCESS at 12:01:43.

How come the data base didn't shrink ? We run audit reclaim and audit db
as well, and the data base is still 6GB.

I checked the number of files per node (LL_NAME) and got the following
results:

adsm> select node_name,count(ll_name) as "# files"  from backups group
by node_name


NODE_NAME         # files
------------------     -----------
BART                     539421
BART                     539421
HOMER                 5728376
LISA                       2918072
MAGGIE                117951
MARJ                     272645
SYDNEY                626943

--
Regards
Regards

Malkit Hayun , UDI
Storage Products Manager
IBM Certified Specialist-ADSM
Office: 972-3-9233440
Fax:    972-3-9233441
Mobile: 972-52-834575
Email: malkit AT udi.co DOT il