× 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.



I think you will find that this is resolved by the way the compiler
generates the event file in V6R1 and later.

With V5R4 and before what you describe is "working as designed" for that
version...

Mike


Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199




From: "Robert Mullis" <rmullis@xxxxxxxxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>,
Date: 2013-07-31 14:34
Subject: [WDSCI-L] SQLRPGLE Compile Errors
Sent by: wdsci-l-bounces@xxxxxxxxxxxx



When I compile an RPGLE source and get errors, I get the error listing.
Clicking on an error in the error list takes me to the line in the
source member with the error and inserts the error text underneath the
source line. This does not happen when the source member is a SQLRPGLE.
I still get the error list and am able to click on the error, but it
does not go to the source for the SQLRPGLE. Instead, RDp opens the temp
source created by the SQL precompiler in EVFTEMPF and goes to the line
in that temp source. I then have to go to the actual source member to
make the correction.



Is there a way to get SQLRPGLE compile errors to go to the actual
source, instead of the temp source in EVFTEMPF? I am running RDp 8.5.1
on V5R4.



Thanks,

Robert J. Mullis




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-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.