MCP-CMS

mcpcms  

  conversational monitoring system  
DCP Shell  

    minimalist clustering paradigm  

  launch   — an MCP cell ¹ provisioned by the Domain Control Program per your current context. ²

Dual 6700, c. 1971/2, binding says MK 0.0, so 2.0.0

This page has an audio track, mouseover for title/credit.

Semantic Roadmap

• 0.9.0  074-11-02  1^st ed. tl;dr story freeze.†
• 1.0.0  075-06-dd  Core DS DCP based, sameboat per node MCPs & Redvant generation chain support cells.
• 1.1.0  075-09-dd  Transparent Ledger (Books), DCP help live in wild.
• 1.2.0  07y-mm-dd  BaselineOfWFL.
• 1.3.0  07y-mm-dd  BaselineOfDCP/DGUI (SPO controlled FRED instances).
• 1.4.0  07y-mm-dd  ∫ x 𝔻 ∂ DS, stable boot KEE SPA.
• 2.0.0  07y-mm-dd  2^nd ed. tl;dr story (feat: visual programming/execution), 1^st WFL w integral DGUI IDE.
• 2.1.0  07y-mm-dd  ∫ VM (CMS, MVS) / DCP ∂ DS, the MF-One story.
• 2.2.0  07y-mm-dd  Mature DDD/KEE product.

MCP-CMS — a platform for the Domain Control Program, with an aesthetic in homage to the Burroughs and IBM OSes.

¹ Resource limits are dynamically set except for F class which always gets the system limit if there is one which for billable accounts is the set spend limit.
² Set parameters for your cloud provider in the DS Dashboard control blocks in your DCMS account or use system inventory.

† This page and About DCP are top level specifying stories, cog arch internals aren't divulged as I mean them to be adaptable without notice, everything else is source accessible by DevOps users.

tl;dr

MCPCMS presents the "CANDE" MCS³ for DS users.

AKPERSONs (see Entitlements), and whitelisted stations can connect with the link above or in a running MCP SPO .

The attempt, if it reaches the DCP, results in completion codes reported in DS control block displays in your DCMS profile.
Only ssh access from the wild, but this page will attempt, using your SAR credentials if the session role is greater than 1.
MCP operator messages will go to your ODT message queue.

---

³ MCS: a message control subsystem of a MCP. MCP 15 System Commands
MCP 3.3 CANDE Reference Card
MCP 14 CANDE Reference

ODT MCS

MCP-CMS connects via a MCS which is usually the CANDE MCS although more generally any MCS with the ODT property can connect for an Operator Display Terminal session with MCP/DCP. Upon mcpcms connect, like the lang specific subshells in the next §, an additional command cande can be used which will process the MCP-CMS system commands analogous to those in the MCP 15 document above.

In Burroughs MCP, the CANDE MCS was used ubiquitously. The ODTs had a full screen editor which just fed lines to CANDE. Commands are implemented per need and some such as the text edit functions likely never will be in mcpcms cande. CANDE is used in current Unisys MCP but neither it nor the MCS have their former prominence especially when the OS runs as a Windows service.

mcpcms

The CMS in MCP-CMS is inspired by VM/CMS and the MCP system command level of the CANDE MCS and the ODT session corresponds to the VM CMS command level. A modified zsh serves as the analog of Burroughs CANDE as one of several shells invocable in an ODT. Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke cande. Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates are available to establish different shell behaviours in support of the KEE:

• shcl
• shhs
• upsh

which have the lisp, haskell, and prolog natures, respectively. shcl is the only one which is a full shell run at the ODT command level like cande, the others are ways to do posix shell things in lang and are run as commands in cande/zsh. While in general Lisp and Prolog implementations can vary in the Boot KEE, these lang shells are integral with DCP which uses sbcl and swipl, respectively. In the Boot KEE epoch, before DCP WFL is available DCP is implemented in these shells over its machine model. mcpcms can be accessed from various connect points such as the launch link above in an AKPERSONs session. mcpcms scope may vary from MCP cell/container to a whole DCP/DS context. Cloud compute resources are dynamically provisioned using either system inventory or user supplied provisioning credentials with supported cloud vendors. Later MCP for Mac and Windows will allow cells there and a the last free version of VM/CMS under Hercules will run as an automous MCP subject.

DCP WFL

is eponymous upon the Burroughs WFL with some preserved semantics and aesthetics but only superficially similar —

• The Job is not the top level construct. The Job or App is the closest construct to heritage WFL in my WFL but with ops on my MCP rather than the Burroughs/Unisys one and expansion beyond batch ops.
• In my WFL, Namespace, Database, and then App/Job is the scope hierarchy. Namespace and Database are elements of a domain space and may span multiple MCP instances but Jobs are limited to a single MCP.

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. DCP WFL has these design goals

1. provide an clear/auditable text for DCP operations as a complement to
2. the MCP which provides the real machine model and
3. with code blocks containing text of other supported langs

DCP WFL is developed in a bottom up manner from this statement of design intent without any spec other than the heritage systems and the DCP/MCP concept. In the initial releases there will be no documentation outside of story text, and the top level pamphlets. Code cannot move into WFL blocks from its free form before the 1.2.0 milestone. In standard Algol convention № 3 above is implemented by these block variants with the same delimitation by BEGIN and END bounded blocks:

MCP Block Types

Declarator	Language	Intrinsic	Purpose/Role
Machine Facing
JOB	MINT 3	Yes	JCL
SUBROUTINE	A60	Yes	JCL Procedures
UNIT	A68	Yes	MCP Libraries
Enterprise Facing
APP¹,DB,NS	WFL	Yes	Job, Database, & Namespace control
CL	Common Lisp	No	Lateral R
HS	Haskell	No	Applications
LP	LogTalk	No	Lateral L
PL	Prolog	No	Plain Prolog
ST	Smalltalk²	No	SPO Context

¹An APP is a JOB with device/station dependencies  ²headless squeak

Intrinsic means the lang is native to MCP/WFL and doesn't require COMPILE or BIND to produce a RUN eligible object title. Enterpise facing means oriented to programming users of the system, Machine facing means me, for my motivation, satisfaction and design intent of real machine independence of the core super-OS. Users can create their own semantic spaces by using WFL and the standard modern high level lang blocks while the MINT and Algol elements are my private programming of DCP/MCP not meant for user consuption but visible to satisfy transparency requirements.

Procedural WFL is translated from source text to A60/C, then compiled and linked to the Barton machine, or directly interpreted by genie or MINT. Non-WFL blocks are compiled and bound and used in the concrete context of the DS which they form as extensions of the WFL/B machine.

'JCL' means things defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general end use procedures are meant to be in Algol dialects. I dont mean it to be an acronym being both more general than job control and serving as the macro assembler of MCP. MCP thus maintains a distinction between what it and the host machine directly interpret.

A Smalltalk code set is part of the system concept and a "WFL workframe" is intended as an IDE and GUI for DCP/MCP (DGUI/SPO) but it is not required for ops and will not be available until I've worked it on the basis of the experience of the first working clusters.

The namestyles are in homage to MCP and VM/CMS mainframe OSes, both still in use and Unisys and VM/CMS are trademarks of the IBM and Unisys corporations, respectively. DS MCP as an actually delivered OS is composed of cells (containers) and OS images (nodes) running system services and jobs with original code in the KEE langs supported by lower level apps runnable on a nodes kernel OS.

The Abydos Kings List   c. -400   to   1400   公元,   Menes — Seti I

---