Anonymous

MCP-CMS: Difference between revisions

From Cibernética Americana
111 bytes added ,  11 October 2023
no edit summary
No edit summary
No edit summary
Line 102: Line 102:
   <b>WFL</b>
   <b>WFL</b>
   <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 style="background-color:aliceblue;"  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>
   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, 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 architecture
   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, 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 architecture
   <ol>
   <ol>
Line 121: Line 121:
     <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>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>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>
     <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></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>
Line 130: 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="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>
   <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 style="background-color:aliceblue;"  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:-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>