Allows you to start and stop a NameServer and check the operational status of a NameServer that is located on either a local or remote NameServer instance. Unlike OpenEdge Management or OpenEdge Explorer, the NSMAN utility does not support a means to view log files or delete configured NameServer instances.
This parameter is required. It specifies the name of the NameServer.
-kill
Stops and removes the NameServer from memory, no matter what it is doing.
-start
Starts the NameServer.
-stop
Tells the NameServer to stop itself.
-query
Queries the NameServer for its status.
-host host-name
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.
-user user-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.
Windows supports three different formats for user-name:
A user name as a simple text string, such as "mary", implies a local user whose user account is defined in 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.
-port port-number
Specifies the port number of the machine on which the AdminServer is running. If a port number is not specified, it defaults to 20931.
A user name as a simple text string, such as "mary", implies a local user whose user account is defined in the local Windows server machine, which is the same machine that runs the AdminServer.