The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well.
[EMAIL PROTECTED] (Gary Green) writes: > http://searchdatacenter.techtarget.com/tip/0,289483,sid80_gci1299376,00.html?track=NL-576&ad=624866&asrc=EM_NLN_3060935&uid=1900046 previous posting mentioning zNextGen program: http://www.garlic.com/2008c.html#45 Young mainframers' group gaims momentum can you say HONE? ... hands-on network experience ... misc. past posts http://www.garlic.com/~lynn/subtopic.html#hone before the 23jun69 unbundling announcements ... novice system engineers would get hands-on experience in customer accounts ... as part of larger team of SEs (with a variety of experience) ... sort of apprentice type program. after the 23jun69 unbundling announcements ... besides starting to charge for software ... SEs time at customer accounts were also charged for. The situation at the time couldn't come up with having apparentice SEs learning on the customer nickle. http://www.garlic.com/~lynn/subtopic.html#unbundle the initial solution was to put in some number of cp67 virtual machine systems ... and provide remote login access to SEs from branch offices. the science center had pioneered virtual machines systems in the mid-60s ... starting with cp40 (on specially modified 360/40 supporting virtual memory) which morphed into cp67 (when standard 360/67 machines with standard virtual memory support become available) http://www.garlic.com/~lynn/subtopic.html#545tech the science center had also ported apl\360 to cms\apl. apl\360 installations had typically been limited to 16kbyte or 32kbyte workspaces. the cms\apl port opened up workspace size to full virtual memory (although parts of apl had to be reworked for virtual memory operation). The dramatically increased workspace size and some other features (added to cms\apl) ... allowed a lot more real-world applications to be done in apl. One instance was that corporate hdqtrs people loaded the most sensitive coporate information on to the cambridge system and ran remote business modeling applications from armonk. This also required a very high level of security since the cambridge system also had various non-employees from the area universities and colleges using the system. a little topic drift regarding the security issue: http://www.nsa.gov/selinux/list-archive/0409/8362.cfm another use of cms\apl was to deploy sales and marketing applications on the HONE systems, supporting branch office (other than SEs). Eventually these sales and marketing applications came to dominate all HONE activity ... to the exclusion of SE "hands-on" use. Before long, it was not even possible for customer machine orders to be submitted unless they had been preprocessed by some HONE application. for slightly other topic drift: http://www.garlic.com/~lynn/2008d.html#17 more on (the new 40+ yr old) virtualization http://www.garlic.com/~lynn/2008d.html#23 more on (the new 40+ yr old) virtualization for other folklore topic drift ... starting in the late 70s, there was constant series of efforts to move HONE (sales & marketing apl applications) off of vm370 and on to MVS. The cycle was approx. two years, a new executive would come in, discover to their horror that the corporation didn't actually run on MVS ... and mandate HONE be moved to a MVS platform. All work would stop for 6-9 months while everybody worked on attempting to move things over ... which would eventually fail miserably ... and then things would be back to almost normal for a short period until the next executive replacement. At one point in one of cycles in the early 80, one of the POK executives admonished the HONE organization that a MVS port would easily be possible if they would just rewrite all the APL applications in assembler. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
