MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (37 intermediate revisions by the same user not shown) | |||
| Line 44: | Line 44: | ||
<a title="mcpcms cli or webssh login if not SAR authenticated" | <a title="mcpcms cli or webssh login if not SAR authenticated" | ||
style="height:50px;background-color:purple;color:white;position: relative; left: 130px; top: -20px;" href=/eg/index.php/MCPCELL><b> launch </b></a> | style="height:50px;background-color:purple;color:white;position: relative; left: 130px; top: -20px;" href=/eg/index.php/MCPCELL><b> launch </b></a> | ||
<span style="position: relative;left:130px;top: -20px;">— an MCP cell ¹ provisioned by the | <span style="position: relative;left:130px;top: -20px;">— an MCP cell ¹ provisioned by the <b>D</b>omain <b>C</b>ontrol <b>P</b>rogram per your current context. ²</span> | ||
</span> | </span> | ||
</div> | </div> | ||
<div style="z-index:150;position:relative;top:-90px;right:60px;"> | <div style="z-index:150;position:relative;top:-90px;right:60px;"> | ||
<img align=right width=300px src="https://meansofproduction.biz/images/b6700nMCP2.png"> | <img align=right width=300px src="https://meansofproduction.biz/images/b6700nMCP2.png"> | ||
<span style="float:right;position:relative;top:270px;left:310px;font-size:10px;">Dual 6700, c. | <span style="float:right;position:relative;top:270px;left:310px;font-size:10px;">Dual 6700, c. '72, binding says MK 0.0, so 2.0.0 vs. 21 in 2023.<br> | ||
<audio style="float:right;height:14px;" title="'Woody'n You' Ahmad Jamal 1958" controls source src="https://meansofproduction.biz/pub/WoodyNYou.mp3" | <audio style="float:right;height:14px;" title="'Woody'n You' Ahmad Jamal 1958" controls source src="https://meansofproduction.biz/pub/WoodyNYou.mp3" | ||
type="audio/mpeg"> This page has an audio but your browser does not support the audio element.</audio><br> | type="audio/mpeg"> This page has an audio but your browser does not support the audio element.</audio><br> | ||
| Line 60: | Line 60: | ||
<tt> | <tt> | ||
<ul> | <ul> | ||
<li>0.9.0 | <li>0.9.0 075-12-11 Freeze 1.x Era Timeline. 1<sup>st</sup> stable tl;dr.<sup>†</sup> </li> | ||
<li>0.9.1 07y-mm-dd | <li>0.9.1 07y-mm-dd BaselineOfBOOTKEE, doorbell migrated to JSX/HSX cells.</li> | ||
<li>1.0.0 07y-mm-dd DCP provisions FRED, C-六/SB, CLFE, and DCMS cells.</li> | <li>1.0.0 07y-mm-dd DCP provisions FRED, C-六/SB, CLFE, and DCMS cells.</li> | ||
<li>1.1.0 07y-mm-dd DSAP appgen baseline | <li>1.1.0 07y-mm-dd <a href=https://redvant.ai-integration.biz>DSAP appgen baseline</a>.</li> | ||
<li>1.1.2 07y-mm-dd FRED fully automated.</li> | |||
<li>1.1.2 07y-mm-dd | |||
<li>1.2.0 07y-mm-dd </html>[[WFL/DCP SPO| BaselineOfDCP]]<html> (DGUI/SPO). </li> | <li>1.2.0 07y-mm-dd </html>[[WFL/DCP SPO| BaselineOfDCP]]<html> (DGUI/SPO). </li> | ||
<li>1.2.1 07y-mm-dd BaselineOfWFL. </li> | <li>1.2.1 07y-mm-dd Transparent Ledger (Books IX), DCP agency live at perimeter.</li> | ||
<li>1. | <li>2.0.0 07y-mm-dd BaselineOfWFL. </li> | ||
<li>2. | <li>2.1.0 07y-mm-dd ∫ x 𝔻 ∂ DS, BaselineOfKEE.</li> | ||
<li> | <li>2.2.0 07y-mm-dd 1<sup>st</sup> WFL Workframe. </li> | ||
<li>3. | <li>3.0.0 07y-mm-dd ∫ VM (CMS, MVS) / DCP ∂ DS mainframe redux.</li> | ||
<li>3.1.0 07y-mm-dd Mature DDD/KEE product.</li> | |||
</ul></tt></blockquote> | </ul></tt></blockquote> | ||
<center> | <center> | ||
MCP | DCP/MCP — an OS platform with an aesthetic in homage to mainframes. | ||
</center> | </center> | ||
<blockquote style="position: relative;"> | <blockquote style="position: relative;"> | ||
<span style="z-index: 100;position: relative;font-size: 10px;">¹ Resource | <span style="z-index: 100;position: relative;font-size: 10px;">¹ Resource quotas are entitlement based.</i><br> | ||
² Use a supported cloud provider by supplying credentials in control blocks in your profile or system inventory.<br> | |||
² | |||
</span> | </span> | ||
</blockquote> | </blockquote> | ||
<blockquote style="position:relative;left:-5px;top:-10px;z-index:200;font-size:8px;">† This page and <a href="https://devops1.sameboat.network/About_DCP">About DCP</a> | <blockquote style="position:relative;left:-5px;top:-10px;z-index:200;font-size:8px;">† For security and flexibility reasons and to the extent feasible, DCP internals aren't divulged, MCP however is source accessible by DevOps users. This page and <a href="https://devops1.sameboat.network/About_DCP">About DCP</a>, which is within the core perimeter, are top level specifying stories.</blockquote> | ||
<button title="show/hide the story details" type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button> | <button title="show/hide the story details" type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button> | ||
<div class="content"> | <div class="content"> | ||
<blockquote style="width: 70%;font-weight: bold;" > | <blockquote style="width: 70%;font-weight: bold;" > | ||
<center>MCPCMS | <center>DCP/MCP presents the MCPCMS shell and the "</html>[[:en:CANDE|CANDE]]<html>" MCS³ to whitelisted <a style="color: lime;" href=https://commons.sameboat.network/stationHistory>stations</a> upon connect.<br>AKPERSONs (see <a href=/eg/index.php?title=AKPERSON>Entitlements</a>) can connect with the link above or in a running <a style="color: lime;" href=https://eg.meansofproduction.biz/eg/index.php/WFL/DCP_SPO>SPO</a> image. | ||
</center></blockquote> | |||
<blockquote style="width: 80%;> | |||
In a tx-authenticated user session, should result in a mcpcms <a href=https://devops1.sameboat.network/roles>session role</a> sensitive cell prompt. In the wild, presents a form with parameters for a manual connect. SPO AX msgs to your MCP ODT or SPO message queue may be configured to go the cell. | |||
In a tx-authenticated user session, should result in a mcpcms <a href=https://devops1.sameboat.network/roles>session role</a> sensitive cell prompt. | |||
<hr width="50%" style="float: left;"> | <hr width="50%" style="float: left;"> | ||
</blockquote> | </blockquote> | ||
| Line 120: | Line 112: | ||
<b>mcpcms</b> | <b>mcpcms</b> | ||
<blockquote> | <blockquote> | ||
The CMS in MCP-CMS is inspired by VM/CMS and the MCP system command level of the CANDE MCS and the ODT session corresponds to the VM CMS command level. | The CMS<sup>*</sup> in MCP-CMS is inspired by VM/CMS and the MCP system command level of the CANDE MCS and the ODT session corresponds to the VM CMS command level. | ||
A modified <b>zsh</b> serves as the analog of Burroughs CANDE as one of several shells invocable in an ODT. | A modified <b>zsh</b> serves as the analog of Burroughs CANDE as one of several shells invocable in an ODT. | ||
Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter 'cell' to the connect to invoke <b>cande</b>. | Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter 'cell' to the connect to invoke <b>cande</b>. | ||
Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates can be specified and are equivalent to <b>cande <subshell></b> | Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates can be specified and are equivalent to <b>cande <subshell></b> by using the <i>mcpcms command</i> form field lang specific values: | ||
<ul><li><b>shcl</b> </li><li><b>hsh</b></li><li><b>upsh</b></li></ul> | <ul><li><b>shcl</b> </li><li><b>hsh</b></li><li><b>upsh</b></li></ul> | ||
for lisp, haskell, and prolog respectively. MCP embeds sbcl, ghc, and swi prolog as libs and code in these shells can interact with those parts of DCP/MCP directly. In the BootKEE epoch, before DCP WFL is generally available, DCP is programmed as jobs via these shells . | for lisp, haskell, and prolog respectively. MCP embeds sbcl, ghc, and swi prolog as libs and code in these shells can interact with those parts of DCP/MCP directly. In the BootKEE epoch, before DCP WFL is generally available, DCP is programmed as jobs via these shells . | ||
| Line 130: | Line 122: | ||
<b>mcpcms</b> scope may vary from a single MCP cell or node to a whole DCP/DS context. Cloud compute resources are dynamically provisioned using either system | <b>mcpcms</b> scope may vary from a single MCP cell or node to a whole DCP/DS context. Cloud compute resources are dynamically provisioned using either system | ||
inventory or user supplied provisioning credentials with supported cloud vendors. Later MCP for Mac and Windows will allow cells there and the last free version of VM/CMS under | inventory or user supplied provisioning credentials with supported cloud vendors. Later MCP for Mac and Windows will allow cells there and the last free version of VM/CMS under | ||
Hercules will ultimately run as an autonomous MCP subject, with other possible mainframe emulations, particularly Unisys should their licensing permit. | Hercules will ultimately run as an autonomous MCP subject, with other possible mainframe emulations, particularly Unisys should their licensing permit.<br> | ||
*<span style="position:relative;font-size:10px;top:5px;"> Not to be confused with DCMS, the domains content management system.</span> | |||
</blockquote> | </blockquote> | ||
<b>DCP WFL</b> | <b>DCP WFL</b> | ||
| Line 140: | Line 133: | ||
batch ops.<li> | batch ops.<li> | ||
<li>In my WFL, Namespace, Database, and then App/Job is the scope hierarchy. Namespace and Database are elements of a domain space and may span multiple MCP instances but Jobs are limited to | <li>In my WFL, Namespace, Database, and then App/Job is the scope hierarchy. Namespace and Database are elements of a domain space and may span multiple MCP instances but Jobs are limited to | ||
a single MCP.</li> | the nodes and cells of a single MCP. Essentially there is a single whole space level job which the DCP implements.</li> | ||
</ul> | </ul> | ||
In Burroughs systems, WFL didn have as high a profile as IBM JCL, the main punch of the overall system, in an industry installation, would be its system of transactions and these ran from | In Burroughs systems, WFL didn have as high a profile as IBM JCL, the main punch of the overall system, in an industry installation, would be its system of transactions and these ran from | ||
