Re: Modules using NOMAIN, but not in a Service Program

Security reasons. We typically bind licensing and other security modules
(they do not change often) directly into executable objects so that their
execution cannot be intercepted as with an external call, be that call to a
program or service program. With an external call you can always get
between the caller and the called routine and inspect parameter values and
such.

Stu




On Sun, Jan 16, 2011 at 17:42, <KSinner@xxxxxxxxxxxxxxxxx> wrote:

This is my first post to this list, so if I need to provide more
information, please let me know.

I am running into several cases where a module is bound to 1 or more
programs and the module has the NOMAIN keyword, with only 1 subprocedure,
and it is not bound into a service program.

Are there any advantages or disadvantages to this method? (I am
accustomed to using service programs for modules like these, but want to
be open to other methods if there are benefits to do so.)

Thanks! I appreciate any information you may have on this!

Kim Sinner

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.