× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Data base triggers
  • From: "Nelson C. Smith" <ncsmith@xxxxxxxx>
  • Date: Mon, 24 Jan 2000 18:22:33 -0500

A trigger program that is "fired" by data base management is an
"interruption" in the normal update process of the record (kinda like an
exit program).  That's why you set an *ESCAPE message to end the program
right there if you find an error and want to stop the normal completion of
the record update.  By the same token, you can change the buffer and then
let the update go on through and the effect is that you have just updated
the update.

BTW, you want *YES on the ALWREPCHG parm.

----- Original Message -----
From: "Jim Langston" <jlangston@conexfreight.com>
To: <RPG400-L@midrange.com>
Sent: Monday, January 24, 2000 4:36 PM
Subject: Re: Data base triggers


> I believe you want to specify ALWREPCHG(*NO) on the ADDPFTRG
> command.  Help for this is:
>
> Allow Repeated Change (ALWREPCHG) - HELP
>
> Specifies whether repeated changes to a record within a
> trigger are allowed.
>
> The possible values are:
>
> *NO
>   Repeated changes to a record within a trigger are not
>   allowed
>
> *YES
>   Repeated changes to a record within a trigger are
>   allowed.
>
> >From what I understand, that means if a trigger program changes a record
> if you have a *CHANGE trigger, it will be called if ALWREPCHG is set
> to *YES, otherwise, it will not call it a second time.
>
> Regards,
>
> Jim Langston
>
> Tom Tufankjian wrote:
>
> > Is it possible to have a trigger program update the record whose update
> > triggered it without having it re-trigger itself infinitly?
> >
> > I know that's an awfully long sentence so I'll try to give an example.
> > 1.  A record is updated in a file
> > 2.  The update triggers a program
> > 3.  The trigger program updates a timestamp field, for example.
> >
> > Would step 3 cause the trigger program to execute again?
>
> +---
> | 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
> +---
>

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.