Re: Line number for missing ENDyy?

[craigs@xxxxxxxxx]

Thanks Booth.
I think that helps since it is easier to see.  I guess I had been searching
for something that would take me right to the line.  It seems like the line
number could be calculated though like other errors show line numbers in
EVFEVENT.

Craig Strong

** Booth wrote:
Sorry for the broken message:

Look under "View" and choose "indent"  This gives an indented view that can
be closed with F3.  Its a view so you can't edit it, but it'll show you
your
indents at any time; even before you verify.


---------------------------------------------------------
Booth Martin http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------

-------Original Message-------

From: code400-l@midrange.com
Date: Tuesday, April 30, 2002 11:38:27
To: code400-l@midrange.com
Subject: Line number for missing ENDyy?

Can we get to the line number of the error about missing ENDyy in CODE/400
without looking at the compile listing? If so, can the link (line number)
be included in the corresponding member of the event file EVFEVENT on the
AS/400 or C:\WDT400\Tmp\XXXX.EVT like other errors?
That way we can get to it by a double-click on the error in the error list.
Since I have been trying to use the Verify Program function more, I have
noticed this more. I had some good IF statements in my RPG and I forgot an
ENDIF. Using either compile or verify, I got "RNF5177 ENDyy operation
missing for ELSE operation group at statement 1662; END assumed." In the
error list, double-clicking on this error went to the beginning of the
source and showed the error in pink there. The best way I knew to find
this error in the source, was to look at the compilation, find statement
1662, find the sequence number to the very right, then locate the sequence
in CODE/400. Obviously, this process does not work on a verify if there is
not a current compile listing. I thought sequence numbers were saved in
the event file, but when I looked at the file, it turns out that line
numbers are being saved, except for missing ENDyy errors. I don't see line
numbers anywhere in the compile listing, so they must be a calculation or
stored somewhere else. Would it be possible to scan the RNF5177 error line
for "statement X" where X is the statement number of the error, find it in
the compilation, calculate the line number based on the sequence number at
the very right, and store it in the event file? This has probably already
been considered and there is also probably something I am not aware of. I
thought I should bring it to the attention of someone in case they weren't
aware. I haven't found a discussion of this topic on this list.

Thanks,
Craig Strong