Re: FILE TRIGGER

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxxxxxxxx>]

Ken:

In i5/OS or OS/400, you can always issue an OVRDBF at runtime, to 
specify "blocking" or to change the "blocking factor" using the SEQONLY 
parameter on the OVRDBF command, without ever having to change or 
recompile your programs.

Write a small RPG/400 program that writes records to a file and compile 
with CRTRPGPGM ... GENOPT((*LIST) and study the generated OPM MI 
assembler language instructions in the listing spool file to see the 
code that is generated for the I/O.  There is no code generated in the 
program to do "blocking", and so, all blocking must be done by the 
system, within the database I/O routines that are called from the 
generated code.

Hope that helps,

Mark S. Waterbury

> On 12/3/2010 10:51 AM, Ken Sims wrote:
> Sorry Duane, but no, that does NOT make sense.  When a file is
> blocked, the program holds the records in its own storage and does not
> call database management until it is ready to write the block to the
> file.
>
> (This is all irrespective of when records are actually written to some
> type of permanant media.)