The error I am getting is at runtime, not compile time. It is a MSGW job status. So the joblog message relating to the level 40 error tells me which line number it is on but that line number only seems to relate to the compile listing.
The OPTION(*SrcStmt) H-spec idea seems good, but will the MSGW error line number have the same source line number? If I lose those statement line numbers from the compile listing by using that OPTION then I have no way of finding out which line in the source the program broke at.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of mgarrison@xxxxxxxxxx
Sent: 16 December 2011 15:33
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Line numbers, source line numbers and sequence line numbers
Paul,
If you received the "Error List" window then all you need to do is double click on the error message and the LPEX edit should navigate to the line of code for the error. Very nice feature when using RDP.
Kind regards,
Mike Garrison
From: Paul Bailey <PaulBailey@xxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 12/16/2011 09:13 AM
Subject: [WDSCI-L] Line numbers, source line numbers and sequence
line numbers
Sent by: wdsci-l-bounces+mgarrison=werner.com@xxxxxxxxxxxx
I am programming in RPGLE using RDP 8.0.3. I compile my program, and then
test it, but it throws an error and the joblog tells me which source line
this is on.
How do I locate that source line within Rational?
In SEU I would press F15, select option 2 and press enter. Then I would
"find" the source line number in the spooled file.
There are two LPEX actions to find line numbers in RDP: locateLine
(CTRL-L) and locateSequenceLine. Neither find the line that the joblog
mentions.
Surely there is a way to easily view the spooled file just created by a
compile in RDP? The spooled file "feature" of RDP seems to do nothing,
and it takes more than just three keypresses to locate the spooled file
anyway, so I'm not entirely happy with that route. (I know Softlanding's
plugin for RDP has some useful spooledfile features, but it is still not
as quick as F15, 2, ENTER to load the compiler listing.)
Cheers,
Paul.
Chistmas and New Year Closures
Our offices will be closed for Christmas on 26, 27 and 28 December. We
will also be closed for New Year on 2 January 2011. May we take this
opportunity of wishing you a very happy Christmas and New Year
------------------------------------------------------------
Important
This email transmission and any files with it are strictly
confidential to the intended recipient and may be legally
privileged. Any views or opinions presented are solely
those of the author and do not necessarily represent those
of BHSF. If you are not the intended recipient, you must
not copy, disclose or distribute its contents in any way.
If you have received this e-mail in error, please notify
the sender and delete the e-mail from your system.
We have taken steps to ensure this e-mail and attachments
are free from any virus but do not accept any
responsibility once this e-mail has been transmitted. You
should scan any attachments for viruses.
No contract may be concluded on behalf of BHSF Limited by
e-mail.
Registered Office:
BHSF Limited
Gamgee House, 2 Darnley Road, Birmingham B16 8TE.
www.bhsf.co.uk
Registered in England number 35500.
BHSF is authorised and regulated by the Financial Services
Authority.
midrange.com
