MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search

MCP-CMS (view source)

Revision as of 22:27, 8 March 2023

65 bytes removed ,  8 March 2023
no edit summary
No edit summary
No edit summary
Line 102: Line 102:
   <blockquote>
   <blockquote>
     is derived from <a href=https://jmvdveer.home.xs4all.nl/en.algol-68-genie.html><b>a68g</b></a>, runs as shebang scripts under <b>mcpcms</b>, and is based on selected elements of <a href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> reimagined for our systems concept. It serves as the central point of a bottom up integration of MCP/DCP elements.<br><br>
     is derived from <a href=https://jmvdveer.home.xs4all.nl/en.algol-68-genie.html><b>a68g</b></a>, runs as shebang scripts under <b>mcpcms</b>, and is based on selected elements of <a href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> reimagined for our systems concept. It serves as the central point of a bottom up integration of MCP/DCP elements.<br><br>
   The main other differences from what you see in the sample jobs of the Unisys WFL reference are
   While my WFL is based superficially on the Burroughs WFL reference, it's basically just a point of departure:
   <ol>
   <ol>
     <li>Built in access to MCP machine model.</li>
     <li>Built for the MCP machine model which is implicit as the Burroughs systems were for the original.</li>
     <li>Algol68 based instead of Algol60/Elliot Algol based and a superset not a subset.</li>
     <li>The job control language is the base upon which that model is developed.</li>
     <li>Addition of modal units to support other langs than A68, specifically haskell, lisp, and prolog. COMPILE and BIND are setup to use the supported tools for these langs.</li>
    <li>The reimagined JCL supports ops over many actual hosts unified by the MCP.</li>
     <li>Besides the JCL blocks may contain other supported langs.</li>
   </ol>
   </ol>
   WFL is developed in a bottom up prototyping style rather than top down from a spec, although the original is something of one, so there will be no documentation for some time  
   As far as the elaboration of JCL statements and so forth WFL is developed in a bottom up prototyping style without any spec other than the mainframe reference and the nascent MCP concept, so there will be no documentation for some time  
   other than the working job text. #3 above is implemented by variants for BEGIN&lt;suffix&gt; and END&lt;suffix&gt; with &lt;suffix&gt; empty for A68, and CL, HS, LP, or PL
   other than the text of actual jobs. &numero; 4 above is implemented by variants for the SUBROUTINE statement, with the same attachment of BEGIN and END blocks.<br><br>
  for the text in the KEE langs. CL is common lisp, HS is some version of GHC, LP is logtalk and PL is plain prolog. Lang specifics are determined by governing COMPILE and BIND statements.<br><br>
   Unlike standard unix shell scripts, WFL jobs are compiled first rather than interpreted and executed line by line.
   Unlike standard unix shell scripts, WFL jobs are compiled first then interpreted.
   </blockquote><br><br>
   </blockquote><br><br>
   <span style="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> main
   <span style="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> main
Retrieved from "https://eg.meansofproduction.biz/eg/index.php/Special:MobileDiff/21216"

Navigation menu