MCP-CMS: Difference between revisions
No edit summary |
No edit summary |
||
| Line 62: | Line 62: | ||
<b>mcpcms</b> | <b>mcpcms</b> | ||
<blockquote> | <blockquote> | ||
is derived from <b>zsh</b> and is the shell variant which is set in /etc/shells for MCP. | is derived from <b>zsh</b> and is the shell variant which is set in /etc/shells for MCP. In an authenticated session, the launch link normally results is a tty session with this shell. Aside from the modification for the MCP machine model. Aside from access to and controls for that model, it is otherwise just zsh. | ||
</blockquote> | </blockquote> | ||
<b>WFL</b> | <b>WFL</b> | ||
<blockquote> | <blockquote> | ||
is derived from <b>a68g</b>, runs as shebang scripts under <b>mcpcms</b>, and is based on selected elements of <a href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> reimagined for our systems concept. It | is derived from <b>a68g</b>, runs as shebang scripts under <b>mcpcms</b>, and is based on selected elements of <a href=https://meansofproduction.biz/pub/mcpWFL.pdf>MCP 12 WFL</a> reimagined for our systems concept. It serves as the central point of a bottom up integration of MCP/DCP elements. | ||
</blockquote> | </blockquote> | ||
<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 | <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 | ||
Revision as of 01:32, 2 March 2023
mcpcms
master control program
CMS MCS shell
conversational monitor system launch — a shell on a MCP¹, provisioned per your current SSO context. ²
MCPCMS, the default or "CANDE" MCS³, controls DCP/MCP message traffic and implements WFL.
A running SPO counts against launch limits.
Launch code ABORTED implies additional info in your home profile DS control blocks.
At least S class SSO entitlement is required and only one launch at a time is permitted at this station .
ABORTED, ACTIVE, COMPLETEDOK, or STOPPED are the possible job completion codes for the launch attempt.
¹ Resource limits are dynamically set except for F class which always gets the system limit if there is one.
² MCP nodes must have sub-millisecond ping. Set parameters for your own AWS or Linode accounts or your manually provisioned hosts in the Remote Inventory DS block in your home profile.
³ MCS: a message control subsystem of a MCP.
mcpcms
is derived from zsh and is the shell variant which is set in /etc/shells for MCP. In an authenticated session, the launch link normally results is a tty session with this shell. Aside from the modification for the MCP machine model. Aside from access to and controls for that model, it is otherwise just zsh.
WFL
is derived from a68g, runs as shebang scripts under mcpcms, and is based on selected elements of MCP 12 WFL reimagined for our systems concept. It serves as the central point of a bottom up integration of MCP/DCP elements.
The namestyles are a homage to MCP and VM/CMS main frame operating systems which are both still in use and Unisys WFL (Work Flow Language).
Roadmap
- 0.1.0 4721-00-00 BaselineOfDomainSpace (Squot pkg from the then current).
- 0.2.0 4721-00-00 BaselineOfKEE.
- 1.0.0 4721-00-00 SPO supports geonode budding (MCP head with the DCMS> C-六 backend, proxy master, and worker(s)).
- 1.3.0 4721-00-00 All pre MCP hosts migrated.
- 2.0.0 47yy-00-00 First working WFL workframe.
- 3.0.0 47yy-00-00 Mature DDD/KEE product.
All of above had delivery landings with long tails back in time, best start of which is the first under in the 'text' box in the left nav.
² High Order Language ³ The states COMPLETED, COMPILEDOK and SCHEDULED are invalid for the launch WFL job, but its task steps may have COMPLETED codes, usable in other interfaces.
