[ 3 4 4 , 6 1 ] R E A D M E . 1 S T CCL VERSION 9.1A This version of CCL is essentially a maintenance release for V9.1. A few bugs have been fixed; most notably several typographical errors in SPAWN.MAC. At this point in time, it is still impossible to support long command lines in "flying-install" requests under Mplus. The problem lies in the fact that M still used a command queue for external tasks with list head @$MCRCB while Mplus now puts all command lines out in secondary pool. Building a privileged CCL under Mplus V2.x provides NO advantages, and should be considered an invalid option. A privileged CCL DOES have advantages for all M versions and Mplus V1.0. Some refinements have been made to CCL when its installed as an alternate CLI. Specifically, if CCL was installed with a non-proto-type taskname (eg. NOT ...CCL) there was a problem in not having correctly assigned the TI: device as the task processes commands from multiple terminals; this has been corrected. Another problem has been resolved in that CCL may issue a "syntax error" type message for a command line, but the parent task spawning the command line would not be notified until CCL exitted. This was typically a short (to 0) delay as long as CCL was assigned to a single terminal (installed with proto-type task name). This version now correctly "EMITS STATUS" to any parent when errors in processing a command are detected. Four new symbols are defined at task build time to improve customizing CCL; CCLCA1/CCLCA2 and CLICA1/CLICA2 define the RAD50 task names for the task CCL should chain to when a command match cannot be found. CCLCA1/CCLCA2 control the task CCL chains to when it's installed as ...CA.; CLICA1/CLICA2 control the task CCL chains to when it's installed as an alternate CLI. Typically, CCLCA1/CCLCA2 are defined as ...CA0, and CCL tasks installed as ...CA0-...CA8 will still automatically attempt to chain to the next higher level catchal, eg. ...CA0 -> ...CA1, ...CA4 -> ...CA5. CLICA1/CLICA2 are normally directed to "MCR...". Setting CCLCA1 and/or CLICA1 to 0 will disable chaining to any catchall task. A major new feature has been included with CCL in this release...Alternate CLI support for MV3.2/MplusV1.0. While more constrained than DEC's implementation, as much functionality has been retained to provide a useful tool for users locked into these older versions of M/Mplus. Consult ALTCLI.DOC(RNO) for a full description of how alternate CLIs may be installed on these systems. A proto-type CLI has been included, CLIDSP, along with command procedures to customize CCL to work with this "command dispatcher" task. A major design goal in implementing this functionality was that NO SYSGEN be required !!! To start blindly, use @ALTCLI. FORTRAN entry points have been included for all the alternate CLI routines required (EMST/GCCI/RPOI), but I have not had time to code a quick FORTRAN CLI to see if it can fit in the 12Kw address space of a privileged task. Use of these routines, particularly EMIT-STATUS and REQUEST- PASS-OFFSPRING-INFORMATION, is not restricted to CLI tasks, but as presently coded do require the task to be privileged ans map the executive. If anyone is interested in re-working these routines so they can be added to RSX's system directives, I will be glad to provide any support required. Because of changes in my working environment, I do not have ready access to M V3.2 or Mplus V2.x. Because of this, many of the optional patches discussed in ALTCLI.DOC could not be tested (as was the case for the last release when the problem of building a privileged CCL under Mplus V2.x went undetected). I would greatly appreciate hearing, and will respond as best I can, to any problems or new features that should be incorporated into future releases of CCL. For instance, anyone in the user community interested in layering in command line recall/editing with CCL???? If you can provide me with the line editor code, I can work out the rest. Paul Sorenson American Electric Power/Operations Control Systems 1 Riverside Plaza Columbus, OH 43215 (614)-223-3833