Re: Some database discussions...

few RPG programmers write code to detect errors, much less handle
them.

I think we should clarify that "errors" in the context of this discussion
means various types of messages placed in various call-stack message
queues, which may be sent by IBM i components and applications, which are
normally accompanied by a *ESCAPE type message, which raises an "exception"
that leaves a JOB in a *MSGW status by default.

Given the number of possible variations in this architecture, is it any
wonder that application developers would rather write code to prevent
"errors", rather than try to deal with them?

If your search-for-errors routine doesn't *REMOVE them after finding them,
the same messages will show up in the next search-for-errors call. It seems
to me that one's search-for-errors routines would be prone to failure.