|
Alan, What's being done differently between an OPENIFS with *NEW or *APPEND? I don't see the reason for the option. If I open a file and it already exists then it should automatically *APPEND. If it doesn't already exist it should be *NEW. If *NEW would truncate/clear the file if it already existed don't do that using OPENIFS but provide another procedure that could be called beforehand to clear an IFS file. How about a zen question - why do you need OPENIFS & CLOSEIFS functions? SQL doesn't open and close tables so why should your functions OPEN/CLOSE the IFS files. Why not just pass a required file name along on the WRITEIFS function? If it's the first reference to that file you open it up and process it. Your WRITEIFS function could store a table of files so subsequent calls could use the same file handle from the first call. If you passed a file name to the WRITEIFS function you could work with more than one IFS file at the same time. Also, do the files really need to be closed? Could you just automatically close the IFS files whenever a SQL statement completes? Is it possible to hook into SQL to know when to a statement completes? Or is the overhead for a open/close to an IFS file low enough you could afford to open/write/close on every call to WRITEIFS? Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.