• Subject: ##EMailNumber 01-WNY-1832912 Recursive Triggers
  • From: jmoreno@xxxxxxxxxxxxxxxx
  • Date: Tue, 12 May 1998 09:49:53 -0400

Hello Everybody,

Have a number of SIMPLE questions regarding a trigger Implementation.

These are the questions, and hopefully your experiences can give me
 guidelines for the writing of the trigger programs.

1.-    I read in the v4r2 DB2/400 Programming Book that Recursive
        Triggers are supported and the maximum number of recursions is 200

        Question: Is this Recursion Supported in V3R2 and if it is
                            what is the maximum number of recursions ?

2.-   Because of the nature of the recursion ... Do I need to create
        an ILE program ?

        Is there a  Simple *AFTER Update, Recursive Trigger
        Example anywhere ?

3.-   I Only Need 1 Level Of Recursion........
        I have contemplated to have a *DTAQ  BATCH program
         running in the background to simulate the Recursive
         Update. Is there any problems with this approach ?

 4.-   Can I Just simply Update the NEW_RCD area
          in the *BEFORE Update Trigger and let the
          *AFTER Update Trigger Occur, eliminating the need for recursion ?

  Thanks for your response.


   Regards                                Jorge Moreno / Military Car Sales
/ Woodbury, NY

jmoreno@militarycars.com


 PS. David ... How about a  NEW archive of TRIGGERS and data base Issues ?



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


This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2019 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].