MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (4 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 108: | Line 108: | ||
In Burroughs MCP, the CANDE MCS was used ubiquitously. The ODTs had a full screen editor which just fed lines to CANDE. Commands are implemented per need and some such | In Burroughs MCP, the CANDE MCS was used ubiquitously. The ODTs had a full screen editor which just fed lines to CANDE. Commands are implemented per need and some such | ||
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. | <br><br> In DCP/MCP, an ODT is simply a linux PTY which operates in MCP/MCS context. | ||
</blockquote> | </blockquote> | ||
| Line 115: | Line 115: | ||
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. | 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 | Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied the default <b>cande</b> for the parameter 'mcpcms command' to the connect above. Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates can be specified or run as a subshell with <b>cande <subshell></b>. You can also leave the field blank in which case you will be at the ODT level with bash. | ||
<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 123: | 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 | Hercules will ultimately run as an autonomous DCP 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> | *<span style="position:relative;font-size:10px;top:5px;"> Not to be confused with DCMS, the domains content management system.</span> | ||
</blockquote> | </blockquote> | ||
| Line 129: | Line 128: | ||
<blockquote> | <blockquote> | ||
is eponymous upon the <a style="background-color:aliceblue;" href=https://meansofproduction.biz/pub/mcpWFL.pdf>Burroughs WFL</a> with some preserved semantics and aesthetics but | is eponymous upon the <a style="background-color:aliceblue;" href=https://meansofproduction.biz/pub/mcpWFL.pdf>Burroughs WFL</a> with some preserved semantics and aesthetics but | ||
the following essential differences — | |||
<ul> | <ul> | ||
<li>The Job is not the top level construct. The Job or App is the closest construct to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one and expansion beyond | <li>The Job is not the top level construct. The Job or App is the closest construct to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one and expansion beyond | ||
| Line 137: | Line 136: | ||
</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 | ||
a database which the Burroughs architecture delivered seamlessly | a database which the Burroughs architecture delivered seamlessly with little or no WFL to ODTs from a MCS running db stack or programmers using CANDE while WFL was used for operations. DCP WFL has these design goals | ||
<ol> | <ol> | ||
<li>provide an clear/auditable text for DCP operations as a complement to</li> | <li>provide an clear/auditable text for DCP operations as a complement to</li> | ||
