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



Yes, the location of the record data has shifted.  If your trigger programs
use the offsets provided you won't run into this problem.  Here is how I
define my record data and map it to the correct spot in the trigger buffer.

     DOld_ORDDTL     E DS                  ExtName(ORDDTL)

     D                                     Prefix(O_)
     d                                     based(old_recordp)

     DNew_ORDDTL     E DS                  ExtName(ORDDTL)

     D                                     Prefix(N_)
     d                                     based(new_recordp)

     C                   Eval      old_recordp = %addr(Parm_01) + Old_Offset
     C                   Eval      new_recordp = %addr(Parm_01) + New_Offset

Scott Mildenberger

> -----Original Message-----
> From: Bill Erhardt [mailto:ERHARDT@BaldwinHQ.com]
> Sent: Friday, November 08, 2002 8:13 AM
> To: 'Mid Range list - Questions'
> Subject: V5R1 - and Trigger Programs
>
>
> This message is in MIME format. Since your mail reader does
> not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> We've just installed V5R1 and now have problems with trigger
> programs.  I've
> heard that the parameter has changed but how?  I've gone to
> the infocenter
> and found the trigger buffer section but this doesn't seem correct.


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.