Hi all,
 
A client site I work with started using IMAGE logging recently in order to
pinpoint the source of some application problems. I wrote a quick-and-dirty
logfile analyzer to convert the IMAGE logging information into a
people-readable form so that we could find out who was doing what to whom and
with which program.
 
The problem is that their data base is fairly dynamic: they use a
restructuring tool to add and remove items, and this can happen a couple of
times a month.
 
Besides running the analysis tool every night and saving the results -- which
could be huge -- has anyone else solved the problem of creating a useful
analysis of an IMAGE log file after the data base structure has changed?
Obviously big changes can't be coped with, but if there's some strategy for
handling small ones, I'd like to find out about it.
 
-- Bruce
 
--------------------------------------------------------------------------
Bruce Toback    Tel: (602) 996-8601| My candle burns at both ends;
OPT, Inc.            (800) 858-4507| It will not last the night;
11801 N. Tatum Blvd. Ste. 142      | But ah, my foes, and oh, my friends -
Phoenix AZ 85028                   | It gives a lovely light.
[log in to unmask]                   |     -- Edna St. Vincent Millay