MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 110: | Line 110: | ||
<b>ODT MCS</b> | <b>ODT MCS</b> | ||
<blockquote> | <blockquote> | ||
MCP-CMS connects via a MCS which is | MCP-CMS connects via a MCS which is usually the CANDE MCS although more generally any MCS with the ODT property can connect for an Operator Display Terminal session with MCP/DCP. | ||
Upon <b>mcpcms</b> connect, like the lang specific subshells in the next §, an additional command <b>cande</b> can be used which will process the MCP-CMS system commands | Upon <b>mcpcms</b> connect, like the lang specific subshells in the next §, an additional command <b>cande</b> can be used which will process the MCP-CMS system commands | ||
analogous to those in the MCP 15 document above. | analogous to those in the MCP 15 document above. | ||
<br><br> | <br><br> | ||
In Burroughs MCP, the CANDE MCS was used ubiquitously. | In Burroughs MCP, the CANDE MCS was used ubiquitously. The ODTs had a full screen editor which just fed lines to CANDE. Commands are implemented per need and some such | ||
as the text edit functions likely never will be in <b>mcpcms cande</b>. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence when the OS runs | as the text edit functions likely never will be in <b>mcpcms cande</b>. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence | ||
especially when the OS runs as a Windows service. | |||
</blockquote> | </blockquote> | ||
<b>mcpcms</b> | <b>mcpcms</b> | ||
<blockquote> | <blockquote> | ||
A modified <b>zsh</b> | The CMS in MCP-CMS is inspired by VM/CMS and the MCP system command level of the CANDE MCS and the ODT session correspond to the VM thing. | ||
Aside from | A modified <b>zsh</b> serves as the analog of Burroughs CANDE as one of several shells invocable in an ODT. | ||
Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke <b>cande</b>. | |||
Aside from adaptations for the MCP machine model, it is just zsh however and within it the following commands are available to establish different shell behaviours in support of the KEE: | |||
<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 | 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 | ||
