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

The whole idea of the module is break processing down into pieces of code
that perform some single function. For example, my standard error handler
has three modules.

XVERRH_M01 provides throw and re-throw functions.
XVERRH_M02 provides message storage functions.
XVERRH_M03 provides ILE condition handling.

Now obviously I could have put all three modules together into one big
module but it makes more sense to break them down by function. In addition,
some of the modules have global variables. Restricting access to those
variables to only the functions that needs them makes for better code.
Information hiding.

So to answer your question, service programs can have one or multiple
modules just depending on what functions you are programming.





On Thu, Feb 7, 2013 at 10:26 AM, Horn, Jim <jim.horn@xxxxxxxxxxxxxx> 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

***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.
--
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.