RE: New command request: EDNZMBJOB

QSPL?  Can you even end a writer using ENDJOBABN?  Back in the early days of
TCP/IP printing to network devices I had to end uncooperative writer jobs
all the time.  ENDJOBABN did not work for writers.  IBM support had me call
a program:

CALL QSPENDWA PARM(<writer name>)

...which was supposed to be SPool END While Active.  It worked pretty well.
Yesterday, for the first time in ages, I had to use it on an HP Laser Jet
device.  The program still works in V5R1.  I've never had to end the spool
subsystem -- the program usually kills jobs within five minutes.

Actual results may vary.

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@xxxxxxxxxxxxxxxxx>


-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Friday, March 14, 2003 1:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: New command request: EDNZMBJOB


QSPL.  Hey, that's the one I tried also.  So, what I thought should be a 
simple fix effectively stopped all printer writers until the next IPL. 
Could not start that subsystem back up because it hadn't ended all the 
way.  I missed that chapter in "How to Win Friends and Influence People".

If you want the same sort of rotten lock out of QINTER, I suppose you 
could try it there also.  Me - I'd rather be staked n@xxx to an ant hill.

This is why I said NOT to try ENDSBS.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




Raul A Jager <raul@xxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/14/2003 01:41 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: New command request: EDNZMBJOB


I already tried ENDSBS. It didn't work for QSPL, it ended all writers 
except the zomby one.  It may work fo QINTER.

rob@xxxxxxxxx wrote:

>Welcome to the iSeries.  This is part of IBM's attempt to make it more 
>Unix compatible.
>
>Do NOT try ENDSBS!  The jobs will still not end, and you've effectively 
>prevented any new jobs from starting in that subsystem until the next 
IPL.
>
>I did notice some obscure function in iSeries Navigator to track down 
some 
>misbehaving threads.  This was quite useful for some Domino jobs.  I 
might 
>try this the next time that TSM gets to be a bother.
>
>Rob Berendt
>