MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
22 bytes added ,  4 November 2023
no edit summary
No edit summary
No edit summary
Line 44: Line 44:
             <a  title="mcpcms cli or webssh login if not in a SSO session" style="position: relative; left: 130px; top: -20px;" target=_blank href=https://dcms.ai-integration.biz><b>launch</b></a>
             <a  title="mcpcms cli or webssh login if not in a SSO session" style="position: relative; left: 130px; top: -20px;" target=_blank href=https://dcms.ai-integration.biz><b>launch</b></a>
             <span style="position: relative;left:130px;top: -20px;">&mdash; a shell on a <a style="color: lime;" title="About the MCP reinvention"  
             <span style="position: relative;left:130px;top: -20px;">&mdash; a shell on a <a style="color: lime;" title="About the MCP reinvention"  
               href=https://eg.meansofproduction.biz/eg/index.php/MCP>MCP</a> node, &sup1;  provisioned per your current SAR context. &sup2;</span>
               href=https://eg.meansofproduction.biz/eg/index.php/MCP>MCP</a> node, &sup1;  provisioned per your current SSO context. &sup2;</span>
           </span>
           </span>
</div>
</div>
Line 62: Line 62:
         </span>
         </span>
         </blockquote>
         </blockquote>
        <blockquote style="position: relative;top: -50px;">Devops Roadmap
        <tt>
        <ul>
        <li>0.3.0 c. 4721-04-17&nbsp; Stable told tl;dr story.&sup1; </li>
        <li>0.9.0 c. 47yy-00-00&nbsp; BaselineOfDomainSpace. </li>
        <li>1.0.0 c. 47yy-00-00&nbsp; BaselineOfKEE. </li>
        <li>1.1.0 c. 47yy-00-00&nbsp; Provisions generic base cluster, working geonode budding, shown tl;dr story.  All public pre MCP hosts migrated.</li>
        <li>1.2.0 c. 47yy-00-00&nbsp; First dependent SKUs made GA.</li>
        <li>2.0.0 c. 47yy-00-00&nbsp; First working WFL workframe, a UI for job edit and debug with visual execution. </li>
        <li>3.0.0 c. 47yy-00-00&nbsp; Mature DDD/KEE product.</li>
        </ul></tt>
<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.
</blockquote>
<hr>
     <button type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button>  
     <button type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button>  
  <div class="content">
  <div class="content">
Line 146: Line 130:
   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.
   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.
   </div></blockquote><br><br>
   </div></blockquote><br><br>
   <span style="position:relative;top:-30px;font-size:12px;">Name styles in 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>). My WFL machine will be ported to other vendors (Google, Azure, et. al.) after workout in Akamai (linode) and AWS.</span>
   <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>
<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>
</blockquote>
  </div>
  </div>
        <blockquote style="position: relative;top: -50px;">Devops Roadmap
        <tt>
        <ul>
        <li>0.3.0 c. 4721-04-17&nbsp; Stable told tl;dr story.&sup1; </li>
        <li>0.9.0 c. 47yy-00-00&nbsp; BaselineOfDomainSpace. </li>
        <li>1.0.0 c. 47yy-00-00&nbsp; BaselineOfKEE. </li>
        <li>1.1.0 c. 47yy-00-00&nbsp; Provisions generic base cluster, working geonode budding, shown tl;dr story.  All public pre MCP hosts migrated.</li>
        <li>1.2.0 c. 47yy-00-00&nbsp; First dependent SKUs made GA.</li>
        <li>2.0.0 c. 47yy-00-00&nbsp; First working WFL workframe, a UI for job edit and debug with visual execution. </li>
        <li>3.0.0 c. 47yy-00-00&nbsp; Mature DDD/KEE product.</li>
        </ul></tt>
<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.
</blockquote>
<hr>
</div></div>
</div></div>


Navigation menu