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



I was thinking about what Scott suggested concerning using syslog(3) for
the error messages when I thought it might be a good idea to change where
scs2pdf writes it's output.  So I made it so that if the environment
variable TN5250_PDF is set scs2pdf would open the filename specified
there, otherwise it opens stdout.  But after doing so I realized that by
smart use of the outputfile argument to lp5250d pretty much anything could
be done without needing an environment variable.  So I'm wondering if
anyone can think of a use for being to set the name of the generated PDF
via a method other than the outputcommand argument.  Its only about 10
lines of code, but this ain't MicroSoft and we don't features for the sake
of having features.

I'm still thinking about syslog.  It is probably the best way to, any
enterprise-level (buzzword!) program ought to tell people what it is doing
if they need it.  Maybe with priority LOG_DEBUG?

Anyway, if people think its useful, the diff is at:

http://www.eaerich.com/tn5250.diff

This includes an update to the ChangeLog.

James Rich
james@eaerich.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.