Re: Program failure analysis

On 10/12/2017 1:21 PM, D*B wrote:

After the first stable release of ArdGate, most enhancements where made
to the logging (adding log statements) to make problem analysis more
effective. I'm even using the debug features of Eclipse only in very
rare cases, preferring to add some log statements only running in debug
mode. In production there is only very few logging, to see the real
error situations very fast, but it could be leveraged just making a
minor change to a config file.

Many, many years ago, when I was first playing with CGI programs I did
something similar, but using a *DTAARA to trigger 'debug' mode. Which
wrote a 'log' to QSYSPRT via EXCEPT and O-specs. Made QSYSPRT USROPN
and it only generated a spooled file when needed.

Maybe I'll try Log4RPG and see if I can log enough information to
isolate failures. The advantage of that would be that I would be
writing more 'defensive' code up front, rather than waiting to let the
dumps I get during testing lead me to write error traps. Sometimes
being lazy is expensive.

Thanks!