Re: Trigger problems after upgrading to V5R1

Check whether the offsets in the trigger buffer are
hardcoded.  The positions changed with V5R1.

If the trigger is softcoded, it doesn't have this
problem.

hth,

Phil

> From: "Mike Silvers" <msilvers@hbs-inc.com>
> To: <midrange-l@midrange.com>
> Subject: Trigger problems after upgrading to V5R1
> Date: Fri, 12 Apr 2002 07:59:45 -0400
> Organization: Hainey Business Systems
> Reply-To: midrange-l@midrange.com
>
> All,
>
> I have a PF trigger that was installed on V4R5.  It
was working well.  The
> trigger program itself is written in RPG and calls
another program.  There
> are other triggers on this file also.  The machine was
upgraded to V5R1 and
> our problems began.  There are other triggers on the
file, but they are from
> the package and I have no control over them.  One
other thing that has
> changed is that the package vendor has added
journaling to the file.  I have
> a CL program that checks the status of the trigger
and, if it was detached,
> it attaches the trigger.  I learned (the hard way)
that the number of
> triggers that can be attached to a file has
increased.  The program kept
> attaching triggers to the file.  At that time the
triggers worked.  I
> changed the program to create a name for the trigger
and replace the
> previous trigger on the file.  The trigger shows as
attached and enabled,
> but it does not fire the program.
>
> Any ideas?
>
> Thanks
>
> Mike