MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (29 intermediate revisions by the same user not shown) | |||
| Line 60: | Line 60: | ||
<tt> | <tt> | ||
<ul> | <ul> | ||
<li>0.9.0 074-11-02 1<sup>st</sup> | <li>0.9.0 074-11-02 1<sup>st</sup> structurally complete tl;dr.† </li> | ||
<li>0.9.1 07y-mm-dd BOOTKEE, doorbell migrated to JSX/HSX cells.</li> | <li>0.9.1 07y-mm-dd BOOTKEE, doorbell migrated to JSX/HSX cells.</li> | ||
<li>1.0.0 07y-mm-dd DCP provisions FRED, C-六/SB, CLFE, and DCMS cells.</li> | <li>1.0.0 07y-mm-dd DCP provisions FRED, C-六/SB, CLFE, and DCMS cells.</li> | ||
<li>1.1.0 07y-mm-dd | <li>1.1.0 07y-mm-dd DSAP appgen baseline from DCP (flat code for manual programming).</li> | ||
<li>1.1.1 07y-mm-dd AKPERSON tx's to Transparent Ledger (Books), DCP agency live in wild.</li> | <li>1.1.1 07y-mm-dd AKPERSON tx's to Transparent Ledger (Books), DCP agency live in wild.</li> | ||
<li>1.2.0 07y-mm-dd </html>[[WFL/DCP SPO| | <li>1.1.2 07y-mm-dd DSAP appgen with baseline of DS G (visual programming/execution).</li> | ||
<li>1.2.0 07y-mm-dd </html>[[WFL/DCP SPO| BaselineOfDCP]]<html> (DGUI/SPO). </li> | |||
<li>1.2.1 07y-mm-dd BaselineOfWFL. </li> | <li>1.2.1 07y-mm-dd BaselineOfWFL. </li> | ||
<li>1.2.2 07y-mm-dd ∫ x 𝔻 ∂ DS, | <li>1.2.2 07y-mm-dd ∫ x 𝔻 ∂ DS, BaselineOfBOOTKEE.</li> | ||
<li>2.0.0 07y-mm-dd 2<sup>nd</sup> ed. tl;dr story | <li>2.0.0 07y-mm-dd 1<sup>st</sup> SPO integral WFL. 2<sup>nd</sup> ed. tl;dr story. </li> | ||
<li>2.0.1 07y-mm-dd ∫ VM (CMS, MVS) / DCP ∂ DS, the MF-One story.</li> | <li>2.0.1 07y-mm-dd ∫ VM (CMS, MVS) / DCP ∂ DS, the MF-One story.</li> | ||
<li>3.0.0 07y-mm-dd Mature DDD/KEE product.</li> | <li>3.0.0 07y-mm-dd 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;">† This page and <a href="https://devops1.sameboat.network/ | <blockquote style="position:relative;left:-5px;top:-10px;z-index:200;font-size:8px;">† 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 | 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 | In the wild, presents a form for the FQDSA parameters for a manual connect to a DCP determined cell.<br> | ||
AX msgs | 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 122: | Line 123: | ||
A modified <b>zsh</b> serves as the analog of Burroughs CANDE as one of several shells invocable in an ODT. | A modified <b>zsh</b> serves as the analog of Burroughs CANDE as one of several shells invocable in an ODT. | ||
Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke <b>cande</b>. | Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke <b>cande</b>. | ||
Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates | Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates derived from existing pkgs to support the KEE: | ||
<ul><li><b>CANDE shcl</b> </li><li><b>CANDE HSH</b></li><li><b>CANDE upsh</b></li></ul> | <ul><li><b>CANDE shcl</b> </li><li><b>CANDE HSH</b></li><li><b>CANDE upsh</b></li></ul> | ||
which | which work with CL, HS, and PL MCP blocks, respectively. Here the CANDE prefix indicates the received pkgs are modified to run as commands from the CANDE/zsh MCS. While in general Lisp and Prolog implementations can vary in the BootKEE, these lang shells are intrinsic in DCP. 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. | ||
| Line 156: | Line 156: | ||
<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¹</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 </td></tr> | <tr style="background-color:white;font-size:10px;"><td colspan=4 align=right>Machine Facing </td></tr> | ||
<tr><td> | <tr><td>None²</td><td align=center>MINT 3</td><td align=center>Yes</td><td><font size=1>MTRANS WFL Compiler</font></td></tr> | ||
<tr><td> | <tr><td><i>N/A</i></td><td align=center>Smalltalk²</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 167: | Line 167: | ||
<tr style="background-color:white;font-size:10px;"><td colspan=4 align=right>Enterprise Facing </td></tr> | <tr style="background-color:white;font-size:10px;"><td colspan=4 align=right>Enterprise Facing </td></tr> | ||
<tr><td | <tr><td>CL</td><td align=center>Common Lisp</td><td align=center>Yes (sbcl-librarian)</td><td>Lateral R</td></tr> | ||
<tr><td> | <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> | <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>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>< | </table><font size=1>¹Intrinsic means directly compiled/interpreted by MCP and doesn't require COMPILE or BIND to produce a RUN eligible object title.<br>²Mint code is monolithic with security by obscurity for some application, database, and namespace elements.</font> ³<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. | |||
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 consumption but visible to satisfy transparency requirements. | for user consumption but visible to satisfy transparency requirements. | ||
| Line 182: | 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çade for it . | ||
</div> | </div> | ||
</blockquote><br><br> | </blockquote><br><br> | ||
