MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 105: | Line 105: | ||
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> | ||
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 | 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 | 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.<br> | especially when the OS runs as a Windows service.<br> | ||
<br><br> In DCP/MCP, an ODT is simply a linux PTY which operates in MCP/MCS context. | |||
</blockquote> | </blockquote> | ||
<b>mcpcms</b> | <b>mcpcms</b> | ||
