Re: A problem in embedded SQL -- RPG400-L

Subject: Re: A problem in embedded SQL
From: Nick <nicola.brion@xxxxxxxxxxxx>
Date: Thu, 12 Dec 2019 00:10:30 +0100
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: RPG programming on IBM i <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

Il 11/12/2019 16:19, Marvin Radding ha scritto:

Jean,

I do trim the fields. And the same sql statement that fails in the RPGLE program, works in STRSQL. The exact same statement.

Basically, this is hard to accept, and, if true, the only way to fix it would be to open a PMR with IBM,as it is a flaawn in the SQL engine, and we canot do anything about it.

Most probably, the statemnt you are executing *isn't* the one SQL execute. As someone stated, using host variables, you are not seeing the same statement that the SQL is executing.

If i run into a similar problem, either i'll use the PRTSQLINF as suggested, or use SQL exit point to monitor the very statement that came to the engine.

OTH

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: A problem in embedded SQL , Charles Wilt

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.