RE: RPG code versioning

Dane,

First off I suggest you contact your CMS vendor.  They will be able to help you 
decide how to best handle this.


To use Aldon CMS terminology:
In your scenario you'd have multiple BASE releases ( versions ) multiple DELTA 
releases ( PTF levels)  for a given Application.  Every delta can have one and 
only one release as its parent.  Every release can have 0 or more child DELTAs.



Application - My In-house Application Suite
  Release - Base Version 1 v1r0m0
    Release - Delta PTF level v1r1m1
      Release - Delta PTF level v1r1m2
    Release - Delta PTF Level v1r2
    Release - Delta PTF Level v1r3
  Release - Base Version 2 v2r0m0
    Release - Delta PTF level v2r1m0
    Release - Delta PTF level v2r2m0
  Release - Base Version 3 v3r1m0


One thing to keep in mind is that the DELTA releases don't usually include all 
objects.  To have a working v1r1m2, you have to take all objects in v1r1m2, 
v1r1m1, and the base v1r0m0.

On the other hand, the base v1r0m0 is complete by itself.



HTH,
        

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Dane Cox
> Sent: Friday, February 18, 2005 11:51 AM
> To: RPG programming on the AS400 / iSeries
> Subject: RPG code versioning
> 
> 
> 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.
> 
>