Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Strange job scheduler issue
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
250
Members:
0
Total:
250
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Strange job scheduler issue
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
LauraPat
Veteran Member
Posts: 50
2/5/2019 3:38 PM
Had an issue last night that in 25 years working with Lawson I've never seen. I had a batch job (that's been running for 3 years without issue), that has 66 steps. On step 26 it failed and went into needs recovery. Only error msg as "Stopped on Exit 1". Any attempt to recover the job resulted it in going back into needs recovery immediately. Tried putting a trace on the program to see where it was failing and it wasn't getting into the program. Appears to be a hiccup in the job scheduler and it "lost it's place". I had to create another job, with all the remaining steps and run that and that worked fine. Has anyone seen anything like this happen in the job scheduler? We are on Version 10 on-premise. Thx
John Henley
Senior Member
Posts: 3348
2/5/2019 4:28 PM
I have seen it a lot recently on LSF 10 on windows.
LauraPat
Veteran Member
Posts: 50
2/5/2019 4:44 PM
Wow - that's very disconcerting. We are on Linux but if the issue is occurring on Windows, it's not all that surprising that we are seeing it. I've opened a ticket with Infor but I'm not sure they are going to be much help because even though it is clearly a job scheduler issue - the programs being run are custom programs .. But this is very ugly when it happens and I hope this doesn't mean it is going to start happening more often.
You are not authorized to post a reply.