Re: Jobs in subsystems with status END

[rob@xxxxxxxxx]

I once had a printer writer that even an ENDJOBABN wouldn't end.  So I got 
real stupid and tried ENDSBS QSPL *IMMED.  Now, not only was that writer 
dead, but so was every other writer on the system until we IPL'ed.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/20/2004 11:21 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: Jobs in subsystems with status END






That's my experience also.  Generally jobs that get stuck in END status 
will
keep the subsystem from ending also.  There are ways to go in through
Display/Alter/Dump in Service Tools and correct the problem (if you can
figure out what it is) but that is risky and can cause unforeseen 
additional
problems, and you'll probably end up IPLing anyway.

We had a few problems last year with the MQ Series agent jobs (AMQZLAA0,
IIRC) hanging in END status.  The only thing that ever worked was 
ENDJOBABN,
fortunately we were on V5R1 at the time and not putting on many Cumes.  To
my knowledge the developers never did figure out what the problem was; we
finally got migrated to an 810 on V5R2 and it hasn't happened since.

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Fri, 20 Feb 2004 08:47:35 -0500
from: rob@xxxxxxxxx
subject: Re: Jobs in subsystems with status END

Will it?  Because I have jobs that I do an ENDSBS *IMMED on and they stay 
in END status until I do an ENDJOBABN.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

 
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains 
information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent 
responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, 
dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this 
communication
in error, please notify us immediately by e-mail, and delete the original
message.

_______________________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.