RE: Why keep "old" code (Was RPG III)

The only problem with this method is during the transition, you end up with
two shop standards (which is to say no standards). Also, if you are running
a vendor package which has not converted yet, you can't change their code
without having to merge the changes with every release for thousands
programs. How do you propose to do that ?
Thanks
Tom 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Bob Cozzi
Sent: Friday, February 09, 2007 7:35 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Why keep "old" code (Was RPG III) 

That is a wonderful policy, and one I think most people need to consider
embracing.

-Bob Cozzi
www.i5PodCast.com
Ask your manager to watch i5 TV



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On
Behalf Of Harvell, Joel
Sent: Friday, February 09, 2007 9:12 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Why keep "old" code (Was RPG III) 

Our policy on switching from RPG III to RPG IV is like so.  We do not
have a project to convert each RPG III program over to RPG IV.  However,
if we have to modify a program that is written in RPG III we are to
convert it over to RPG IV first then make our modifications.  

 
Joel B. Harvell
Food Lion, LLC
(704) 633-8250 x2709
jbharvell@xxxxxxxxxxxx