IBM, I echo Michael Schutte when I say "I wonder if there is a way to
change that." Currently, it seems that the only solution to this problem
is to look at a compile listing. That kinda defeats one of the advantages
of using WDSC.
Thank you to all of you who responded to my question:
Do you use OPTION(*SRCSTMT) in your H spec? Someone may have changed
your compile command defaults to use OPTION(*SRCSTMT) when you compile
from PDM or command line....
Also, as far as matching up nesting levels, the "Show Indentation" option
in Source (menu bar) should help you see where you missed an ENDxx.....
hth,
Eric DeLong
Thanks, Eric, I have OPTION(*NODEBUGIO:*SRCSTMT) DEBUG in the H spec.
"Show Indentation" is great, I use it all the time, although I find it not
too helpful when using /free. However, with over 6000 lines of code to go
through, it is faster to use the compile print.
------------------------
From WDSC, with the source member open, click on Source(at the top of the
screen), then select Show indentation. A new window will open, showing
your indented source.
Also, WDSC still produces compiler listings. Just switch to a terminal
session and do WRKSPLF.
Steven Morrison
Fidelity Express
903-885-1283 ext. 292
Thanks you, Steve, I have noticed the compiler listings, but haven't
pursued that avenue. I was using Verify, which does not produce a
compiler listing, but does position the cursor in the program if you are
using SQLRPGLE.
------------------------
You maybe did not know that you can have WDSC automatically insert the
ENDxx opcode - personally it kind of drives me nuts, but I have it set. I
get around it by using Alt-S instead of Enter, if the ENDxx is already
there.
HTH
Vern
Thanks, Vern, it drives me nuts, too, especially if I am putting the
condition around existing code. That is why I turned it off. In this
case, I moved code to a new subroutine and missed an END.
-----------------------
That's what I've been doing looking that the spool file to get the line
number. The error listing that shows up in WDSC doesn't show the source
line number... doesn't matter if you specify (*SRCSTMT) in the HEADER
SPECS. I wonder if there is a way to change that.
Michael Schutte
I should mention that in the WDSC error listing, you can double click on
it
and it will take you to the line in error. But with SQLRPGLE, it opens a
new source window and takes you to the line.
Michael Schutte
Could you elaborate on the "new source window" in SQLRPGLE. I just get a
message stating "The error messages could not be inserted into the
original source file." Details says something about using a TOSRCFILE
parm on the compile. How would I change the default command and what
should I use as the value for this parm?
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of
KLockwood@xxxxxxxxxxxxxxxxxxx
Sent: Thursday, October 02, 2008 4:33 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] I'm sure no one else ever forgets to type an ENDyy
statement in RPG, but if anyone has, please help!
I get this WDSc error on Verify (I am running WDSc ver 7.0, but this has
been a problem ever since I started to use WDSc ver 6):
RNF5177: ENDyy operation missing for ELSE operation group at statement
6269; END assumed.
Does anyone have a solution for this problem:
- I verify my program and I get the RNF5177 error (missing End statement)
- I double click on the error expecting to position somewhere close to
the error (at least the same subroutine!)
- I am positioned to the first line of the program. As far as I can
tell, the statement # in the message (6269 in my example) means nothing -
not the source line # and not the WDSc line #. This is somewhat annoying
in a program with over 6000 lines of code.
- I end up doing a green screen compile and immediately get a Source code
line number that tells me where to look in my code.
What do I do when green screen compiles go away?!?
Mr. Kerry Lockwood
Celadon Trucking, Inc.
9503 E. 33rd Street
Indianapolis, IN 46235
(317) 972-7000 ext. 2147
midrange.com
