• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Monitoring lase

 5 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
scott--
New Member Send Private Message
Posts: 1
New Member
12/15/2011 11:12 PM
Hello all

I have a couple of Lawson systems that have been having trouble with lase.

I'm looking for a good way to automatically verify lase is up and functioning.   Is there a command line program that does some kind of simple lookup that depends on lase?

Ideally something (pseudo-code)

$ lawshowuser chbrown

I could then wrap that in a script and monitor the output.

Any clever ideas? 

Thanks

Scott
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
12/18/2011 11:05 PM
If you issue a startlase command, it will either start lase or tell you that it is already running? Will that suffice for your use?
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
12/18/2011 11:15 PM
Oh, also, if lase is not running, startlase will start it AND[\b] tell you that it started..
ie. If lase is not running your output will look similar to
lase: security environment 9.0.1.7.181 2010-08-10 04:00:00 (201010) started.

If lase is running, your output will be similar to:
Security Environment already started.
Xin Li
Veteran Member Send Private Message
Posts: 134
Veteran Member
12/19/2011 3:58 PM
If your Lawson is on Unix platform, you should be able to use ps -ef|grep lase to check whether lase process exists or not.
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
12/19/2011 4:10 PM
If you use what Xin Li suggests, make sure you exclude the actual grep command. ps -ef|grep lase|grep -v grep
EricS
Veteran Member Send Private Message
Posts: 80
Veteran Member
12/20/2011 1:52 PM
One of the things that I look for on my AIX platform is $LAWDIR/system/lase.pid. If its not there, I know lase is down and was brought down cleanly. If it is there, it gives me the PID of the lase process. You can ps -ef | grep `cat lase.pid` | grep -v grep