From Cibernética Americana


master control program  
CMS MCS shell  
    the launch task reports: ABORTED .


If the launch request status above is not ABORTED or STOPPED, a MCP¹ shell session is or shortly will be running on support provisioned from core domain space or DIY inventory². These and the remaining states ACTIVE, INUSE, or COMPLETEDOK, implicitly reference the DS station at which you're currently authenticated. It may be explicitly accessed at <station-name> where

  • <station-name>  ::= ipV6Address | ipV4Address | FQAgentName 
  • <domain>        ::= ai-integration | | <yourTLD>[.dom]
  • FQAagentName    ::= your C-六 nick FQDN, e.g. 'janedoe@<domain>:<port>'.
  • <yourTLD>       ::= your alt-root TLD or its public linking zone.

Add a device control block to your profile dashboard and enable CMS which assigns a port for the station, then ssh as usual post a 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.

MCP shells may have any one of the following natures:

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

  • or
  • CMS, the default nature for mcpcms, which is zsh modified for DCP/MCP/WFL.

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

SYSTEM/CMS is the prototypical CL/MCS. It is meant to be a generalization of CANDE and VM/CMS .

While initially the linux bash capable terminal is supported, ODT and 3270 support are intended.

Version/Schedule Milestone Roadmap

  • 2020-12-15 SSI PoC, proto CL/MCS and CMS MCS, ansible provisioning from C-Liu backend.
  • 1.1 First level maturity of base lisp MCP codeset.
  • 1.2 AI legacy systems salvage and integration complete and devops ready in the shell service.
  • 2.0 Mature DDD/KEE product.

² High Order Language