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



Paul,

Thank you for your prompt response.  I have a question on performance.
If I have all my modules in one binding directory would that affect
performance?  I am picturing a program that only needs one file and yet
I have attached a binding directory with thousands of modules to the
program.  Is that a problem?

I thought of separating the subprocedures to one module for each file
and logicals.  The only benefit I can see is that my modules would be
smaller, which will be a cleaner way of doing it.  Why would you do it
that way?  I am open for suggestions...

Thanks,

Isa



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Morgan
Sent: Thursday, September 01, 2005 10:33 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Subprocedure Question

Isa,

You could create a module for each file with every module listed in the
binding directory.  You could also create a service program using those
modules with every service program in the binding directory.  Either way
something is going to have to be listed in the binding directory.  You
will
end up with a binding directory with thousands of modules just as you
have
thousands of files.

If you use service programs you will be sharing that file between
programs.
The file would be opened once in the service program.  If two programs
use
that file (service program) but one program calls the other program.
The
second program called from the first could do something with the file
(SETLL, READ, CLOSE) that interferes with the first program.

With modules a copy of the module gets created in each program.  Two
programs that use that file would each get a copy of the module.  In the
same example above the second program wouldn't intefer with the first
program as the file would be opened twice.

Sometimes sharing a file between programs is desirable.  Maybe the file
is a
code file that only has random retrieval (chain) of records.  In that
case
use a service program otherwise stick with modules.

Have you considered making separate modules for the logical files
instead of
including them in the same module with the physical file?  You'd have a
module for the physical file and one module for each logical file.

Paul


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.