×
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.
Joe wrote :
<A drawback to dynamic SQL (your second example) is that during impact analysis you really have no way to track which programs are using a given table.>
Mark wrote :
<This is precisely why you need to do "impact analysis" at the field level.>
Rob wrote :
<IBM has discouraged the use of 'select * into :myds'>
I think this example would be difficult to treat, if RS were hardcoded.
'SELECT * FROM ' + filename;
EXEC SQL
FETCH C1 INTO : RS;
Wouldn't it be a simple rule to at least impose that if 'SELECT *' were used then RS must be declared with 'DS EXTNAME' or 'LIKEREC'?
If so, would there be a preference to using one or the other?
IF 'SELECT *' were never used, then there's no problem if "impact analysis" is at the field level. Right?
Finally,
Eric wrote :
<This is one reason to avoid dynamically prepared sql.>
I have to take this into account. I've discovered that one of our services relies totally on DSPPGMREF using the record identifier when a file is modified. They have strict programming rules so that this covers all the possibilties. This could prevent the rest of us from using dynamically prepared sql.
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.
midrange.com
