MCP-CMS: Difference between revisions

     <button type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button>  

  <div class="content">

  <b>CANDE MCS</b>   

   <b>cande</b> like the lang specific subshells in the next &sect;, which invokes the MCS command processor at a <b>mcpcms</b> prompt.  

   The command processor is also available as a pane in the WebKEE legacy SPA and the CANDE MCS is the default ubiquitous DCP/MCP MCS. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence when the OS runs under Windows.

     is derived from  <b>zsh</b> for MCP and the shell variant set for it in /etc/shells. In an authenticated session, the launch link normally results in a WebSSH session with this shell. Aside from the modification for the MCP machine model, it is otherwise just zsh however the following (mode) commands are available to establish different shell behaviour in support of the KEE:

   <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

# save as &lt;fileName&gt; and invoke with &lt;fileName&gt;  &lt;connect-spec&gt; where             

     <tr><td>UNIT</td><td align=center><a style="background-color:aliceblue;"  href=https://jmvdveer.home.xs4all.nl/en.algol-68-genie.html><b>A68</b></a></td><td align=right>Yes</td></tr>

     </table>

   Intrinsic means the lang is native to MCP/WFL and doesn't require COMPILE or BIND to produce an executable job title.<br>

   MAKE binds job titles to files executable by the <b>cande</b> MCS with the START or SCHEDULE commands.

   <div style="width:60%;text-align:justify;">

   WFL(JCL) job streams are translated from source text to A60/C, A68, and MINT then  compiled and linked to the Barton machine, or interpreted by genie or MINT, respectively. WFL(JCL) is A60 translated to C, compiled and bound, interspersed with the JCL statements interpreted by the B machine. Non-intrinsic code forms unified code trees in the DGUI and is maintained there under the control of the governing build  statements and commands. Thus, a general WFL job orchestrates an application divided into system part executed by the B machine and application parts executed in the OS image extended from the base OS by the B machine.<br><br>'WFL' used without the JCL qualifier or 'WFL workframe' refers to general source processing framework of the high level part of the DCP. Build statements and commands refers to COMPILE/BIND/MAKE.

   <span style="position:relative;top:-30px;font-size:12px;">The namestyles are 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> mainframe OSes, both still in use and Unisys WFL (<a style="background-color:aliceblue;"  href=https://public.support.unisys.com/aseries/docs/clearpath-mcp-18.0/86001047-516/index.html>Work Flow Language</a>). The machine thus defined will be ported to other cloud vendors (Google, Azure, et. al.) after workout in Akamai (linode) and AWS.</span>

<div  style="float:right;text-align:center;font-size:12px;position:relative;left:-150px;top:-230px;width:400px;font-family:Papyrus;" ><a href=https://en.wikipedia.org/wiki/Abydos_King_List><img align=right width=400px src=https://meansofproduction.biz/images/kings_list.012.jpg></a><br>The Abydos Kings List &nbsp; c. -400 &nbsp; to &nbsp; 1400 &nbsp; 公元, &nbsp; Menes &mdash; Seti I</div>

</blockquote>

  </div>

         <tt>

         <ul>

<blockquote style="font-size:8px;">

&sup1; This page and <a href="https://devops1.sameboat.network/About DCP">About DCP</a> are specifying stories, describing the system as seen from the outside. I don't divulge the cog arch internals, everything else is source accessible by devops users. Stable just means broadly, not immutable.

<hr>

</div></div>