Some of you have complained that SET HOST doesn't work properly
from KIM, giving CLI errors about "can't parse REST" and so on.  Some of
you haven't.  Some of you just haven't found out about it yet.

	The culprit is that they apparently changed the command tables
and did away with the entity REST, and implemented the SET HOST command
differently.  Unfortunately, we don't all use the command tables that
come with the operating system.  Specifically, if you use C for the 68000,
you execute a command file which loads a different set of command tables,
which were built on a different base of DEC's command tables.  This has been
fixed--I rebuilt the tables to use the V4.4 command tables.

	So, the next time (after now) that you log in, executing the
CDEFS command file won't blow away your SET HOST command.  Also, you'll
be able to use the new commands available with V4.4;  They are:

CALL, SUBROUTINE, ENDSUBROUTINE:  CALL is like an @samefilename, and
requires a label (like a goto).  That label must be followed by a
SUBROUTINE statement (command) which turns the rest of the line after the
call into parameters (starting with P1).  Subroutines are terminated
by an EXIT or ENDSUBROUTINE command.  If a SUBROUTINE command is
encountered through a GOTO or falling into it, everything between the
SUBROUTINE and the matching ENDSUBROUTINE is ignored.

GOSUB and RETURN: GOSUB works like it does in Basic:  It does a GOTO and
remembers where to come back when a RETURN is encountered.  A CALL defines
a new procedural level.

There is also a new command SET SYMBOL/SCOPE=([NO]LOCAL,[NO]GLOBAL) which
makes (higher-level-local, global) symbols [in]accessible to this procedural
level (and all levels invoked from within this level).  As a procedural
level is exited, the global level is restored to what it was at the time
that level was entered, so that deeper-nested po
procedures can't modify the global accesibility on their callers.
Setting symbol scope off makes the symbols undefined for that procedural
level, without trashing them for lesser-nested levels.

	If this message sounds as jumpy as I expect it to, I apologize; I
was interrupted while I sent it.  Ask me (by mail) if you want it clarified.

sas

'MONITOR' doesn't work if I run my CDEFS file which I have duplicated
below. Am I using the current versions of what I need to run?

	Thanks,

		Jed

$ USER$_FILE_DEFEXT :== .ASM

$ @sys$sysdevice:[C68r3v1.com]cdefs.com

$ CSYM		:== $SYS$SYSDEVICE:[UTILITIES.EXE]GENSYM.EXE
$ CMAP 		:== GSMAP

$ NCC		:==$SYS$SYSDEVICE:[GREEN.1v7v1]CC68

$ cxr*ef 	:== $ sys$sysdevice:[general]cxref

$ lnk		:== @lnk.com
$ lnkvg		:== @lnk_vgtst.com

$ HEX		:== TYPE TC68.HEX
$ SYM		:== TYPE TC68.SYM
$ EEX		:== $ utl$exe:nextek/b=0FFFFA000 [MARGOLIN.TMS320]TMS320
$
$ QDF		:== $UTL$EXE:QDF

$ LTO*OL	:== $UTL$EXE:LTOOL

$ EXIT