Service Program Question.

Even though your application may only have two explicit activation
groups, it is always possible for system services that you may be
implicitly using to have their own activation groups.

I have seen RCLACTGRP *ELIGIBLE "accidently" impact Utilities, Exit
Registration facility, and communications.  *ELIGIBLE is dangerous.

Bruce

>
>Right,
>
>i forgot to mention that there are only two activation groups in our
>application - one for the startup, and one for the rest (and service
>programs with *CALLER).
>So it's the same in this case - there is only one eligible.
>
>>
>> RCLACTGRP *ELIGIBLE can lead to unexpected results if there are
>> several activation groups going at the same time.  I believe it's
>> safer to reclaim them by name.
>>
>


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