× 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.



More useful information. Thanks.

If only the manual were as helpful but increasingly the DB2 stuff seems to be getting more and more "technically correct" while being less and less actually useful.


On 2013-11-12, at 10:54 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 11-Nov-2013 18:49 -0800, Jeff Young wrote:
Is there any way to determine generically how many tokens are needed
so that this logic could be used in a catch all exception routine for
SQL exceptions?


The condition-information-item DB2_TOKEN_COUNT should reveal how many
tokens [message replacement variables] there are.

So if a sufficiently large number [max of 100] of sufficiently large
DB2_ORDINAL_TOKEN_n items [max VARCHAR(32740)] were coded as well, then
I suppose one could write generically the processing of that GET
DIAGNOSTICS data. I suppose the limits could be tempered by actual
interrogation of the message descriptions in the QSQLMSG message file...
assuming no new messages were added since.

--
Regards, Chuck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.