On Jan 16, 2019, at 2:41 AM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:
And if I were mapping to a DB2 table and needed to do read next type operations that would matter to me - but I'm having trouble seeing why it matters when I'm changing the UPDATE in the RPG to and SQL update on another system. Normally doing that I'd be using some kind of handle/cursor/whatever to keep track of the connection anyway and if that is stored in the state info then I'm golden.
chain and insert are trivial. For update and delete it might depend, because rla is using positioned updates. the best way to keep track of the position I see, is a SQL cursor, but you can't create dynamicly cursor instances with embedded sql, so you would end up with SQL CLI or use bind by copy.
Some additional remarks: First heared of OA, my idee was to have a generic OA handler translating all rla operations to SQL, with the final goal to enable existing RLA programms to use true SQL indexes. This would decouple RLA programms from the database without major changes, opening up the possibility for redesign steps of the database.
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com