× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Buck wrote:
David Gibbs 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?

I'm on WDSC here but that seems to be about it:

CRTSQLRPGI OBJ(lib/pgm) SRCFILE(lib/QRPGLESRC) SRCMBR(pgm)
OBJTYPE(*MODULE) OPTION(*EVENTF *XREF) RPGPPOPT(*NONE) REPLACE(*YES)
TOSRCFILE(*CURLIB/QSQLTEMP1) COMPILEOPT('DBGVIEW(*LIST)')

When it compiles, I get a new editor tab with the errors. I use Ctrl-.
to find the next error, then Ctrl-F6 to switch to the actual source I
can edit. A lot.
--buck

That actually seems to work!!! Thanks a lot Buck! I've been needing this
for a long time.

- --
Pete Hall
pete@xxxxxxxxxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAksYWfAACgkQXczQcKdXKg552ACePllZlQNVyuncmHMGpECm47Vh
T3oAmwfgzMCNxzLi5p18TEwg55UDaj70
=6wTW
-----END PGP SIGNATURE-----

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.