|
>> Nuts. I was afraid of that. Too bad there isn't a way to define file resources at the service program level... I guess I'll be using SQL instead. But why _not_ put all procedures related to that file in one source ? It makes much more sense than having multiple tiny sources. This is the normal approach - to build a set of service routines that do the file I/O and all I/O to that file is done through them. Hence sharing is implicit. You can use the "handle" approach if you prototype and use the C I/O routines. But not in RPG without coding it yourself. Not sure how SQL will help - but that is probably as much my SQL knowledge as anything. Jon Paris Partner400
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.