Re: ALARMPROGRAM (was DSA 7.22 UC1 on HP-UX 10.10 Crash )

>Mark Collins wrote: [...] >> It seems that for some reason, under 7.23.UC6 at least, that a blank value for ALARMPROGRAM >> may cause the engine to default to $INFORMIXDIR/etc/log_full.sh, whether you want it or not. >> Remember, I said I left the ALARMPROGRAM blank in the onconfig, yet we see that the engine >> notes the parameter has changed. To get around this, I changed it to >> $INFORMIXDIR/etc/no_log.sh. Has anyone else seen this? John contributes: [...] >Informix will automatically assume an ALARMPROGRAM is active. Not too >bad, really . . . I've always wanted to experiment with Informix alarm >capabilities. The release notes for 7.23 mention bug #67335, described as "ONCONFIG.STD ALARMPROGRAM SETTING INCORRECT." At the moment I'm web-impaired, so I'll leave it as an exercise for the reader to research more about that bug. The engine does indeed default to log_full.sh if there is no value in the onconfig parameter ALARMPROGRAM, but you can change it to be whatever you want. I've wondered why people don't use the ALARMPROGRAM more often. It is a very powerful feature that we used to have to kludge up for ourselves. I strongly advise any DBA to automate monitoring functions. Let us rejoice to have a vendor that provides it for us! A tutorial on the practical implementation of the ALARMPROGRAM, especially with field-proven examples, sounds like an excellent topic for the IIUG technical track. Anyone care for a free conference pass in Seattle? (Submit your proposal--it's easy--at the IIUG site http://www.iiug.org .) ___________________________________________________________ Clem Akins (aka clem@informix.com) Informix Software, Inc (Standard disclaimers apply) International Technical Support Last seen: Reveling in the view of a Fujiyama sunrise