MCP: Difference between revisions

(28 intermediate revisions by the same user not shown)

Line 1:

<blockquote><h1>Master Control Program</h1>

== <div align=right><span style="text-align: right;">Geschichte</span></div> ==

~~A timeline of~~ "MCP" in my life course.

"[[MCP-CMS|DCP/MCP]]" is a working abstraction of real machines and operating systems supporting domain space (DS). It has this antecedent timeline in my life course —

=== 4681-84 Experience ===

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

I was the systems programmer in a [[:en:Burroughs_MCP|Burroughs]] shop, the talk page has footnotes on this.

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

«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. DCP/MCP ~~has these components/layers~~:

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

* ~~The information flow level which is a distributed lisp image running a generic blackboard model of realtime operations~~ control ~~and knowledge base management~~.

* MCS — 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 — conventional OS and process programming level in support of DCP.

* ~~A message~~ flow ~~layer close to machine~~ level ~~using the c++ actor framework and optionally a custom debian kernel~~.~~<br>~~

* DCP — knowledge and high level realtime control flow at the whole enterprise level.

</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 peer~~.</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>

=== 4718-20 ===

=== 4718-21 ===

α/β period:

Line 28:

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:

<ol>

Line 42:

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

Navigation menu

Page actions

Page actions

Personal tools

About

Search

forewords

novel

Tools

@@ Line 1: / Line 1: @@
 <div style="background-color: black; color: white;">
-<br><blockquote>
+<blockquote><h1>Master Control Program</h1>
-{{TOCleft}}
+{{TOCright}}
 == <div align=right><span style="text-align: right;">Geschichte</span></div> ==
-A timeline of "MCP" in my life course.
+"[[MCP-CMS|DCP/MCP]]" is a working abstraction of real machines and operating systems supporting domain space (DS). It has this antecedent timeline in my life course &mdash;
 === 4681-84 Experience ===
-I was the systems programmer in a Burroughs shop, the talk page has footnotes on this.
+I was the systems programmer in a [[:en:Burroughs_MCP|Burroughs]] shop, the talk page has footnotes on this.
 === 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><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. DCP/MCP 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>
-* The information flow 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 message flow 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>
-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 peer.</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>
-=== 4718-20 ===
+=== 4718-21 ===
 &alpha;/&beta; period:
@@ Line 28: / Line 28: @@
 <blockquote style="background-color: gray;color: white;">
 <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>
 <ol>
@@ Line 42: / Line 42: @@
 === 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 ==