master control program
CMS MCS shell
Use the launch link to get a MCP¹ shell provisioned from my 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). The IPV6 and suffix-free domain forms require DS routing and peering, respectively. Sessions launched by ip do not persist and are strictly contained within the agent's session.
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 mcpcms launch against account limits.
¹NB: 'Unisys CANDE', 'Unisys MCP', and 'Unisys WFL' are distinct from the unaffixed names and will be supported in a free feature of later DCP versions.
² 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.
mcpcms may be accessed at the command line @ <station-name> where
<station-name> ::= ipV6Address[port] | ipV4Address[port] | FQDSAgentName
FQDSAgentName ::= <sameboatUserid>@<sameboatDomain>:<port>
examples [2601:603:1481:30a0:7a4f:21f:3026:6a5e]:50142 firstname.lastname@example.org:50142 email@example.com 184.108.40.206 where the port is system assigned in the last two
MCP shells may have any one of the following natures:
- shcl, common lisp nature
- HsShellScript, haskell nature
- upsh, prolog nature
CMS, the default nature for mcpcms, which is zsh modified for DCP/MCP/MCS.
Only mcpcms can be set in /etc/shells, the others execute as commands in a mcp shell, and only shcl gives a live default command line like fish under standard zsh. The other two require a user supplied hs or pl script, and are not general interactive shells unless that script provides that functionality.
Shells have either MCP (single linux host) or DCP (whole cluster) scope, ip shells are limited to the former.
GHC and SWI are assumed for haskell and prolog, but lisp can be any combination of Allegro, CCL, (user supplied) or sbcl (the default).
The CMS level is always present, the others are outer shells adapted for the domain space knowledge engineering context.
Although adapted for MCP, I try to keep them close to the standard versions, as generic lang specific outer shells.
My preferred DDD uses the three HOLs² listed but the bash level is appropriate for shell ops with MCP unaware software, CANDE, and WFL jobs.
- 1.0.0 PoC: first DCP, lisp and prolog MCSes, composed image MCP and mcpcms, provisioning via the DCM> 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.