From Cibernética Americana

A timeline of "MCP" in my life course.

MCP 4 Era

The first referent of the acronym is the operating system of the same name, which was at release 19 in 2019. I was the systems programmer at Daytona Beach Community, now Daytona State College which was then a Burroughs shop as my second multi-year job out of college ('83-'85). [1]

See the talk page for more recent experience with the system which (no more than) inspired the name. The IBM docker container is actually much closer to what I'm doing with DCP so unless the next release of MCP Express has a lot of improvements, MVS (as modern zOS) may replace MCP as far as first mainframe nodes are concerned unless there's no affordable path to support their docker images.

4715 Story

In a my domain space concept, it is the designation for nodes of a Domain Control Program (DCP).

«MCP» is the operating system abstraction on a single node of a cluster, or cloud of computers with fast interconnectivity, miniminally 1 gigabit per second. The MCPs operate as the nodes of the larger OS construct, the DCP. MCP itself has these components/layers:

  • The top level which is a distributed lisp image running a generic blackboard model of realtime operations control and knowledge base management.
  • The workflow level which is implemented by the Work Flow Language, another Burroughs inspiration, reimagined as a context for literate programming and revival of the job control concept based on an adaptation of WFL to the DCP context.
  • A base layer close to machine level using the c++ actor framework and optionally a custom debian kernel.

So DCP, in my scheme, is actually the thing analogous to Unisys MCP, comparing whole OS constructs to each other. OTOH, DCP is principally a domain knowledge engineering environement, its OS aspects are fully encapsulated in the network of MCPs abstraction. Also, per the discussion, MVS is likely to be the first actual mainframe OS based MCP.


α/β period:

In this period the elements of the DCP are prototyped, marshalled, deployed then productized:

  1. Get working build of all packages in same form they will ultimately be used in the product.
  2. Get working build of newly created elements such as the DGUI/SPO and WFL.
  3. Apply the above to the proto domains.
  4. Workout in service of the proto domains.
  5. Do productization/packaging for mass deployment

CP 4721 roughly corresponds to what is produced by 1 and 2 and the AKDOMHST/SVC SKUs to 5.

Sometime between milestone 2 and 4, a MCP shell/remote SPO service will be made available to authenticated users.

CP 4721

Blank for formatting purpose.

See also