Re: Failure options in RGPLE Db2 SP -- 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.

I found that in the docs before I posted the question, but the docs lack a
lot of details. I did some trial-and-error, but didn't go farther than
adding the parms. I didn't dig into how the caller handled them upon
return.

Thanks

date: Thu, 17 Sep 2020 13:53:21 -0600

from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Re: Failure options in RGPLE Db2 SP

Not really in my book...

The SQL create or replace procedure doesn't include them...

But yes, the RPG procedure has to define the additional parms.

The point is the DB will pass back your status as the SQLSTATE, which the
.NET/ODBC/JDBC drivers are aware of.

If you set an error state, the driver will know something is wrong, and
throw and exception in the client code.

If you just define your own "status/message" field, then the driver doesn't
know and you're dependent on the client code to examine and do something
with it.

Note to mention properly written client code still needs to handle
exceptions via SQLSTATE anyway.

Just cleaner to have errors all returned the same way IMHO.
Charles

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.