× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I checked the archives and found the discussions on this list.  The problem
is not the buffer length.  The trigger did work until I gave the trigger a
name when adding it to the file and had the trigger replaced when adding it
to the file.

Old code (worked):
ADDPFTRG   FILE(PFVEHICLE) TRGTIME(*BEFORE) TRGEVENT(*UPDATE) PGM(DFN001R)

New code (does not work):
ADDPFTRG   FILE(PFVEHICLE) TRGTIME(*BEFORE) TRGEVENT(*UPDATE) PGM(DFN001R)
RPLTRG(*YES) TRG(FINANCE_SYSTEM_BEFORE_UPDATE_TRIGGER)


The trigger program itself (the RPG program) was not changed at all.

Any ideas?

Mike

ps... yes Rob, I do use pointers :)


To: midrange-l@midrange.com
Subject: Re: Trigger problems after upgrading to V5R1
From: rob@dekko.com
Date: Fri, 12 Apr 2002 08:03:51 -0500
Reply-To: midrange-l@midrange.com

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Documented in V5R1, somewhere.

Been discussed in the archives, maybe the rpg archives.

Jon and Susan had an article in some email newsletter but I can't find my
copy, anyone have a link?

Many people refused to use the offsets provided in a trigger program but
instead hardcoded where their data was.  Problem is, that IBM extended the
length of the header data to support blob's, etc in a trigger program.
Thus the users failure to follow the rules bit them in the fanny.  I'd ask
for code, but that should probably go to one of the language specific
lists.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Mike Silvers" <msilvers@hbs-inc.com>
Sent by: midrange-l-admin@midrange.com
04/12/2002 06:59 AM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        Trigger problems after upgrading to V5R1


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

================================
Mike Silvers
AS/400 Senior Programmer/Analyst
AS/400 IBM Certified RPG IV Developer
AS/400 IBM Certified Solutions Expert
Hainey Business Systems
8 E. Canal St
Dover, PA 17315
Branch Office:  (410) 397-8739
Phone:  (800) 932-3380 ext. 237
Fax:  (717) 292-9474
Web: http://www.hbs-inc.com
________________________________
Providing E-Commerce, EDI, AS/400
Development, Java Development,
and related services nationwide.
================================


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.






As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.