alrmprogram

hello we recently upgraded from version 11.7.FC4 to 11.7.FC5 on AIX 6.1. The scripts we use for the backups and alarms are the same (except for the new paths, of course) and we have ADMIN and PAGER set to ALARMADMIN=3 , ALARMPAGER=4 - just as before. The difference we are seeing now is that when i start a level 0 backup and then abort the backup, we no longer receive a page for the abort. We use NetBackup and so didn't think there is any additional configuration needed in conjunction with that so we are stumped why the page used to go out but now does not - ? thanks in advance for any help Tom

On Tuesday, June 26, 2012 9:28:44 AM UTC-5, tom...@gmail.com wrote: > hello > > we recently upgraded from version 11.7.FC4 to 11.7.FC5 on AIX 6.1. > The scripts we use for the backups and alarms are the same (except for the new paths, of course) and we have ADMIN and PAGER set to > ALARMADMIN=3 , ALARMPAGER=4 - just as before. > The difference we are seeing now is that when i start a level 0 backup and then abort the backup, we no longer receive a page for the abort. We use NetBackup and so didn't think there is any additional configuration needed in conjunction with that so we are stumped why the page used to go out but now does not - ? > thanks in advance for any help > Tom I haven't looked at this alarm program very much, but a quick look at the default $INFORMIXDIR/etc/alarmprogram.sh shows that it does a comparison of the event severity to the value of ALARMPAGER and if it's less then it does an echo of the message "Event Severity = $EVENT_SEVERITY is lower than ALARMPAGER=$ALARMPAGER" followed by "No mail will be sent to PAGEREMAIL". So in theory that should be going some where...I'm just not sure where that echo is going. So you could do a temporary modification of the script to echo that message along with a date/time to a known file and verify when the backup is aborted if the alarm program script is still getting kicked off or not, and if it is getting kicked off, then you'll see if the level of the event severity perhaps has been changed such that it's now in 11.70.FC5 less then 4. Once you verify that, perhaps you could work around it in the script, or open a PMR with support and attempt to report it as a defect/change in behavior. I'm not sure but it might have been an intentional change to the event severity of an aborted archive. Jacques Renaut IBM Informix Advanced Support APD Team

On Tuesday, June 26, 2012 9:55:43 AM UTC-5, jrenaut wrote: > On Tuesday, June 26, 2012 9:28:44 AM UTC-5, tom...@gmail.com wrote: > > hello > > > > we recently upgraded from version 11.7.FC4 to 11.7.FC5 on AIX 6.1. > > The scripts we use for the backups and alarms are the same (except for the new paths, of course) and we have ADMIN and PAGER set to > > ALARMADMIN=3 , ALARMPAGER=4 - just as before. > > The difference we are seeing now is that when i start a level 0 backup and then abort the backup, we no longer receive a page for the abort. We use NetBackup and so didn't think there is any additional configuration needed in conjunction with that so we are stumped why the page used to go out but now does not - ? > > thanks in advance for any help > > Tom > > I haven't looked at this alarm program very much, but a quick look at the default $INFORMIXDIR/etc/alarmprogram.sh shows that it does a comparison of the event severity to the value of ALARMPAGER and if it's less then it does an echo of the message "Event Severity = $EVENT_SEVERITY is lower than ALARMPAGER=$ALARMPAGER" followed by "No mail will be sent to PAGEREMAIL". So in theory that should be going some where...I'm just not sure where that echo is going. So you could do a temporary modification of the script to echo that message along with a date/time to a known file and verify when the backup is aborted if the alarm program script is still getting kicked off or not, and if it is getting kicked off, then you'll see if the level of the event severity perhaps has been changed such that it's now in 11.70.FC5 less then 4. Once you verify that, perhaps you could work around it in the script, or open a PMR with support and attempt to report it as a defect/change in behavior. I'm not sure but it might have been an intentional change to the event severity of an aborted archive. > > Jacques Renaut > IBM Informix Advanced Support > APD Team Thank you much - we have an open PMR so will give this a shot Tom

strange - we went to an existing system and tried a test there and it also did not send a page on a level 0 abort. so the mystery deepens.