1 – child
Creates a child pointer at the master replica of the parent
directory. When DECdns looks up a name in the namespace, it uses
child pointers to locate directory replicas.
SYNOPSIS
CREATE CHILD child-name CLEARINGHOUSE clearinghouse-name
ARGUMENTS
child-name
The full name of the child pointer.
clearinghouse-name
The name of a clearinghouse that contains a replica of the child
directory.
NOTE
The create child command should be used only to re-create a
child pointer that was accidentally deleted.
ACCESS RIGHTS
You must have read access to the orphaned child directory and
write access to parent directory of the orphaned child
directory.
PRIVILEGES REQUIRED
You must have system administrator's privileges.
1.1 – example
The following command creates the child pointer for the .sales.east directory in the .ny_ch clearinghouse. dns> create child .sales.east clearinghouse .ny_ch
2 – directory
Creates a directory. The master replica of the new directory is
stored in the same clearinghouse as the master replica of the parent
directory unless you specify otherwise.
SYNOPSIS
CREATE DIRECTORY directory-name
[CLEARINGHOUSE clearinghouse-name]
Arguments
directory-name
The full name of the directory.
clearinghouse-name
The name of the clearinghouse where the directory is created.
ACCESS RIGHTS
You must have write access to the clearinghouse in which you are
creating the new directory and write access to the parent of the new
directory.
2.1 – example
The following command creates a new directory named .region1 and stores it in a clearinghouse named .eng_ch1 rather than in the same clearinghouse as the master replica of the parent directory. dns> create directory .region1 clearinghouse .eng_ch1
3 – dns
3.1 – clerk
Creates a clerk on the specified node. You can also enter this
command through the NCL interface. This command should not
normally be executed outside of the DECnet startup procedure.
SYNOPSIS
CREATE [NODE node-id] DNS CLERK
Argument
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
NOTE
To create a clerk on a VMS system, enter the
@SYS$STARTUP:DNS$CLERK_STARTUP command from the VMS system
prompt. You must have the NET$MANAGE rights identifier to
execute this command. You can only use the command locally;
you must be logged into the system where the clerk resides.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.1.1 – example
The following command creates a clerk on node .mfg.umbriel. dns> create node .mfg.umbriel dns clerk
3.1.2 – known_namespace
Adds a namespace to the list of namespaces cached by a specified
DECdns clerk.
SYNOPSIS
CREATE [NODE node-id] DNS CLERK
KNOWN NAMESPACE name NSCTS nscts
Arguments
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
name
A simple name for the namespace.
nscts
The value of the namespace creation timestamp (NSCTS) that is
automatically assigned when the namespace is created. The format
of the NSCTS is 14 pairs of hex digits (xx-xx).
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.1.2.1 – example
The following command adds the namespace with the name jns and NSCTS value of 08-00-2B-0D-C0-9D-CD-3B-C6-16-EC-3B-94-00 to the list of namespaces cached by the local clerk. dns> create dns clerk known namespace jns NSCTS - _> 08-00-2B-0D-C0-9D-CD-3B-C6-16-EC-3B-94-00
3.1.3 – manual_nameserver
Creates knowledge in the local clerk's cache about a server that
exists across a wide area network (WAN).
SYNOPSIS
CREATE [NODE node-id] DNS CLERK
MANUAL NAMESERVER name TOWER TowerSet
Arguments
node-id
The name of the node on which the clerk exists. If you do not
specify a node name, the local node is assumed.
name
A simple name for the manual nameserver. The name is used only as a
handle for managing this entity.
TowerSet
The DNA TowerSet address of the server node. (You must use a
continuation character (-) for commands that extend beyond one line
of text, but this only works if it is the very last character on the
line of text.) The format of a TowerSet is:
{([DNA_OSInetwork , nsap-value ])}
Description
This command creates knowledge in the local clerk's cache about a
server that exists across a WAN. It gives the clerk the information
it needs to contact the server across a WAN and cache the other
information that the clerk needs to communicate with that server.
You can also enter this command through the NCL interface.
NOTE
You should not normally enter this command from DNSCP. You can
use the configuration program to accomplish what this command
does.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.1.3.1 – example
The following command informs the clerk on node .mfg.umbriel about
the existence of the server nrl.
dns> create node .mfg.umbriel dns clerk manual nameserver nrl tower -
_> {([ DNA_OSInetwork , 49::00-04:AA-00-04-00-6A-11:20 ])}
3.2 – server
Creates a server on the specified node. The server software
must be installed on the target node. You can also enter this
command through the NCL interface. This command should not
normally be executed outside of the DECnet startup procedure.
SYNOPSIS
CREATE [NODE node-id] DNS SERVER
Argument
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
NOTE
To create a server on a VMS system, enter the
@SYS$SSTARTUP:DNS$SERVER_STARTUP command from the VMS system
prompt. You must have the NET$MANAGE rights identifier to
execute this command. You can only use the command locally;
you must be logged into the system where the server resides.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.2.1 – example
The following command creates a DECdns server on the local node. dns> create dns server
3.2.2 – clearinghouse
Creates a clearinghouse on the specified node. You can specify
the directory version, the initial replica to be stored in the
clearinghouse, and the filename. This command is useful after moving
a clearinghouse or if you have moved the clearinghouse file. You can
also enter this command through the NCL interface.
SYNOPSIS
CREATE [NODE node-id]
DNS SERVER CLEARINGHOUSE clearinghouse-name
[NEW DIRECTORY VERSION version-number,]
[INITIAL REPLICA replica-name,] [FILE filespec]
Arguments
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
clearinghouse-name
The full name of the clearinghouse.
version-number
The DECdns version number the new directories will have at this
clearinghouse. Specify the value as Vx.y.z, where x defines the
major release number, y specifies the minor version number, and z
specifies an ECO level. This argument is optional. Set the value to
V1.0.0 if you intend to create DNS Version 1 directories. Set it to
V2.0.0 to create only DECdns Version 2 directories. If you omit this
argument, the default is V2.0.0.
replica-name
The full name of the first directory replica to store in the
clearinghouse. This argument is optional. If you omit this argument,
the parent directory of this clearinghouse becomes the initial
replica.
filespec
A file specification that will contain the clearinghouse. This
argument, which is optional, is useful if you have moved an existing
clearinghouse and do not want new default names to be generated
automatically. On ULTRIX systems, the default is /var/dss/dns. On
VMS systems, the default is the default directory for the DNS$SERVER
account.
NOTE
This command is normally executed only by the DECdns
configuration program during the configuration of a
DECdns server in an existing namespace. You should
use this command only to re-create a clearinghouse
whose database files are relocated on another server
system.
ACCESS RIGHTS
The account executing the command needs write access to the
directory in which you want to name the clearinghouse. This
access must be propagated to all members of the directory's
replica set before you enter this command. Otherwise, the
command fails.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.2.2.1 – example
The following command creates a clearinghouse named .sales.ny_ch on node .sales.orion. dns> create node .sales.orion dns server clearinghouse .sales.ny_ch
4 – group
Creates a group.
SYNOPSIS
CREATE GROUP group-name
Argument
group-name
The full name of the group.
ACCESS RIGHTS
You must have write access to the directory in which you intend to
create the group.
4.1 – example
The following command creates a group named .sales_group1 in the directory .sales. dns> create group .sales.sales_group1
5 – link
Creates a soft link and optionally specifies an expiration time and
an extension time.
SYNOPSIS
CREATE LINK link-name DESTINATION destination-name
[EXPIRATION expiration-time] [EXTENSION extension-time]
Arguments
link-name
The full name of the soft link.
destination-name
The full name of the entry to which the soft link points.
expiration-time
A date and time after which DECdns checks for existence of the soft
link's target and either extends or deletes the soft link. The value
is specified as yyyy-mm-dd-hh:mm:ss. This argument is optional.
If you omit the argument, the soft link is permanent and must be
explicitly deleted.
extension-time
A period of time in which to renew the soft link's life if it
expires but still points to an existing name. The value is specified
as ddd-hh:mm:ss. This argument is optional. The default is 000-00:00:00.
ACCESS RIGHTS
You must have write access to the directory in which you intend to
create the soft link.
5.1 – example
The following command creates a permanent soft link named .sales.asia.price-server that points to an object entry named .sales.eur.price-server. dns> create link .sales.asia.price-server destination - _> .sales.eur.price-server
6 – object
Creates a new object entry. This task is usually done through a
client application.
SYNOPSIS
CREATE OBJECT object-name DNS$Class class-name
DNS$ClassVersion value
Arguments
object-name
The full name of the object entry.
class-name
The class of object entry being created. You can specify an
application-defined class name. A class is specified as a simple
name limited to 31 characters.
value
The version of the class assigned to the object. Specify the value
as v.n, where v defines the major release number and n specifies
the minor version number. Specifying a class version is useful for
allowing the definition of a class to evolve as an application is
revised.
ACCESS RIGHTS
You must have write access to the directory where you intend to
store the object entry.
6.1 – example
The following command creates an object entry named .sales.east.floor1ln03 with the DNS$Class printer and DNS$ClassVersion value 1.0. The object entry describes an LN03 printer on the first floor of the company's eastern sales office. dns> create object .sales.east.floor1ln03 DNS$Class printer - _> DNS$ClassVersion 1.0
7 – replica
Adds a replica of an existing directory to the specified
clearinghouse. You are creating a read-only replica, which is a
copy of the directory to which users cannot make changes.
SYNOPSIS
CREATE REPLICA directory-name [AT] CLEARINGHOUSE
clearinghouse-name
Arguments
directory-name
The full name of the directory.
clearinghouse-name
The full name of the clearinghouse in which you want to create the
replica.
ACCESS RIGHTS
You must have read, write, delete, and control access to the
directory you are replicating. You also need write access to that
directory's parent directory, and write access to the clearinghouse
in which you are storing the replica.
7.1 – example
The following command creates a replica of the .mfg directory in the clearinghouse .paris1_ch: dns> create replica .mfg at clearinghouse .paris1_ch