Source change control WAS: RE: IBM pushing Java

On 03/29/99 04:48:47 AM Colin Williams  wrote:

>Problem is, sometimes when error fixing, the error fix doesn't work and
>introduces a new error, so code may need to be back out. If you dont
>comment out your changes, they're lost! 

We had that debate here also.  It turns out that we really don't often back 
out the changes we've made, but if we had to, "deleting by commenting" 
doesn't help unless we comment out every single line that was added, 
changed or deleted and then type the replacement line(s) right after. 

We settled on a poor man's source archive: copy the original source to 
QRPGSAV and put a version number on it so we can see the progression of 
changes.  Original member=PRTBILLR, archived members=PRTBILLR01, 
PRTBILLR02, PRTBILLR03 and so on.  With CMPPFM, it becomes fairly simple to 
find all the adds, changes and deletes from one version to the next. Hardly 
a great solution, but we find that it works better than only having one 
source member with a bunch of commented out lines in it.  We can always use 
WRKMBRPDM to find the old members and remove them when we need DASD.

Buck Calabro
Billing Concepts Inc (formerly CommSoft), Albany, NY
mailto:mcalabro@commsoft.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---