NSMAN utility

Use the NSMAN utility to control the operation of a configured NameServer. The utility allows you to start a NameServer, query its status, and shut down a NameServer.

Syntax

Operating System	Syntax
UNIX Windows	nsman { { -name name-server { -kill \| -start \| -stop \| -query } [ -host host-name -user user-name\| -user user-name ] [ -port port-number] } \| -help }

Parameters

Specifies the name of the NameServer. This parameter is required.

Stops and removes the NameServer from memory, no matter what it is doing.

Starts the NameServer.

Tells the NameServer to stop itself.

Queries the NameServer for its status.

Specifies the name of the machine where the AdminServer is running. If a host name is not specified, it defaults to the local host name.

Specifies a user name and prompts for a password. A user name and password are required only when you use the -host parameter and specify a remote host name. If you specify a remote host name with the -host parameter, but do not specify a user name with the -user parameter, you receive a prompt for a user-name and password.

Specifies the port number of the machine on which the AdminServer is running. If a port number is not specified, it defaults to 20931.

Displays command-line help.

Notes

A single NameServer can simultaneously support all of the AppServer, WebSpeed, and DataServer products.

When you specify a user name with the -user parameter, Windows supports three different formats:

A user name as a simple text string, such as "mary," implies a local user whose user account is defined on the local Windows server machine, which is the same machine that runs the AdminServer.

A user name as an explicit local user name, in which the user account is defined on the same machine that runs the AdminServer, except the user name explicitly references the local machine domain, for example ".\mary".

A user name as a user account on a specific Windows domain. The general format is Domain\User, in which the User is a valid user account defined within the domain and the Domain is any valid Windows Server, including the one where the AdminServer is running.