MCP

Minimalist Clustering Paradigm

Not to be confused with: Model Context Protocol AKA Master Control Program

This page has a music track, mouseover for title.

" DCP / MCP", a control program abstracting real machines, systems and applications programs, in support of a knowledge based name or domain space (DS). It has this antecedent timeline in my life course —

Geschichte

33-35 प्रतीत्यसमुत्पाद

I was the systems programmer in a Burroughs shop, the talk page has footnotes on this.

70s θεωρῐ́ᾱ — πρᾶξις

In my domain space conceit, it is the designation for the OS superstructure supporting the Domain Control Program (DCP).

«MCP» is the operating system abstraction of a cluster, or unit cloud of computers with fast interconnectivity, miniminally 1 gigabit per second. DCP/MCP consists of:

• MCS — uniform message control, operating as an MCP subject.
• MCP — conventional OS and process programming level in support of DCP.
• DCP — knowledge and high level realtime control flow at the whole enterprise level.

in decreasing order of physical, increasing logic scope. DCP, in my scheme, has no analog in conventional operating systems.

MCP and MCS are primarily c++ and lisp, respectively, and realize the OS concept at the real machine level.
DCP/MCP constitutes a haskell, prolog, and lisp based OS.

68-78

φρόνησῐς — ποίησις :

In this period the elements of the DCP are conceived in detail, 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. Prepare for later productization/packaging for non-core DCP deployments.

CP 4721 roughly corresponds to what is produced by 1 and 2 and the AKDOMHST/SVC SKUs to 5. However 5 is a frill. It will certainly suffice to build it for my satisfaction and edification. The prior text (below the list) was written b4 76 AP when CC unblocked the backlog. So 5 is more likely than it was back when.

Mainframe Redux

The first referent of MCP is the OS 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). . See the talk page for more recent experience with the system that inspires my use of the name. A/the Hercules/Herc390 docker container is actually much closer to what I'm doing with DCP so unless the next release of MCP Express (2021) has a lot of improvements, MVS (3.8) may replace MCP. Similarly, as far as first mainframe production nodes are concerned, zOS will likely replace MCP unless there's no affordable path to it, MCP Express is near current and free which the anywhere near current and even some of the old IBM stuff isn't. In any case my concepts are under this name only as a homage, as is common in the industry, and is not based on the large systems architecture.

MCP and WFL²

Like MCP, WFL has a sense in my works that is superficially quite close to the thing in Unisys MCP OS but the effective thing is actually quite different:

• As it was written in the tl:dr story of mcpcms fulfills the job control lang aspect completing the embodiment of MCP as a low level architecture.
• Provide a vehicle for creating DCP jobs in a way opposite to the NL emphasis of DCP and grounds on a zero address arch, for reasons.
  
• Provide a vehicle for comprehensive literate programming of a whole system as demonstrated in the end use systems code presented in the Docs as WFL job streams.

¹ Requiring first class entitlement. ²Redacted, see history.

CP 4721

Continues to use ceremonial, feudal epoch.

See also

• Documentation

Footnotes