RE: Triggers

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                                           
Parm 1's length will vary based on the triggered file's length - just
like the trigger program.  By the way I wrote the RPG first.  THe CL
took about 10 seconds.
Bill Erhardt
> -----Original Message-----
> From: Art Tostaine, Jr. [SMTP:Art@link400.com]
> Sent: Friday, February 18, 2000 10:25 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: Triggers
> 
> Do you have some sample code for the CLP trigger program that you
> could post?
> 
> BTW, making a CLP the trigger is a great idea.  Why didn't I think of
> that?
> 
> Art Tostaine, Jr.
> CCA, Inc.
> Jackson, NJ 08527
> 
> 
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Bill Erhardt
> Sent: Thursday, February 17, 2000 5:32 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: Triggers
> 
> 
> There are few, if any, "gotcha's" with triggers.
> 1) A file that is triggered can not be cleared.  That is, it can not
> be
> the target of a CPYF or CLRPFM command.  If it has to be cleared, it
> can
> be done with a SQL delete or through stick build RPG.
> 2) I would strongly suggest that your trigger program be a CLP.  That
> is, have a CLP nammed as the trigger program and have it pass the
> trigger parameters to a RPG routine.  That way you can make changes to
> the RPG without having to get a lock on the actual trigger program.
> 3) Be carefull about cascading triggers.  It can effect performance.
> Remeber the update that pulls the trigger is not complete until the
> trigger program completes.
> 
> 
> > -----Original Message-----
> > From:       Graziano, Marie [SMTP:mgraziano@badgermeter.com]
> > Sent:       Thursday, February 17, 2000 10:22 AM
> > To: 'Midrange'
> > Subject:    Triggers
> > 
> > Does anyone have any gotcha's on using triggers?  We have a product
> > being
> > installed and they are using data ques and triggers.  We are not
> > really
> > educated in triggers.  
> > 
> > mgraziano@badgermeter.com <mailto:mgraziano@badgermeter.com> 
> > 
> > 
> > Marie Graziano
> > 
> > +---
> > | 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
> > +---
> 
> 
> +---
> | 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
> +---
> 
> +---
> | 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
> +---


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