Scott,
Good thought.
In this case it was coded in the program and was, in fact, in error.
Although I am not sure that an externally defined DS would/should
fail to raise an error if there were an SQL cursor mismatch ?
(not sure you meant to imply that)
I currently use external DS mostly for sub procedure RLA (legacy) IO,
as my cursors almost never match a defined record format.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Mildenberger
Sent: Wednesday, July 03, 2013 8:23 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: SQLRPGLE attribute question
Is the receiving data structure externally defined? If so, that could cause a mismatch with the cursor if the external definition source has changed since 2010.
Scott
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Wednesday, July 03, 2013 7:56 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: SQLRPGLE attribute question
Another detail, the source member and object had last been changed in December 2010. The dates and times were all as expected: source changed just prior to object creation.
But, today, the compile failed due to a mismatch between an SQL cursor and the receiving data structure. Apparently the compiler got "tighter"
in the last few years -
--
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.
midrange.com
