Actually, one of my reasons for using RPG procedure wrappers around QC2IO
functions (lately) as opposed to RPG I/O opcodes (open, close, write,
update, delete, etc.), is to encapsulate error handling and reporting into
a single service program, which can be used within applications. Yes, that
service program implements a generic error handler that scans call-stack
message queues, which comes up with at least an *ESCAPE message, if not
other semi-meaningful messages.
Wouldn't you agree; that is better than application developers embedding
that type of logic in their applications? If there are system error
messages, they just appear in an array that is shared with the I/O service
program.
But this is tangent from my original concern about transforming generic RI
constraint messages into more meaningful messages for end-users.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
