Re: FW: IBM's RPG Strategy (was: Long Procedure Names)

On Thu, 24 Mar 2005 13:01:30 -0600, Lim Hock-Chai
<Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:
> I would think a ovrdbf with share(*yes) will make F spec work like what you 
> described below.
> 
> If you are using the RPG IO opcodes, I not sure why you even coding your 
> application in RPG language.  The beauty of RPG is its IO opcodes.
> 1) F spec allows programmer to easily know what files a program a using and 
> how it is used.

Lim, it also makes it easy for one procedure in a module to close the
file that another procedure has opened and is expecting to stay open. 
Not very modular!

> 2) RPG io opcodes if far more readable than the _Rreadf, _Rwrite....

I agree. I write a set of procedures for every database file. 
CustMaster_Chain, Employee_Write is readable.

> 3) You get level check error if a file is changed and programmer forgot to 
> recompile the program.  This might view as bad thing, but I think is far 
> better than taking a chance of processing corrupted data.

your right.  the absence of level check support is a problem.  That
and having to explicitly close the files.

-Steve