Hi, Mark,
?
Mark,
?
I hope you and yours are doing well, and preparing for the Thanksgiving holiday.
?
I just saw this message from September.? (replying to an older message)
?
I did manage to install SEDIT, but it was a good number of years ago, and I have slept too many? times since then to remember exactly how long ago that was.
?
But, I did use SEDIT for a while back then.? IIRC, this was before the advent of "EE".
?
First, you also need to install "The PROC System" from the same Waterloo tapes, from the same place that SEDIT came from, because SEDIT is written using "The PROC System" macros.? ?
?
The other thing you need to be aware of is that there are certain "features" of SEDIT that will not work "out of the box", for example, there are many extended commands that have a file type of SEDITMOD.? Those are relocatable modules, but not using the standard from VM/SP and above, because SEDIT was all developed way before then, starting on VM Rel. 3 (maybe even earlier?)
?
The problem is, they used a proprietary relocating loader called RSIFETCH that no one seems to have a copy of, and that no one has "reverse engineered."? In theory, you could just use CMS TEXT decks and then use the OS LOAD macro to load them dynamically.? But, I am not sure how much work this would entail, to retrofit that to SEDIT.
?
Next, one of those SEDITMODs is called "FS" or "FSEDIT" -- a "full-screen editor" front-end for SEDIT.? But, you need to know that they were not using 3270s; this only worked with a very obscure async. "glass teletype" terminals made by a company called "Delta Data" (long since out of business), who sold their "TEMPEST approved" (hardened) terminals to the DoD.? And, they also had somehow integrated their own special software to manage the Delta Datas, so that meant mods deep inside VM/370 CP.? ?So, you can forget about that "FS" for now.
?
?The third thing you need to know is, some "commands" in SEDIT were actually "EDEXECs" -- they took the source code for the CP-67/CMS version of EXEC, and modified it to integrate it into SEDIT, so it would allow you to write edit macros for SEDIT.? Very powerful, but also somewhat cumbersome, as this was way before "EXEC II" appeared, and so it used a kludge to work around the 8-byte tokenization issues.
?
SEDIT, like The PROC System, is a rather large collection of many CSECTs or ASSEMBLE source files.
?
Let me know if you really want to dig into this, and I can try to spend some time to resurrect my knowledge of this artifact, having worked with it for a while back in the day.
?
All the best,
?
Mark S. Waterbury
