Hi,
I have always had this issue with SQL ILE COBOL and following the wiki instructions I get the same as Robert. The .CBLLE pre-compiled source is opened, even though I have the source of the .SQLCBLLE open already.
We are at V6R1.
This is nothing more than an annoyance but it would be nice if it went into the source that actually has to be changed.
Best regards,
Mark Austin
IT Consultant
Universal Music Publishing Group
Email: mark.austin@xxxxxxxxxx
Tel: +44 (0) 20 8742 5520
Fax: +44 (0) 20 8742 5699
Post: 347-353 Chiswick High Road, London W4 4HS
Universal Music Publishing International Limited
Registered in England. Number 02050403
Registered Office: 20 Fulham Broadway, London, SW6 1AH
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Mullis
Sent: 31 July 2013 20:40
To: Rational Developer for IBM i / Websphere Development Studio Clientfor System i & iSeries
Subject: Re: [WDSCI-L] SQLRPGLE Compile Errors
Thanks Mike. We should be upgrading to V7R1 soon.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Hockings
Sent: Wednesday, July 31, 2013 3:34 PM
To: Rational Developer for IBM i / Websphere Development Studio Client forSystem i & iSeries
Subject: Re: [WDSCI-L] SQLRPGLE Compile Errors
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
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
________________________________
“**Confidentiality**
The information contained in this e-mail is confidential, may be privileged and is intended solely for the use of the named addressee. Access to this e-mail by any other person is not authorised. If you are not the intended recipient, you should not disclose, copy, distribute, take any action or rely on it and you should please notify the sender by reply. Any opinions expressed are not necessarily those of the company.
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
midrange.com
