Sounds like its trying to rollback uncommitted DB updates.... Take a look at the call stack for that job and see what it's working on...
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of James Lampert
Sent: Thursday, September 18, 2008 4:56 PM
To: Midrange Systems Technical Discussion
Subject: Job taking forever to end -- never seen this before.
We've got a batch job that we canceled from WRKACTJOB, *IMMED, and it
seems to be taking forever to go away.
Any idea why? It doesn't have any spooled files.
There's SQL (and possible sql errors) involved, if that has anything to
do with it.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.