TCL Alert configuration

The first error (invalid command name “alert_test”) could have been that the name of your proc didn’t match what was in the Alert configurator, or your alert hadn’t been added to the tclIndex. I think the Cloverleaf TCL editor should do that for your automatically, or you can run mktclindex from the command line. In any case, it looks like that error went away and you’re on to another problem.

I’m not sure about the “missing close-brace” error. The braces in the config file that you posted all seem to match. Are you using the script editor with the Alert configurator or are you editing the default.alrt file with a text editor? I recommend using the configurator.

When you used the script editor did you specify it was an alert proc?  The alert engine looks at the proc header for TPS type

In version 5.8.4, and possibly others, the Alert function failed to process an alert if the text ‘Alert’ was part of the name. Not sure if lowercase ‘alert’ has the same issue. Can you try renaming the alert to something else?

I’d like to see resolution to this thread because I am seeing the same problem here. I basically did all the same things that Brian did and I’m getting the “invalid command name” error. I’m using the same default tcl code provided through the designer with a couple minor tweaks to the proc name, very basic, etc. and can’t get it to fire.

Additionally, it would be nice to know what exactly the Comparing: value is related to. I’ve tried 0 — I think that covers all bases — but the thing never fires. Of course, an invalid command name “my_test” could be preventing it, but it’s hard to say what is going on.

Ken, Have you tried setting your retval to 1 to see if it fires? I have a script that is monitoring a print queue that might help.

{ALERT

   { NAME {PLUE FOD has print jobs queueing} }

   { VALUE tcl }

   { SOURCE {

       { TCL {alrt_plue_printer plueprod} }

       { TIME {count 12} }

   } }

   { WITH -1 }

   { COMP {== 1} }

   { FOR {nmin 5} }

   { REPEATING {

       { MAX 30 }

       { TIME {nmin 5} }

   } }

   { WINDOW */*/*/* }

   { ACTION {

       { notify {} }

       { email {

           { FROM cloverleaf@infor.com }

           { TO staff@myfacility.com }

           { SUBJ {cloverleaf alert – picis_rx_file_out has 50+ messages queued} }

           { MSG {the FOD print queue has print jobs queued for more than 5 minutes.  Check prodsiteone – This affects Plue Prescrioption Printing.  

} }

       } }

   } }

}

Hey, Bret!

Thanks for your feedback. I see where I was going wrong – I didn’t have the keylist variable set up properly – it’s the VALUE that triggers the message. Man, I’ve been working on getting this to work for quite a few hours – Thanks!

Incidentally – I *do* have to restart the monitor daemon after making changes to the tcl code.

Hey Ken,

I am having the same issue with this I think that you are. What did you set your keylist variable to?

Thanks,

Send me an email and I’ll send you all I found out about this with screenshots and sample email message.

I kind of lost interest in this because the alerts seem to be inconsistent and we were diverted to more important stuff for the time being. There is an email link in my reply.

Incidentally – I *do* have to restart the monitor daemon after making changes to the tcl code.

This was the last piece of the puzzle for me.  Thanks!  I followed all of the tips given by everyone else here, from choosing tclalert as the proc type to making certain that I was returning values properly, but nothing worked… until I restarted the monitor.  At that point, all three versions of the alert I had built started firing off e-mail to me.  Many thanks, again, for your contribution (though I admit to feeling silly for not having restarted it on my own 🙂 ).