MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
41 bytes removed ,  12 October 2024
no edit summary
No edit summary
No edit summary
Line 117: Line 117:
     A modified <b>zsh</b> for MCP serves as analog of the CMS from VM/CMS. Upon successful connect, the launch link above results in a terminal session with this shell in the browser.
     A modified <b>zsh</b> for MCP serves as analog of the CMS from VM/CMS. Upon successful connect, the launch link above results in a terminal session with this shell in the browser.
     Aside from the modification for the MCP machine model, it is otherwise just zsh however the following (mode) commands are available to establish different shell behaviour in support of the KEE:
     Aside from the modification for the MCP machine model, it is otherwise just zsh however the following (mode) commands are available to establish different shell behaviour in support of the KEE:
     <ul><li><b>shcl</b> (common lisp nature)</li><li><b>shhs</b> (HsShellScript, haskell nature)</li><li><b>upsh</b> (prolog nature)</li></ul> Lisp and prolog implementations are variable, and multiple can be combined but shcl and upsh themselves use sbcl and swipl, respectively.
     <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. Lisp and prolog implementations can vary but shcl and upsh require sbcl and swipl, respectively.
   <b>mcpcms</b> can be accessed with ssh using the following script. Using the FQDSAgentName syntax is equivalent to what the launch link does in an AKPERSONs session.<pre><tt>#!/usr/bin/bash
   <b>mcpcms</b> can be accessed with ssh using the following script. Using the FQDSAgentName syntax is equivalent to what the launch link does in an AKPERSONs session.<pre><tt>#!/usr/bin/bash
# save as &lt;fileName&gt; and invoke with &lt;fileName&gt;  &lt;connect-spec&gt; where             
# save as &lt;fileName&gt; and invoke with &lt;fileName&gt;  &lt;connect-spec&gt; where             

Navigation menu