MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
← Older edit
No edit summary
No edit summary
 
(143 intermediate revisions by the same user not shown)
Line 25: Line 25:
   background-color: #FFFFFFF;
   background-color: #FFFFFFF;
}
}
.content {
.content {
   padding: 0 18px;
   padding: 0 18px;
Line 45: Line 44:
             <a  title="mcpcms cli or webssh login if not SAR authenticated"  
             <a  title="mcpcms cli or webssh login if not SAR authenticated"  
             style="height:50px;background-color:purple;color:white;position: relative; left: 130px; top: -20px;" href=/eg/index.php/MCPCELL><b> &nbsp; launch &nbsp;</b></a>
             style="height:50px;background-color:purple;color:white;position: relative; left: 130px; top: -20px;" href=/eg/index.php/MCPCELL><b> &nbsp; launch &nbsp;</b></a>
             <span style="position: relative;left:130px;top: -20px;">&mdash; an MCP cell &sup1;  provisioned by the Domain Control Program per your current context. &sup2;</span>
             <span style="position: relative;left:130px;top: -20px;">&mdash; an MCP cell &sup1;  provisioned by the <b>D</b>omain <b>C</b>ontrol <b>P</b>rogram per your current context. &sup2;</span>
           </span>
           </span>
</div>
</div>
<div style="z-index:150;position:relative;top:-90px;right:60px;">
<div style="z-index:150;position:relative;top:-90px;right:60px;">
<img align=right width=300px src="https://meansofproduction.biz/images/b6700nMCP2.png">
<img align=right width=300px src="https://meansofproduction.biz/images/b6700nMCP2.png">
<span style="float:right;position:relative;top:270px;left:310px;font-size:10px;">Dual 6700, c. 1971/2, binding says MK 0.0, so 2.0.0<br>
<span style="float:right;position:relative;top:270px;left:310px;font-size:10px;">Dual 6700, c. '72, binding says MK 0.0, so 2.0.0 vs. 21 in 2023.<br>
<audio style="float:right;height:14px;" title="'Woody'n You' Ahmad Jamal 1958" controls source src="https://meansofproduction.biz/pub/WoodyNYou.mp3"  
<audio style="float:right;height:14px;" title="'Woody'n You' Ahmad Jamal 1958" controls source src="https://meansofproduction.biz/pub/WoodyNYou.mp3"  
type="audio/mpeg"> This page has an audio but your browser does not support the audio element.</audio><br>
type="audio/mpeg"> This page has an audio but your browser does not support the audio element.</audio><br>
Line 56: Line 55:
<br>
<br>
</span>
</span>
</div>
</div>
<div style="position: relative; top: -100px;">
<div style="position: relative; top: -100px;">
  <blockquote style="position: relative;top: 0px;"> Semantic Roadmap
  <blockquote style="position: relative;top: 0px;"> Semantic Roadmap
         <tt>
         <tt>
         <ul>
         <ul>
         <li>0.9.0 &nbsp;074-11-02&nbsp; 1<sup>st</sup> ed. tl;dr story freeze.&dagger; </li>
         <li>0.9.0 &nbsp;075-12-11&nbsp; Freeze 1.x Era Timeline. 1<sup>st</sup> stable tl;dr.<sup>&dagger;</sup> </li>
         <li>1.0.0 &nbsp;07y-mm-dd&nbsp; Core DS DCP based, sameboat per node MCPs.</li>
        <li>0.9.1 &nbsp;07y-mm-dd&nbsp; BaselineOfBOOTKEE, doorbell migrated to JSX/HSX cells.</li>
         <li>1.1.0 &nbsp;07y-mm-dd&nbsp; BaselineOfDCP/DGUI (SPO controlled FRED instances). </li>
         <li>1.0.0 &nbsp;07y-mm-dd&nbsp; DCP provisions FRED, C-六/SB, CLFE, and DCMS cells.</li>
         <li>1.2.0 &nbsp;07y-mm-dd&nbsp; Transparent Ledger (Books), DCP live in wild.</li>
        <li>1.1.0 &nbsp;07y-mm-dd&nbsp; <a href=https://redvant.ai-integration.biz>DSAP appgen baseline</a>.</li>
         <li>1.3.0 &nbsp;07y-mm-dd&nbsp; BaselineOfWFL. </li>
         <li>1.1.2 &nbsp;07y-mm-dd&nbsp; FRED fully automated.</li>
         <li>1.4.0 &nbsp;07y-mm-dd&nbsp; &int; x &Dopf; &part; DS, stable boot KEE SPA.</li>
        <li>1.2.0 &nbsp;07y-mm-dd&nbsp; </html>[[WFL/DCP SPO| BaselineOfDCP]]<html> (DGUI/SPO). </li>
         <li>2.0.0 &nbsp;07y-mm-dd&nbsp; 2<sup>nd</sup> ed. tl;dr story (feat: visual programming/execution), 1<sup>st</sup>  WFL w integral DGUI IDE. </li>
         <li>1.2.1 &nbsp;07y-mm-dd&nbsp; Transparent Ledger (Books IX), DCP agency live at perimeter.</li>
         <li>2.1.0 &nbsp;07y-mm-dd&nbsp; &int; VM (CMS, MVS) / DCP &part; DS, the MF-One story.</li>
         <li>2.0.0 &nbsp;07y-mm-dd&nbsp; BaselineOfWFL. </li>
         <li>2.2.0 &nbsp;07y-mm-dd&nbsp; Mature DDD/KEE product.</li>
         <li>2.1.0 &nbsp;07y-mm-dd&nbsp; &int; x &Dopf; &part; DS, BaselineOfKEE.</li>
         <li>2.2.0 &nbsp;07y-mm-dd&nbsp; 1<sup>st</sup>  WFL Workframe. </li>
         <li>3.0.0 &nbsp;07y-mm-dd&nbsp; &int; VM (CMS, MVS) / DCP &part; DS mainframe redux.</li>
         <li>3.1.0 &nbsp;07y-mm-dd&nbsp; Mature DDD/KEE product.</li>
         </ul></tt></blockquote>
         </ul></tt></blockquote>
<center>
<center>
MCP-CMS &mdash; a platform for the Domain Control Program, with an aesthetic in homage to the Burroughs and IBM OSes.
DCP/MCP &mdash; an OS platform with an aesthetic in homage to mainframes.
</center>     
</center>     
         <blockquote style="position: relative;">
         <blockquote style="position: relative;">
         <span style="z-index: 100;position: relative;font-size: 10px;">&sup1; Resource limits are dynamically set except for F class which always gets the system limit
         <span style="z-index: 100;position: relative;font-size: 10px;">&sup1; Resource quotas are entitlement based.</i><br>
              if there is one which for billable accounts is the set spend limit.</i><br>
         &sup2;  Use a supported cloud provider by supplying credentials in control blocks in your profile or system inventory.<br>
         &sup2;  Set parameters for your cloud provider in the DS Dashboard control blocks in your DCMS account or use system inventory.<br>
         </span>
         </span>
         </blockquote>
         </blockquote>
<blockquote style="position:relative;left:-5px;top:-10px;z-index:200;font-size:8px;">&dagger; This page and <a href="https://devops1.sameboat.network/About DCP">About DCP</a>
<blockquote style="position:relative;left:-5px;top:-10px;z-index:200;font-size:8px;">&dagger; For security and flexibility reasons and to the extent feasible, DCP internals aren't divulged, MCP however is source accessible by DevOps users. This page and <a href="https://devops1.sameboat.network/About_DCP">About DCP</a>, which is within the core perimeter, are top level specifying stories.</blockquote>
are top level specifying stories,  cog arch internals aren't divulged as I mean them to be adaptable without notice, everything else is source accessible by DevOps users.</blockquote>
<button title="show/hide the story details" type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button>  
<button title="show/hide the story details" type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button>  
<div class="content">
<div class="content">
<blockquote  style="width: 70%;font-weight: bold;" >
<blockquote  style="width: 70%;font-weight: bold;" >
  MCPCMS presents the "</html>[[:en:CANDE|CANDE]]<html>" MCS&sup3; for DS users.
  <center>DCP/MCP presents the MCPCMS shell and the "</html>[[:en:CANDE|CANDE]]<html>" MCS&sup3; to whitelisted <a style="color: lime;"  href=https://commons.sameboat.network/stationHistory>stations</a> upon connect.<br>AKPERSONs (see <a href=/eg/index.php?title=AKPERSON>Entitlements</a>) can connect with the link above or in a running <a style="color: lime;" href=https://eg.meansofproduction.biz/eg/index.php/WFL/DCP_SPO>SPO</a> image.
<blockquote style="width: 80%;font-weight: bold;">
</center></blockquote>
 
<blockquote style="width: 80%;>
  AKPERSONs (see <a href=/eg/index.php?title=AKPERSON>Entitlements</a>), and whitelisted <a style="color: lime;"  href=https://commons.sameboat.network/stationHistory>stations</a>
In a tx-authenticated user session, should result in a mcpcms <a href=https://devops1.sameboat.network/roles>session role</a> sensitive cell prompt. In the wild, presents a form with parameters for a manual connect. SPO AX msgs to your MCP ODT or SPO message queue may be configured to go the cell.
  can connect with the link above or in a running MCP <a style="color: lime;" href=https://eg.meansofproduction.biz/eg/index.php/WFL/DCP_SPO>SPO</a> .
</blockquote>
  The attempt, if it reaches the DCP, results in completion codes reported in DS control block displays in your DCMS profile.<br>
Only ssh access from the wild, but this page will attempt, using your SAR credentials if the <a href=https://devops1.sameboat.network/roles>session role</a> is greater than 1.<br>
  MCP operator messages will go to your ODT message queue.
<hr width="50%" style="float: left;">
<hr width="50%" style="float: left;">
</blockquote>     
</blockquote>     
Line 110: Line 102:
  <b>ODT MCS</b>   
  <b>ODT MCS</b>   
   <blockquote>
   <blockquote>
     MCP-CMS connects via a MCS which is often referred to as the CANDE MCS although it is more general than that being the default ubiquitous DCP/MCP MCS.
     MCP-CMS connects via a MCS which is usually the CANDE MCS although more generally any MCS with the ODT property can connect for an Operator Display Terminal session with MCP/DCP.
     Upon <b>mcpcms</b> connect, like the lang specific subshells in the next &sect;, an additional command <b>cande</b> can be used which will process the MCP-CMS system commands
     Upon <b>mcpcms</b> connect, like the lang specific subshells in the next &sect;, an additional command <b>cande</b> can be used which will process the MCP-CMS system commands
     analogous to those in the MCP 15 document above. The system command processor is also available as a pane in the SPO.
     analogous to those in the MCP 15 document above.  
   <br><br>
   <br><br>
   In Burroughs MCP, the CANDE MCS was used ubiquitously. I recall using a full screen editor which i think fed CANDE. Commands are implemented per need and some such  
   In Burroughs MCP, the CANDE MCS was used ubiquitously. The ODTs had a full screen editor which just fed lines to CANDE. Commands are implemented per need and some such  
as the text edit functions likely never will be in <b>mcpcms cande</b>. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence when the OS runs under Windows.
as the text edit functions likely never will be in <b>mcpcms cande</b>. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence  
especially when the OS runs as a Windows service.
   </blockquote>
   </blockquote>
   <b>mcpcms</b>
   <b>mcpcms</b>
   <blockquote>
   <blockquote>
     A modified <b>zsh</b> for MCP has the role CMS has in VM/CMS. Upon successful connect, the launch link above results in a terminal session with this shell in the browser.
    The CMS<sup>*</sup> in MCP-CMS is inspired by VM/CMS and the MCP system command level of the CANDE MCS and the ODT session corresponds to the VM CMS command level.
     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:
     A modified <b>zsh</b> serves as the analog of Burroughs CANDE as one of several shells invocable in an ODT.  
     <ul><li><b>shcl</b> </li><li><b>shhs</b></li><li><b>upsh</b></li></ul>
    Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter 'cell' to the connect to invoke <b>cande</b>.
     which have the lisp, haskell, and prolog natures, respectively. <b>shcl</b> is the only one which is a full shell, the others are ways to do posix shell things in lang. While in
     Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates can be specified and are equivalent to <b>cande &lt;subshell&gt;</b> by using the <i>mcpcms command</i> form field lang specific values:
  general Lisp and prolog implementations can vary, shcl and upsh require sbcl and swipl, respectively. During early dev, before DCP WFL is available DCP is implemented in these shells plus MCP.
     <ul><li><b>shcl</b> </li><li><b>hsh</b></li><li><b>upsh</b></li></ul>
     for lisp, haskell, and prolog respectively. MCP embeds sbcl, ghc, and swi prolog as libs and code in these shells can interact with those parts of DCP/MCP directly. In the BootKEE epoch, before DCP WFL is generally available, DCP is programmed as jobs via these shells .
   <b>mcpcms</b> can be accessed from various connect points such as the launch link above in an AKPERSONs session.
   <b>mcpcms</b> can be accessed from various connect points such as the launch link above in an AKPERSONs session.


  <b>mcpcms</b> is implemented first for MCP nodes and cells which are whole or containerized linux instances. Cloud compute resources are dynamically provisioned using either system
  <b>mcpcms</b> scope may vary from a single MCP cell or node to a whole DCP/DS context. Cloud compute resources are dynamically provisioned using either system
  inventory or user supplied provisioning credentials with the MCP 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 the last free version of VM/CMS under
    VM/CMS instead of mcpcms.
    Hercules will ultimately run as an autonomous MCP subject, with other possible mainframe emulations, particularly Unisys should their licensing permit.<br>
*<span style="position:relative;font-size:10px;top:5px;"> &nbsp; Not to be confused with DCMS, the domains content management system.</span>
   </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  
   batch ops.<li>
   batch ops.<li>
  <li>In my WFL, Namespace, Database, and then App/Job is the scope hierarchy. Namespace and Database are elements of a domain space and may span multiple MCP instances but Jobs are limited to
  <li>In my WFL, Namespace, Database, and then App/Job is the scope hierarchy. Namespace and Database are elements of a domain space and may span multiple MCP instances but Jobs are limited to
   a single MCP.</li>
   the nodes and cells of a single MCP. Essentially there is a single whole space level job which the DCP implements.</li>
</ul>
</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
   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
   a database which the Burroughs architecture delivered seamlessly without WFL to terminals as a special db stack. DCP WFL has these design goals
   <ol>
   <ol>
     <li>implements the DCP machine model as a complement to</li>
     <li>provide an clear/auditable text for DCP operations as a complement to</li>
     <li>the MCP which provides the real machine model and</li>
     <li>the MCP which provides the real machine model and</li>
     <li>with code blocks containing text of other supported langs</li>
     <li>with code blocks containing text of other supported langs</li>
Line 154: Line 149:
       <div style="font-size:10px;position:relative;left:0px;"><b>MCP Block Types</b></div>
       <div style="font-size:10px;position:relative;left:0px;"><b>MCP Block Types</b></div>
     <table border=2 style="color:black;background-color:lemonchiffon;width:600px;">
     <table border=2 style="color:black;background-color:lemonchiffon;width:600px;">
     <tr style="background-color:black;color:white;font-size:10px;"><td width=125 align=center >Declarator</td><td align=center width=90>Language</td><td align=center
     <tr style="background-color:black;color:white;font-size:10px;"><td width=125 align=center >WFL Declarator</td><td align=center width=90>Language</td><td align=center
         width=180>Intrinsic</td><td align=center width=205>Purpose/Role</td></tr>
         width=180>Intrinsic&sup1;</td><td align=center width=205>Purpose/Role</td></tr>
      
      
     <tr style="background-color:white;font-size:10px;"><td colspan=4 align=right>Machine Facing &nbsp; &nbsp; </td></tr>
     <tr style="background-color:white;font-size:10px;"><td colspan=4 align=right>Machine Facing &nbsp; &nbsp; </td></tr>
     <tr><td>JOB</td><td align=center>MINT 3</td><td align=center>Yes</td><td>JCL</td></tr>
     <tr><td>None&sup2;</td><td align=center>MINT 3</td><td align=center>Yes</td><td><font size=1>MTRANS WFL Compiler</font></td></tr>
    <tr><td><i>N/A</i></td><td align=center>Smalltalk&sup2;</td><td align=center>No</td><td>GUI and Object Model</td></tr>
     <tr><td>SUBROUTINE</td><td align=center><a href=https://www.gnu.org/software/marst/><b>A60</b></a></td><td align=center>Yes</td><td>JCL Procedures</td></tr>
     <tr><td>SUBROUTINE</td><td align=center><a href=https://www.gnu.org/software/marst/><b>A60</b></a></td><td align=center>Yes</td><td>JCL Procedures</td></tr>
     <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>
     <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>
Line 164: Line 160:


  <tr style="background-color:white;font-size:10px;"><td colspan=4 align=right>Enterprise Facing &nbsp; &nbsp;</td></tr>
  <tr style="background-color:white;font-size:10px;"><td colspan=4 align=right>Enterprise Facing &nbsp; &nbsp;</td></tr>
     <tr><td align=left>APP&sup1;,DB,NS</td><td align=center>WFL </td><td align=center>Yes</td><td><font size=1>Job, Database, &amp; Namespace control</font> </td></tr>
     <tr><td>CL</td><td align=center>Common Lisp</td><td align=center>Yes (sbcl-librarian)</td><td>Lateral R</td></tr>
     <tr><td>CL</td><td align=center>Common Lisp</td><td align=center>No</td><td>Lateral R</td></tr>
     <tr><td>HS</td><td align=center>Haskell </td><td align=center>Yes (ghc-pkg)</td><td><font size=1>Enterprise Applications</font></td></tr>
     <tr><td>HS</td><td align=center>Haskell </td><td align=center>No</td><td>Applications</td></tr>
     <tr><td align=left>JOB</td><td align=center>WFL </td><td align=center>Yes</td><td> JCL</td></tr>
     <tr><td>LP</td><td align=center>LogTalk</td><td align=center>No</td><td>Lateral L</td></tr>
     <tr><td>LP</td><td align=center>LogTalk</td><td align=center>No</td><td>Lateral L</td></tr>
     <tr><td>PL</td><td align=center>Prolog</td><td align=center>No</td><td>Plain Prolog</td></tr>
     <tr><td>PL</td><td align=center>Prolog</td><td align=center>Yes (MQI/pengine)</td><td>Plain Prolog</td></tr>
    <tr><td>ST</td><td align=center>Smalltalk&sup2;</td><td align=center>No</td><td>SPO Context</td></tr>
    </table><font size=1>&sup1;Intrinsic means directly compiled/interpreted by MCP and doesn't require COMPILE or BIND to produce a RUN eligible object title.<br>&sup2;Mint code is monolithic with security by obscurity for some application, database, and namespace elements.</font> &nbsp;&sup3;<font size=1>headless squeak using my cog build for Sista and multi-threading .</font><br>
    </table><br>&sup1;<font size=1>An APP is a JOB with device/station dependencies</font> &nbsp;&sup2;<font size=1>headless squeak</font><br>
     </center>
     </center>
   Intrinsic means the lang is native to MCP/WFL and doesn't require COMPILE or BIND to produce a RUN eligible object title. Enterpise facing means oriented to programming users of the
   Enterprise facing means oriented to programming users of the system, Machine facing means me, for my motivation, satisfaction and design intent of real machine independence of the core super-OS as much as in the nominal sense.  
  system, Machine facing means me, for my motivation, satisfaction and design intent of real machine independence of the core super-OS.  
   Users can create their own semantic spaces by using WFL and the standard modern high level lang blocks while the MINT and Algol elements are my private programming of DCP/MCP not meant  
   Users can create their own semantic spaces by using WFL and the standard modern high level lang blocks while the MINT and Algol elements are my private programming of DCP/MCP not meant  
   for user consuption but visible to satisfy transparency requirements.
   for user consumption but visible to satisfy transparency requirements.
   <div style="width:60%;text-align:justify;">
   <div style="width:60%;text-align:justify;">
   Procedural WFL is translated from source text to A60/C, then compiled and linked to the Barton machine, or directly interpreted by genie or MINT. Non-WFL blocks are compiled and bound  
   Procedural WFL is translated from source text to A60/C, then compiled and linked to the Barton machine, or directly interpreted by genie or MINT. Non-WFL blocks are compiled and bound  
  and used in the concrete context of the DS which they form as extensions of the WFL/B machine.<br><br>
  and used in the concrete context of the DS which they form as extensions of the WFL/B machine.<br><br>
  'JCL' means things defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general end use procedures are meant to be in Algol dialects. I dont mean it to be an acronym being both more general than job control and serving as the macro assembler of MCP. MCP thus maintains a distinction between what it and the host machine directly interpret.<br><br>
  'JCL' means things defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general end use procedures are meant to be in Algol dialects. I dont mean it to be an acronym being both more general than job control and serving as the macro assembler of MCP. MCP thus maintains a distinction between what it and the host machine directly interpret.
  A Smalltalk code set is part of the system concept and a "WFL workframe" is intended as an IDE and GUI for DCP/MCP (DGUI/SPO) but it is not required for ops and will not be  
<br><br>
available until I've worked it on the basis of the experience of the first working clusters.
  DCP/MCP are embodied in a central </html>[[:en:Simula|simulacrum]]<html> containing an object model for them. SPO a system supervisor GUI, and LibraryBrowser which maps code trees to MCP object files and maintains MCP file system attributes, run as a Smalltalk vm/image in the regular MCP job mix. LibraryBrowser/SPO are the things an end user
works with to perform dev/ops with the former constituting a "WFL workframe",  the pair functioning as the IDE and GUI of DCP/MCP (DGUI). Much of it can run headless, the form which the actual DCP can dynamically change by altering its methods, and the one used by non-KEE users. Separately, an available FOSS visual programming pkg is being adapted for what I am calling DS G based on my experience with LabView/G, and which will be developed before WFL but with intent of later being a fa&ccedil;ade for it in concert with LibraryBrowser.
   </div>
   </div>
</blockquote><br><br>
</blockquote><br><br>
   <span style="position:relative;top:-30px;font-size:12px;">The namestyles are a homage to  
   <span style="position:relative;top:-30px;font-size:12px;">The namestyles are 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
     <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>). MCP  
     and Unisys and VM/CMS are trademarks of the IBM and Unisys corporations, respectively. DS MCP as an actually delivered OS is composed of cells (containers) and OS images (nodes)  
  as an actually delivered OS is composed of cells (containers) and OS images (nodes) running system Apps and Jobs coded in WFL, the KEE langs, and general OS binary subjects. </span>
    running system services and jobs with original code in the KEE langs supported by lower level apps runnable on a nodes kernel OS.  
<div style="float:right;text-align:center;font-size:12px;position:relative;left:-125px;top:-240px;width:400px;font-family:Papyrus;" >
  </span>
   <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  
<div style="float:right;text-align:center;font-size:12px;position:relative;left:-125px;top:-240px;width:400px;font-family:Papyrus;" >
    &nbsp; c. -400 &nbsp; to &nbsp; 1400 &nbsp; 公元, &nbsp; Menes &mdash; Seti I</div>
   <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></div></div></div>
</div>
<hr style="position:relative;left:20px;" width=80%>
<div style="position:relative;top:-100px;">
<img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=MCPCMS>
  <hr style="position:relative;left:20px;" width=80%>
<div style="position:relative;top:-10px;"><div id="10CC" style="position: relative;text-align:center;height:150px;">
<div id="10CC" style="position: relative;text-align:center;height:150px;">
<video id="10C" style="position: relative;top:-10px;" title="Pharoah bids Hebrews glean own straw with same count of bricks, presumably for Pi Rameses. The court snickers, Nefertari and Aaron look to Moise who stalks out." poster="http://meansofproduction.biz/images/TIVlarge.png" controls>
<video id="10C" style="position: relative;top:-10px;" title="Pharoah bids Hebrews glean own straw with same count of bricks, presumably for Pi Rameses. The court snickers, Nefertari and Aaron look to Moise who stalks out." poster="http://meansofproduction.biz/images/TIVlarge.png" controls>
         <source src="https://meansofproduction.biz/pub/tldrMCPWFL.webm" type='video/webm'; />
         <source src="https://meansofproduction.biz/pub/tldrMCPWFL.webm" type='video/webm'; />
         <p>No content matching HTML5 video setup!</p>
         <p>No content matching HTML5 video setup!</p>
   </video></div></div></div></div>
   </video>
</div></div>
<script>
<script>
var coll      = document.getElementsByClassName("collapsible");
var coll      = document.getElementsByClassName("collapsible");
Line 241: Line 238:
(function fade(){  
(function fade(){  
  if (!isPlaying) {(s.opacity-=.025)<0?s.display="none":setTimeout(fade,150)}})();
  if (!isPlaying) {(s.opacity-=.025)<0?s.display="none":setTimeout(fade,150)}})();
</script><br><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=MCPCMS>
</script>
</html>
</html>
Retrieved from "https://eg.meansofproduction.biz/eg/index.php/MCP-CMS"