Re: Service Programs in Named Activation Groups

Static storage is scoped to activation group, so if programs from different
activation groups are calling modules in a service program, running in a
named activation group, they should expect to see changes to static
variables, made in previous calls, even coming from unrelated activation
groups.

Automatic (local) storage is allocated in stack and is not affected by
activation group.

Heap storage is also scoped to activation group, so all dynamic allocations
made from service program modules will go to the same heap (which will be
freed when this activation group ends).
This may lead to orphan pointers in other activation groups.

Basically, there is no problem in using named activation group for service
program if you understand what you are doing.


Best regards
    Alexei Pytel



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