×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




The easiest thing to change to get this to work without problems is to
create a copy of the QSQLTEMP1 source file in your development library.
Next, change your compile commands to point to this copy of the source
file: TOSRCFILE(*CURLIB/QSQLTEMP1)
*CURLIB or your development library name will work.
This is where the pre-processor puts the temporary source that it generates,
and needs to use, to display any errors.

Gene

On Tue, Dec 1, 2009 at 9:16 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:

I've made my first foray's into writing RPG SQL programs and found that
RDi's support for them to be somewhat lacking.

When I compile the program, the error list points to the temporary source
that the SQL pre-processor generated.

If I override the temporary source to a real source-pf, I can get the
errors to display (more or less, as they point to code that wasn't really
written), but I also get a object lock error eventually (which I don't have
the details of at the moment).

Is there any trick to working with RPG SQL in RDi?

Thanks!

david

--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.