Difference between revisions of "MCP"

From Cibernética Americana
m (Protected "MCP" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
 
(89 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<div style="background-color: black; color: white;">
 
<div style="background-color: black; color: white;">
<br>{{TOCright}}
+
<br><blockquote>
<blockquote>
+
{{TOCright}}
A timeline of "MCP" in my life course.
+
== <div align=right><span style="text-align: right;">Geschichte</span></div> ==
 +
A timeline of "[[MCP-CMS|MCP]]" in my life course.
  
== MCP 4 Era ==
+
=== 4681-84 Experience ===
The first referent of the acronym is the [[Burroughs_MCP_Architecture|<span style="color: pink;">operating system</span>]] 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). <font color=lime><ref>[https://meansofproduction.biz/aii/node12.html Go There]</ref></font>
+
I was the systems programmer in a [[:en:Burroughs_MCP|Burroughs]] shop, the talk page has footnotes on this.
  
== 4715 Story ==
+
=== 4715 Story ===
In a my domain space concept, it is the designation for nodes of a Domain Control Program (DCP).
+
In my domain space concept, it is the designation for the OS superstructure coordinate with the Domain Control Program (DCP).
 
<blockquote style="background-color: gray;color: white;">
 
<blockquote style="background-color: gray;color: white;">
 
<blockquote><br>
 
<blockquote><br>
&laquo;MCP&raquo; 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:
+
&laquo;MCP&raquo; 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:
 
<blockquote>
 
<blockquote>
* The top level which is a distributed lisp image running a generic blackboard model of realtime operations control and knowledge base management.
+
* MCS &mdash; uniform message control, operating as an MCP subject.
* 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 <span class="plainlinks" style="background-color: white;">[https://meansofproduction.biz/pub/mcpWFL.pdf WFL]</span> to the DCP context.
+
* MCP &mdash; conventional OS and process programming level in support of DCP.
* A base layer close to machine level using the c++ actor framework and optionally a custom debian kernel.<br>
+
* DCP &mdash; knowledge and high level realtime control flow at the whole enterprise level.
 
</blockquote>
 
</blockquote>
So DCP is actually the thing analogous to Unisys MCP, comparing whole OS constructs to each other.</blockquote><br>
+
in decreasing order of physical, increasing logic scope. DCP, in my scheme, has no analog in conventional operating systems. MCP and MCS are primarily lisp and constitute a high level lisp OS.</blockquote><br>
 
</blockquote>
 
</blockquote>
  
== Elliott AI &trade; ==
+
=== 4718-21 ===
 
 
<blockquote style="background-color: gray;color: white;">
 
<blockquote><br>
 
After dropping their CMOS line and completing the transition to commodity Intel, Unisys made MCP  available free for personal use to run from Windows 64 bit as "MCP Express". I don't recall learning of this before 2019Q3 and didn bring it up till end of Q1 '20 (version 5). It has to be replaced by a new download every July 31st.
 
 
 
Thus, after 35 years, I now have hands on a current MCP (18) system and that opens a role for the Unisys MCP in the DCP, where "Unisys MCP" will be used wherever the distinction needs to be made clear. Usages like ODT, DMS II or MARC unambiguously refer to the Unisys product line as we never intended taking more than inspiration from it.<span style="background-color: black; color: lime;"><ref><font size=1 color=black> "CANDE", "WFL", and "MCP" are the actual overloads, "SPO" isn't really used in the modern Unisys culture, it's been lost from the mainframe days, so the smalltalk thing I'm doing doesn't map to anything specific, although functionally MARC and the ODT would be the analogs. The original SPO was just an ODT with supervisor permissions. Whose thing, mine or Unisys that is referred to by the overloaded terms will be clear in context (within Unisys MCP or not) and use the same "Unisys" modifier where needed.</font></ref></span>Much of the base mainframe stuff is available in the Windows based product and updated for the current epoch, though obviously it's a limited version of the actual priced product that runs on their hardware.
 
 
 
The most natural form of integration of Unisys MCP is to allow it as an alternate to linux node in a DCP. A design principle to inform and guide such an effort is that Unisys MCP shall only have integration with the DCP cognitive architecture and not the physical one, each Unisys MCP in a DCP will be an island (Unisys internetworking notwithstanding) unlike the linux nodes which form a single system image. Thus, the integration can be in software built with the standard Unisys dev kit targeting the DCP cognitive architecture.<span style="background-color: black; color: lime;"><ref><font size=1  color=black> Seems like a good enough place to say I have no interest in the Unisys Univac stuff. There appear to be only a couple hundred MCP sites still running and a good number of them are software houses serving the remainder, a mix of banks, govt units, etc.</font></ref></span>
 
 
 
Thus, "Elliot AI", where Elliot suggests the Algol, Organick, or perhaps the ET display :). Obviously, the proviso in the README for domain space about intentions versus production realizations applies to this a fortiori. However it is a serious intention and due to the small size of any possible market, I will make anything that does reach the stage of distribution available at no cost (other than standard first class capitation and the passed thru cost of any used hosting resources).<span style="background-color: black; color: lime;"><ref><font size=1 color=black>When I first encountered MCP and its arch and product lines they were already decades old and I would remark that if Burroughs had followed the advancement of computer science over that time they would have various features they lacked as common business oriented systems, such as OO, AI, etc. Elliot AI is a possible realization of that, albeit now with 3X times the elapsed time since the inaugural MCP. Current MCP bears mark 59.* which I take it roughly marks years from the first mark release.</font></ref></span>
 
<br><br>
 
</blockquote>
 
</blockquote>
 
 
 
== 4718-20 ==
 
  
 
&alpha;/&beta; period:
 
&alpha;/&beta; period:
Line 43: Line 28:
 
<blockquote style="background-color: gray;color: white;">
 
<blockquote style="background-color: gray;color: white;">
 
<blockquote><br>
 
<blockquote><br>
In this period the elements of the DCP are prototyped, marshalled, deployed then productized:
+
In this period the elements of the DCP are conceived in detail, prototyped, marshalled, deployed then productized:
 
<blockquote>
 
<blockquote>
 
<ol>
 
<ol>
Line 56: Line 41:
 
</blockquote><br></blockquote>
 
</blockquote><br></blockquote>
  
Sometime between milestone 2 and 4, a MCP shell/remote SPO service <span class="plainlinks">[https://meansofproduction.biz/mcplaunch.html <span style="color: cyan;">will be</span>]</span> made available to authenticated users.
+
=== Mainframe Redux ===
 +
The first referent of '''MCP''' is the [[Burroughs_MCP_Architecture|<span style="color: pink;">OS</span>]] 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). <font color=lime><ref>[https://meansofproduction.biz/aii/node12.html Go There]</ref></font>. 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 ==
 +
 +
<blockquote style="background-color: gray;color: white;">
 +
<blockquote><br>
 +
Prior to milestones 2 and 4 in the 4718-20 story &sect;, <span class="plainlinks">[https://meansofproduction.biz/mcplaunch.html <span style="color: cyan;">a MCP shell/remote SPO service </span>]</span> presenting a modified bash with the following features will be deployed&sup1;:<br>
 +
* modified regular LSB bash, default debian 10 or ubuntu 18
 +
* integrated with the C-六 python ADT (ansible, docker, twisted) service
 +
* carries basic model and implementation of the single system image on its swarm
 +
* built-in inventory and playbooks for provisioning on AWS and linode
 +
Like MCP, WFL has a sense in my works that is quite close to the thing in Unisys MCP OS but the overall thing is quite different. My WFL concept is more scoped to literate programming and DDD support  but one aspect <i><b>is</b></i> job control mapped to lang, centrally a dialect of Algol. 1st service just gets a nascent platform up and is essentially the low level bootstrap for the OS concept. Details in the bookshelf docs.
 +
<br><br>
 +
&sup1; <span style="font-size: 10px;">Requiring first class entitlement.</span>
 +
</blockquote></blockquote>
 
== CP 4721 ==
 
== CP 4721 ==
  
Line 65: Line 64:
  
 
* [[Documentation]]
 
* [[Documentation]]
* [[:en:Elliott ALGOL]]
 
* [[:en:Elliot Organick]]
 
  
 
== Footnotes ==
 
== Footnotes ==

Latest revision as of 12:01, 21 March 2022


Geschichte

A timeline of "MCP" in my life course.

4681-84 Experience

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

4715 Story

In my domain space concept, it is the designation for the OS superstructure coordinate with 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 lisp and constitute a high level lisp OS.


4718-21

α/β period:


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


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). [1]. 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


Prior to milestones 2 and 4 in the 4718-20 story §, a MCP shell/remote SPO service presenting a modified bash with the following features will be deployed¹:

  • modified regular LSB bash, default debian 10 or ubuntu 18
  • integrated with the C-六 python ADT (ansible, docker, twisted) service
  • carries basic model and implementation of the single system image on its swarm
  • built-in inventory and playbooks for provisioning on AWS and linode

Like MCP, WFL has a sense in my works that is quite close to the thing in Unisys MCP OS but the overall thing is quite different. My WFL concept is more scoped to literate programming and DDD support but one aspect is job control mapped to lang, centrally a dialect of Algol. 1st service just gets a nascent platform up and is essentially the low level bootstrap for the OS concept. Details in the bookshelf docs.

¹ Requiring first class entitlement.

CP 4721

Blank for formatting purpose.

See also

Footnotes