On Wed, 11 Oct 2017 12:01:19 -0700, Anne & Lynn Wheeler wrote: > >One of the VM/370 issues was even though (originally CP/67) maintenance >distribution was all done using the CMS multi-level source ... every new >release ... they would permanently apply all maintenance & development >updates and resequence each module. ... > Why?
> ... Lots of internal sites and customers >had developed extensive source updates (some claim there was more source >updates on the VM/370 SHARE Waterloo tape than in the base system). > >The release-to-release resequencing became something of hassle ... so in >the late 70s, I wrote a couple programs ... one would take a previous >release with all maintenance applied and the new resequenced release and >generate an update that represented the change (mostly development) from >the old release to the new release, but using the previous release >sequence numbers. > Nowadays, SuperC will do that for you. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
