|
I know what Chris wants to do and it would be convinient to have. It's hard to explain unless you are really using ILE heavily and trying to keep things seperated in logical pieces. I remember asking for this some time ago. I also wondered why once it found a reference to a subprocedure if it found it again (in another service program) that it would error out. I was hoping it would be like a library list. Use the first one found. Brad > -----Original Message----- > From: Scott Klement [mailto:klemscot@klements.com] > Sent: Friday, January 12, 2001 2:13 PM > To: Midrange-L (E-mail) > Subject: Re: Binding Directories > > > > I'm confused. Why don't you just create a single binding > directory that > contains all the service programs and modules listed in all the other > binding directories? > > The binding directory is only used at bind time to determine > which service > programs to search for procedures in. Simply adding all the service > programs to a single binding directory would have the same > result as a > "binding directory of binding directories" > > > > On Fri, 12 Jan 2001, Chris Bipes wrote: > > > I would like to be able to create a master binding > directory that has a list > > of binding directories that our shop uses. This way we > only have to list > > the one binding directory in our source. This program > uses QC2LE and CROSS > > while that only needs CROSS..... We have modules that are > application > > specific, general to all application, then IBM's. We don't > want to have to > > list all the necessary binding directories. > > > > OK we are getting lazy now, but hey who wants to think when > about old stuff > > when cloning? ;-) > > > > How many others would like to have this feature? Is it > available and I just > > missed it? > > > > Christopher K. Bipes mailto:Chris.Bipes@Cross-Check.com > > Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com > > CrossCheck, Inc. http://www.cross-check.com > > 6119 State Farm Drive Phone: 707 586-0551 x 1102 > > Rohnert Park CA 94928 Fax: 707 586-1884 > > > > > > > > +--- > | 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 > +--- > +--- | 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.