Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ tnscp(1) — TeMIP Framework 3.2A

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

tns_clerk_start(1)

tns_clerk_stop(1)

tns_start(1)

tns_stop(1)

tns_browser(1)

tns_server_setup(1)

tnscp(1)  —  Commands

NAME

tnscp − Starts the TNS control program

SYNOPSIS

tnscp

DESCRIPTION

The TNS control program, tnscp, is a command line interface with which you can manage the components of the TeMIP Name Service (TNS) and the contents of a namespace. To start the control program, enter tnscp.  For online help from within the control program, enter help at the tnscp> prompt.  To exit the control program, enter exit at the tnscp> prompt. 
 

TNS Entities

 
The TNS control program is based on commands targeted for specific entities. An entity is any individually manageable TNS component or part of the namespace.

You can manage the following entities with tnscp :
 

 
TNS Clerk

 
The clerk is the interface between TeMIP and TNS servers.

 
TNS Clerk Known Namespace

 
Known namespaces are namespaces that a clerk has discovered and cached as a result of configuration, datagrams received on a local area network (LAN), or an explicit management command.

 
TNS Clerk Remote Clearinghouse

 
Remote clearinghouses are clearinghouses that a clerk has discovered and cached. The clerk can learn about clearinghouses as a result of configuration, datagrams received on a LAN, an explicit management command, or during the process of finding a name. To the clerk, all clearinghouses are remote, even if they exist on the clerk’s own system.

 
TNS Server

 
A server handles lookup requests from clerks and maintains the contents of the clearinghouse or clearinghouses at its node.

 
TNS Server Clearinghouse

 
The TNS Server Clearinghouse entity represents a collection of directory replicas on a TNS server. Commands directed to this entity manage attributes of the clearinghouse and perform management functions such as enabling or disabling the clearinghouse.

 
Child

 
Child pointers connect parent and child directories in a hierarchical namespace. They are stored in the parent directory.

 
Clearinghouse

 
A clearinghouse is a database containing a collection of directory replicas on a particular server. Commands directed to the Clearinghouse entity manage TNS attributes of the clearinghouse (for example, its ACS).

 
Directory

 
A directory contains objects and other namespace entries that are logically stored under one name (the directory name).

 
Group

 
Groups let you assign a uniform set of access rights to several users at once.  They do this by mapping a set of names representing the group members to a single name (the group name).

 
Link

 
Soft links are pointers providing an alternate name for an object, directory, or other soft link.

 
Object

 
An object represents a resource (for example, a TeMIP director, or TeMIP domain or SNMP global entity) that is named in the namespace.

 
Replica

 
A replica is a copy of a directory. Each copy, including the original, or master, is a replica.

 
Subtree

 
A subtree is a specific directory and its contents, or a hierarchy of directories and their contents.
 
 

Attribute Groups

 
Every TNS entity has attributes, which are pieces or sets of data associated with that entity. Attributes fall into one of four categories:
 

IdentifiersUniquely distinguish an entity from any other entity. 

CharacteristicsReflect or affect the operational behavior of an entity. Some characteristics are static and cannot be modified; others can be modified with tnscp commands. 

CountersRecord the number of times a particular event or problem occurred since the entity was last enabled.  Counters are maintained only by clerks, servers, clearinghouses, and remote clearinghouses. 

StatusReflect the current operational state of an entity. Status attributes are maintained only for clerks, servers, and clearinghouses. 
 

Prepositional Phrases

 
Most tnscp commands accept optional prepositional phrases that can affect the destination and content of command output. Generally these phrases are  most useful with the show and directory commands.  The tnscp online help for individual commands describes prepositional phrases where their use is most appropriate. 

You may use as many prepositional phrases as you want, being sure to precede each phrase with a comma.  The following is an overview of the prepositional phrases:
 

, with attribute [relop] valueLimits a directive only to those entities whose attributes have certain values.  If you do not specify a relop (relational operator), the default is an equal sign.  Other valid relational operators are greater than (>), less than (<), greater than or equal to (>=), and less than or equal to (<=).  If you specify multiple with phrases in a command, the target entity must satisfy all of them to be selected.  This phrase works only with commands that can operate on multiple items at a time (such as show and directory commands). 
 

, to file=filenameRedirects the output to a file specified in filename.  If the file does not exist, this command creates it. 

, to extend file=filenameAppends the output to an existing file specified in filename. 

, to terminalDirects the output to the terminal.  This is the default option. 
 

RELATED INFORMATION

Additional information is available from the tnscp Help system. 
 

RESTRICTIONS

tnscp must be run under super-user to manage the TNS Clerk ∗ and TNS Server ∗ entities. 
 

FILES

/usr/sbin/tnscp -
Specifies the command path

 

SEE ALSO

tns_clerk_start(1), tns_clerk_stop(1), tns_start(1), tns_stop(1), tns_browser(1), tns_server_setup(1). 

TeMIP Utilities

TNS Administration Guide
 

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026