|
> This is a place where I still use dynamic CALLs. > Just the opinion of a furniture salesman, I'll buy furniture from you. After my first taste of bind by copy for *PGM objects, I never did it again. /COPY is better than that. Speech over. I think the iSeries model favours separate dynamic calls for display I/O. You could put all the display formats in a single *DSPF but then making a change to any one format requires that everyone get out of the display file (because all formats are in there, many people are using it simultaneously.) Linking the I/O logic to a single program is the best we can do, because there are no F-specificatitions in procedure bodies. I have not tinkered with UIM in this light, however. --buck
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.