Re: create DB trigger that will call a stored procedure

Gerald,
In your trigger procedure, you can not directly reference data base field
names for a call. You need to declare and set a variable then use that as
you do in the 2nd example.

Jeff Young
Sr. Programmer Analyst

On Thu, Dec 15, 2016 at 2: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....
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD