Scanning the old messages I came across a "suspicion" from Neil Truby
that IDS 9.2 was't recording all changes to ONCONFIG in the message
log.
I've recently spent many days trying to find why a problem had recurred
and eventually I discovered that it was because a previous change to
ONCONFIG had been undone. The problem I now have is to find out who
undid the change, and why?
I thought I would find out when the change occurred but it doesn't
appear in the message log, which fortunately hasn't been cleared down
for a long time.
Does anybody know why all ONCONFIG changes are not recorded to the log?
And what mechanisms can I use to track all the changes.

regards

Malcolm

mweallans@panacea.co.uk wrote:
> Scanning the old messages I came across a "suspicion" from Neil Truby
> that IDS 9.2 was't recording all changes to ONCONFIG in the message
> log.
> I've recently spent many days trying to find why a problem had recurred
> and eventually I discovered that it was because a previous change to
> ONCONFIG had been undone. The problem I now have is to find out who
> undid the change, and why?
> I thought I would find out when the change occurred but it doesn't
> appear in the message log, which fortunately hasn't been cleared down
> for a long time.
> Does anybody know why all ONCONFIG changes are not recorded to the log?

Because there isn't enough room in the reserved pages for all the
parameters that can exist in the ONCONG file.

> And what mechanisms can I use to track all the changes.

I use RCS; you could use CVS, SCCS, Clearcase, Subversion, Perforce,
Tour de Force, Tour de France - or any other configuration management
package that takes your fancy.


--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.01 -- http://dbi.perl.org/