MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
← Older editNewer edit →
No edit summary
No edit summary
Line 120: Line 120:
   <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 correspond to the VM thing.
     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.
     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 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 to the connect to invoke <b>cande</b>.
     Aside from adaptations for the MCP machine model, it is just zsh however and within it the following commands are available to establish different shell behaviours in support of the KEE:
     Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates are available to establish different shell behaviours in support of the KEE:
     <ul><li><b>shcl</b> </li><li><b>shhs</b></li><li><b>upsh</b></li></ul>
     <ul><li><b>shcl</b> </li><li><b>shhs</b></li><li><b>upsh</b></li></ul>
     which have the lisp, haskell, and prolog natures, respectively. <b>shcl</b> is the only one which is a full shell, the others are ways to do posix shell things in lang. While in  
     which have the lisp, haskell, and prolog natures, respectively. <b>shcl</b> is the only one which is a full shell run at the ODT command level like <b>cande</b>, the others are ways
  general Lisp and prolog implementations can vary, shcl and upsh require sbcl and swipl, respectively. During early dev, before DCP WFL is available DCP is implemented in these shells plus MCP.
    to do posix shell things in lang and are run as commands in cande/zsh. While in general Lisp and Prolog implementations can vary in the Boot KEE, these lang shells are integral with
    DCP which uses sbcl and swipl, respectively. In the Boot KEE epoch, before DCP WFL is available DCP is implemented in these shells over its machine model.
   <b>mcpcms</b> can be accessed from various connect points such as the launch link above in an AKPERSONs session.
   <b>mcpcms</b> can be accessed from various connect points such as the launch link above in an AKPERSONs session.


  <b>mcpcms</b> is implemented first for MCP nodes and cells which are whole or containerized linux instances. Cloud compute resources are dynamically provisioned using either system
  <b>mcpcms</b> scope may vary from MCP cell/container to a whole DCP/DS context. Cloud compute resources are dynamically provisioned using either system
  inventory or user supplied provisioning credentials with the MCP supported cloud vendors. Later MCP for Mac and Windows will allow cells there and a version supporting Hercules will use  
  inventory or user supplied provisioning credentials with supported cloud vendors. Later MCP for Mac and Windows will allow cells there and a version supporting Hercules will use  
     VM/CMS instead of mcpcms.
     VM/CMS from the last free version.
   </blockquote>
   </blockquote>
<b>DCP WFL</b>
<b>DCP WFL</b>
Retrieved from "https://eg.meansofproduction.biz/eg/index.php/MCP-CMS"