× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Finding Indicators Used (was: RE: MOVEA -> EVAL)
  • From: "Joe Giusto II \(E-mail\)" <juicenetdps@xxxxxxxxxxxxxx>
  • Date: Tue, 19 Jun 2001 14:04:52 -0400
  • Importance: Normal

Thanks Barb,
   I've seen the line numbers on the right and on most of the error messages
of a compile listing.  I was thinking more about the Cross-reference part of
the listing that shows where a variable is used or modified.
I just started living with it when I started using RPGLE and never thought
to keep checking for a solution as PTF's and new released came out.  Seemed
kind of trivial as I could always compile and get the source line number
from the compile listing and split screen while debugging a problem.
It never ceases to amaze me how much this list can point out the simple
things that make life so much easier (programming life that is).



Joe Giusto II
Programmer/Analyst
Ritz Camera
Beltsville, MD
301-419-3209 x347
410-813-2812 x347

 -----Original Message-----
From:   owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]  On
Behalf Of bmorris@ca.ibm.com
Sent:   Monday, June 18, 2001 10:59 PM
To:     RPG400-L@midrange.com
Subject:        Finding Indicators Used (was: RE: MOVEA -> EVAL)


>Date: Mon, 18 Jun 2001 14:45:56 -0400
>From: "Joe Giusto II \(E-mail\)" <juicenetdps@crosswinds.net>
> ...
>(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, to get the compiler to show source line numbers, add OPTION(*SRCSTMT)
to your H spec.  Or, if you're on V4R4, you can specify this on the CRT
command.  OPTION(*SRCSTMT) is available through PTFs back to V3R2.  If
SEU doesn't like it, don't worry; there were no PTFs for SEU.  Just save
your file and unless you're way down-level on PTFs, the compiler will
like it fine (the PTFs are about 3 years old).

Without OPTION(*SRCSTMT) you can still find the source line number in the
listing, but it's way over to the right for source lines.  For error
messages,
the source line number is listed with the message just before the message
text begins.

Barbara Morris



+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.