|
TMTOWTDI - There's more than one way to do it - the motto for Perl, the language created by Larry Wall. BTW, the HLD/WTR means that the outq is held and there is an active writer attached. I concur - no stupids living here. Regards At 08:39 AM 3/15/02 -0500, you wrote: >You're not a moron at all, I learnt about it my self in 98 and I've been on >the system since late 90. That is the beauty of the system in my opinion, >there is just not one way to do things. > >Dare > >----- Original Message ----- >From: "Jeff Crosby" <jlcrosby@dilgardfoods.com> >To: "Midrange Mailing List" <MIDRANGE-L@midrange.com> >Sent: Friday, March 15, 2002 8:20 AM >Subject: Held OUTQ > > > > I learned a new one today. > > > > One of our print devices (P6) was not printing. WRKWTR showed it > > started and released properly. I put an 8 in front of it to show the > > OUTQ. The spool files were listed normally. Didn't understand what was > > happening. > > > > Then I noticed at the top of the screen it said: > > > > Status: HLD/WTR > > > > But the writer wasn't held. I couldn't release it. I could hold it, > > then release it, but it still showed held. Stopped and started the > > writer. No good. Power cycled the printer. No luck. Was about ready > > to delete/recreate the device description thinking it was damaged, but I > > decided to do a WRKOUTQ *ALL first. Lo and behold, it showed the _OUTQ_ > > as held. I didn't know you could do that. Put a 6 in front of it to > > release it and away it went. > > > > I've been using an AS/400 since almost it's inception. I didn't know > > until today that an OUTQ could be held/released independantly of the > > writer. The rest of you are probably thinking what a moron <g>. I > > wonder who held it and why. > > > > Learn something new every day. > > > > -- > > -Jeff > > > > The opinions expressed are my own and not necessarily > > the opinion of my company. Unless I say so. > > > > _______________________________________________ > > 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/cgi-bin/listinfo/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. > > > >_______________________________________________ >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/cgi-bin/listinfo/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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.