× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Binding Directories
  • From: "McCallion, Martin" <MccalliM@xxxxxxxxxxxxxxxx>
  • Date: Wed, 17 Jan 2001 16:58:01 -0000

> > > As for the explicit lib/module parameter of the CRTPGM cmd,
> > > sadly, CRTPGM
> > > binds all the modules listed in the list, even if they are
> > > never referenced,
> > > leading to bloated objects containing orphaned *MODULEs.
> >
> > Erm, no it doesn't.  It does put a lock on them all at compile time,
> > which can cause a few problems, and I don't think is 
> necessary, but it
> > only binds the objects it actually needs.
> 
> I wish you were correct Martin, but for the case Mark 
> suggested, that I
> outlined, were you use the MODULE parm of the CRTPGM,  
> **all** the modules
> listed on that parm are bound into the resultant program 
> object, even if as
> I said before, they are never used (go try it for proof).

Oops. sorry, I should read more carefully.  I thought you meant every
module on the binding directory was bound.
 
> You are correct however, if you list your modules in a 
> BNDDIR, then only the
> ones needed are bound in to the program object. But that 
> doesn't solve the
> issue of determining which duplicate export to use...

Well, as with programs, I expect the highest version of an object in the
library list to be the correct one to use, so a combination of
populating the binding directory as I outlined in another response (with
our RBDBNDDIR command) and *DUPPROC, works well for us.

Cheers,

Martin.

--                                                                     
Martin McCallion                 
Midas-Kapiti International
Work:  mccallim@midas-kapiti.com
Home: martin.mccallion@ukonline.co.uk

Apologies for the length of this sig, but company policy says:
This email message is intended for the named recipient only.  It may be
privileged and/or confidential.  If you are not the intended named
recipient of this email then you should not copy it or use it for any
purpose, nor disclose its contents to any other person.  You should
contact Midas-Kapiti International as shown below so that we can take
appropriate action at no cost to yourself.

Midas-Kapiti International Ltd, 1 St George's Road, Wimbledon, London,
SW19 4DR, UK
Email: Postmaster@midas-kapiti.com Tel: +44 (0)208 879 1188 Fax: +44
(0)208 947 3373
Midas-Kapiti International Ltd is registered in England and Wales under
company no. 971479 
+---
| 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.