|
On Wed, 2003-10-15 at 19:13, Johnson, Duane wrote: > Joel, > > Basically, a binding directory is updated every time it is changed. > Currently, the only way to change one, is to use the ADDBNDDIRE, RMVBNDDIRE > and DSPBNDDIRE commands. WRKBNDDIRE - very easy > It always seemed to me that the main reason for not having a binding > directory for each program was that it was such a pain to add or remove a > module or service program from said directory. It was much easier to add > everything, including the kitchen sink, to one directory and then reference > that directory from the CRTPGM command. The main reason not to have a binding directory for every program is that it is a lot of overkill. I have one global binding directory that I access from all my programs and one application specific binding directory for each application (as Bob said earlier application<>program). > I decided to make that job easier, ergo the program to update a binding > directory. This means that I can add or remove modules or service programs > online, simply by adding a name, type and location to a blank line or lines, > (and I start with 16 blank lines per screen) or by clearing out a line or > lines, and even sort them alphabetically if I want to. (Never used that > function, I once read somewhere that you always want to have the main module > first, and I've never wanted to test that theory. Although now that I think > about it, that really can't be true, or the single binding directory for > many programs wouldn't work) Try the WRKBNDDIRE, I think you'll be surprised. When you talk about Main modules being first and such, you have to understand that a binding directory doesn't care about that stuff. Neither does a program for that matter as long as you specify which module you want as the entry module. The default is *FIRST. Joel http://www.rpgnext.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.