Trevor,
What I do is make a copy of the dsmaccnt.log file (I don't know what kind of
platform you are on, but if you were on an AIX platform, you could issue a
grep command for, say the string ADSM,03/ to get the Mar records) for a
particular month and then go in with vi and delete the records that I have
copied out. If you do this while session activity is low, you will be in
good shape - maybe miss the occasional session while you are vi'ing the file
<G>.
Once you've pruned the dsmaccnt.log, then you could go through with ADSM and
archive that file with the -deletefile option to clean up the space on
/usr/lpp/adsmserv/bin (or if you're using HSM, selectively migrate that file
to ADSM).
It would be nice to have ADSM support an automatic pruning of dsmaccnt.log
to a second file (like can be done for the dsmsched.log file) in a future
release.
It would also be interesting to see what type of reports people have
actually produced using the dsmaccnt.log data...
John Rushton
Lockheed Martin M&DS
> ----------
> From: Trevor Foley[SMTP:Trevor.Foley AT BANKERSTRUST.COM DOT AU]
> Reply To: ADSM: Dist Stor Manager
> Sent: Sunday, March 29, 1998 22:45
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ADSM accounting file
>
> Hi,
>
> Our ADSM accounting file is starting to get quite large. I am after some
> ideas about how others handle this file. Certainly I have used the
> information in this file quite a number of times. So I don't want to
> just delete it, for example, on each system restart. But on the other
> hand, I don't think that it is necessary to back the whole thing up
> every day.
>
> I am thinking about something like renaming it monthly. Any suggestions?
> If I were to just rename it while ADSM is running, does it handle it
> nicely by just created a new file?
>
>
> Trevor
>
|