Re: The SAGA or is it Soap Opera Continues

Pete

This is the long-time known behavior with embedded SQL. One solution is to change the respective CRT commands to put the generated source into source files not in QTEMP - there is an option for that which is hidden on about page 5 or the prompt.

I thought there had been some improvements in this area in later versions of WDSC or RDi - not sure. I am using WDSC 7 and go to WRKSPLF or even SEU to find errors in the output spooled file.

HTH
Vern

Pete Hall wrote:

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

darren@xxxxxxxxx wrote:

Have you tried compiling with the OPTINON(*EVENTF)? Using this option
brings up the error list natively in WDSC for me, so that I can click on an
error, and be taken there. The error listing is one of the primary reasons
to use WDSC for me.

Yes, I use OPTIONS(*EVENTF). The Implementer plugin requires it. Are you
working with embedded SQL? The problem seems to be that the SQL
precompiler modifies the source and places it in a temporary source
member in QTEMP, which is then processed by the RPG compiler. QTEMP (the
actual source) is no longer available after the compile completes, so
selecting an error message doesn't take you to the error. It just cause
a lot of messages, which are mostly meaningless gibberish to be inserted
in the IDE, and complains that the error can't be located. Something
similar happens with the validator.

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

iEYEARECAAYFAkrvYZQACgkQXczQcKdXKg4RqQCgqzLSizovMpzYPeahBE4wIuUG
aIQAn2wTKELjT4FKuFZDoCdHjQwflOL5
=yQzM
-----END PGP SIGNATURE-----