MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
(47 intermediate revisions by the same user not shown)
Line 49: Line 49:
<div style="position: relative; top: -100px;">
<div style="position: relative; top: -100px;">
<blockquote  style="width: 70%;font-weight: bold;" >
<blockquote  style="width: 70%;font-weight: bold;" >
  MCPCMS, the default or "</html>[[:en:CANDE|CANDE]]<html>" MCS&sup3;, controls DCP/MCP message traffic and implements WFL.
  MCPCMS presents the operator display terminal CONTROLLER for MCP ops and the default or "</html>[[:en:CANDE|CANDE]]<html>" MCS&sup3;.
<blockquote style="width: 80%;font-weight: bold;">
<blockquote style="width: 80%;font-weight: bold;">
           Restricted to 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> .<br><br>
           Restricted to 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> .<br><br>
Line 81: Line 81:
# save as &lt;fileName&gt; and invoke with &lt;fileName&gt;  &lt;connect-spec&gt; where             
# save as &lt;fileName&gt; and invoke with &lt;fileName&gt;  &lt;connect-spec&gt; where             
#         
#         
#  &lt;connect-spec&gt;::= &lt;ipV6Address&gt;:&lt;port&gt; | &lt;ipV4Address&gt;:&lt;port&gt; | FQDSA&lt;whiteSpace&gt;&lt;FQDSAgentName&gt;  
#  &lt;connect-spec0&gt;::= 'skip' &lt;FQDSAgentName&gt; | &lt;connect-spec&gt;
#  FQDSAgentName ::= &lt;agentId&gt;@&lt;domain&gt;[:&lt;port&gt;]
&lt;connect-spec&gt; ::= &lt;ipV6Address&gt;:&lt;port&gt; | &lt;ipV4Address&gt;:&lt;port&gt;
#  FQDSAgentName ::= &lt;agentId&gt;@&lt;domain&gt;[:&lt;port&gt;]
#
#
#  and the values are displayed in the DCMS account profile.   
#  and the values manually supplied from control blocks in the DCMS account profile where connect attempt results will also be available.   
#
#
if [ -z $2 ] then
if [ -z $2 ] then
Line 91: Line 92:
fi
fi
#
#
# Get connect values from FQDSA.
# Try a connect based on just the FQDSA assuming an eligible station.
#
#
FQDSA=getmcpcms.ai-integration.biz/?FQDSA=$2
FQDSA=getmcpcms.ai-integration.biz/?FQDSA=$2
Line 102: Line 103:
   <blockquote>
   <blockquote>
     is derived from the <a href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> job control model, runs underneath <b>mcpcms</b> and serves as the physical base of MCP/DCP elements.<br><br>
     is derived from the <a href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> job control model, runs underneath <b>mcpcms</b> and serves as the physical base of MCP/DCP elements.<br><br>
   Burroughs WFL is basically just an inspiration and point of departure to a WFL
   Unisys WFL is just a point of departure to our WFL. In Burroughs systems, WFL didn have as high a profile as IBM JCL, the main punch of the overall system 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 architecture
   <ol>
   <ol>
     <li>built for the MCP machine model</li>
     <li>is built for the MCP machine model</li>
     <li>which is a prime driver for the development of that model</li>
     <li>which is a prime driver for the development of that model</li>
     <li>with code blocks containing text of other supported langs</li>
     <li>with code blocks containing text of other supported langs</li>
   </ol>
   </ol>
   As far as the elaboration of JCL statements and so forth WFL is developed in a bottom up prototyping style without any spec other than the mainframe reference and the nascent MCP concept, so there will be no documentation for some time  
   As far as the elaboration of JCL statements and so forth WFL is developed in a bottom up prototyping style without any spec other than the mainframe reference and the DCP/MCP concept, so there will be no documentation for some time  
   other than the text of actual jobs. &#8470; 3 above is implemented by variants for the SUBROUTINE statement, with the same attachment of BEGIN and END bounded blocks:
   other than the text of actual jobs. &#8470; 3 above is implemented by variants for the SUBROUTINE statement, with the same attachment of BEGIN and END bounded blocks:
     <center><table style="color:black;background-color:white;width:300px;">
     <center><table style="color:black;background-color:white;width:300px;">
Line 119: Line 120:
     <tr style="font-size:10px;"><td></td><td align=center>System Internal</td><td></td></tr>
     <tr style="font-size:10px;"><td></td><td align=center>System Internal</td><td></td></tr>
     <tr><td>MINT</td><td align=center>MINT 3</td><td align=right>Yes</td></tr>
     <tr><td>MINT</td><td align=center>MINT 3</td><td align=right>Yes</td></tr>
     <tr><td>UNIT</td><td align=center><a href=https://jmvdveer.home.xs4all.nl/en.algol-68-genie.html><b>Algol 68</b></a></td><td align=right>Yes</td></tr>
    <tr><td>PROC</td><td align=center><a href=https://www.gnu.org/software/marst/><b>A60</b></a></td><td align=right>Yes</td></tr>
     <tr><td>UNIT</td><td align=center><a href=https://jmvdveer.home.xs4all.nl/en.algol-68-genie.html><b>A68</b></a></td><td align=right>Yes</td></tr>
     </table>
     </table>
   <div style="font-size:10px;position:relative;left:20px;"><b>MCP Block Types</b></div>
   <div style="font-size:10px;position:relative;left:20px;"><b>MCP Block Types</b></div>
</center>
</center>
   Intrinsic means the lang is native to MCP/WFL and doesn't require COMPILE or BIND to produce a RUNable title.<br>
   Intrinsic means the lang is native to MCP/WFL and doesn't require COMPILE or BIND to produce an executable job title.<br>
   Job titles are bound to files by the <b>cande</b> WFL command after which they can be STARTed.<br>
   MAKE binds job titles to files executable by the <b>cande</b> MCS with the START or SCHEDULE commands.
   The WFL compiler translates JCL to A68, MINT, and assembly which are run by genie, mint, and da Fe, respectively.
  <div style="width:60%;text-align:justify;">
  </blockquote><br><br>
   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.
   <span style="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> main
  </div></blockquote><br><br>
  frame operating systems which are both still in use and Unisys WFL (<a href=https://public.support.unisys.com/aseries/docs/clearpath-mcp-18.0/86001047-516/index.html>Work Flow Language</a>).</span>
   <span style="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 operating systems which are both still in use and Unisys WFL (<a href=https://public.support.unisys.com/aseries/docs/clearpath-mcp-18.0/86001047-516/index.html>Work Flow Language</a>).</span>
<div  style="float:right;text-align:center;font-size:12px;position:relative;left:-150px;top:-120px;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>
Line 136: Line 138:
         <tt>
         <tt>
         <ul>
         <ul>
         <li>0.3.0 c. 4721-03-03&nbsp; Told tl;dr story. </li>
         <li>0.3.0 c. 4721-04-17&nbsp; Stable told tl;dr story. </li>
         <li>0.9.0 c. 4721-00-00&nbsp; BaselineOfDomainSpace. </li>
         <li>0.9.0 c. 47yy-00-00&nbsp; BaselineOfDomainSpace. </li>
         <li>1.0.0 c. 4721-00-00&nbsp; BaselineOfKEE. </li>
         <li>1.0.0 c. 47yy-00-00&nbsp; BaselineOfKEE. </li>
         <li>1.1.0 c. 4721-00-00&nbsp; Provisions generic base cluster, working geonode budding, shown tl;dr story.  All public pre MCP hosts migrated.</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. 4721-00-00&nbsp; First dependent SKUs made GA.</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>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>
         <li>3.0.0 c. 47yy-00-00&nbsp; Mature DDD/KEE product.</li>
Line 148: Line 150:
</blockquote>
</blockquote>
<hr>
<hr>
&sup2; <span style="font-size: 10px;">High Order Language</span>
</div></div>
</div></div>