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

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.
2) RPG io opcodes if far more readable than the _Rreadf, _Rwrite....
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.

   

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Steve Richter
Sent: Thursday, March 24, 2005 12:04 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: FW: IBM's RPG Strategy (was: Long Procedure Names)
<clip>
the big advantage for me is that it is modular and procedure friendly.
 I can open a file in a procedure in one module, use it in another
module, then close it in a 3rd. What controls the show are the
parameters passed from one procedure to the next.  Which is what
modular programming is all about.
<clip>
-Steve
-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.