RE: RPG Trigger program

Aaron wrote:

>I have a trigger on a file that calls a particular RPG
>program so I can do further processing with the record.
>Has anyone ever come across a trigger file that doesn't
>always work?

Never.  To eliminate system issues, make sure you have the latest database
group PTF applied.

>Sometimes a group of records will get written to this trigger
>file and some of them will get processed by the program
>and others wont.

How are you verifying this?  Because of a field that the trigger changes in
the record?  Is the trigger set up to allow repeated changes?  Many
questions, few answers.  Sorry.  Here's how I would try to debug this one:
1) Journal the file to see if the records you want are being updated in the
first place.  Also, see if the record is being updated a second time, later
in the run in such a way that the update would undo the trigger program's
actions.
2) Pull the "logic" from the trigger program and update every record that
comes in.  If you still have records that haven't been touched, there's some
problem with the trigger buffer declarations.  If all the records are
updated, then there's some problem with the conditioning logic.
3) Put the trigger program in debug and work with the last "good" record,
follow it through the program and then follow the next (a "bad") record
through.  See if there are dangling pointers/indicators/fields from the
"good" record.  Don't focus on just the "bad" records.

I hope this helps some,
  buck