MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 131: Line 131:


  <b>mcpcms</b> scope may vary from MCP cell/container to a whole DCP/DS context. Cloud compute resources are dynamically provisioned using either system
  <b>mcpcms</b> scope may vary from MCP cell/container to a whole DCP/DS context. Cloud compute resources are dynamically provisioned using either system
  inventory or user supplied provisioning credentials with supported cloud vendors. Later MCP for Mac and Windows will allow cells there and a version supporting Hercules will use
  inventory or user supplied provisioning credentials with supported cloud vendors. Later MCP for Mac and Windows will allow cells there and a the last free version of VM/CMS under
    VM/CMS from the last free version.
    Hercules will run as an automous MCP subject.
   </blockquote>
   </blockquote>
<b>DCP WFL</b>
<b>DCP WFL</b>
<blockquote>
<blockquote>
   is eponymous from the <a style="background-color:aliceblue;"  href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP WFL</a> with some preserved aesthetics but as a vehicle for DCP and arch
   is eponymous upon the <a style="background-color:aliceblue;"  href=https://meansofproduction.biz/pub/mcpWFL.pdf>Burroughs WFL</a> with some preserved semantics and aesthetics but
   for MCP &mdash;
   only superficially similar  &mdash;
<ul>
<ul>
  <li>The Job is not the top level construct. The Job or App is the closest construct to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one and expansion beyond  
  <li>The Job is not the top level construct. The Job or App is the closest construct to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one and expansion beyond