Shmuel Metz , Seymour J. wrote:
I'm not sure when it came along, but by VM/SE there was a somewhat more sophisticated UPDATE facility[1] with aux files, control files and update files. I'd love to see a similar facility integrated with ISPF.[1] Not only could the XEDIT editor process them, but it could generate update files to reproduce the effects of an edit session. That's one of the CMS facilities I miss the most.
re: http://www.garlic.com/~lynn/2006o.html#19 Source maintenance was Re: SEQUENCE NUMBERS the aux files, control files, update files scheme was what was created for the effort for building 370 virtual machine support into a cp67 kernel (running on 360/67). however, it was implemented all in EXEC with EXEC processing figuring out the control & aux files and making interative calls to UPDATE command. this was picked up as part of the original vm370 release and update command was enhanced to directly process control, aux, and update files (in one pass) and spitting out the (temporary, working) source file for compile/assemble. a little later, editors were enhanced to directly support the control, aux, and update files as part of loading a source file for editing ... with option that all changes made in the edit session resulted in an "update" file (as opposed to a new complete source). this recent posting, in a different thread, has more detailed description of some of the operations ... as well as URLs to current CMS documentation (including an example "update" from an internal editor that predated xedit). http://www.garlic.com/~lynn/2006n.html#45 sorting a few other recent postings that happen to also mention xedit: http://www.garlic.com/~lynn/2006n.html#34 Not Your Dad's Mainframe: Little Iron http://www.garlic.com/~lynn/2006n.html#43 MTS, Emacs, and... WYLBUR? http://www.garlic.com/~lynn/2006n.html#55 The very first text editor
