Buck,
I tried your suggestion, but can not seem to get it to work.
In the Outline View, I double click a field that has a + next to it (indicating it is used in multiple places), and it brings me to the source statement defining the field. With the field selected in the view (highlighted), when I right click, nothing happens.
Am I missing a step here?
Thanks,
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3
----- Original Message ----
From: Buck <kc2hiz@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Sent: Wednesday, November 21, 2007 2:19:40 PM
Subject: Re: [WDSCI-L] Fields Used in SQL Statements
Bill Barnes wrote:
When I look at the outline view and choose fields the :fields only find
the D spec and not where they are used in an SQL program. I learned to
put indicator variables in my Fetch Into fields to reduce the number of
log entries. The outline view shows these as being defined but not
used. Is this a feature and I should just live with it, or am I the
only one to which this is happening?
You are not the only one. To complicate matters, I generally use the
compiler listing cross reference instead of the outline view. I'll be
happy to rehash that in a different thread. The crux is that there
isn't a single compiler where SQL is involved. The SQL precompiler adds
kinks even for all-green-screen work. I think a DCR is the right thing
to do in this case.
I'm not sure what you're using the outline view for but if you're trying
to see where a field is used, you can try to double click (select) the
field name, then right click, Selected->Filter Selected. If you're
command-line oriented, you can do the same thing with 'findText all
field_name'
Ctrl-W to go back to the normal view.
--buck
midrange.com
