What does DB2_Ordinal_Token tell you that Get Diagnostics doesn't? -- RPG400-L

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

Subject: What does DB2_Ordinal_Token tell you that Get Diagnostics doesn't?
From: Vicki Wilson <VWilson@xxxxxxxxxxxxx>
Date: Wed, 29 Jul 2015 20:59:45 +0000
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Hi all,

I built an SQL error handling service program based on articles by Jon Paris and Scott Klement.
Here's Jon's article:
http://www.ibmsystemsmag.com/ibmi/developer/rpg/unexpected_errors/?page=1

The program has been working pretty nifty for half a year. But I just had a glitch in it while looping through the Error Tokens.

I'm not really seeing anything in the tokens that I'm not already getting from GET DIAGNOSTICS. And I can't remember what the reasoning was for including the Tokens in the Message Text being built.

My question - What does db2_ordinal_token tell you that Get Diagnostics doesn't? If you are using ordinal_token - do you use all of them or limit them?

Thanks.
Vicki Wilson

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.