RE: ILE question : parmameters, modules and service programs

David,

I use modules to organize source and to make use of the multiple levels of
privacy.

For instance:

I might have an INVENTORY *SRVPGM made up of multiple modules.

One module is INVENTORY which contains all the upper level public procedures
related to inventory.

Then there might be a module for each inventory related file, which contains
exported procedures I
instead to use only by one or more of the other modules within the INVENTORY
service program.

The key idea is that there are two levels of exports, from a module via the
EXPORT key word and from
the service program as a whole. Any procedure EXPORT'ed by a module is only
usable inside the program
or service program into which the module is bound. To make a exported
procedure in a service program
module usable outside the service program, you need to specify that the service
program exports the
procedure via the EXPORT() parameter of the CRTSRVPGM command. The recommend
way to handle the
service program exports is using binder source; so on the CRTSRVPGM command
you'd specify
EXPORT(*SRCFILE) SRCFILE(MYLIB/QSRVSRC). The other option, which I strongly
urge you not to use is
just having your service program export every EXPORT'ed procedure from every
module in the service
program via EXPORT(*ALL) on the CRTSRVPGM command.


HTH,
Charles

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Foxwell
Sent: Monday, May 07, 2007 9:32 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: ILE question : parmameters, modules and service programs

Thanks for all the help.

My problem now with service programs is that I don't see why
I would put exported procedures anywhere else!
If I create an exported procedure it's surely to be able to
call it from more than one program, so why have we been
putting everything in modules?
Answers, please.

We DO have an application that recompiles all the necessary
objects when a module is modified. Trouble is, more and more
programs are binding the same procedures and the application
seems to want to compile the whole machine when one of our
more popular modules is modified!

As for adding parameters, is this not a an idea ? :

Calling procedure
/COPY QRPGLESRC,DSPEC_P1

WPARM1 = IPARM1
WPARM2 = IPARM2

/COPY QRPGLESRC, CALL_P1

*************************************

QRPGLESRC/DSPEC_P1
D WPARM1 S LIKE(REF_PARM1)
D WPARM2 S LIKE(REF_PARM2)
*************************************

QRPGLESRC/CALL_P1
CALLP ( WPARM1 : WPARM2 )

*************************************

I haven't tried this, maybe someone will see a flaw right
away and save me some time.


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

This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please reply
to the message immediately by informing the sender that the message was
misdirected. After replying, please delete and otherwise erase it and any
attachments from your computer system. Your assistance in correcting this
error is appreciated.