|
Hmm... seems everyone is on vacation... anyway I finally found the solution to this cups issue. For some reason printing does not work properly if the -l ( that is the lower case letter L! )option is not given for the lpr command. To get printing working fine, the outputcommand statement must be as follows: scs2ascii | lpr -h -l -Pprintername the same is true for scs2ps. with scs2ps and ibmmfrtypmdl=*hp4 the printer only prints the header for each page, and dumps the rest of the content if the -l is not used. bit annoying that. The -h is needed to suppress header pages which cups also insists on printing.... cheers, and welcome back from vacation! Elmars Ositis __________________ Update on the lp5250d issue I have fixed the compile of the 16.5 version on suse 9.1. A diff with the cvs version of tn5250.c showed that a \ was missing on line 181. However the ''chgwtr'' issue remains the same. when the writer prints from a different queue, there is no output to printer, even though it appears that data processing takes place... Elmars Ositis __________________ Folks- I'm having a bit of a problem with the latest cvs version and suse 9.1 using cups. When I start the lp5250d daemon to an outq on the as/400, I can print fine. However, if I would like to move the writer to another outq with the command 'chgwtr eeprn001 tlxlib/ina' the writer moves to the new outq, processes the files, but I do not get any output to the printer, event though the process manager shows that lp5250d, lpr and cups are doing their job i.e. processing data. previously I was using the latest release on redhat enterprise server 2, and this worked fine, but the release was not compiling correctly on suse. anybody have any ideas? thanks Elmars Ositis
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.