MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (16 intermediate revisions by the same user not shown) | |||
| Line 40: | Line 40: | ||
<div style="position:relative;top:-60px;"> <a style="position: relative;top: -15px;" title="Home Profile" | <div style="position:relative;top:-60px;"> <a style="position: relative;top: -15px;" title="Home Profile" | ||
href=https://sameboat.network/user><img src=https://meansofproduction.biz/images/corbusierDuHaut.jpg width=100></a> | href=https://sameboat.network/user><img src=https://meansofproduction.biz/images/corbusierDuHaut.jpg width=100></a> | ||
<span style="position: relative; top: -40px;"><a style="color: lime;" title="About the MCP reinvention" | <span style="position: relative; top: -40px;"><a style="color: lime;" title="About the MCP reinvention (and the Anthropic MCP)" | ||
href=/eg/index.php/MCP> <tt style="background-color: black; color: yellow; font-weight: bold;"> minimalist clustering paradigm </tt></a><br><br> | href=/eg/index.php/MCP> <tt style="background-color: black; color: yellow; font-weight: bold;"> minimalist clustering paradigm </tt></a><br><br> | ||
<a title="mcpcms cli or webssh login if not SAR authenticated" | <a title="mcpcms cli or webssh login if not SAR authenticated" | ||
| Line 49: | Line 49: | ||
<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 075-12-11 1<sup>st</sup> stable tl;dr.<sup>†</sup> </li> | <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 BaselineOfBOOTKEE, doorbell migrated to JSX/HSX cells.</li> | <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 | <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 FRED fully automated.</li> | ||
<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 Transparent Ledger (Books IX), DCP agency live at perimeter.</li> | <li>1.2.1 07y-mm-dd Transparent Ledger (Books IX), DCP agency live at perimeter.</li> | ||
<li>2.0.0 07y-mm-dd BaselineOfWFL. </li> | <li>2.0.0 07y-mm-dd BaselineOfWFL. </li> | ||
<li>2.1.0 07y-mm-dd ∫ x 𝔻 ∂ DS, BaselineOfKEE.</li> | <li>2.1.0 07y-mm-dd ∫ x 𝔻 ∂ DS, BaselineOfKEE (sans boot) .</li> | ||
<li>2.2.0 07y-mm-dd 1<sup>st</sup> WFL Workframe. </li> | <li>2.2.0 07y-mm-dd 1<sup>st</sup> WFL Workframe. </li> | ||
<li>3.0.0 07y-mm-dd ∫ VM (CMS, MVS) / DCP ∂ DS mainframe redux.</li> | <li>3.0.0 07y-mm-dd ∫ VM (CMS, MVS) / DCP ∂ DS mainframe redux.</li> | ||
| Line 109: | Line 109: | ||
as the text edit functions likely never will be in <b>mcpcms cande</b>. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence | as the text edit functions likely never will be in <b>mcpcms cande</b>. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence | ||
especially when the OS runs as a Windows service. | especially when the OS runs as a Windows service. | ||
<br><br> In DCP/MCP, an ODT is simply a linux PTY which operates in MCP/MCS context. | |||
</blockquote> | </blockquote> | ||
<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 122: | Line 123: | ||
<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 132: | Line 134: | ||
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 | ||
