The best session of the entire week! I love hearing about the ancients. Too bad they didn't have handouts, I was writing like crazy.
A long, long time ago, IBM was deep in development of the S/360 (known at the time as "NPL", or "New Product Line"). This was a particularly long and uncomfortable pregnancy for IBM, and as they wrestled with NPL they began to lose sales in their 70x0 mainframe product line.
A garage project ("Project Moonlight") was started to try to extend the life of the 7090/94 mainframe. The engineers lashed a 7040/44 to the 7090 and used it as a peripheral processor -- basically a separate computer to do spooling. The little experiment was wildly successful, and where you used to get 150 jobs per day through the 7090, now you could get 400 jobs per day.
Later when the S/360 was out, the former Project Moonlight team from Houston went to Los Angeles to build the "Attached Support Processor" for S/360. They took ASP back with them to Houston, but NASA - then the big account in Houston - didn't want to double the number of processors on the floor to get spooling. The Project Moonlight team wrote a program called "SPOOL" in January 1967. But since "SPOOL" was a common acronym, and there were lots of programs around the industry called "SPOOL", a contest was held within the Houston branch office to name the program. The winner was... HASP!
HASP became a type III program literally overnight, when a customer queried one of IBM's executives about it. HASP picked up steam rapidly after that, and customers passed the news amongst themselves. Within a relatively short period of time, the support burden became far too big for the Houston branch to handle. So the HASP team moved to Washington. There they added RJE and released HASP version 2.
Meanwhile, the operating system weenies kept spinning their own wheels, and so eventually MFT-II and MVT were released. These were able to do multi- jobbing. Because such a large percentage of the OS/MFT community was already dependent on HASP, the staff in Washington adapted HASP to the new OS releases and introduced HASP-II version 1.
(The SHARE HASP project first met in Houston in March 1968. The meeting was hastily put together, and was in fact held in a roped-off corner of the parking garage. Later that year, in Atlantic City, the HASP project met for the second time (at the one-and-only joint GUIDE and SHARE meeting). Purely by accident, SCIDS at this second meeting produced the first HASP singalong, or "Esprit de Corps".)
In 1973, HASP became a real "class A" product, which implies real support. All known PTFs were collected together in one place, and HASP was reissued as version 2.3. Up until version 3, HASP was a single assembly of 55,000 lines of code. Broken up into 10 modules, the HASP developers were constrained to a single hour of test time each day -- between 4:00 and 5:00 p.m.
At about the same time, OS/VS1 was announced (internally it was known as "AOS1"). AOS1 integrated JES and RES along with the operating system, and although JES1 had no particular glaring deficiencies, users HATED it. It turned out that the user community had accumulated a stunning little multitude of modifications to HASP, and they couldn't do without these.
The AOS2 team within IBM was horrified by the reaction to JES1, and asked Washington for one last release of HASP -- please. HASP-II version 4 was made available to OS/VS2 users with support for virtual storage.
All the development and all the support for HASP was done by a team of six people, each of whom had personal ownership of certain components. The development machine at the time that HASP-II version 4 was released was an engineer's special -- an S/370 model 144, affectionately dubbed "the Yellow Turtle". Customers never saw such a thing as a model 144; it was essentially a model 145 with core memory and address translation.
You may recall a not-so-secret project that IBM was working in the early '70s. The "Future System" (FS) project was to be a successor to the S/370. When AOS1 and AOS2 came online, the FS project was dragging on and on. IBM management made the decision to develop MVS as a sort of stopgap measure to keep OS/VS alive until FS came up.
(FS eventually was given up too, but many of its ideas and concepts formed the nucleus for the System 38.)
The HASP team was reassembled for MVS in a "burned out A&P" storefront. There they put together the first cut of JES2 (its new name). The machine they tested it on was an S/370 model 162: yet another model that never officially existed outside of IBM. The 162 was a model 165 that had been refitted for FS.
JES2 multiaccess SPOOL was preceded by similar mods written at NIH and Mellon. Likewise, NJE was preceded by user written modifications at the University of Iowa and Triangle Universities Computation Center.
When FS was buried, one of the designers was assigned to the JES2 team, where he authored HASPSNA -- the SNA support for JES2. (This was way back when SNA was first being promulgated, and was known as "Single Network Architecture" instead of "Systems Network Architecture".) This same guy (one of the speakers at this session) told a horrifying war story: once upon a time an errant 3330 selector channel at a customer location rewrote the entire JES2 checkpoint dataset, shifting its contents left by one bit! He remembers spending one very long night repunching the checkpoint dataset from a dump.
Not until MVS/SE came out (what -- in around 1978?) did IBM legitimize JES2 by making it a part of the BCP, or "Base Control Program".