|
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. 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. 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) Duane -----Original Message----- From: Joel Cochran [mailto:jrc@xxxxxxxxxx] Sent: Wednesday, October 15, 2003 9:00 AM To: RPG programming on the AS400 / iSeries Subject: RE: Function Opinion On Wed, 2003-10-15 at 16:00, Johnson, Duane wrote: > Yes, good point, I forgot to mention that I wrote a program that makes > updating a binding directory possible. I have to claim stupidity at this point, I have no idea what you mean by updating a binding directory. A binding directory is a list of Modules and Service programs. At compile time, if referenced, a module reads through the binding directory to find procedures it references. That's all a binding directory does, so updating/changing a binding directory has no impact on any existing module/procedure/program. Joel http://www.rpgnext.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.