|
I have written a WRKRMTWTR utility for just these cases. It's only for outq's defined for an IP connection. Get your copy today---> http://home.columbus.rr.com/jbmmdietz/iseries.html ------------------------- Bryan Dietz 3X Corporation 614-410-9205 midrange-l-bounces@xxxxxxxxxxxx wrote on 07/24/2003 09:48:31 AM: > Okay. I think I'm starting to see where this is going. > > We usually just type WRKWTR which creates the impression that EVERYTHING is > displayed since no selection criteria is stated. > > However adding *ALL has unmasked the "outq only" devices! > > It appears the difference lies in that printers normally visible are type > PRT whereas others are RMT. > > Do you think there will be any problems if I change the device type to PRT? > > Also some of the libraries for these printers is QGPL whereas most are > QUSRSYS. For the sake of consistency do you forsee any problems with moving > the QGPLs over to QUSRSYS? > > Thanks Jan. This was probably a very easy question to begin with but I > unearth this stuff as I move along in little bits and pieces :) > > Alan > > > > "Jan Rockstedt" > <jan.rockstedt@xxxxxxxxxxxxxxxxx> wrote in > message news:03Jul24.151047cest.119066@xxxxxxxxxxxxxxxxxxxxxxxxx > > Hi Alan ! > > > > Have you try wrkwtr *all ? > > > > //Jan > > > > -----Original Message----- > > From: Alan Kincer > [mailto:w2kprofessional@xxxxxxxxx] > > Sent: den 24 juli 2003 15:11 > > To: midrange-l@xxxxxxxxxxxx > > Subject: Differences among network printer setups > > > > Jobs in most of the IP printers in our organization are managed via > > WRKWTR > > however some can only be reached by directly accessing the respective > > outq. > > Can anyone tell me why this would be and if it's possible to get the > > latter > > associated with writers? > > > > Thanks. > > > > Alan
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.