Re: File encapsulation

> 
> Personally, I've found that what makes it the most valuable is to have it 
> so that the module does MORE than just database access.  Instead, have it 
> do some business logic as well as simply loading the record.

Agreed.  I would rather encapsulate business logic rather than simply
file I/O.

Things I look for:
1) needs to happen in many places 
2) Has some complexity to it
3) perhaps updates many different files or records
4) perhaps causes other actions, like e-mailing someone

As in 'post_transaction', 'inactivate_account' or 'generate_invoice'.  

I haven't (yet) been convinced that there is a great way to encapsulate
I/O (or great reason) in RPG.  Any program you write must be compiled
and 'know' the attributes of the fields you want it to work with.  

For example, if your customer id is a five digit number, and you want to
change it to be a ten character alphanumeric field, you will most likely
have to change all sorts of things in display files, printer files, and
all kinds of calc specs.  I don't believe that encapsulating I/O in a
service program radically helps this situation.

Regards,
Rich