|
On Friday, October 02, 1998 1:48 AM, James W. Kilgore [SMTP:qappdsn@ibm.net] wrote: > If a program -always- opens a particular file, IMHO, just let the system > open > it. If a program has several files where, depending on what is passed to > the > program, only a minority of them are needed per call, you may choose to > explicitly open /close them. If the same program is called repetatively, > unless > you have a compelling reason to close a file, once opened, leave it that > way. > > In any case, it's an "it depends" issue for UC. There is one good reason to do UC opens in RPG: Error trapping. If you let RPG do the implicit open and you get an I/O error (file locked by backups, etc.) then the default error handler will get control even if you have an INFSR for the file. The only way I've found to trap this sort of I/O error is to do a user controlled open. Buck Calabro Commsoft, Albany, NY mailto:mcalabro@commsoft.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.