|
Hi Joe! >Well frankly, our advice was valid: *NEW on top-level >programs, *CALLER on others. Show me where that's a >BAD thing, and maybe I'll be more amenable to your comment. How about this? First step into ILE. Programmer adds her first subprocedure to an RPG IV program. There's literally only one ILE program in the application. Time passes. Our intrepid programmer has become comfortable with subprocedures and has written her first service program. She hasn't had to touch the top level of the application; just a dozen programs at different stages throughout the application. *CALLER puts us in the DAG under these scenarios. I don't see that as desirable, but perhaps I'm operating under more obsolete assumptions? For the lurkers, this discussion should be about choices and trade-offs. There isn't an absolute answer that will work under all circumstances. --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.