MCP: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
<div style="background-color: black; color: white;"> | <div style="background-color: black; color: white;"> | ||
<br>{{ | <br>{{TOCleft}} | ||
<blockquote> | <blockquote> | ||
== <div align=right><span style="text-align: right;">Geschichte</span></div> == | == <div align=right><span style="text-align: right;">Geschichte</span></div> == | ||
| Line 58: | Line 45: | ||
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. 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. | ||
== MCP and WFL == | |||
<blockquote style="background-color: gray;color: white;"> | |||
<blockquote><br> | |||
Prior to milestones 2 and 4 in the 4718-20 story §, <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¹:<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> | |||
¹ <span style="font-size: 10px;">Requiring first class entitlement.</span> | |||
</blockquote></blockquote> | |||
== CP 4721 == | == CP 4721 == | ||
