Re: Programming a trigger audit in ILE -- RPG400-L

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

Buck Calabro wrote:
> 
> The definition of the trigger buffer is incorrect.  Filler 2 is not integer,
> but character.  After the new null length comes a 16 char filler and then
> the record images.
>   --buck

For structures with documented field offsets like this trigger buffer
and the output structures for APIs, I think it's better to define the
structure like this, with explicit positions.  Then you don't have to
define the filler fields at all, and it's way easier to determine that a
given subfield is defined as documented.

 * Trigger Buffer passed to the program from the system.
D TrgBuffer       ds
D  TFilename                    10    overlay(trgBuffer:1)
D  TLibraryName                 10    overlay(trgBuffer:11)
D  TMemberName                  10    overlay(trgBuffer:21)
D  TEvent                        1    overlay(trgBuffer:31)
D  TTime                         1    overlay(trgBuffer:32)
D  TCommitLock                   1    overlay(trgBuffer:33)
D  TCCSID                       10i 0 overlay(trgBuffer:37)
D  TRRN                         10i 0 overlay(trgBuffer:41)
D  TOldOffset                   10i 0 overlay(trgBuffer:49)
D  TOldLength                   10i 0 overlay(trgBuffer:53)
D  TOldNullOff                  10i 0 overlay(trgBuffer:57)
D  TOldNullLen                  10i 0 overlay(trgBuffer:61)
D  TNewOffset                   10i 0 overlay(trgBuffer:65)
D  TNewLength                   10i 0 overlay(trgBuffer:69)
D  TNewNullOff                  10i 0 overlay(trgBuffer:73)
D  TNewNullLen                  10i 0 overlay(trgBuffer:77)

This mailing list archive is Copyright 1997-2025 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.