RE: One trigger per PF event ?

["Schenck, Don" <Don.Schenck@xxxxxxxxxx>]

You are my hero.

Thanks.

-- Don Schenck

-----Original Message-----
From: Carsten Flensburg [mailto:flensburg@novasol.dk]
Sent: Tuesday, August 14, 2001 11:00 AM
To: midrange-l@midrange.com
Subject: Re: One trigger per PF event ?


Here's the iSeries DB/2 homepage - where you'll find some coding examples:
http://www-1.ibm.com/servers/eserver/iseries/db2/db2tch_m.htm

- and here's a redbook DB2/400 Advanced Database Functions - check out
chapter 5 &10:
http://publib-b.boulder.ibm.com/Redbooks.nsf/9445fa5b416f6e32852569ae006bb65
f/b282c9e6ca929c8e862568ab0058b669?OpenDocument

Best regards,
Carsten Flensburg


----- Original Message ----- 
From: <midrange-l-admin@midrange.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, August 14, 2001 4:40 PM
Subject: RE: One trigger per PF event ?


> 
> 
> Thanks!
> 
> Now I can only hope my client has V5R1 ... which I'm sure they DO NOT.
> 
> Can you point me to any information for older OS/400 versions?
> 
> -- Don Schenck
> 
> -----Original Message-----
> From: Carsten Flensburg [mailto:flensburg@novasol.dk]
> Sent: Tuesday, August 14, 2001 10:33 AM
> To: midrange-l@midrange.com
> Subject: Re: One trigger per PF event ?
> 
> 
> As of V5R1 the limit is 300 (and a read trigger event has been added as
> well).
> 
> Best regards,
> Carsten Flensburg
> 
> ----- Original Message -----
> From: <midrange-l-admin@midrange.com>
> To: <midrange-l@midrange.com>
> Sent: Tuesday, August 14, 2001 4:05 PM
> Subject: One trigger per PF event ?
> 
> 
> >
> >
> > Is the one trigger per PF event still true?
> >
> > In that case, how do you handle this constraint?
> >
> > My thinking is to write a CL program for the event; if anyone wants to
> add
> > their RPG program as an event handler, they can call it from the CL
> > program.
> >
> > Comments?
> >
> > Peace,
> >
> > -- Don Schenck, Schenck Technical Consulting
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> >
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> 

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com