|
|
| Line 59: |
Line 59: |
| <button type="button" class="collapsible"><div id="tldrDet">details</div></button> | | <button type="button" class="collapsible"><div id="tldrDet">details</div></button> |
| <div class="content"> | | <div class="content"> |
| | <blockquote> |
| | <b>mcpcms</b> |
| <blockquote> | | <blockquote> |
| <span style="position: relative;top:-5px;">The namestyle is a homage to <a href=https://en.wikipedia.org/wiki/Burroughs_MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a>.</span><br>
| | is derived from <b>zsh</b> and is the shell variant which is set in /etc/shells for MCP. |
| While initially only linux is supported, ultimately heterogeneous and in particular emulated mainframe kernel OS support is intended. A command and edit (CANDE) MCS wraps the ssh protocol.<br>
| | </blockquote> |
| Operators use a CANDE MCS for MCP command line ops which can use:
| | <b>WFL</b> |
| <ul>
| | <blockquote> |
| <li><p style="width: 60%;">mcpcms, the default, a custom zsh.</p> </li>
| | is derived from <b>a68g</b>, runs as shebang scripts under <b>mcpcms</b>, and is based on selected elements of <a href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> reimagined for our systems concept. It |
| and any of <br><br>
| | serves as the central point of a bottom up integration of MCP/DCP elements. |
| <li><b>shcl</b> (common lisp nature)</li>
| | </blockquote> |
| <li><b>shhs</b> (HsShellScript, haskell nature)</li>
| | <span style="font-size:12px;">The namestyles are a homage to <a href=https://en.wikipedia.org/wiki/Burroughs_MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a> main |
| <li><b>upsh</b> (prolog nature)</li>
| | frame operating systems which are both still in use and Unisys WFL (Work Flow Language).</span> |
| </ul>
| | </blockquote> |
| <blockquote> Only mcpcms need be set in /etc/shells, the others are available as the listed commands in a mcpcms session. The sources for the versions forked for MCP and how they operate there as opposed to their original authors intents are in my github repos. CANDE may be local or MCP or DCP depending on the operators context.<br><br> GHC is the haskell implementation. Lisp and prolog implementations are variable, and multiple can be combined but shcl and upsh themselves use sbcl and swipl, respectively.
| | </div> |
| </blockquote>
| |
| The mcpcms level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
| |
| The KEE uses the three HOLs² listed but the mcpcms level is appropriate for regular command line ops in MCP.<br>
| |
| Although diverged for DS, an effort will be made to track changes in still vital original lang specific shells.
| |
| </blockquote>
| |
| <blockquote>
| |
| Assuming the target is configured and ready, invoke <b>mcpcms</b> with:
| |
| <pre><tt> mcpcms <req-spec>
| |
| | |
| where
| |
|
| |
| <req-spec> ::= ipV6Address:port | ipV4Address:port | FQDSAgentName
| |
| FQDSAgentName ::= <agentId>@<domain>[:<port>]
| |
| | |
| and the port is displayed in a DS control block in the user's DCMS account profile or provided dynamically by automation in an authenticated session.
| |
| </tt></pre>
| |
| Semantics
| |
| <blockquote>
| |
| The port cannot be 22. The semantics are different depending on whether addr:port or agentId forms are used.<br><br>
| |
|
| |
| The bare address:port forms presume the user's client OS account name is a valid agentId and DCMS username. In this case the address is a pre allocated MCP element and ssh could be used instead.<br>
| |
| | |
| The agentId form assigns existing or allocates a new MCP element from context implicit in the users account. In this case the CANDE MCS is required.
| |
| </blockquote>
| |
| </blockquote>
| |
| </div>
| |
|
| |
|
| <blockquote style="position: relative;top: -50px;">Roadmap | | <blockquote style="position: relative;top: -50px;">Roadmap |
