I feel the final checking, the last gate to pass, should be the
constraints. If I can put stuff in there using UPDDTA that I couldn't by
using the application, then something is wrong.
Now, error checking in your applications is a matter of style. Yes, you
could check the status on writes or updates, and perhaps evaluate that
further (maybe even down into the joblog) and evaluate the errors thrown
by the constraints and triggers. And that would be 100% effective (or at
least better be). And, you should probably have this logic in there
anyway in case a new constraint is added. I'll agree with you, it's a
I can understand if you want to duplicate this checking in your
application. Makes it easier to highlight fields in error, etc.
This thread ...
Re: Which of the SYSIBM tables/views show the row count for, (continued)
This mailing list archive is Copyright 1997-2019 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