RE: trigger program: can I fool a program into reading some selec t fields from another file?

> The logical file is a good idea, but I need to include logic in the trigger
> program; ie it is not always read one corporate record for each divisional
> record.  For example, pricing would require loads of logic to fetch prices
> from a coporate file.
>
> Any other ideas??


Two more ideas pop into my mind...

The first would be a service program.  Create a service program to do the
file access, and change all of your programs to use that service program.
Granted, this involves changes to your programs -- but if you make the
service program routines work in a similar fashion to the file operations
that you're doing now, the changes to the logic might be minimal.

The other idea (assuming that your programs are written in RPG) would be
to use "SPECIAL" files.   This is an RPG feature which makes a call to a
given program when a file operation is executed.   Since each operation is
basically calling a program, you can insert any logic that you like...
See Chapter 18 of the WDS ILE RPG Programmers Guide, or chapter 5 of the
RPG/400 Users Guide for info on Special files.

Hope that helps...