|
For the record, I agree with you guys and I took out the F spec. I was only pointing out that I could see it possibly causing a problem, based on my own ignorance. I didn't know it was possible to update a file without coding the filename on the F-Spec, SQL or not. And I imagine I'm not the only one who didn't know that. Mike rpg400-l-bounces@xxxxxxxxxxxx wrote on 09/19/2005 11:16:25 AM: > Coding the F spec just so that someone can see that a file is updated > sounds more confusing. I would think that the /EXEC SQL would give them > enough pause to think what happens. Especially when they start to > understand SQL and wonder why you left in the F spec. > > And I do realize what you are trying to accomplish. I converted all my > *ENTRY PLIST's to Procedure Interfaces as recommended by the Sorcerer's > Guide, yet for those who still scan for *entry I still put in > D MYPGM PI *ENTRY PLIST > Which probably won't come in good to the list since of wrapping, but > basically the *ENTRY PLIST is off in the comment section. > > Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.