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

Debug/Killing a Lawson 10 Job

 5 Replies
 2 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
pops
Advanced Member Send Private Message
Posts: 46
Advanced Member
5/4/2016 6:36 PM

I'm looking for the steps to take to debug when a job is hung in Lawson 10, how to view the queues, how to get the status, etc.

In Lawson 9 we used to be able to use the ps -ef command to isolate a job running and use other UNIX commands to get information/handle a rogue process.

 

I'm not sure how to accomplish this in Lawson 10.

Thank you!

Allen

This_Guy
Veteran Member Send Private Message
Posts: 93
Veteran Member
5/5/2016 12:48 PM

Why can't you still grep the PID and kill it? Or jobschd ? 

pops
Advanced Member Send Private Message
Posts: 46
Advanced Member
5/5/2016 1:02 PM

Is that still the correct way to do it?

pops
Advanced Member Send Private Message
Posts: 46
Advanced Member
5/6/2016 5:13 PM

When we do a command like ps -ef it doesn't show any jobs it only shows our own process

 

Can you provide  me a couple examples of how to debug/kill a job in Lawson 10?  Lets say a user is running a GL290, how do I see this and how do I see this if I don't know the user running the GL290 just that a GL290 is running?

Vijay S
Veteran Member Send Private Message
Posts: 174
Veteran Member
5/11/2016 12:07 PM
We are on Lawson 9. jobschd works fine. Jobschd ----> F7 ---> select A ---> F8 (select A, B, C as per your requirement) ---> F9 delete. It should work fine for Lawson 10 since it is also S3........
Jeff Shumate
Advanced Member Send Private Message
Posts: 31
Advanced Member
5/11/2016 8:11 PM
If you are running version 10 on Unix it is the same method as version 9. Did you also move to Windows when you upgraded?