MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
8 bytes added ,  9 December 2024
no edit summary
No edit summary
No edit summary
Line 118: Line 118:
     <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 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.
     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 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.
   <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/local/bin/cande
# 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