How long are you keeping your activity log information ?

     What are your copy group specifics...?

     The data base is just tracking all the information saved by ADSM... if
     you are keeping a BUNCH you will have a BUNCH of data base entries...
     also remember that directory information is kept in the longest
     management class by default so each archive into a 7 day management
     class will place an entry into the longest (10 year keep if it exists)
     for the directory under which the file resides.

     And if you look into the .h files you will see that the HLqualifier is
     a var1024, LLqualifier is var256, filespace is (I think) var1024,
     etc... where a 10 byte file could use up over 200 times its size in a
     data base entry based on its directory path and file name.

     A bunch of our backups seem to press this limit with about 10 miles of
     date & time stamps down to the 10,000th of a second time stamp in
     their name.  (drives me nuts!)

     anyway,
            later,
                  Dwight


______________________________ Reply Separator _________________________________
Subject: Rapid database growth
Author:  connorj (connorj AT NIMO DOT COM) at unix,mime
Date:    6/23/98 10:47 AM


We are running an ADSM MVS server at level 3.1.0.2 since about the 2nd week
in April. Over the last month we've only added a couple new nodes but our
database keeps growing at an unusually high rate.  It has doubled in size
in the last month from 4GB to 8GB.  We run expire inventory daily and
delete volumehistory weekly.  Anyone else experienced this kind of growth
at maintenance level(3.1.0.2)?  Anyone have any tips on how to determine
what is causing the rapid increase?


Thanks,
Jeff Connor
Niagara Mohawk Power Corp
Syracuse, NY