Re: Kill this job!!!

[Raul A Jager <raul@xxxxxxxxxx>]

I had already tryed

SPLFILE(*YES), 
your sugestion provoked this response:  Job is already ending by 
ENDJOBABN, I think that was caused when the spool file got full, it 
changed the log limit, and the next meesage tells me that the spool was 
already suppressed.

I will try to end the subsystem at a time when there are less people 
using QINTER.

3>> wrkusrjob magnolia
    500523/MAGNOLIA/CAMPA_02 ya finalizando debido a ENDJOBABN.
    LOGLMT cambiado para el trabajo 500523/MAGNOLIA/CAMPA_02.
    Se ha suprimido anteriormente la salida en spool del trabajo
      500523/MAGNOLIA/CAMPA_02.
    500523/MAGNOLIA/CAMPA_02 ya finalizando debido a ENDJOBABN.


fiona.fitzgerald@notes.royalsun.com wrote:

> As a last resort, you might have to end the subsystem the job is running
> in.
> Better than an IPL anyway.
>
> Have you tried ENDJOB
> OPTION(*IMMED)
> SPLFILE(*YES)
> LOGLMT(0)
>
> That might just do it.
>
> We had a rogue job like that & had to end & restart QINTER to get rid of
> it.
> After a few hours it stopped showing as a job or a task & just slowed
> everything down.
>
> Fiona
> fiona.fitzgerald@notes.royalsun.com
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>