Re: Procedures, Modules, Service Programs

On 20/05/2009, at 11:19 PM, David FOXWELL wrote:

So, if I'm dealing with apples and pears, I'd have an apples SRVPGM and a pears SRVPGM so that my pears users don't unnecessarily activate apple functions and vice versa?

Yes.

I could always have a fruit SRVPGM that bound the apples and pairs, for the general fruit department, couldn't I?

Not if you've already built the APPLES and PEARS service programs. Dumb idea if the FRUIT *SRVPGM simply contains the APPLEs and PEARS modules. If the 'general fruit department' needs to use APPLES or PEARS then bind directly.

However, you might have a FRUIT *SRVPGM that provides functions common to both APPLES and PEARS (since they are both pome fruit there are similarities that might be better abstracted out to a common service program). Or you might make FRUIT handle generic functions for all kinds of fruit (pome, stone, nuts, berries, citrus, etc.).

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------