Lawson status alerts

I'd write your script to do a ps -ef | grep latm and ps -ef | grep ladb and ps -ef | grep lase (if you are on LS security) and ps -ef | grep queue

If any of these don't return results, lawson (or some part of lawson) is likely down.

You may have to modify it to exclude the actual grep return. And I'm sure there are other ways to do it as well.

Much thanks Greg. Will keep you posted with how it goes.
Initially I was thinking on the lines for grepping for error messages in the log files and scanning for any core dumps.

Not sure what system you are on, but on my AIX box $LAWDIR/system has two files, ladb.pid & lase.pid, I look at those two files and see if the PID listed is running.

Badri,

Because you are running 803 without portal, the primary processes you need to monitor for are latm, ladb, lajs, jobqueue, and perhaps queue.

You have no apache http, tomcat, rmi, processflow, or other web based processes to worry about.

Give me call.  I may have some scripts you could execute with a kron job that would give you everything you need.  If not, I can definitely work with you to accomplish your goals.

Good point EricS. He's on Solaris like we are here. I've only got a ladb.pid and lase.pid in my $LAWDIR/system though. 901.9
badri could combine both of our approaches though... depends on what .pid files are there in 803.

Thanks Guys ! I am planning to monitor the ladb.pid . As Greg points out, we are not using lase .
But I have a question, have you had the Lawson freeze with a core dump ?

Thanks again !

I've never seen Lawson freeze with a core dump... occasionally there will be core files around, but I've never had them be the cause of a freeze in Lawson. Defunct/Zombie tasks in tmmon/tmcontrol, now that's another story.