MCP: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
(44 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{TOCright}}
<div style="background-color: black; color: white;">
<div style="background-color: cyan; color: black;">
<br>__NOTOC__
<blockquote>
<blockquote>
A timeline of "MCP"
A timeline of "MCP" in my life course.


== My Early Career ==
== MCP 4 Era ==
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 thenn a Burroughs shop as my second job out of college. <ref>[https://meansofproduction.biz/aii/node12.html Go There]</ref>
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. <ref>[https://meansofproduction.biz/aii/node12.html Go There]</ref>


The first referent of the acronym is the [[Burroughs_MCP_Architecture|<span style="color: pink;">operating system</span>]] of the same name.  
== 4715 Story ==
In a my domain space concept, it is the designation for nodes of a 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. The MCPs operate as the nodes of the larger OS construct, the DCP. MCP itself has these components/layers:
<blockquote>
* The top level which is a 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 <span class="plainlinks" style="background-color: white;">[https://meansofproduction.biz/pub/mcpWFL.pdf WFL]</span> to the DCP context.
* A base layer close to machine level using the c++ actor framework and optionally a custom debian kernel.<br>
</blockquote>
BTW, about this time Unisys made MCP available to run from Windows 7 or 10 64 bit as "MCP Express" although I didn learn of this until 2019Q3 and didn bring it up till some time later.</blockquote><br></blockquote>


In a modern context, it is the encompassing operational context for the development of DCP nodes.
== 4716-18 ==
 
&alpha;/&beta; period:


== 4715 Story ==
<blockquote style="background-color: gray;color: white;">
<blockquote style="background-color: gray;color: white;">
&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 a larger OS construct, the DCP or domain control program. MCP itself has these components/layers:
<blockquote><br>
 
In this period the elements of the DCP are prototyped, marshalled, deployed then productized:
* The top level which is a lisp image running a generic blackboard model of realtime operatons control.
<blockquote>
* 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 a generalization of the algol wiffle.
<ol>
* A modified linux kernel to support the above.
<li>Get working build of all packages in same form they will ultimately be used in the product.</li>
<li>Get working build of newly created elements such as the DGUI/SPO and WFL.</li>
<li>Apply the above to the proto domains.</li>
<li>Workout in service of the proto domains.</li>
<li>Do productization/packaging for mass deployment</li>
</ol>
<br>
CP 4721 roughly corresponds to what is produced by 1 and 2 and the AKDOMHST/SVC SKUs to 5.
</blockquote>
</blockquote>
</blockquote><br></blockquote>


== 4716/17 ==
Sometime between milestone 2 and 4, a MCP shell/remote SPO service will be made available to authenticated users.
 
Precursors marshalled, extant, then in prodtest .


== 4721 ==
== CP 4721 ==


Intentionally blank for formatting purpose.
Blank for formatting purpose.


== See also ==
== See also ==


* Current docs
* [[Documentation]]


== References ==
== Footnote ==
<div style="background-color: white;">
<references/>
<references/>
</div>
<br>
</blockquote>
</blockquote>
</div>
</div>

Revision as of 13:25, 19 November 2019


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

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

BTW, about this time Unisys made MCP available to run from Windows 7 or 10 64 bit as "MCP Express" although I didn learn of this until 2019Q3 and didn bring it up till some time later.


4716-18

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

Footnote