Re: Service Programs in Named Activation Groups

Simple answer - ignore it.

More complicated answer. I find it hard to imagine what they are talking about.
I don't have access to the manual right now - is it possible that this is a V4R4
change?  If so it may be a badly worded comment on managing memory related to
thread usage.

There is really nothing you have to worry about in a Service program that you
wouldn't have to worry about if (for example) you were using a separate
dynamically called program to handle (say) your I/O operations.  If the thing
can be called from multiple points in your system, you need to be aware of this
and implement mechanisms to protect yourself.  Again this is 'business as usual"
- nothing to do with SPs in themselves.

That's about it - maybe someone else can think of something, but since the SP
instance is unique to the AG and the AG is unique to the job we can only be
talking about multiple clients within one job.  IBM can create system-wide AGs
and at one time were thinking of allowing us mortals to use the capability (be
happy that they decided against this) it is possible that the text found its way
into the manual when a writer encountered internal documentation and didn't
fully understand the implications.


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---