× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



At 08:46 AM 3/7/02 -0600, you wrote:

>Vern wrote:
>"Dumb question time - is there any point to the printers being different
>types? We have no control over this, right?"
>
>"Am trying an experiment with remote outqs."
>
>Vern -
>
>Not sure what you meant by "the printers being different types".

Like a 5225 and a 3812, etc. Multiple printers attached to an outq this way
should all put out the same result, I would think. On the same paper size, etc.

There would seem to be little point in using remote printers as multiple
destinations for printing, unless they're all in the same room at some far
off building. Eh?

>When TCP/IP printing was originally introduced on the '400, remote outqs
>were the (only) way to go.  In the last few years, however, IBM has
>enhanced the IP printing implementation so that printer devices of type
>*LAN are, in most cases, the preferred method of TCP/IP printing.  I say
>"in most cases" because there are shops where it is necessary to do LPR/LPD
>printing via remote outqs.  I don't know if your shop fits in this category
>or not.  If it does not fit in this category, I suggest investigating the
>use of *LAN type printer devices.  If your shop *does* fit in this
>category, read on.

Are they not LPR/LPD under the cover? I've not looked at this in some time.

>The 'writers to autostart' parm of the CRTOUTQ command makes absolutely no
>sense to me.  Here's why:
>If I am creating an outq with this command and giving it an IP address
>(this is what makes it a remote outq), there is only one IP address that I
>can provide per outq.  If I start more than one writer pointed at the same
>IP address the LPR daemon on the other end is going to be overwhelmed (or
>at least whelmed) by the multiple LPD requests coming from those multiple
>writers.  (This is why you were seeing RUN and DLYW statuses (statii?).)
>Apparently, you've come to this same conclusion, based on your statement "
>they are all going to the same LPD port, so what can you expect?"  When I
>use RMTOUTQs, I only start one writer for this very reason.

Would you believe the plural of status, in the original Latin, is status?
No kidding.

>Again, unless you have an immovable obstacle which forces you to use
>RMTOUTQ, you should be using CRTDEVPRT DEVCLS(*LAN).
>
>HTH,
>
>Steve
>
>_______________________________________________
>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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.