jrobe...@dhs.state.ia.us (Roberts, John J) writes: > I'm surprised the old-timers didn't comment on my mention of APL. > This was the original "write-only" language - maintenance was only > possible by the original author. It was very heavily touted by IBM in > the early 70's.
somewhat because of litigation, 23jun69 unbundling announcement started charging for application software (but case was made that kernel software would still be free), se services, maintenance, etc. up until then a lot of se training was journeyman/apprentice as part of large groups of SEs at customer site. after 23jun69, nobody could figure out how to have all that SE training using customer resources w/o charging the customer for it. to address the issue several cp67 virtual machine datacenters were created to provide branch office SEs ability to login remotely and practice guest operating system in virtual machine. This was the HONE system ... some past posts: http://www.garlic.com/~lynn/subtopic.html#hone and some old email http://www.garlic.com/~lynn/lhwemail.html#hone the science center ... some past posts http://www.garlic.com/~lynn/subtopic.html#545tech besides virtual machines, internal network, a bunch of other stuff, also ported apl\360 to cms for cms\apl. cms\apl workspaces were now as large as virtual address space size (which required rewritting how apl managed it workspace allocation) as compared to common 16k or 32kbytes in apl\360 ... also an API was added to cms\apl that allowed invoking cms system services like file i/o. The combination allowed cms\apl to be used for real-world applications ... for instance the business planners in armonk loaded the most valuable of corporate information (detailed customer data) on the cambridge system and implemented business models in cms\apl. This required some security issues since the cambridge cp67/cms system was also used by some number of non-employees from various educational institutions in the boston/cambridge area. HONE also started offering marketing&sales applications implemented in cms\apl. Eventually the sales&marketing use began to dominate all HONE use and the virtual guest use died off. By the mid-70s *ALL* mainframe orders had to be first processed by HONE aids&configurators ... all implemented in APL (and HONE virtual machine clones were started to sprout up all over the world). HONE was part of the sales&marketing organization and periodically some branch manager would be promoted into executive position that included responsibility for HONE ... and they would find to the horror that the company (especially sales&marketing) ran on vm370 (not *MVS*). They would come to believe that their career in the corporation would be made if they could convert HONE to MVS. A huge amount of resources would go into a MVS migration attempt and eventually fail ... then there would eventually be executive shuffle and the whole thing forgotten until the next new executive. Recent (linkedin) discussion about several features implemented for the HONE vm370 operation in the late 70s, that are finally in the process of being included in zVM ... aka from the annals of release no software before its time: http://www.garlic.com/~lynn/2011m.html#46 From The Annals of Release No Software Before Its Time http://www.garlic.com/~lynn/2011m.html#47 From The Annals of Release No Software Before Its Time http://www.garlic.com/~lynn/2011m.html#59 From The Annals of Release No Software Before Its Time -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
