Re: RPG code versioning -- RPG400-L

What I have been using is CVS and WDSc. Now this isn't exactly
deployable (from what I figured out so far), but it does maintain
versions of the source which could then easily be restored and
recompiled. I like that Aldon option though...


On Fri, 18 Feb 2005 10:50:52 -0600, Dane Cox <DCox@xxxxxxxxxxxxx> wrote:
> I've been doing some research into the mechanics of 'versioning' RPG
> code on the iSeries.  Because versioning tends to mean one thing to one
> person and one thing to another person, let me try and make my
> definition clear, even if it is not quite accurate.  I have no doubt
> I'll get lots of advice on the proper terminology, which of course, is
> one of the reasons I'm posting this.
> 
> Versioning as I understand is the distinction of one version of
> 'something' from another version of the same 'something'.  For the sake
> of specificity, let's say that I have a simple program that performs an
> inquiry on an account.  It receives 2 input parameters, chains to a
> file, and returns 50 output parameters, nothing too complicated.  Now, I
> have the very first version of this program in a library call TEST2005.
> 
> What are my options for modifying this program to return an additional
> 10 output parameters?  At this point, let's say I already have a change
> management application that helps me promote my code changes from
> development to test/QA to production.  Typically, this change management
> application simply overlays the old object with the new, right?  Well,
> what happens if I need to be able to deploy multiple versions of this
> program throughout a development life cycle?  How do I keep this old
> copy in a deployable state while also making changes and creating new
> versions of it over time?  Stated another way, how do I handle 'minor'
> versions of the code (PTF's or 'hot fixes') during the life cycle of a
> major version of the code.
> 
> My first reaction would be a separate promotion path with target
> libraries different from the original (e.g. TEST2005V1).  Is that the
> only option on the iSeries?  As I understand it, PC versioning is done a
> little differently where the code is labeled or 'versioned' and any
> version can be deployed at will.  Is this correct?  If so, how is this
> accomplished on the iSeries?
> 
> I have searched the archives on this topic, and can't seem to find any
> recent information that is related to this closely enough.  If I've
> missed something, by all means point me in the right direction.
> 
> Best regards,
> Dane
> 
> --
> 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.
> 
> 


-- 
Mike Wills
Midrange Programmer/Lawson Administrator
koldark@xxxxxxxxx
http://www.mikewills.name
Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.