× 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.


  1.  Home
  2. MIDRANGE-L
  3. June 2009

Re: Space used by bind by copy vs space used by bind by reference

Of course. If you bind by copy you are making a copy of every module in
every program. Hopefully you are not creating one service program for all of
that.

On Fri, Jun 26, 2009 at 9:04 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:

Hi,

I have two modules that weigh 901120 and 1060864 bytes. (Is it bytes?
Octets in French).

Total 1961984

I compiled these into a service program that weighs 2072576 bytes.

Now, these two modules are bound by copy to virtually ALL our modules. With
DSPMOD export and imports I calculate 1491 modules that import from both
these modules. Does that mean that the total disk space occupied by these
modules is around 1491 times the total of the two modules, ie 2925318144? I
think that says nearly 3Gb. Does that mean I'd gain around 2.8Gb disk space
with a service program?
Or am I just being naïve as it's quitting time on a Friday?

Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.