|
Jim, Jim Langston wrote: > <snip> > 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 a great place to use the Product Library feature of OS/400 commands. A Product library get's inserted at the beginning of a commands execution and is automagically removed when the command's CPP completes. (If you want to see an example check out your library list before and after entering the STRPDM command). IMHO, the most important reason to use Product library in this case is that it precludes you from having to hard code a library into a CL program. I STRONGLY discourage this practice because it makes testing more complicated and potentially much more dangerous. > 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. For the same reason just listed above (testing), we use JOBD to set the library list. It's much easier to configure, doesn't require a program change everytime you make an adjustment, and best of all, doesn't require a last minute (untested) program change right before a program is moved from test to production. HTH, jte -- John Earl johnearl@powertechgroup.com The PowerTech Group 206-575-0711 PowerLock Network Security www.400security.com The 400 School www.400school.com -- +--- | 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-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.