Re: Triggers not always executing.

<If you use DSPFD of the affected file, specifying TYPE(*TRG), you can 
verify
that the trigger is defined correctly, as to before/after,
insert/update/delete.>

When I have to make a mod to the trigger program, I use dspfd to ensure 
the triggers are properly defined. 

<Anything in this person's joblog to indicate an error?> 

Job log shows nothing abnormal.

<May be this option

Trigger update condition . . . .   *ALWAYS       *ALWAYS, *CHANGE(second 
page)>

Triggers are applied after an add and after a change.


FYI - I'm using the trigger template programs (from an article in eServer 
magazine) by Jon Paris & Susan Gantner to be able to assign the trigger at 
the field level during an update (see link below). Yesterday, I discovered 
that I didn't have null field support enabled in one program, and when a 
field changed from a non-blank to a blank value the field level change was 
not detected. That has since been corrected.

But that doesn't remedy my situation as the original trigger problem is 
related to a non-blank value being changed to different non-blank value.

http://eservercomputing.com/iseries/articles/index.asp?id=169&dir=/iseries/articles/

Again thanks for the replies.


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