Re: MIDRANGE-L Digest, Vol 3, Issue 272

Thanks All!
 
I did try the ENDJOBABN command and the job dropped off of the WRKACTJOB screen 
for a minute, but it reappeared!  I never considered trying to end the 
subsystem because the job was still there.
 
We IPL'd the system and all is well now.
 
Note:  We had just applied the latest cume tape earlier this week before this 
started happening... hmmm...
 
-ww3
 
date: Thu, 19 Feb 2004 22:30:39 -0000
from: "Colin Williams" 
subject: Re: Jobs in subsystems with status END

William,

have you already tried ENDJOBABN on the the first job that had a problem,
sometimes this gets them.

I have seen this happen only a couple of times in my time on a '400. If the
ENDJOBABN doesnt get it, its IPL time I think, unless someone else has
another method

cheers
Colin.W

----- Original Message -----
From: "William Washington III" 
To: 
Sent: Thursday, February 19, 2004 9:11 PM
Subject: Jobs in subsystems with status END


> There are a number of jobs on our system that have a status of END, but
they are not dropping off of the WRKACTJOB screen. They are getting zero
cpu. They have no I/O.
>
> I cancelled a batch job yesterday, and it is still in the QBATCH subsystem
with status of END.
>
> Has anyone had this problem before? Do I need to stop and restart the
subsystem to get rid of these jobs? Of must I do something more drastic?
(e.g. IPL the system...)
>
> William