	
NCP is the Network Control Program.  Commands are:

   CLEAR	LOAD	    SET		TELL	     ZERO
   EXIT		LOOP	    SHOW	TRIGGER

Most of the commands operate on network components.  The component types are:

   ALIAS	LINE	    NODE	PROCESS
   EXECUTOR	LOGGING	    OBJECT	SYSTEM

NCP will prompt for missing parameters when a partially complete command line
has been entered.  I response to these prompts, you may type an ESC character
for a brief description of what may be entered at that point.

Commands may be executed either locally or remotely at the option of the user
of NCP.  These concepts are discussed in the help for EXECUTOR.

For more help use:

   NCP>HELP command
   NCP>HELP component-type
1 ACCESS
Whenever a command implies a logical link connection, access control
information may be required.  This information may be provided either within
the command, or automatically through the use of an alias. There are two
formats for specifying access control information:

    node-id [USER user-id] [PASSWORD password] [ACCOUNT account]

    node-id[/user-id[/password[/account]]]

The access control fields (user-id, password, and account) are strings of
any characters.  In the keyword form, the fields can be in any order.  In
the slash form, the positions are fixed.  To include a blank, tab or slash
in a field, enclose the field in quotes (").  A quote within a quoted string
is indicated with a double quote ("").  User-id and account can be 0-16
characters, password can be 0-8 characters.

Some examples of equivalent access control in the two forms are:

   ELROND USER 305,317 PASSWORD SECRET
   ELROND/305,317/SECRET

   BERGIL ACCOUNT A/B PASSWORD SHHH
   BERGIL//SHHH/"A/B"
2 CONTROL
Whenever a command implies a logical link connection, access control
information may be required.  This information may be provided either within
the command, or automatically through the use of an alias. There are two
formats for specifying access control information:

    node-id [USER user-id] [PASSWORD password] [ACCOUNT account]

    node-id[/user-id[/password[/account]]]

The access control fields (user-id, password, and account) are strings of
any characters.  In the keyword form, the fields can be in any order.  In
the slash form, the positions are fixed.  To include a blank, tab or slash
in a field, enclose the field in quotes (").  A quote within a quoted string
is indicated with a double quote ("").  User-id and account can be 0-16
characters, password can be 0-8 characters.

Some examples of equivalent access control in the two forms are:

   ELROND USER 305,317 PASSWORD SECRET
   ELROND/305,317/SECRET

   BERGIL ACCOUNT A/B PASSWORD SHHH
   BERGIL//SHHH/"A/B"
1 ALIAS
An alias is an alternate name for a node.  They are specified in the forms:

   ALIAS alias-name - a specific alias.
   ALL ALIASES      - all aliases regardless of scope.
   KNOWN ALIASES    - known aliases within a scope.

The alias name is a string of 1-6 alphanumeric characters, containing at least
one alphabetic character.

Aliases are applied within a defined scope.  Whenever a node name is used, the
aliases for the appropriate scope are first searched for match.  If one is
found, the real node name associated with it is actually used instead of the
alias.

In addition to this, if a connect is being initiated, no access control
information was provided with the connect request, and access control
information is associated with the alias, the alias associated access control
information is used in forming the connection.

For more help use:

   HELP ACCESS CONTROL
   HELP ALIAS SCOPE
   HELP SET ALIAS
   HELP CLEAR ALIAS
   HELP SHOW ALIAS
2 SCOPE
Scope defines the connect requests to which an alias applies.  Scope is
specified in one of the forms:

   [SCOPE] GLOBAL
   [SCOPE] TERMINAL terminal-id

Where terminal-id is a terminal identification.

If no scope is specified for a command to the local node, the default is the
terminal that the command is from.  Scope must be specified for a command to a
remote node.

Aliases of global scope are applied to connect requests coming from programs
associated with any terminal.  Aliases of terminal scope are applied only to
programs associated with the specific terminal.  When attempting to map an
alias to a real node name, first the aliases for the terminal are searched,
then the global aliases.

Specifying scope is a privileged option.  Non-privileged users may only control
aliases for their own terminal.
1 EXECUTOR
The executor is the network node that is executing a command.  It is
specified in either of the equivalent forms:

   EXECUTOR
   NODE executor-node-id

Note that the system that is executing the command is not necessarily the
system on which the command is typed to NCP.  This is because NCP is
capable, on request, of directing commands to other nodes.

For more help use:

   HELP TELL
   HELP SET EXECUTOR
   HELP CLEAR EXECUTOR
   HELP SHOW EXECUTOR
   HELP ZERO EXECUTOR
1 LINE
A line is a hardware communications path.  They are specified in the forms:

   LINE line-id - a specific line or group of lines.
   KNOWN LINES  - all lines known to the executor.
   ACTIVE LINES - known lines in ON or SERVICE state.

A line identification is a string of 4-16 characters in one of the forms:

   device-controller
   device-controller-unit
   device-controller.tributary
   device-controller-unit.tributary

Device is an alphabetic device mnemonic, such as DMC, DA, or KDZ.

Controller is the decimal device controller number.

Unit is the decimal unit on the controller.  It is allowed only if the device
is multiplexed.

Tributary is the decimal logical tributary number.  It is allowed only if the
line is multipoint.

Controller, unit, and/or tributary may be replaced with an asterisk (*) as a
wild card to indicate all known values in that position.  A wild card cannot
be used to the left of a specific number in a line identification.

For more help use:

   HELP SET LINE
   HELP CLEAR LINE
   HELP SHOW LINE
   HELP ZERO LINE
1 LOGGING
A logging component is a sink (or destination) for logging information.  They
are specified in the form:

   LOGGING sink-type - for a specific logging sink type.
   KNOWN LOGGING     - for all sink types known to the executor.
   ACTIVE LOGGING    - for known sink types in the ON or HOLD state.

The logging sink types are CONSOLE, MONITOR, and FILE.

For more help use:

   HELP LOGGING EVENTS
   HELP SET LOGGING
   HELP CLEAR LOGGING
   HELP SHOW LOGGING
2 EVENTS
Logging events are specified in the form:    class.types

The format of types is:                      range[,types]

The format of range is:                      type[-type]

In a range, the second type must be greater than the first.  The event class
is a decimal number in the range 0-512.  An event type is a decimal number in
the range 0-31.

Some examples of event specifications are:

   Specification         Specific events included:

   4.3                   4.3
   4.3-6,9               4.3, 4.4, 4.5, 4.6, 4.9
   4.3,9-11,15,18-21     4.3, 4.9, 4.10, 4.11, 4.15, 4.18, 4.19, 4.20, 4.21

Events may be qualified by a line or node and/or sent to a remote node.

For more help use:

   HELP LOGGING EVENTS QUALIFIERS
   HELP LOGGING EVENTS SINKS
3 QUALIFIERS

Events can be qualified by a line or node.  An event which is set with a 
qualifer will only be logged if the event occurred over the specified
component.

The format for a qualifier is the same as the entity identification.

For more help use:

   HELP NODE
   HELP LINE
3 SINKS

A sink node is the node at which an event will be logged.  The event will be 
logged only if the logging state of the sink type on the sink node for which 
the event is destined is in the ON state.

All filtering of events is done at the node on which the event was generated.
The sink node will log the event whether or not that event filter has been
set up on the sink node.
1 NODE
A node is a network system that can support logical links.  They are specified
in the forms:

   NODE node-id - a specific node.
   KNOWN NODES  - all nodes seen by the executor as reachable or having a name.
   ACTIVE NODES - known nodes that are reachable.
   LOOP NODES   - nodes that are loopback paths to the executor over a line.

A node identification is either a node name or a node address.  A node name is
a string of 1-6 alphanumeric characters, containing at least one alphabetic
character.  A node address is the guarenteed network-wide unique identification
of a node and is a decimal number in the range 1-32767.

In most cases, node addresses and names may be used interchangably.

For more help use:

   HELP SET NODE
   HELP CLEAR NODE
   HELP SHOW NODE
   HELP ZERO NODE
1 OBJECT
An object is a network addressable program.  They are specified in the forms:

   OBJECT object-type - a specific object.
   KNOWN OBJECTS      - all objects known to the executor.

An object type is a decimal number in the range 0-255.

For more help use:

   HELP SET OBJECT
   HELP CLEAR OBJECT
   HELP SHOW OBJECT
1 PROCESS
A process is a control program that operates in the network system (the
Communications Executive).  They are specified in the forms:

   PROCESS process-name - a specific process.
   KNOWN PROCESSES      - all processes known to the executor.
   ACTIVE PROCESSES     - known processes that are in the ON state.

A process name is 3 alphabetic characters.

For more help use:

   HELP SET PROCESS
   HELP CLEAR PROCESS
   HELP SHOW PROCESS
1 TELL
Use the TELL prefix to send a single command to a remote node (or to the
remote command facility on the local node).  The format is:

   TELL node-id [access-control] command

This prefix on the command causes only that command to be sent to the
remote node.  It is not effected by previous commands and has no effect on
on subsequent commands.

For more help use:

   HELP ACCESS CONTROL
   HELP EXECUTOR
   HELP SET EXECUTOR NODE
1 SYSTEM
The system is the network operating environment, known as the Communications
Executive.  It is specified in the form:

   SYSTEM
1 CLEAR
@NCPCLE.HLP
1 EXIT
EXIT simply exits NCP.  It is equivalent to a ^Z.
1 LOAD
@NCPLOA.HLP
1 LOOP
@NCPLOO.HLP
1 SET
@NCPSET.HLP
1 SHOW
@NCPSHO.HLP
1 TRIGGER
@NCPTRI.HLP
1 ZERO
@NCPZER.HLP
1 NCP>

Commands are:

   CLEAR	LOAD	    SET		TELL	     ZERO
   EXIT		LOOP	    SHOW	TRIGGER

Use the HELP command to obtain complete information.

1 Account:

A string of 1-16 characters.

1 Active
2 polling
3 ratio:

A decimal number in the range 1-255.

1 Address:

A decimal node address in the range 1 to the maximum address for the executor.

1 Alias
2 name:

A string of 1-6 alphanumeric characters with at least one alphabetic character.

1 Clear
2 component:

Component types are:

   ALL ALIASES     KNOWN ALIASES      LINE             OBJECT
   ALIAS           KNOWN LINES	      LOGGING          PROCESS
   EXECUTOR        KNOWN OBJECTS      NODE	       SYSTEM

2 line
3 options:

The only option is ALL.

2 logging
3 options:

The options are EVENT, LINE, NODE or SINK. 

2 node
3 options:

Options are NAME or LINE for remote nodes, or HOST, NODE, RECEIVE PASSWORD,
or TRANSMIT PASSWORD for the executor.

2 object
3 options:

The only option is ALL.

1 Copies:

Options are SINGLE or a decimal number in the range 1-64.

1 Cost:

A decimal number in the range 1-25.

1 Command:

The command you wish to TELL the executor.

1 Component
2 type:

Options may be:

   ALIASES       LOGGING         OBJECTS
   LINES         NODES           PROCESSES

1 CSR
2 address:

An octal number in the range 160000-177776.

1 Dead
2 polling
3 ratio:

A decimal number in the range 1-255.

1 Destination
2 node:

The name or address of the destination node, optionally with access control.

1 Duplex:

Options are FULL or HALF.

1 Event
2 identification:

In the form class.types;  where class is a decimal number in the range 0-511
and types are decimal numbers in the range 0-31 separated by commas or hyphens.

For example, 4.0-4,6-13 means class 4, events 0-4 and 6-13.
1 Hexadecimal
2 password:

A hexadecimal number in the range 0-FFFFFFFFFFFFFFFF (8 bytes).

1 Host
2 node
3 identification:

A node name or address.

1 Length
2 of
3 test
4 data:

A decimal number in the range 1-65535.

1 Line
2 identification:

A line identification in the form device-controller[-unit][.tributary].
Examples are:	DMC-0, DZ-1-2, KDZ-1-2.1

2 state:

Options are ON, OFF or SERVICE.

1 Load
2 options:

Options are NODE or VIA.

2 image
3 input
4 file:

A local file specification.

1 Location
2 in
3 memory:

Options are FIRSTFIT or TOPDOWN.

1 Logging
2 sink
3 type:

Options are CONSOLE, MONITOR, FILE.

2 state:

Options are ON or OFF.

2 sink
3 node:

Options are EXECUTOR or node-id.

2 sink
3 name:

Options are valid terminal id (CONSOLE),valid task name (MONITOR),
and valid file name (FILE).

2 line
3 identification:

A line identification in the form device-controller[-unit][.tributary].
Examples are:	DMC-0, DZ-1-2, KDZ-1-2.1

2 node
3 identification:

A node name or address.

1 Loop
2 component:

Options are LINE or NODE.

1 Maximum
2 option:

Options are CONTROLLERS or LINES.

2 controllers:

A decimal number in the range 0-16384.

2 lines:

A decimal number in the range 0-16384.

1 Multipoint
2 ratio
3 type:

Options are ACTIVE or DEAD.

1 Node
2 identification:

A node address or name.

2 name:

A string of 1-6 alphanumeric characters with at least one alphabetic character.

2 state:

Options are ON, OFF, or SHUT.

1 Number
2 of
3 test
4 messages:

A decimal number in the range 1-65534.

1 Object
2 name:

A task name.
 
2 number:

A decimal number in the range 0-255.

2 user:

Options are DEFAULT or LOGIN.

2 verification:

Options are ON, OFF, or INSPECT.

1 Output
2 file/device:

A local file or device specification.

1 Owner
2 name:

Options are DLX or NSP.

1 Partition
2 name:

A partition name.

1 Priority:

A decimal number in the range 4-7.

1 Process
2 name:

A 3 character DECnet process name.

1 Scope:

Options are GLOBAL or TERMINAL.

1 Set
2 component:

Options are:

   ALIAS             LINE                   PROCESS
   EXECUTOR          LOGGING                SYSTEM
   KNOWN LINES       NODE

2 alias
3 options:

Options are SCOPE or DESTINATION.  A destination is required, a scope
may only be provided if you are privileged.

2 line
3 options:

Options are ALL or one or more of:

   CONTROLLER CSR        MULTIPOINT ACTIVE        STATE
   COST                  MULTIPOINT DEAD          TRIBUTARY
   DUPLEX                OWNER                    UNIT CSR
   LOCATION              PRIORITY                 VECTOR

2 logging
3 options:

Options are EVENT, LINE, NODE, SINK or STATE.

2 node
3 options:

Options are NAME or LINE for remote nodes, or HOST, NODE, RECEIVE PASSWORD,
STATE, TRANSMIT PASSWORD, or VERIFICATION STATE for the executor.

2 object
3 options:

Options are COPIES, NAME, USER, or VERIFICATION.

2 process
3 options:

Options are ALL or one or more of:

   LOCATION                MAXIMUM LINES
   MAXIMUM CONTROLLERS     PARTITION

1 Show
2 component:

Options are:

   ACTIVE ALIASES, LINES, LOGGING, NODES, or PROCESSES
   ALL ALIASES
   EXECUTOR
   KNOWN ALIASES, LINES, LOGGING, NODES, OBJECTS or PROCESSES
   LINE
   LOGGING
   LOOP NODES
   NODE
   OBJECT
   PROCESS
   SYSTEM

1 Sink
2 node
3 identification:

The options are EXECUTOR or node-id.

1 Terminal
2 identification:

A terminal device specification. (TTn:)

1 Text
2 password:

A string of 1-8 characters.

1 Tributary
2 address:

A decimal number in the range 1-255.

1 Trigger
2 options:

Options are NODE or VIA.

1 Type
2 of
3 test
4 data:

Options are MIXED, ONES, or ZEROES.

1 User
2 identification:

A string of 1-16 characters.

1 Vector:

An octal number in the range 0-1000.

1 Verification
2 state:

Options are ON or OFF.

1 Zero
2 component:

Options are:

   EXECUTOR           KNOWN NODES          NODE
   KNOWN LINES        LINE                 SYSTEM

