Hi there,
for the Tampa symposium I developed and introduced a "log4rexx" class library/framework, which has
been modelled oafter "log4j".
In essence it allows one to include log-statements in a Rexx program which remains in the code.
Depending on the loggers in place you could then use this to allow Rexx programs in the field to be
even remotely debugged by having the log-output routed via a (read-only) TCP/IP socket connection to
everywhere you happen to be in the world.
Here you can find the article and the reference card for "log4rexx" and a link to the class
library/framework which would work on ooRexx up to, but not including ooRexx 4.0 (which handles
requires-statements differently to earlier versions):
<http://wi.wu.ac.at:8002/rgf/rexx/orx18/log4r/>
Today I was able to concentrate on updating the "log4rexx" package for ooRexx 4.0 and higher in a
fashion, that allows the same code to be usable in pre-4.0-ooRexx environments. Here's the link to
this version, which hereby gets into beta-test:
<http://wi.wu.ac.at:8002/rgf/rexx/orx18/log4r/log4rexx_20090929.zip>
Please check/test this version and supply any feedback you may have.
---rony