Concurrent job issue

I’m looking for feedback from the group. We had an issue where LP140 was running at the same time as PR140 which caused a database deadlock issue. Our users know not to run these jobs at the same time, but the situation still occurred due to human error.

We have recovered from the error, but I’m wondering how other users prevent this type of conflict from occurring.

0712131256598360.doc

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

A harsh solution would be to create a job queue which only allows one job at a time, then assign that job queue to LP and PR. Another method would be to create a multi-step job with both those jobs. Allowing whomever is last (LP or PR) to run it.

cbertagnolli

We also refer to the PR00 and LP00 after every update job to make sure one is complete before processing another

unknown

Why not use IPA? Have it perform the Inquiry for you. You could put it into an indefinite loop until the appropriate status and/or perform an exit with an inappropriate status. Many choices.

deanna-plant

Curious...does this deadlock only happen if the PR140 & LP140 are running for the same Process Level/Processing Group? Or can this happen if the PR140 is running for P/L ABC and the LP140 is running for P/L XYZ?

unknown

The setup here is one company and 3 process levels. Both the PR140 and the LP140 were running at the company level. The deadlock occurred on the TAEMPSERV table. I assume both programs were accessing the same employee record on this table.

Introduction.mp4

unknown

Thanks to everyone for the suggestions.....they have been very helpful.

Copyright © 2025 Infor. All rights reserved.