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

Re: How to Find what module a procedure is located in

Exactly what I meant. Instead of distributing 4 objects you send just one
and the modules object can be kept or deleted.


On Thu, Feb 7, 2013 at 2:56 PM, Peter Dow <petercdow@xxxxxxxxx> wrote:

Hi Jim,

What do you mean by "fewer objects to distribute"?

Modules are not required for anything except creating the service
program -- once the service program has been created, the *MODULE
objects are not required for execution.

So if you're a software vendor, I'd recommend getting rid of all *MODULE
objects in your distribution package.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx>/


On 2/7/2013 9:26 AM, Horn, Jim wrote:
Other than having a fewer objects to distribute, is there an advantage to
having multiple modules in a service program, rather than 1 service
program
per module?

Jim


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