Re: Triggers not always executing.

A common error in trigger programming is to assume that the trigger will 
be called from a highly structured application that has the library list, 
etc, set up just right.
For example, many triggers will fail if you do an EDTLIBL and remove any 
user defined libraries, and then do an UPDDTA.
I remember seeing documentation somewhere that your trigger program should 
be in your file library.  Perhaps that was because a restore, done wrong, 
may disassociate the trigger program from the file.

Is the trigger called from a 5250 job?  Does the joblog show anything?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





GKern@xxxxxxxxxxxxxxxx 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
04/26/2004 10:37 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
Triggers not always executing.






Does anyone know of any type of DB commands/utilities that could be used 
to diagnose trigger processing?

I have a situation where record updates should trigger a program to 
execute but for some reason the trigger doesn't always execute. Almost all 

of the time (99.9%) of the time the trigger appears to work. 

I wrote the trigger program, and included code in it to log triggered 
update requests to a logfile. Other than logging the trigger requests, is 
there anything else I can do to monitor the triggers?

Regards,

Gerald Kern
IBM Certified AS/400 RPG IV Developer & RPG IV Programmer
MIS Project Leader, Lotus Notes/Domino Administrator
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.