×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
A recent thread spoke of warning messages in the context of adding
columns to a file. So I thought I'd post something about the
relationship between SQLCODEs and message descriptions.
There are both positive and negative SQLCODEs, the latter are typically
warnings or information, while the latter are errors.
The general connection between SQLCODEs and message descriptions is that
the SQLCODE digits are the final digits in a message ID that generally
starts with SQL.
So an SQLCODE of 100 (row not found) has a message description in
QSQLMSG of SQL0100 of severity 0.
And SQLCODE of -206 (column not in table) has a message description in
QSQLMSG of SQL0206 of severity 30.
There are some 5-digit negative SQLCODEs, and all 5 digits are at the
end of the message ID. So SQLCODE of -30000 (DRDA protocol error) has
message ID SQ30000, severity 30.
So with all that, one should STILL check SQLCODE in programs - AND one
can easily see a more expansive explanation of the meaning by looking in
the joblog.
I hope this is useful - Buck, maybe this can go in the WIKI.
Cheers
Vern
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.