9.1;ctnode (catalog_node), revision 9.1, 85/05/16
CTNODE (CATALOG_NODE) -- Catalog a node in the network.
usage: CTNODE {node_name [net.]node_id [-ROOT] | -N [net.]node_id | -UPDATE}
[[-FROM //node... [-MD|-MS]]
[-ON //node...] [-R] [-L] [-IDUPL]
[-LC] {CL}
FORMAT
CTNODE [node_name [net.]node_id ...] [options]
CTNODE informs the local node that a remote node exists, thereby enabling
network file access to the remote node. The command catalogs the node_name in
the local copy of the network root directory as the entry directory for the
remote node. In other words, CTNODE adds the directory //node_name to your
copy of the network root directory. For information on deleting a node_name
entry, type HELP UCTNODE.
We assign a node ID to every node during the manufacturing process. To find
out the node ID of a node, type the following command at its keyboard:
$ lcnode -me
At SR9.0, CTNODE supports the ability to merge information from another node's
network root into your own, or any other node's network root. The merge
options (-MD and -MS) add the entry for a node to the target provided the
entry does not already exist and the source has exactly one entry for that
node. In the case of one source and one target entry for a node which match,
those entries are assumed to be correct. All other cases are considered to be
ambiguous and the "confusion resolution protocol" is invoked.
This "confusion resolution protocol" first attempts to verify the correct
entry name with the node itself. If the node is available, then the reply
from the node is cataloged regardless of whether -MD or -MS is used. This is
because an answer from the node itself is assumed to be the truth.
If the node is unavailable to resolve an ambiguity, then the entry containing
the most recent UID (latest time stamp portion of the UID), is used. In this
case, existing entries in the target directory are only updated if the -MS
option is used.
ARGUMENTS
node_name
(optional) Specify the name of the node you wish to catalog. If the
'[net.]node_id' argument is specified, then 'node_name' is
required.
Default if omitted: must use -N, -UPDATE, or -FROM
[net.]node_id
(optional) Specify the hexadecimal ID (and optional network ID) of the
node you wish to catalog. The node must be connected to
the network when this command is executed. If the
'node_name' argument is specified, then 'node_id' or
'net.node_id' is required.
Default if omitted: must use -N, -UPDATE, or -FROM
Multiple name/ID pairs are permitted.
OPTIONS
If neither -N, -UPDATE, or -FROM is specified, then the 'node_name' and
'[net.]node_id' arguments are required. The -N, -UPDATE, and merge options
work only for remote nodes running AEGIS SR5.0 or later. The '[net.]node_id'
forms work only when both the local and remote nodes run AEGIS SR9.0 or later.
-ROOT Catalog 'node_name' as the entry directory name for
'node_id' in both the master network root directory and the
local copy of the network root directory. This option is
valid only if the 'node_name' and 'node_id' arguments are
specified. This option is not valid if the -N option is
specified.
-N [net.]node_id...
Copy the entry directory name from the network root
directory of the specified remote node, to the network root
directory of the local node. You do not need to know the
entry directory name. However, you must specify the
node_id or the net.node_id of the remote node. Multiple
node_id's and net.node_id's may be specified. Use this
option instead of the 'node_name'/'[net.]node_id' argument
pair. This option is not valid if the -R option is
specified.
-UPDATE Obtain a list of nodes currently responding to a network
inquiry and perform the same operation as "-N" for each
node. Names are replaced with the most current version, if
they already exist in your local copy of the network root
directory, and new names are added.
-FROM //node ...
Look in the specified list of network root directories for
the names to add to the target network root, or use this
network root as the source for names to merge into the
target network root. Wildcards may be used to specify
source node names. The -FROM option is not supported in a
DOMAIN internet enviroment.
-MD Used with -FROM. Merges all names in the source network
root into the target network root. Preference is given to
existing names in the target if there are unresolved
conflicts (see the discussion of "confusion resolution
protocol" above).
-MS Same as -MD, except that preference is given to entries in
the source network root when there are unresolved conflicts
(see the discussion of "confusion resolution protocol"
above).
-ON //node ...
Catalog names in the network root of the specified nodes
instead of the local network root. Wildcards may be used
to specify target node names. The -ON option is not
supported in a DOMAIN internet enviroment.
-R Replace cataloged names if they already exist. An error
occurs if you do not specify this option and try to add a
node_name that has already been cataloged (unless you are
using -UPDATE).
-L List node names as they are cataloged.
-IDUPL Ignore entry (suppress error messages) if name already
exists in the target.
-LC List invocations and resolutions of the "confusion
resolution protocol".
This command uses the command line parser, and so also accepts the standard
command options listed in HELP CL.
EXAMPLES
1. $ ctnode os 21 Add the node whose ID is 21 and whose entry
directory name is "os" to your node's catalog.
2. $ ctnode -update Bring your node's catalog up to date with any
new nodes on the network.
3. $ ctnode os eve -from //master
Copy names "os" and "eve" from the network
root on //master.
4. $ ctnode os 21 -on //a?*
Add node ID 21 with the name "os" to
the network root of all nodes whose names
begin with "A".
5. $ ctnode -md -from //os
Merge network root of OS into local network
root, resolving conflicts.