Re: re. Access Groups and Threads

I just wanted to add couple of additional points to Nelson's excellent
coverage:

----- Original Message -----
From: "Smith, Nelson" <NSmith@lincare.com>


> For a one shot program, *NEW is not too bad.  The benefits are that it
> automatically cleans up behind itself.  The drawback is the overhead of
> creating the activation group.
>
> Where you don't want to use it is in any situation where it is called
> repeatedly, like in a looping batch process or on a trigger program.  The
> overhead of the building-running-deleting process can kill you.

This is true. If you're using *new in a program that's called repeatedly,
you're going to feel the pain. :)  In those situations, I use a named AG
myself, but QILE would work if you don't have to worry about shared ODP's.
For more on the named .vs. QILE issue, refer to an earlier thread on this
same list:

http://archive.midrange.com/rpg400-l/200105/msg00096.html

With respect to trigger programs, they should run in *caller so that they're
within the commitment control boundaries of the calling application.


> Small gotcha to note: If you want to do a RCLACTGRP on a named activation
> group, you need to be out of it at time you run that command, i.e. back to
> the program that called the program with a named activation group. It's
also

Or use CEETREC.


John Taylor


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