Re: create DB trigger that will call a stored procedure

Yes, this works and is very fast. You will also want to have a monitor program to ensure that the NEP stays active, otherwise the Data Queue could gain too many entries, and data queue operations will start taking a long time. It may also be a good idea in some instances to start a second or third NEP to prevent a single bad entry from clogging up the works, and depending on the environment, it may even give you a throughput boost.

Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx


-----Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx> wrote: -----
To: midrange-l@xxxxxxxxxxxx
From: Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
Date: 12/15/2016 03:31PM
Subject: Re: create DB trigger that will call a stored procedure


my stored procedure program is taking too long....
has someone created a trigger that is just using the QSNDDTAQ api?

so then I can have a nep running to receive and process these entries?



On Thu, Dec 15, 2016 at 1:11 PM, Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx

wrote:

I found an example (that doesn't work...)
create trigger gemlib.iimtrgr1
after update of IDESC , IUMS, IUMP, IITYP
on gemlib.iim
REFERENCING NEW as n
FOR EACH ROW
BEGIN ATOMIC
CALL KSQLLIB.UPDIIMDTA1 (n.IPROD) ;
END

the above fails saying "variable IPROD not found or usable"...

however, If I do this:

create trigger gemlib.iimtrgr1
after update of IDESC , IUMS, IUMP, IITYP
on gemlib.iim
REFERENCING NEW as n
FOR EACH ROW
BEGIN ATOMIC
Declare iprod15 CHAR(15) ;
SET iprod15 = n.IPROD;
CALL KSQLLIB.UPDIIMDTA1 (iprod15) ;
END

that works....
But that seems like I am overdoing it....