On Wed, Nov 7, 2012 at 10:21 AM, McKown, John <john.mck...@healthmarkets.com > wrote:
> <...snip...> > > So, other than being "non main stream" and even "obsessively weird", is > there any *technical* reason to maintain sequence numbers? > > -- > John McKown > Systems Engineer IV > IT > > John, We use sequence numbers to extract change lines from edited source modules. The developer making the change maintains the sequence numbers on new or on changed lines he adds/changes. When the change is finished, he then uses SUPERC with process option UPDMVS8 and compares the new changed source module to the prior release of that same source module. SUPERC then emits a change file in IEBUPDTE format. Those change files (we call them 'delta' files) identify which lines were changed and how. Multiple such delta files can then be saved and applied later, or backed out if need be. This lets more than one developer work on the same source module at the same time. It ain't CVS, but it works.... -- Mike Shaw MVS/QuickRef Support Group Chicago-Soft, Ltd.
