MCP-CMS

mcpcms  

master control program  
CMS MCS shell  

    conversational monitor system  

launch

The launch link leads to a MCP¹ shell provisioned from core domain space or the AWS, linode, or LAN/DIY inventory ² configured in the KEE Dashboard Control Block in your home profile. ABORTED, ACTIVE, INUSE, COMPLETEDOK, or STOPPED are the possible job completion codes ³ for the launch attempt from the DS station at which you're currently authenticated.

Configuring a device control block for it in your profile dashboard enables system port management, or you can manually manage ssh as usual (e.g using ssh-copy-id).

Launch states ABORTED, COMPLETED, OR STOPPED, imply receipt of diagnostic info by the currently selected means of notification in your home profile (icon above, left of launch status). ABORTED is the immediate result if you are not authenticated.

A running SPO counts as a against account launch limits.

---

¹Core space resources are only dynamically allocated for AKPERSONs.
² AWS, Linode, or your Gb LAN. DCP nodes must have sub-millisecond ping. Set cloud vendor credentials in your commons dashboard or run the DCP leader in your LAN.

hide/show

The namestyle is a homage to MCP and VM/CMS.
While initially only linux is supported, more kernel OS support is intended. MCP communicates with clients via an MCS, and operators one wrapping the ssh protocol. The end command processor is just the assigned shell for the ssh connection which can be:

• shcl, common lisp nature
• HsShellScript, haskell nature
• upsh, prolog nature

or


• mcpcms, the default, a custom zsh.
  
  Only mcpcms need be set in /etc/shells, the others execute as commands in a mcpcms session, and only shcl gives a shell like live command line. The other two require a user supplied haskell or prolog script, and are not general interactive shells unless that script provides that functionality.

Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.
GHC is the assumed for haskell. Lisp and prolog implementations are variable, and multiple can be combined.

The mcpcms level is always present, the others are outer shells adapted for the domain space knowledge engineering context.
Although diverged for DS, an effort will be made to track changes in still vital original lang specific shells.
The KEE uses the three HOLs² listed but the bash/zsh level is appropriate for regular unix shell ops with MCP.

Assuming the target is configured and ready, invoke mcpcms with: ssh @ <station-name> where

• <station-name>  ::= ipV6Address[port] | ipV4Address[port] | FQDSAgentName 

• FQDSAgentName   ::= <sameboatUserid>@<sameboatDomain>:<port>

•  where the port is system provided in the user's DCMS account profile 

Roadmap

• 1.0.0 PoC: first DCP, lisp and prolog MCSes, composed image MCP and mcpcms, provisioning via the DCMS> C-六 backend.
• 1.1.0 First working SPO and WFL language server.
• 1.2.0 Consolidation and productization release.
• 2.0.0 Mature DDD/KEE product.

---

² 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.