RE: Triggers

[bmorris@xxxxxxxxxx]

>Date: Fri, 18 Feb 2000 11:56:52 -0500
>From: Bill Erhardt <ERHARDT@baldwinhq.com>
>
>Sure, try this
> PGM        PARM(&PARM1 &PARM2)
>  DCL        VAR(&PARM1) TYPE(*CHAR) LEN(1418)
>  DCL        VAR(&PARM2) TYPE(*CHAR) LEN(4)
>  CALL       PGM(RHPKMSTRGR) PARM(&PARM1 &PARM2)
>  RCLACTGRP  ACTGRP(*ELIGIBLE)
> ENDPGM

RCLACTGRP(*ELIGIBLE) in a trigger program?  This could have the
same level of effect as doing a CLRLIB QTEMP in a trigger program.

It might be ok for a particular application if the application
is all in the same activation group, and therefore not eligible
to be reclaimed, and there is no possibility of other activation
groups now or later that can be affected.  But as a general
purpose template, this is very dangerous.

RCLACTGRP(*ELIGIBLE) isn't always wise even at the end of an
application (better to reclaim activation groups explicitly
by name).  Coding it as part of a trigger program, to be done
on every trigger event, is likely to cause problems in your
application if there are programs that have ended with LR off,
expecting to be in the same state the next time they get called.
But even if LR-OFF programs can safely get reinitialized at
any time during the application, reclaiming idle activation
groups during the application will cause the activation groups
to be recreated the next time a program gets called.  This
can be expensive.

Barbara Morris


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