Programming a trigger audit in ILE

["Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>]

 >> Okay.  I understand that and what a *null value is then.  Does that mean
the null maps are there to help the programmer to check the value of fields
as part of the trigger processing?

As a general rule based on default behavior, if the file was created with
SQL then the fields are null-capable - if the file was created by DDS they
are not.  So if you created the file with DDS and do not specify that
specific fields are null capable (ALWNUL ?) then there are no null capable
fields and no need to even specify the null field map.

If you have null capable fields then the "nullness" can be tested/set in a
regular RPG program through the use of the %NULLIND BIF.  As Barbara pointed
out in the trigger buffer they are represented as one byte flags and you
simply test the character value in the trigger program rather than using
%NULLIND.

If you were not familiar with null flags, it is highly unlikely that your
database uses them.


Jon Paris
Partner400