Difference between revisions of "MCP"

From Cibernética Americana
(29 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>
+
{{TOCleft}}
== MCP and WFL ==
+
== <div align=right><span style="text-align: right;">Geschichte</span></div> ==
 +
A timeline of "[[MCP-CMS|MCP]]" in my life course.
  
<blockquote style="background-color: gray;color: white;">
+
=== 4681-84 Experience ===
<blockquote><br>
 
Prior to milestones 2 and 4 in the current period (4719) &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>
 
  
== <div align=right><span style="text-align: right;">Geschichte</span></div> ==
+
I was the systems programmer in a Burroughs shop, the talk page has footnotes on this.
A timeline of "MCP" in my life course.
 
  
 
=== 4715 Story ===
 
=== 4715 Story ===
In  my domain space concept, it is the designation for the OS superstructure on a node 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, 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.</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>
  
Line 52: Line 42:
  
 
=== Mainframe Redux ===
 
=== 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. 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 (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.
+
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 ==
  

Revision as of 21:40, 15 January 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-20

α/β 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.


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