RE: Finding Indicators Used (was: RE: MOVEA -> EVAL)

My standard for maintainablility is stricter.  I want to be able to look at
the source at 3AM and not have to worry about anything but the immediate
problem when I'm in a state of (even more than usually) diminished capacity.
I hate typing as much as anybody, but I'm willing to compromise my
principles when I consider that someone like my 3AM self may have to read
the code.


The line number problem can be solved with the H spec directive
"option(*srcstmt)".  It also makes the runtime error messages show the
source line number.   

> -----Original Message-----
> From: Joe Giusto II (E-mail) [mailto:juicenetdps@crosswinds.net]
> Sent: Monday, June 18, 2001 11:46 AM
> To: RPG400-L@midrange.com
> Subject: Finding Indicators Used (was: RE: MOVEA -> EVAL)
> 
> 
> <snip>
> "Why?  Maintainability.  I'm maintaining a huge program.  I 
> want to use a
> new indicator or see where one is used, such as *IN42.  So 
> what do I do?"
> <snip>
> 
> You could just compile the program to QTEMP and look at the resulting
> compile listing.  Go to the bottom and scroll up a few pages 
> and you will
> see the indicators used and even what line numbers the are used on.
> (although since the compiler started referencing statement 
> number instead of
> actual source line number makes it kind of useless when 
> trying figure out
> what "lines" they are used on, but that is another story)
> 
> 
> Joe Giusto II
> Programmer/Analyst
> Ritz Camera
> Beltsville, MD
> 301-419-3209 x347
> 410-813-2812 x347
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---