Google
 

Trailing-Edge - PDP-10 Archives - cuspbinsrc_1of2_bb-x128c-sb - 10,7/declar/declar.rnh
There are no other files named declar.rnh in the archive.
.;COPYRIGHT (c) DIGITAL EQUIPMENT CORPORATION 1984,1988.  ALL RIGHTS RESERVED.
.;
.;
.;THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
.;ONLY  IN  ACCORDANCE  WITH  THE  TERMS  OF  SUCH LICENSE AND WITH THE
.;INCLUSION OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE OR ANY  OTHER
.;COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
.;OTHER PERSON.  NO TITLE TO AND OWNERSHIP OF THE  SOFTWARE  IS  HEREBY
.;TRANSFERRED.
.;
.;THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT  NOTICE
.;AND  SHOULD  NOT  BE  CONSTRUED  AS A COMMITMENT BY DIGITAL EQUIPMENT
.;CORPORATION.
.;
.;DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY  OF  ITS
.;SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY DIGITAL.
.rm72
[DECLARE.HLP	17-June-1988]
.s1
The DECLARE program allows a user to manipulate user-defined commands.
.s1
The syntax to define a command is:
.s1.i8
NAME=FILESPEC
.BR
or
.I8
NAME/UNIQUE:n=FILESPEC
.br
where "n" can be any of 1, 2, 3, 4, ALL, or NONE, or a list of any of these
values enclosed in parentheses, as in (1,2,4).
.s1
or
.i8
NAME/AUTOPUSH=FILESPEC
.br
or a combination of the above.
.s1
When a command has been defined, the monitor will from then on search
the user's command table in parallel with the monitor command table. In
the case of conflicts, exact definitions are given precedence, and in the
case of conflicts within this, the user's commands are given precedence.
.s1
In the case of conflicts arising from an abbreviation being given, the monitor
re-searches its own command table without searching the user's command table,
and if it finds a unique match, it will use it.
.s1
A user may define "uniqueness" for a command, which the monitor will behave
as if the command had been given an exact definition for that many characters.
.s1
Examples:
.s1.lit
	.DECLARE TECO=SYS:STECO
	.TECO	;Will run SYS:STECO
	.TEC	;Will run SYS:TECO (Monitor overrides in the case of abbrev.)
	.TE	;Will run SYS:TECO
However,
	.DECLARE TECO/UNIQUE:2=SYS:STECO
	.TECO	;Will run SYS:STECO
	.TEC	;Will run SYS:TECO (Monitor command has /UNIQUENESS:3)
	.TE	;Will run SYS:STECO
	.T	;Will say ?T? since even the monitor commands conflict
And,
	.DECLARE TECO/UNIQUE:(2,3)=SYS:STECO
	.TECO	;Will run SYS:STECO
	.TEC	;Will run SYS:STECO
	.TE	;Will run SYS:STECO
	.T	;Will say ?T? as before
.el
.lm0.s1
Note that most programs will only recognize a very few command names, and
should be invoked only with such a command name.  For example, to run CRSCPY
via a command, the command must be "CRSCPY" or some abbreviation thereof.
.s1
Other options allowed by this program are:
.s1
/AUTOPUSH
.LM16
When this switch is given on a command definition, it causes that command
to do an auto-push, thus causing that command to leave the previous core
image intact. This feature is dependent upon having context service (CTXSER)
loaded in your monitor. CTXSER is loaded by default.
.b
However, a command which is run via an auto-push cannot change TMPCOR,
pathological name definitions, or command definitions
for your job. Thus, many programs will not
perform as expected if they are run via an auto-push command.
.s1.lm0
/CLEAR
.lm16
Clear all user defined commands. This is a standalone switch.
.s1.lm0
/LIST
.lm16
Lists the command names that the user currently has defined. This
is also a standalone switch.
.s1.lm0
/KILL
.lm16
This switch will remove the definition of a command. This switch also
requires a COMMAND NAME.
.s1.lm0
/SORT
.lm16
Sorts the commands that the user currently has defined. Sometimes this is
necessary due to the way the monitor scans the command tables. This is a
standalone switch.
.s1.lm0
DECLARE name
.lm16
Lists the full definition for the command "name".
The command name may contain wildcards, in which case any matching
user-defined commands will have their definitions listed.