|
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] We experienced a problem today that I've not encountered before. A pick list print job was running and entered a LCKW state (as shown on WRKACTJOB) and stayed in that state for a long time. So long, in fact, that I ended up ENDJOB *IMMED and then eventually needed to use ENDJOBABN. What confounds me is that I was unable to determine what resource the job was waiting on. When I displayed job record locks, there were none. I tried using the WRKOBJLCK from the job's list of locks and besides being tedious, I was still unable to identify a resource for which the job was waiting. I also used WRKACTJOB and scanned the job lists to see if any other jobs were in an unusual state that might have been causing the conflict (especially the QDBSRVxx jobs) - and found none. Finally, I used DSPLOG to see if the system was reporting any messages like damaged objects or such - again, nothing reported (I also checked DSPMSG QSYSOPR). Interestingly, there were no other user-submitted "batch" jobs running at the time - so I couldn't blame it on a query building an index! As soon as the job was ended, other queued jobs which ran the same process began running and continued without incident. Does anyone have an idea of what may have been behind this? Is there another command or way to see what resources a job is waiting for? ==Kevin TEL: (614) 659-1666 FAX: (614) 659-1667
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.