peter.far...@broadridge.com (Farley, Peter x23353) writes:
> PMFJI here, but IMHO the pipeline paradigm, though obviously powerful
> and useful, is not the major advantage of VM and CMS over z/OS and TSO
> for developers, Rexx or otherwise.
>
> Rather, I would argue that it is the even more the powerful concept of
> DVM's, Disconnected Virtual Machines, and the resulting ability for
> even ordinary application developers, not just sysprogs, to very
> simply arrange to pass data between them via VMCF and/or IUCV.  Then
> add the power of VM Rexx and pipeline support and XEDIT and the other
> CMS tools as the only code needed to actually run in and interact with
> those DVM's and many extremely useful and powerful applications can be
> coded with nary a compiler or assembler in sight, never mind in use.
> No authorized coding or cross-memory complexity required.  Add DB2 and
> networking support for Rexx and many full-function business
> applications are added to the possibilities.
>
> I bemoan the failure decades ago of the CMS on MVS project.  That
> would, indeed, have changed the history and practice of our computing
> lives.

I recently mentioned pipelines and doing internal adtech conference in
spring 1982.
http://www.garlic.com/~lynn/2013o.html#91 Learning Rexx

there was also a presentation on CMS running on MVS. 

A couple yrs earlier, Endicott had gotten the corporation to announce
that vm370/cms was the strategic online, interactive solution. The TSO
product administrator had contacted me if I would redo the
dispatcher/scheduler for MVS ... attempting to make MVS much more
interactive friendly. I declined since the MVS problems with good
interactive human factors went way beyond its
dispatching&scheduling. old email ref.
http://www.garlic.com/~lynn/2006b.html#email800310

This then further came out in the CMS under MVS work ... they could get
it to run functionally ... but because of all the other problems, the
question then was "why"

this talks about the internal SPM ... which was superset of VMCF, IUCV
SMSG combined ... originally done at Pisa Science Center for cp67 but
then moved to vm370.
http://www.garlic.co/~lynn/2006k.html#email851017
in this post
http://www.garlic.com/~lynn/2006k.html#51 other cp/cms history
also
http://www.garlic.com/~lynn/2006w.html#16 intersection between autolog command 
and cmsback (more history)
http://www.garlic.com/~lynn/2007.html#11 vm/sp1

I included it in my internal "csc/vm" system distribution (for internal
datacenters).
http://www.garlic.com/~lynn/2006w.html#email750102
http://www.garlic.com/~lynn/2006w.html#email750430

Original service virtual machine was RSCS ... and as referenced, the
later RSCS that eventually shipped to customers ... included SPM support
(even if SPM didn't ship to customers).

The author of REXX did a multi-user client/server spacewar game that
used SMSG (users could be on the same machine with the server ... or
because of the RSCS support ... could be anywhere on the internal
network). The client had a 3270 GUI ... however the client/server
protocol was very straight-forward and rather quickly several people did
spacewar bots ... that started to trample all the human players (in part
because they moved much faster). The spacewar server was eventually
modified to increase the power use non-linearly as the interval between
commands/moves dropped ... as a way of trying to provide a level playing
field between humans and bots.

this is increasingly becoming common in the current virtual machine
world ... it has morphed into "virtual appliances" ... highly customized
operating system & applications running in service virtual machine
... very much like RSCS.

trivia ... some years ago, the author of RSCS was working for company
doing some realtime stuff with a major industry realtime system. He
eventually realized that the core part of the system appeared similar to
parts of RSCS ... with major core RSCS 360 assmbler translated into C
language ... but preserving all the same comments.

... and some psuedo device trivia

PROFS email (used extensively internal, among customers, and even
involved in the white house iran contra affair) used a very early
version of an internally developed email client called VMSG. When the
VMSG author tried to offer them an updated version ... they tried to get
him fired (because they had claimed credit for everything in
PROFS). They whole thing quieted down when the VMSG author showed then
every PROFS email in the world carried his initials in a non-displayed,
control field. After than the VMSG author restricted source distribution
to only two other people.

The VMSG author also did PARASITE/STORY ... CMS application and HLLAPI
like language (in the 70s, predating IBM/PC) for automated scripts for
simulating terminals on the same machine or other machines in the
internal network (using psuedo device interface). Past post with 
PARASITE/STORY details:
http://www.garlic.com/~lynn/2001k.html#35
... includes a "story" for automatically logging into RETAIN and
retrieving latest PUT bucket
http://www.garlic.com/~lynn/2001k.html#36

-- 
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

Reply via email to