Re: Field Loses Value When Returned By Stored Procedure

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Assuming you're doing things right in A and B, the only possible
answer I can think of is memory corruption caused by mismatching
parameters.

Note: this doesn't necessarily mean A or B are mismatched, it could be
a C called by either A and/or B..

If you put together some example code, we can tell if there's anything
wrong with A & B.

If you can't get a simple example A & B to show the same error, start
looking at all the C's.

HTH,
Charles




On Thu, Sep 9, 2010 at 11:12 AM, Michael Naughton
<michael_naughton@xxxxxxxxxxxx> wrote:
> I recently ran into this, and I'm wondering if anyone might know if there's a way to make it work.
>
> I have module B that does some lookups in a file and returns the values in parameters. This is called by program A, which takes those values, plus others, loads them into a MODS, and exports it as a recordset using SQL SET RESULT SETS.
>
> In the first version, module B used embedded SQL to retrieve the values, but I when I tested the stored procedure in iSeries Navigator the values retrieved in program B (and only those vaues) showed up as zeros. I put the program into debug and confirmed
> that a) module B was retrieving the correct values, b) the parameters coming back into program A contained those values, and c) both before and after the SQL SET RESULT SETS the MODS contained those values. But the recordset in iSeries Nav did not.
>
> Then I made one change: I modified module B to use Chains and Reads instead of embedded SQL. After I did that the stored procedure worked -- the values were returned correctly. No change at all was made to program A.
>
> Does anyone know why using embedded SQL in module B would cause the stored procedure export in program A to lose the values?
>
> TIA,
>
> Mike Naughton
> Senior Programmer/Analyst
> Judd Wire, Inc.
> 124 Turnpike Road
> Turners Falls, MA  01376
> 413-676-3144
> Internal: x 444
> mnaughton@xxxxxxxxxxxx
> ****************************************
> NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
> strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.
>
> --
> This is the RPG programming on the IBM i / System i (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.