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



Tracy,

In the data structure that's passed to your trigger program there's
some fields that give you offset of where the record, null maps, etc
are located in memory.

You need to use those numbers to locate the data.

If you use something like a "filler field" what will happen if they pass
you a different number on the next call?   Or maybe on the next release
of OS/400?

I posted a (really old and somewhat outdated) example of this type
of code here:
  http://archive.midrange.com/rpg400-l/199908/msg00110.html

Keep in mind that in newer releases of OS/400 you can eliminate the
awkward array logic and replace it with pointer arithmetic... but
this code will still work.


On Thu, 20 Mar 2003, Tracy Ball wrote:
>
> I have just done my first trigger program in ILE.  I could not get my
> program to work until I inserted (what seems) is an extra filler field
> in the parameter 1 buffer field between the old record null map and the
> new record field.
>
> I just downloaded the redbook from V5R1 and it has no mention of this
> spacing issue.  Here is my program, can someone tell me what I am
> missing or if that is the way I needed to do it.  Once I understand this
> process more, I will use the offset fields to pick up the start/end
> positions of the old/new records, however, I am still puzzled why I
> needed this additional field.
>

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.