Anonymous

MCP-CMS: Difference between revisions

From Cibernética Americana
39 bytes added ,  20 June 2024
no edit summary
No edit summary
No edit summary
Line 144: Line 144:
   <b>WFL</b>
   <b>WFL</b>
   <blockquote>
   <blockquote>
   has eponymous origin in the <a style="background-color:aliceblue;"  href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> job control model and supports the DCP with a line of demarcation between the minimalist MCP and its extension specific to DCP which is meant to protect properties of its internals. A way to think about it and my design intent is that MCP is a basic unix cluster machine to host any common mix, while the WFL machine is a private specialization. <br><br>
   is eponymous from the <a style="background-color:aliceblue;"  href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP WFL</a> and retains some superficial aesthetics but is radically different in that"
  Unisys WFL is just a point of departure to our WFL. In Burroughs systems, WFL didn have as high a profile as IBM JCL, the main punch of the overall system, in an industry installation, would be its system of  transactions and these ran from a database which the Burroughs architecture delivered seamlessly without WFL to terminals as a special db stack. Our WFL is the central driver and basis of our MCP architecture
<ul>
<li>The Job is not the top level construct. Jobs are the closest elements to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one.<li>
<li>In my WFL, Enterprise, Domain, and then Job is the top level. Enterprise and Domain are elements of a domain space and may span multiple MCP instances but Jobs are limited to a single MCP.</li>
</ul>
  In Burroughs systems, WFL didn have as high a profile as IBM JCL, the main punch of the overall system, in an industry installation, would be its system of  transactions and these ran from a database which the Burroughs architecture delivered seamlessly without WFL to terminals as a special db stack. Our WFL is the central driver and basis of our MCP/DCP architecture
   <ol>
   <ol>
     <li>is built for the MCP machine model</li>
     <li>is built for the MCP machine model</li>