|
On our system we have a number of libraries, too many. There is a START program everyone runs automatically when they sign on to add the standard libraries to their library list. There are a number of production libraries, however, that are not in the library list and programs have to be called from these. I am currently re-writing one such program that calls a number of PGM files all in the same library. Currently, the program is called from a menu using the library/program name (CALL BSTONE/SOMEPRG) which then does some stuff, calls another program (BSTONE/SOMEOTHERPRG) which then adds BSTONE and another library to the library list to call yet a few more programs. This is not all intuitive unless you get down into the source code and see the programs that call others using the LIBRARY/PROGRAM convention, and finding which use the library list, etc... My question is: What is the best way to handle this? Should the initial program add the programs to the library list, then call the others? Or should it CHGCURLIB and then call them? Or should all the programs use the LIBRARY/PROGRAM designation? Any and all opinions are welcome here. Regards, Jim Langston +--- | 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-2025 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.