If you define your tables using DDL statements, every operation you do
using embedded sql returns a SQLCODE. This code determines either the
success or the appropriate error message for the statement you are
executing. Also, you can't write invalid data on a DDL-defined table (there
is no MCH1202!!).
SQL tables are checked at write time, opposed to DDS tables that are
checked only at read time. So, if you have a table with a lot of reads but
few writes/updates, SQL should be faster processing it.
On the other hand, things like RUNSQLSTM "abort" with (mostly) a SQL9010
message and is up to the developer (again) to check any particular error .
HTH,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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
