Re: infxalrm?

Larry Kemmerling wrote: [SNIP] > In the online log, I see: > > 07:36:40 Process exited with return code 137: /bin/sh /bin/sh -c /home1/informix/bin/infxalrm 2 23 "Logical Log 38613> Complete." "Logical Log 38613 Complete." This is not an errno. Return code 137 is the result of a script running some program that fails. I see this most often when someone uses the default logs_full.sh and has not set up a storage manager for onbar it returns codes in the 130's range. > Tech support is saying that the problem lies with the script referenced > by the ALARMPROGRAM setting. I've tried several different scripts, but > it doesn't seem to matter. I have included the script that I was using > when I first found the problem. Could you post that script again in plain text. Netscape is not translating it for me.... [MORE SNIPPING] Don't let tech support intimidate you. I've been using my own ALARMPROGRAMs since 7.13. They told me it HAD to be a ksh script and could not be an executable, but my eventalarm.c has been running now in 5 different 8.xx versions for three years! BTW if you want to test out working event handler code get my submission, utils3_ak, from the IIUG Software Repository. It contains a version of logs_full.sh that uses ontape instead of onbar and my eventalarm.c executable ALARMPROGRAM which does the same and MUCH MUCH more. Art S. Kagel