|
On May 26, 2016, at 7:20 AM, Alan <cfuture@xxxxxxxxxxx> wrote:
Hey folks,
I don’t remember a problem like this, I’ve done this embedded SQL lots of times.
I have a sequence of SQL statements that first clear the records (with a DELETE) in two work files.
The first one is populated, then the second, with INSERT/SELECT statements.
Works like a charm when I run in in Navigator and in interactive STRSQL.
I get 737 rows and then 68, and the results are correct.
BUT! ?? When I run it embedded, I get nothing. With the EXACT same statement and syntax, with two differences:
One, I’m running the interactive version over one database schema (library) at a time, with no overrides, whereas the embedded version runs an override first because this is going to run using the data from a bunch of schemas.
Two, Because of the above, I use the host-variable :Dtaset to include the library name in the embedded run, but in the one-library interactive version it’s CHAR(‘ABC’, 3) as Dtaset.
The overrides are done using a service program procedure. The program is compiled with ACTGRP(*NEW), and the service program with ACTGRP(*CALLER). So it runs in the same activation group, which is the default for the OVRDBF command.
I’ve done this a lot, I don’t get what’s different now. Any ideas?
THANKS!!
--Alan Cassidy
CassidyA@xxxxxxx
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.
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.