t...@harminc.net (Tony Harminc) writes: > One can certainly write a Rexx interpreter (or compiler, for that matter), > and run it under TSO and/or ISPF; in that sense it *tolerates* those > environments. But for reasons known only to IBM, the interfaces needed to > implement *integration* with the TSO/E and ISPF environments are > undocumented. It used to be possible to write one's own Terminal Monitor > Program (TMP), and there was even a book describing how to do so. With > TSO/E that book was dropped, and while one can guess at much of what needs > to be done, there are OCO control blocks and interfaces that inhibit > implementing interfaces like Address TSO and Address ISPF.
early/mid 70s, internal politics from the Future System group was shutting down 370 products (pushing that everything would be moved to completely different Future System). The lack of 370 products during this period is credited with giving clone processor makers market foothold. 32june1969 unbundling announcement started to charge for software & services ... but managed to make the case that kernel software would still be free. when FS imploded there was mad rush to get products back into the 370 pipeline. old IBM reference: http://www.jfsowa.com/computer/memo125.htm at the same time (because of the rise of clone processors) there was decision to transition to charging for kernel software (my resource manager was initial guinea pig). This continued into the early 80s ... then starts the OCO-wars. One of the motivations for OCO-wars was (again) the clone processor competition ... but another motivation was that customers weren't migrating off MVS to MVS/XA according to plan. Part of the blame was placed on customers that had source and made local modifications ... which weren't easily migrated from MVS to MVS/XA. Eliminating source would minimize customers making local modifications and enhance IBM control of their customer base. Complicating things was introduction of clone "hypervisor" (subset of virutal machines in hardware) which allowed concurrent operation of MVS & MVS/XA much more efficiently than traditional virtual machine. IBM was eventually able to respond with PR/SM & LPARS for 3090 (but by that time some amount of the MVS->MVS/XA had passed). -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
