Re: Procedures, Modules, Service Programs

Seems reasonable to have APPLE, PEARS, & FRUIT.

Big question is how much will go into each? Would having everything
in FRUIT make it too big?

Remember, prior to 6.1, APPLE & FRUIT or PEAR & FRUIT will be
activated, so you're really only saving the 1/3 the resources assuming
all three are about the same size and that FRUIT is needed by APPLE &
PEAR.

Charles

On Wed, May 20, 2009 at 9:19 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> 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?

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

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Simon Coulter
Envoyé : mercredi 20 mai 2009 14:07
À : Midrange Systems Technical Discussion
Objet : Re: Procedures, Modules, Service Programs


On 20/05/2009, at 8:01 PM, David FOXWELL wrote:

My question : if one chose the huge service program option with
everything in, isn't that service program activated once only and
shared,

No.

or does it get activated by other users when they need to use it?

Yes.

If I had to guess, it would be one activation per job.

Correct ... unless in a *NEW activation group in which case ...

... or in *CALLER and invoked from different calling
activation groups ...

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  / \
--------------------------------------------------------------------



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

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