MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(18 intermediate revisions by the same user not shown)
Line 60: Line 60:
         <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;074-11-02&nbsp; 1<sup>st</sup> structurally complete tl;dr.&dagger; </li>
         <li>0.9.1 &nbsp;07y-mm-dd&nbsp; BOOTKEE, doorbell migrated to JSX/HSX cells.</li>
         <li>0.9.1 &nbsp;07y-mm-dd&nbsp; BOOTKEE, doorbell migrated to JSX/HSX cells.</li>
         <li>1.0.0 &nbsp;07y-mm-dd&nbsp; DCP provisions FRED, C-六/SB, CLFE, and DCMS cells.</li>
         <li>1.0.0 &nbsp;07y-mm-dd&nbsp; DCP provisions FRED, C-六/SB, CLFE, and DCMS cells.</li>
         <li>1.1.0 &nbsp;07y-mm-dd&nbsp;   DSAP appgen.</li>
         <li>1.1.0 &nbsp;07y-mm-dd&nbsp; DSAP appgen baseline from DCP (flat code for manual programming).</li>
         <li>1.1.1 &nbsp;07y-mm-dd&nbsp; AKPERSON tx's to Transparent Ledger (Books), DCP agency live in wild.</li>
         <li>1.1.1 &nbsp;07y-mm-dd&nbsp; AKPERSON tx's to Transparent Ledger (Books), DCP agency live in wild.</li>
         <li>1.2.0 &nbsp;07y-mm-dd&nbsp; </html>[[WFL/DCP SPO|DGUI]]<html> (SPO controlled FRED instances)/BaselineOfDCP. </li>
        <li>1.1.2 &nbsp;07y-mm-dd&nbsp; DSAP appgen with baseline of DS G (visual programming/execution).</li>
         <li>1.2.0 &nbsp;07y-mm-dd&nbsp; </html>[[WFL/DCP SPO| BaselineOfDCP]]<html> (DGUI/SPO). </li>
         <li>1.2.1 &nbsp;07y-mm-dd&nbsp; BaselineOfWFL. </li>
         <li>1.2.1 &nbsp;07y-mm-dd&nbsp; BaselineOfWFL. </li>
         <li>1.2.2 &nbsp;07y-mm-dd&nbsp; &int; x &Dopf; &part; DS, stable boot KEE SPA.</li>
         <li>1.2.2 &nbsp;07y-mm-dd&nbsp; &int; x &Dopf; &part; DS, BaselineOfBOOTKEE.</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>2.0.0 &nbsp;07y-mm-dd&nbsp; 1<sup>st</sup>  SPO integral WFL. 2<sup>nd</sup> ed. tl;dr story.   </li>
         <li>2.0.1 &nbsp;07y-mm-dd&nbsp; &int; VM (CMS, MVS) / DCP &part; DS, the MF-One story.</li>
         <li>2.0.1 &nbsp;07y-mm-dd&nbsp; &int; VM (CMS, MVS) / DCP &part; DS, the MF-One story.</li>
         <li>3.0.0 &nbsp;07y-mm-dd&nbsp; Mature DDD/KEE product.</li>
         <li>3.0.0 &nbsp;07y-mm-dd&nbsp; Mature DDD/KEE product.</li>
Line 81: Line 82:
         </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; This page and <a href="https://devops1.sameboat.network/About_DCP">About DCP</a>
  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>
  are top level specifying stories,  to the extent feasible, 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">
Line 93: Line 94:
   
   
  </blockquote>
  </blockquote>
  In a DS user session, should result in a mcpcms prompt (<a href=https://devops1.sameboat.network/roles>session role</a> > 1).<br>
  In a tx-authenticated user session, should result in a mcpcms <a href=https://devops1.sameboat.network/roles>session role</a> sensitive cell prompt.<br>
  In the wild, presents a form for the FQDSA parameters for a manual DCP connect (see this article's talk page).<br>
  In the wild, presents a form for the FQDSA parameters for a manual connect to a DCP determined cell.<br>
  AX msgs from your MCP ODT message queue and task completion codes go to DS control blocks in your sameboat profile if enabled.
  SPO AX msgs to your MCP ODT or SPO message queue will be expected to come from the cell.
<hr width="50%" style="float: left;">
<hr width="50%" style="float: left;">
</blockquote>     
</blockquote>     
Line 159: Line 160:
      
      
     <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>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>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><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>
Line 171: Line 172:
     <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>Yes (MQI/pengine)</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>
     </table><br>&sup1;<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><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>
     </center>
     </center>
   The SPO image contains a MCP/DCP </html>[[:en:Simula|simulacrum]]<html> as Smaltalk objects that communicate with the real things and whose vm runs in the regular MCP job mix. 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.  
   The SPO image contains a MCP/DCP </html>[[:en:Simula|simulacrum]]<html> as Smaltalk objects that communicate with the real things and whose vm runs in the regular MCP job mix. 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.  
Line 181: Line 182:
  '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.<br><br>
  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  
  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  
  available until I've worked it on the basis of the experience of the first working clusters.
  available until I've worked it on the basis of the experience of the first working clusters. Separately, I will make a DCP/MCP adaptation based on the available FOSS visual programming pkgs,    and which 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 .
   </div>
   </div>
</blockquote><br><br>
</blockquote><br><br>