AW: Create Service Program

Paul,

a binding directory is only used to find the modules or service programs
that contain the appropriate procedures to bind them to the (service)
program
at compile time in the binding step.
But it has no impact if a procedure is exported or not.

A procedure can be either internal or exported.
Internal means it can only be called within the module where it is defined.
Exported meand it can be called from all procedures located in or outside
the module.

Jeff,

why do you use a copy member?
If the procedure is only used in the first module,
why you don't copy it directly into this source member?

In my opinion a procedure should always be encapsulated,
so that it can be called by any other procedure.
We have made the experience, even if today a procedure is only used by a
single module,
tomorrow or in two weeks we need it in an other procedure, too.

Birgitta



-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von Paul Morgan
Gesendet: Montag, 29. August 2005 21:30
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: Create Service Program


Jeff,

Don't specify the second module when creating the service program (listed in
the MODULE parameter on the CRTSRVPGM command right?).  Put the second
module name in the binding directory used to create that service program
(the BNDDIR parameter on the CRTSRVPGM).  The modules specified in the
binding directory don't get exported from the service program.

Paul

--
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333

Jeff wrote

> Paul,
> The second procedure was the only procedure in the second module.
> I ended up making it a /COPY member and bringing it in that way.



--
This is the RPG programming on the AS400 / iSeries (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.