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).
1 – example
The following command creates a clerk on node .mfg.umbriel. dns> create node .mfg.umbriel dns clerk
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).
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 – 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 – 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 ])}