In fact, nearly all of my programs (interactive and batch) have print files defined "just in case" ;-)
I agree with Terry's notion of avoiding SYSOUT - but I would use a called program/procedure to do the logging. I would also tend to use a database to report to rather than a print file simply because I can use SQL etc. against the debug file to locate entries with specific values. In the past I have built utility routines of this nature that allowed me to print and/or database log specific debug messages. Jon Paris Partner400 www.Partner400.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.