This particular program would not be impacted by the change physical file.
This program in particular is just getting a record count. The RPG program
doesn't care about a record format. The only time that I can forsee a
problem is if you set up an External Datastructure to the file. Then do a
SELECT * INTO :externalDataSctucture Because if you change the file...
then obviously you compile of the program before the change is now
different after the change. I've never actually do a select * into... I
always select the fields I want into the fields I want to prevent this kind
of problem from arising.

So you only need to worry about regular I/O programs and programs that have
external datastructure references.

Michael Schutte
Admin Professional
Bob Evans Farms, Inc.



midrange-l-bounces@xxxxxxxxxxxx wrote on 03/03/2008 09:06:13 AM:

Hi,

We are also currently interested in SQL in our RPG programs.

Can anyone explain this, please.

EXEC SQL
SELECT COUNT ( * ) INTO : wVar
FROM FILE_X;

DSPPGMREF indicates that the program uses FILE_X but gives no
information as to its record format.



wSQL = 'SELECT COUNT ( * ) FROM FILE_Y'
EXEC SQL
PREPARE S1 FROM : wSQL;

DSPPGMREF gives no indacation that the program uses FILE_Y.


Does this mean we can no longer depend upon DSPPGMREF to find the
programs impacted by a changed PF?

TIA.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2019 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].