Bureaucrats, Interface administrators, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), Administrators, Widget editors
23,422
edits
No edit summary |
No edit summary |
||
Line 144: | Line 144: | ||
<b>WFL</b> | <b>WFL</b> | ||
<blockquote> | <blockquote> | ||
is eponymous from the <a style="background-color:aliceblue;" href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP WFL</a> and retains some superficial aesthetics but is radically different in that" | |||
<ul> | |||
<li>The Job is not the top level construct. Jobs are the closest elements to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one.<li> | |||
<li>In my WFL, Enterprise, Domain, and then Job is the top level. Enterprise and Domain are elements of a domain space and may span multiple MCP instances but Jobs are limited to a single MCP.</li> | |||
</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 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 | |||
<ol> | <ol> | ||
<li>is built for the MCP machine model</li> | <li>is built for the MCP machine model</li> |