Difference between revisions of "MCP-CMS"

From Cibernética Americana
(Created page with "<html> <style> .collapsible { background-color: white; color: black; cursor: pointer; padding: 18px; width: 100px; border: none; text-align: left; outline: non...")
 
 
(202 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
<html>
 
<html>
 +
<div style="background-color: white;color: black;">
 
<style>
 
<style>
 
.collapsible {
 
.collapsible {
 
   background-color: white;
 
   background-color: white;
   color: black;
+
   color: lime;
 
   cursor: pointer;
 
   cursor: pointer;
   padding: 18px;
+
   padding: 40px;
 
   width: 100px;
 
   width: 100px;
   border: none;
+
  height: 25px;
 +
   border: navy;
 
   text-align: left;
 
   text-align: left;
 
   outline: none;
 
   outline: none;
   font-size: 15px;
+
   font-size: 12px;
 +
  font-weight: 600;
 
   position: relative;
 
   position: relative;
 
   top: -50px;
 
   top: -50px;
Line 23: Line 26:
 
   display: none;
 
   display: none;
 
   overflow: hidden;
 
   overflow: hidden;
   background-color: #ffffff;
+
   background-color: white;
 
   position: relative;
 
   position: relative;
 
   top: -50px;
 
   top: -50px;
Line 29: Line 32:
 
</style>
 
</style>
 
<div style="text-align: right;">
 
<div style="text-align: right;">
<h1>mcpcms</h1>
+
<h1 style="color: black;">mcpcms &nbsp; </h1>
<h5 style="position: relative;top: -25px;">master control program <br>CMS MCS shell</h5>
+
<h5 style="position: relative;top: 0px;color: black;">master control program &nbsp; <br>CMS MCS shell &nbsp; </h5>
 
</div>
 
</div>
 
<div style="position: relative;top: -75px;">
 
<div style="position: relative;top: -75px;">
 
  &nbsp; <a  style="position: relative;top: -15px;" title="Home Profile"
 
  &nbsp; <a  style="position: relative;top: -15px;" title="Home Profile"
 
             href=https://sameboat.live/user><img src=https://meansofproduction.biz/images/corbusierDuHaut.jpg width=100></a>
 
             href=https://sameboat.live/user><img src=https://meansofproduction.biz/images/corbusierDuHaut.jpg width=100></a>
           <span style="position: relative; top: -60px;"> &nbsp;<tt> the launch task reports: <span style="color: red;">ABORTED</span> .</tt><br><br>
+
           <span style="position: relative; top: -40px;"> &nbsp;<tt style="background-color: black; color: yellow; font-weight: bold;"> conversational monitor system &nbsp; </tt><br><br>
             <a style="position: relative; left: 130px; top: -10px; " href=https://meansofproduction.biz/mcplaunch.html>refresh</a>
+
             <a style="position: relative; left: 130px; top: -10px;" target=_blank href=https://dcms.ai-integration.biz><b>launch</b></a>
 
           </span>
 
           </span>
 
         <div style="position: relative; top: -50px;">
 
         <div style="position: relative; top: -50px;">
         <blockquote  style="width: 60%;" >
+
         <blockquote  style="width: 60%;font-weight: bold;" >
             If the request status above is not ABORTED or STOPPED, a <a title="About the MCP reinvention"
+
             The launch link leads to a <a title="About the MCP reinvention" href=https://eg.meansofproduction.biz/eg/index.php/MCP>MCP</a>&sup1; shell
            href=https://eg.meansofproduction.biz/index.php/MCP>MCP</a>&sup1; shell session is or shortly will be running on support
+
             provisioned from core domain space or the AWS, linode, or LAN/DIY inventory &sup2; configured in the KEE Dashboard Control Block in your home profile. A MCS is a message control system operating under a MCP. ABORTED, ACTIVE, INUSE, COMPLETEDOK, or STOPPED are the possible job completion codes &sup3; for the launch attempt from the
             provisioned from core domain space or DIY inventory. These and the remaining states ACTIVE, INUSE, or COMPLETEDOK, implicitly reference the
+
             DS <a href=https://commons.sameboat.live/stationHistory>station</a> at which you're currently authenticated.
             DS <a href=https://sameboat.live/stationHistory>station</a> at which you're currently a DS agent.
 
  
            <p>It may be accessed at  &lt;station-name&gt; where </p><tt>
+
<blockquote style="width: 80%;font-weight: bold;">
            <ul>
+
          Get ports for it in a device control block in your profile DS Blocks which you can manually operate with ssh as usual (e.g using ssh-copy-id). <br> <br>
                <li style="padding: -2px;"><pre>&lt;station-name&gt;  ::= ipV6Address | ipV4Address | FQDSuserName </pre></li>
+
          Launch states ABORTED, COMPLETED, OR STOPPED, imply receipt of diagnostic info by your currently selected means of notification (home icon above left).
                <li style="padding: 0px;"><pre>&lt;domain&gt;        ::= ai-integration | ai-integration.biz | &lt;yourTLD&gt;</pre> </li>
+
          ABORTED is the immediate result if you are not authenticated.<br><br>
                <li><pre>FQDSuserName    ::= your DS agent nick FQDN, e.g. 'janedoe.&lt;domainName&gt;[.dom]'.</pre></li>
+
           A running <a href=https://ns.meansofproduction.biz/SPO/run>SPO</a> counts against account launch limits.<br>
                <li><pre>&lt;yourTLD&gt;      ::= your alt-root TLD or its public linking zone.</pre></li>
 
            </ul></tt></pre> Launch states ABORTED, COMPLETED, OR STOPPED, imply receipt of diagnostic info by the currently selected means of notification in your home profile (icon).
 
            ABORTED is the immediate result if you are not authenticated.
 
        </blockquote>
 
        <blockquote style="width: 60%;">
 
          Enable ssh access from your commons profile which assigns the port. The suffixless host name and IPV6 forms
 
          require DS routing. Sessions launched by ip do not persist and are strictly contained within the agent's session.<br><br>
 
           A running <a href=https://eg.meansofproduction.biz/index.php/WFL/DCP_SPO>SPO</a> counts as a mcpcms launch against account limits.<br>
 
 
         <hr width="50%" style="float: left;">
 
         <hr width="50%" style="float: left;">
         </blockquote><br>
+
         </blockquote><br></blockquote>       
 
         <blockquote style="position: relative;top: -30px;">
 
         <blockquote style="position: relative;top: -30px;">
         <span style="position: relative;top: -10px;font-size: 10px;">&sup1;<i>NB: 'Unisys CANDE', 'Unisys MCP', and 'Unisys WFL' are distinct from the unaffixed names and will be
+
         <span style="position: relative;top: -8px;font-size: 10px;">&sup1;<i>Core space resources are only dynamically allocated for AKPERSONs.</i><br>
        supported in a free feature of later DCP versions.</i></span>
+
        &sup2; AWS, Linode, or your Gb LAN. MCP nodes must have sub-millisecond ping. Set cloud vendor credentials in your commons dashboard or run the MCP leader in your LAN.
 +
        </span>
 
         </blockquote>
 
         </blockquote>
     <button type="button" class="collapsible">more ...</button>
+
     <button type="button" class="collapsible"><div id="tldrDet">details</div></button>  
    <div class="content">
+
<div class="content">
        <blockquote>
+
  <blockquote>
        MCP shells may have any one of the following natures:
+
<span style="position: relative;top:-15px;">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>
 +
        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>
 +
        Operators use a CANDE MCS for MCP command line ops which can use:
 
         <ul>
 
         <ul>
         <li>shcl, common lisp nature</li>
+
         <li><p style="width: 60%;">mcpcms, the default, a custom zsh.</p> </li>
        <li>shelly, haskell nature</li>
+
        and any of <br><br>
         <li>upsh, prolog nature</li>
+
         <li><b>shcl</b> (common lisp nature)</li>
        <br>or<br>
+
         <li><b>shhs</b> (HsShellScript, haskell nature)</li>
         <li><p style="width: 60%;">CMS, the default nature for mcpcms, which is bash modified for DCP/MCP/WFL.<br><br> Only mcpcms can be set in /etc/shells, the others execute as
+
        <li><b>upsh</b> (prolog nature)</li>
            commands in a mcp shell, and only shcl gives a live default command line like fish under standard bash. The other two require a user supplied
 
            hs or pl script, and are not general interactive shells unless that script provides that functionality.</p> </li>
 
 
         </ul>
 
         </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.
        Shells have either MCP (single linux host) or DCP (whole cluster) scope, ip shells are limited to the former.<br> GHC and SWI are assumed
 
        for haskell and prolog, but lisp can be any combination of Allegro, CCL, (user supplied) or sbcl (the default).
 
        </blockquote>
 
        The CMS level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
 
        Although adapted for MCP, I try to keep them close to the standard versions, as generic lang specific outer shells.<br>
 
        My preferred <a href=https://en.wikipedia.org/wiki/Domain_engineering>DDD</a> uses the three HOLs&sup2; listed but the bash level is appropriate for
 
        shell ops with MCP unaware software, CANDE, and WFL jobs.
 
        </blockquote>
 
  <blockquote>
 
        SYSTEM/CMS is the prototypical CL/MCS. It is meant to be a generalization of
 
        <a href=https://en.wikipedia.org/wiki/CANDE>CANDE</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a> .
 
        <br><br>
 
        While initially the linux bash capable terminal is supported, ODT and 3270 support are intended.
 
 
         </blockquote>
 
         </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&sup2; 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  &lt;req-spec&gt;
 +
 +
                where           
 +
         
 +
                &lt;req-spec&gt;    ::= ipV6Address:port | ipV4Address:port | FQDSAgentName
 +
                FQDSAgentName ::= &lt;agentId&gt;@&lt;domain&gt;[:&lt;port&gt;]
 +
 +
                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>
 
     </div>
         <blockquote style="position: relative;top: -60px;"> Version Roadmap
+
 
 +
         <blockquote style="position: relative;top: -60px;">Roadmap
 
         <ul>
 
         <ul>
         <li>1.0 SSI PoC, proto CL/MCS and CMS MCS, ansible provisioning from C-Liu backend.</li>
+
         <li>1.0.0 PoC: working DCP  provisioning of composed MCP images and mcpcms hosts via the DCMS&gt; C-六 <a href=https://sameboat.live/DCMS>backend</a>.</li>
         <li>1.1 First level maturity of  lisp MCP codeset. </li>
+
         <li>1.1.0 First working SPO and WFL development server. </li>
         <li>1.2 AI legacy systems salvage and integration complete and devops ready in the shell service.</li>
+
         <li>1.2.0 Consolidation and productization release.</li>
         <li>2.0 Mature DDD/KEE product.</li>
+
         <li>2.0.0 Mature DDD/KEE product.</li>
 
         </ul>
 
         </ul>
 
<hr>
 
<hr>
 
&sup2; <span style="font-size: 10px;">High Order Language</span>
 
&sup2; <span style="font-size: 10px;">High Order Language</span>
 +
&sup3; <span style="font-size: 10px;">The states COMPLETED, COMPILEDOK and SCHEDULED are invalid for the launch WFL job, but its task steps may have COMPLETED codes, usable in other interfaces.</span>
 
         </blockquote>
 
         </blockquote>
 
</div></div>
 
</div></div>
  
 
<script>
 
<script>
var coll = document.getElementsByClassName("collapsible");
+
var coll = document.getElementsByClassName("collapsible");
 +
var bText = document.getElementById("tldrDet");
 
var i;
 
var i;
  
Line 115: Line 124:
 
     if (content.style.display === "block") {
 
     if (content.style.display === "block") {
 
       content.style.display = "none";
 
       content.style.display = "none";
 +
      bText.innerHTML = "details";
 
     } else {
 
     } else {
 
       content.style.display = "block";
 
       content.style.display = "block";
 +
      bText.innerHTML = "tl;dr";
 
     }
 
     }
 
   });
 
   });
 
}
 
}
 
</script>
 
</script>
 +
</div>
 
</html>
 
</html>

Latest revision as of 06:55, 1 April 2022

mcpcms  

master control program  
CMS MCS shell  
    conversational monitor system  

launch

The launch link leads to a MCP¹ shell provisioned from core domain space or the AWS, linode, or LAN/DIY inventory ² configured in the KEE Dashboard Control Block in your home profile. A MCS is a message control system operating under a MCP. ABORTED, ACTIVE, INUSE, COMPLETEDOK, or STOPPED are the possible job completion codes ³ for the launch attempt from the DS station at which you're currently authenticated.

Get ports for it in a device control block in your profile DS Blocks which you can manually operate with ssh as usual (e.g using ssh-copy-id).

Launch states ABORTED, COMPLETED, OR STOPPED, imply receipt of diagnostic info by your currently selected means of notification (home icon above left). ABORTED is the immediate result if you are not authenticated.

A running SPO counts against account launch limits.



¹Core space resources are only dynamically allocated for AKPERSONs.
² AWS, Linode, or your Gb LAN. MCP nodes must have sub-millisecond ping. Set cloud vendor credentials in your commons dashboard or run the MCP leader in your LAN.

The namestyle is a homage to MCP and VM/CMS.
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.
Operators use a CANDE MCS for MCP command line ops which can use:

  • mcpcms, the default, a custom zsh.

  • and any of

  • shcl (common lisp nature)
  • shhs (HsShellScript, haskell nature)
  • upsh (prolog nature)

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.

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.

The mcpcms level is always present, the others are outer shells adapted for the domain space knowledge engineering context.
The KEE uses the three HOLs² listed but the mcpcms level is appropriate for regular command line ops in MCP.
Although diverged for DS, an effort will be made to track changes in still vital original lang specific shells.

Assuming the target is configured and ready, invoke mcpcms with:

 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.                          
     

Semantics

The port cannot be 22. The semantics are different depending on whether addr:port or agentId forms are used.

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.
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.

Roadmap

  • 1.0.0 PoC: working DCP provisioning of composed MCP images and mcpcms hosts via the DCMS> C-六 backend.
  • 1.1.0 First working SPO and WFL development server.
  • 1.2.0 Consolidation and productization release.
  • 2.0.0 Mature DDD/KEE product.

² High Order Language ³ The states COMPLETED, COMPILEDOK and SCHEDULED are invalid for the launch WFL job, but its task steps may have COMPLETED codes, usable in other interfaces.