The Fate of VM was: Baby MVS 4444
The Fate of VM was: Baby MVS 4445
re: MVS??? MVS??? for even more drift related to page mapped filesystem related to doing zero...
what's the difference between LFLine Fee and NL New line 4447
The use of fixed records, as with punch cards, was acceptable with data files stored on magnetic tape, but that was also where the usefulness ended and...
in the late 70s and early 80s ... there was joke about pulling 4shift ... working in sjr-28 1st shift ... there was the original relational-sjr implementation system-r
working across street in the disk engineering and product test labs 2nd shift (bldg. 14 & 15),
working down in stl (bldg. 90) 3rd shift and then working up at hone on the weekend.
i had helped build and support hone systems from the time it was on cp67 and then thru much of its life on vm370. much of hone services and applications had been built in apl ... starting originally with cms-apl. the cambridge science center
had ported apl-360 to cms (under cp67). apl-360 had its own mulbreastasking monitor and terminal support ... which could be discarded under cms. apl-360 also supported its own swapping of 16kbyte (sometimes 32kbyte) real memory workspaces. This had to be completely reworked for the large virtual memory environment provided with cms. cms-apl also introduced mechanism for accessing operating system APIs (filesystem operations, etc ... which offended the apl purists). in aggregate, this allowed some major applications to be developed in cms-apl (which wasn't possible in the purely self-contained 16kbyte workspaces provided by apl-360).
HONE evolved a major APL-based delivery vehicle called SEQUOIA which attempted to isolate majority of (cms) computing infrastructure characteristics from the end-user. All HONE APL applications then had major requirements to implement SEQUOIA consistent characteristics.
in the mid-70s, US HONE operations consolidated all their datacenters in northern california ... the new datacenter was across the back parking lot from the palo alto science center. palo alto science center had done the work for apl-cms (as opposed to the earlier work cambridge had done for cms-apl) and also the apl microcode buttist for the 370-145.
what's the difference between LFLine Fee and NL New line 4448
Paul Gilmartin wrote, in part: Yes. (Sort of.) Well, that's UNIX's problem. The characters CR and LF made their existence felt back when page printers were made which...
HONE had its own equivalent of constant attempts to kill vm MVS???
Especially during the late 70s and the 80s ... HONE would get a new executive every couple years. HONE was part of the marketing division and so the new executive typically came up through the marketing and sales ranks.
The corporation constantly had a sales-marketing theme that MVS was the solution to all computing requirements. That HONE was actually a vm370 based infrastructure was pretty well hidden from the world-wide field and marketing people. As a result, it frequently came as quite a shock to the new, incoming executive that HONE wasn't a mvs-based operation.
Then there ensued a period of where the whole organization would be directed to drop nearly everything else and work on moving HONE operation to a mvs-based operation. Usually within 9-12 months, it would be thoroughly proven that it couldn't be done and things would sort of settle back to semi-normal ... at least until the next, new replacement executive came in (which happened about once every two years) and the process would be repeated. As a result, something like 1-3rd to 1-2 of HONE resources went into repeatedly proving to newly appointed executives that you couldn't use MVS as HONE platform.
what's the difference between LFLine Fee and NL New line 4446
Paul Gilmartin As the first C compiler was written in order to facilitate the implementation of UNIX, the two are intimately related. There's nothing wrong with C doing that. The *operating system...