|
Consider also some of the other (albeit minor) benefits of subprocedures, (especially when packaged in a *SRVPGM): - far fewer objects to manage: one *SRVPGM containing several subprocedures might otherwise equate to many *PGM objects - more parameter-passing capabilities, (read-only reference, by value, etc.) - subprocedures can be called recursively Subprocedures complement traditional *PGM calls - not replace them. Consider using subprocedures in those circumstances where you would otherwise resort to subroutines. Instead of proliferating the subroutine code with /COPY use *SRVPGM to provide as a single, shared repository for subprocedure code. Hope this helps. Brian Parkins +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.