Re: Line numbers, source line numbers and sequence line numbers

The suggestions to compile with OPTION(*SRCSTMT) are a great start. But
have you tried the debugger? If you set a service entry point on the
program first, you'll be in the debugger and when the program hits the
error, the debugger will position you right to that error. Or if the
program is already running, you can switch to the debug perspective, then
start an 'iSeries Debug Job'. Once you've selected the job to debug, the
editor will position right to the source line where the error has
occurred. From there you can examine the value of variables, etc. If you
open the source member for editing before starting the debug session, you
can start making whatever modifications are needed. Sometimes the
debugger is more helpful than simply knowing on what line the program has
encountered an error

wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/16/2011 10:37:31 AM:

----- Message from Paul Bailey <PaulBailey@xxxxxxxxxx> on Fri, 16
Dec 2011 15:08:42 +0000 -----

To:

Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] Line numbers, source line numbers and sequence line numbers

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.

. . .
. . .
. . .

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.