Couple of ways. If you wish to be proactive (ie do something before you slam into the wall) you can periodically (ie once a minute) look at sysmaster syslogs view counting the number of rows where is_current = 0 and is_backed_up = 0. Once that number exceeds what ever threshold (as percent of total) you do your warning.
Other possibility is event driven. Place entry in your alarm shell looking for event 20. But now you are FULL and all update stop.
How do you use the log_full.sh with ALARMPROGRAM config parameter?
We use ism/onbar via an interface script our support department has written that works fairly well. Today, however, we had a scare when everything came to a screeching halt because we ran out of available logs. Apparently the logical logging was not started back up yesterday when the tape was swapped out.
Is there anyway to be notified how the logs are doing via email?
We have configured the ALERT log_full.sh to run whenever logical log files are full but i encountered SAP login problem when the logical log files were all full. The backup was not successfully, thus, logical log files were not backed up even when the alert was raised.
Now, i need to know the exact time when the logical log files were all full yesterday, realised the informix log did not mention it.