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



We currently have an IBM 6400 line printer connected via twinax, and an
application that uses the DDS keyword BARCODE in the printfile to print
some bar codes on a report.  The 6400 printer is defined as an IPDS
printer, and when the PRTF is compiled, DEVTYPE(*IPDS) needs to be
specified.

We now wish to attach the 6400 to the AS/400 using TCP/IP via a HP
Jetdirect card.  When we test this, all output except the report containing
the barcodes print OK.  That reports prints all garbage characters.  The
attributes of the spool file show "Barcodes .....Y".

I have searched everything I can think of to find out a way to define this
printer so the barcodes will work.   Creating a 3812 device description
(ie, *LAN 3812 PJL) is not an option, since IBM says this is not supported
for 6400's.  And there doesn't seem to be a way to do a CRTOUTQ that will
support IPDS.  (I'm assuming IPDS is what the BARCODE needs).

Any ideas would be greatly appreciated.

Scott Lindstrom
Zenith Electronics





+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.