It's working below MI. We had a job extending an index that regularly
took ages to end. If you think of MI as the surface of the water, a job
can only know that you've requested an ENDJOB when it comes up for air.
A job in this state cannot report its CPU usage. If you reset WRKACTJOB,
this job will show 0% CPU. In our case it was an EVI index I had been
playing with and forgot to remove.
[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.
James H. H. Lampert
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l
As an Amazon Associate we earn from qualifying purchases.