× 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.




It is currently working with lpr. But we would like to have a regular outqueue that is associated with this printer. Using lpr means we have to invoke the lpr command instead of simply overriding the outqueue using OVRPRTF.

That's not true. You can create a remote output queue with

CRTOUTQ OUTQ(blah) CNNTYPE(*IP) RMTSYS('blah.example.com') RMTPRTQ('lp') AUTOSTRWTR(1)

plus whatever host print transform options or whatever you want... then you can use OVRPRTF OUTQ(blah) to make stuff go there.

HOWEVER, I don't like the iSeries support for LPR in this manner, I've always thought it was really awkward. I prefer to use a regular device description rather than an output queue.

I'm pretty sure we can use any of the protocols (except maybe SMB). Will any of them work in a way so that I can do OVRPRTF OUTQ(IBM1422) and have it start printing?

My preferred method is to use a LAN attached printer. This is basically the whatchacallit... JetDirect? PJL? something like that... the HP protocol that runs on port 9100.


We have an HP 4200 laser printer with a JetDirect card that's configured as follows:

CRTDEVPRT DEVD(PRT01)               +
          DEVCLS(LAN)               +
          TYPE(3812) MODEL(1)       +
          LANATTACH(*IP)            +
          PORT(9100)                +
          FONT(011)                 +
          TRANSFORM(*YES)           +
          MFRTYPMDL(*HP4000)        +       <--- change this
          RMTLOCNAME('10.10.10.10') +       <--- and this
          SYSDRVPGM(*HPPJLDRV)      +
          TEXT('HP4200n in Accounting')     <--- and this.

The same printer supports LPR and other stuff, but we've found that this way works much better because programs see it as a local printer instead of a remote output queue.

I suppose "better" is relative, though. Our people are used to local printers, so maybe that's why this was easier for them.

Anyway, this is the printer that I test most of my PostScript code on, so I know it works :)


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.