|
>This was a multipart message in MIME format. >Careful on ENDSBS! > >I had a writer job that wouldn't end, even with ENDJOBABN. So >I tried ENDSBS QSPL *IMMED. The end result? No printer output >until the next IPL. Because all jobs ended except the stuck job >the subsystem was in an END status and STRSBS wouldn't start it >because it was still ending. I couldn't find this technique in >"How to Win Friends and Influence People". > >Rob Berendt IBM Support once gave us an "at your own risk" solution for ending writers that wouldn't die. This was back in the good old days of pioneering AS/400-based TCP/IP printing. call qspendwa parm(<writer name>) It seems like an ENDJOBABN for writers. IIRC it had the same "you can't run this twice within 10 minutes" stipulation. I haven't had cause to use this method since V3. It worked quite well with writers that lost their mind while communicating to network print modules. The program still exists on my V5R1 system, but I'm afraid to call it. If I were stuck in your situation I would try it before I would try ending QSPL. Of course, I take no responsibility for what it might do to your system. -Jim James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@dollargeneral.com>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.