×
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.
Hello,
because I (deliberately) run an ancient version of OS/400, I have built my own workflow to generate PDFs from spooled output. This is basically a remote *outq sending the spool data to a Linux machine via lpd protocol (IP). The queue was created with transform(*yes), so the data is converted from EBCDIC to PCL ASCII. A custom script is fed with the print data by lpd on Linux, in turn running gpcl to convert the PCL data to PDF. Works like a charm.
But…
The PDFs being generated end up with Courier (typewriter-like) font which is okay, but not particularly nice to read. Hence I want to change the default font to another monospaced font with better readability.
I have skimmed through "Guide to Output", and "Printing IV" but the sheer volume of information is clobbering. What I could glean was that HPT imposes (unclear) limitations which fonts can be chosen. IBM not using names but numbers for fonts doesn't exactly help. Although I have found and compiled a table with font numbers vs. names. Many of them don't ring a bell, tho.
https://try-as400.pocnet.net/wiki/Printers_and_Fonts_Table
Second, what would be the proper place to change font definitions for "generic" *SCS spooled output, such as compiler logs system-wide? The printer *devd? The generic qsysprt file? I have not yet understood how printer devices and *outq work together.
Hints from the experts were to look closely are welcome. Same goes for font recommendations.
Thank you!
:wq! PoC
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.