RE: Service Programs and Naming Conventions

Can you define "other environments"?
I know if major changes to a procedure are required, I do see alternative
naming, (I normally see "foo" and "fooEx" but that's just a variance on your
V1 V2 thing.)
I'm not familiar, however with naming the first born procedure with a V1.

-Bob Cozzi
www.RPGxTools.com
RPG xTools - Enjoy programming again.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Paul Morgan
Sent: Wednesday, September 14, 2005 7:18 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Service Programs and Naming Conventions

Lim,

This is common in other environments.  You could have both xxx_v1 and xxx_v2
versions in production at the same time.  Not every program would have to be
modified to use the _v2 version.  They could remain in place using the _v1
version.  With both versions available you can take your time (or never
finish) converting the calling programs over to xxx_v2.  This makes
upgrading the system an easier proposition.  You upgrade smaller pieces of
your application instead of a 'big bang' upgrade.

Paul