Can I disable the triggers, recompile the trigger programs, and then
re-enable the triggers to pick-up the "new" version of the trigger
program, or do I have to RMVPFTRG and ADDPFTRG to get the new programs.

-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Wednesday, January 02, 2002 12:36 PM
To: midrange-l@midrange.com
Subject: RE: triggers after upgrade to V5R1


Read this:
http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/info/dbp/rbafo
mst471.htm#HDRRZAHFTRC

The problem is that many people ignore the field "Original record
offset"
or "New record offset" and instead go to the last field and hardcode
that
the buffers must exist after that.  And then IBM, which went to great
pains
to give you these offset values, changes the header area in a new
release,
gets complaints from customers that the new release has a bug.  IBM gets
the same complaints from users of list API's which hardcode information
instead of using the offsets from there.



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



                    "Graves, Chuck"
                    <cgraves@roddapaint       To:
<midrange-l@midrange.com>
                    .com>                     cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     RE: triggers
after upgrade to V5R1
                    drange.com


                    01/02/2002 01:51 PM
                    Please respond to
                    midrange-l






Where to I find the documentation for the NEW buffer layout????

-----Original Message-----
From: Scott Mildenberger [mailto:Smildenber@Washcorp.com]
Sent: Wednesday, January 02, 2002 10:11 AM
To: 'midrange-l@midrange.com'
Subject: RE: triggers after upgrade to V5R1

The triggers may be firing but not working correctly.  The trigger
buffer
layout changed so if you had the location of the data buffers hard-coded
they will be incorrect.

Scott Mildenberger

> -----Original Message-----
> From: Graves, Chuck [mailto:cgraves@roddapaint.com]
> Sent: Wednesday, January 02, 2002 11:16 AM
> To: midrange-l@midrange.com
> Subject: triggers after upgrade to V5R1
>
>
> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Has anyone noticed a problem of triggers NOT firing after upgrade to
> V5R1
_______________________________________________
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.

_______________________________________________
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.





_______________________________________________
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-Ups:

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.