Re: Fields Used in SQL Statements

Mea culpa, Joe!!

I think I have blew that one - host variables in character strings used in a PREPARE - I don't remember if there might be some places it can be done.

But your reply made me think of something else - I'd love to see the actual column names and table names listed in the outline - like in SELECT CUSNBR FROM QIWS/QCUSTCDT - you would have an entry for the table QCUSTCDT, as if it came from an F-spec - and for the column CUSNBR. Again, not trivial.

Thanks
Vern

-------------- Original message ----------------------
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>

From: Vernon Hamberg

You are not alone. I've long wished that host variables would be part
of the outline. And file references in SQL statements - they CAN be
parsed, after all, otherwise they could never be run by the system.
So it is not impossible, just not in scope, it seems.

This I agree with. It's possible, but we have to ask for it, because it
requires a little more effort.

One area where it'd be more complicated - again, not impossible, in
my view - is when a statement is held in a character variable and
then prepared. There can be more than one string used in the same
PREPARE, too. But, again, not impossible to deal with.

I don't think this is possible. The string could be modified at any point
in the program, which would change the references. In fact, don't you
typically build those strings dynamically? It's been a while since I used
one.

Joe

--
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing
list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.