MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
15 bytes removed ,  2 January 2022
no edit summary
No edit summary
No edit summary
Line 63: Line 63:
         </span>
         </span>
         </blockquote>
         </blockquote>
     <button type="button" class="collapsible">hide/show</button> <div class="content">
     <button type="button" class="collapsible">hide/show</button>  
  <div class="content">
  <blockquote>
        The namestyle is a homage to
        <a href=https://en.wikipedia.org/wiki/MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a> .
        While initially only linux is supported, more kernel OS support is intended.
  </blockquote>
   <blockquote>
   <blockquote>
     MCP communicates with clients via an MCS, and operators use a command processing one. The end command processor is
     MCP communicates with clients via an MCS, and operators use a command processing one. The end command processor is
Line 76: Line 82:
             hs or pl script, and are not general interactive shells unless that script provides that functionality.</p> </li>
             hs or pl script, and are not general interactive shells unless that script provides that functionality.</p> </li>
         </ul>
         </ul>
        <blockquote>
        <blockquote>
        Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.<br> GHC is the assumed
        Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.<br> GHC is the assumed
        for haskell. Lisp and prolog implementations are variable, and multiple can be combined.
        for haskell. Lisp and prolog implementations are variable, and multiple can be combined.
         </blockquote>
         </blockquote>
         The CMS level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
         The CMS level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
Line 84: Line 90:
         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
         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.
         shell ops with MCP unaware software, CANDE, and WFL jobs.
        </blockquote><blockquote>
    </blockquote>
        The namestyle is a homage to
    <b>mcpcms</b> linux command line invocation uses:  
        <a href=https://en.wikipedia.org/wiki/MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a> .
    <tt> ssh  @  &lt;station-name&gt; where          
        <br><br>
        While initially only linux is supported, more kernel OS support is intended.
        </blockquote>
        <br><b>mcpcms</b> can be directly invoked with ssh  @  &lt;station-name&gt; where  
            <tt>
             <ul>
             <ul>
                 <li style="padding: -2px;"><pre>&lt;station-name&gt;  ::= ipV6Address[port] | ipV4Address[port] | FQDSAgentName </pre></li>
                 <li style="padding: -2px;"><pre>&lt;station-name&gt;  ::= ipV6Address[port] | ipV4Address[port] | FQDSAgentName </pre></li>
Line 97: Line 98:
                 <li><pre> where the port is system provided in the user's DCMS account profile </pre>
                 <li><pre> where the port is system provided in the user's DCMS account profile </pre>
                 </li>
                 </li>
             </ul></tt>  
             </ul>
    </tt>  
     </div>
     </div>
 
         <blockquote style="position: relative;top: -60px;">Roadmap
         <blockquote style="position: relative;top: -60px;">Roadmap
         <ul>
         <ul>

Navigation menu