RE: Activation Group for Service Programs (was DoW (WAS DoU...))

Hi Jon -

>PS.  What on earth is wrong with named AGs?  Since they are 
>the foundation for ILE (i.e. the way it was designed to work) 
>I find it hard to guess at what you find wrong with them.

I did some experimenting with running my service program in a named
activation group, called by a client program running in the default
activation group.  Where's what I found:

1. With the client program ended and after running RCLACTGRP(*ELIGIBLE), the
service program could be activated again, but when a procedure in the
service program was called, the job would terminate.

2. There are a couple of CLLE modules in the service program.  When an error
occurs and an 'I' option is taking to the message, the error percolates up.
This is fine.  However when the client program is called again, the service
program cannot be activated again.

With the service program running the in default activation group: scenario
#1 cannot happen because the default activation group cannot be reclaimed.
Scenario #2 does not occur.  The client program can activate the service
program again without any problem.

Since the only problem I see with running the service program in the default
activation group is RCLRSC, which I already have a method in place to
handle, I'm going to stick with making the service program *CALLER.  Dealing
with RCLRSC is minor compared to the problems running the service program in
a named activation group with a client in the default activation group.

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.

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