Hi everyone,

I have committed to cvs several improvements to the SCS and PDF code. These changes provide support for any page size or CPI, as well as some bug fixes. If you are using lp5250d to create PDFs or are interested in doing so, could you please test the latest cvs code with your printouts. So far it is working perfectly with everything I've thrown at it.

You will need to create a special file for saving printer state information. At some point this will be handled automatically by lp5250d, but for now it is a manual process. This file needs to be read/writable by the user running lp5250d. If this file doesn't exist scs2pdf won't save printer state across print job, occasionally resulting in incorrect output. It can be called anything, but it needs to be unique for each lp5250d instance.

scs2pdf can now also log what it is doing to syslogd. If your PDFs are created with the wrong page or font size starting scs2pdf with the -s switch and checking the syslogd logs can help identify the problem. It has two levels of logging: 0 for basic and 1 for detailed. The amount of logging is controlled by the -l switch (default is basic).

To test this create an entry in ~/.tn5250rc similar to the following:

printtopdf {
host = your.as400.domain.com
env.DEVNAME = PRTTOPDF
outputcommand = scs2pdf -si /tmp/pdfprintinit > /tmp/output.pdf
}

The above example will store printer state information in /tmp/pdfprintinit. So be sure to create this file before starting lp5250d:

touch /tmp/pdfprintinit

Remember, the file needs to be read/writable by whatever user is running lp5250d.

Thanks!

James Rich

It's not the software that's free; it's you.
- billyskank on Groklaw

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].