|
More follow-up on this thread: On a whim, I whipped together the specs to dump every possible condition-information-item. DB2_TOKEN_COUNT & DB2_TOKEN_STRING appear to have the information pertaining to message *data*, but the DB2_TOKEN_STRING appears to max out at 70 characters. Some of the google references seem to indicate that GET CONDITION does away with the small 70-character message data area. Is there supposed to be a larger area? Also, is a D-spec's 10i 0 sufficient to hold an INTEGER, as defined in the SQL Reference? That's what I used, and limited testing didn't show any problems; still I'd like to know what is expected. Thanks, Dan
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.