I don't think that there is one simple solution for all your changes.
For tiny changes, commenting out the old stuff and adding a new line is great! For example, if replacing a hard-coded network path with a variable path:
The "004" is NOT the ticket #, rather the source version # for this particular CL. For example, the following is the 4th change to this pgm since pgm creation. At the top of source is a comment relating the "004" to the ticket #.
/*@004D CHGRDIR RMTDIR('CorpNetworkServer/FTP/Receive/Test') */
/*@004A*/ CHGRDIR RMTDIR(&NET_DIR)
The above is intuitive and is helpful for future pgmrs (or myself as my memory weakens) when it is looked at in 6 months.
For a larger mod such as removing 500 lines of code and replacing with a callable reusable pgm, go ahead and delete the 500 lines and key a comment stating so much.
When people are browsing and searching thru code, it is unlikely that they will have the time to refer to archives in general. Depends on how much time is available and how bad they want to know what "was". Having small changes documented in the source can really be a time saver.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact