Re: Triggers

Actually, you do not need the second step.  The record will be updated with
the updated new record
image in the trigger program.  Your method will work, but the second step
is unnecessary.

In the trigger program, use %subst to move the new record image into an
externally described data
structure with the definition of the file that fired the trigger.  This
makes updating fields in the
image a lot easy.  To apply the changes move the external data structure to
the new record image with
another %subst.

Dave Duerr
Duerr Business Solutions, Inc


Joe Teff wrote:

> If I want to update some information in the same record that caused by
trigger to fire, I would:
>
>    1. Before Add and Before Update - place the new data into the
appropriate position of the
>        "new record" image in the buffer and RETURN.
>
>    2. After Add and After Update - chain out to the record, change to
data in the field, update the
>        record and RETURN.
>
> The difference being is that on the Before action, I make the update by
changing the image in the
> ENTRY parameter and on the After action, I change the record itself. Is
this correct or do I not
> understand what I am reading?
>
> This is a V3R2 system and the parameter on the ADDPFTRG says to allow
repetitive changes.
>
> Joe Teff
> QDS
> Bloomington, MN
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to "MIDRANGE-L@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
> +---
> uucp




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---