|
Ran into an issue with AJS record locking.
If in a job's 8=Change command list, that job will not be submitted
due to the record being locked by the interactive user, AJS monitor
job, QIJSSCD goes into a *LCKW status for 10 minutes.
During this 10 minute window, any other scheduled AJS jobs that
should have run are not submitted because the QIJSSCD job is in a
*LCKW status.
After 10 minutes, IJS6009 is posted, and the scheduled jobs from
above are submitted.
The QIJSSCD job then goes into a 2nd 10 minute *LCKW, trying for the
locked job.
This will continue until the 8=command list is exited.
These 10 minute delays caused other AJS production jobs to be run
later than scheduled, causing production issues. IBM development is
checking to see if this 10 minute lock could be changed.
I'm suggesting changing the 10 minutes to 1 second.
Any thoughts from the group?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.