Starting Your NonStop DOM System
Stopping Your NonStop DOM System
After customizing the configuration scripts, as described in Quick Configuration, you can start the NonStop DOM system processes by running the nsdstart script.
By executing the nsdstart script, you start and configure the PATHMON system that controls the NonStop DOM system.
By default, this script assumes that your system has CPUs 0 thru 3 available. For information on customizing this section of the script, refer to the configuration section Customizing the NonStop DOM PATHMON Process.
To start the NonStop DOM system, issue the following command at your OSS shell:
> nsdstart
You can verify that this step worked by checking for the presence of the $ZNDM PATHMON process. Issue the following command to view this process:
> PATHCOM $ZNDM
Using the default script, the output should resemble the following:
$X8HA: PATHCOM - T8344D44 - (05MAY97) COPYRIGHT TANDEM COMPUTERS INCORPORATED 1980 - 1985, 1987 - 1997 =STATUS SERVER * SERVER #RUNNING ERROR INFO CS 2 ES 1 LSD 1 NS 4 = |
If an error occurs (for example, if one or more of the NonStop DOM servers does not correctly start), check the files outlined in the table below:
| Log File | Process |
|---|---|
etc/cs.log |
Comm Server STDOUT, STDERR and Trace files |
etc/es.log |
Event Service STDOUT, STDERR and Trace files |
etc/lsd.log |
Location Service Daemon STDOUT, STDERR and Trace files |
etc/ns.log |
Naming Service STDOUT and STDERR files |
<STDOUT> |
Trace file |
To terminate your NonStop DOM session, execute the nsdstop script, as shown in the following command:
> nsdstop
This command terminates the PATHMON process that runs the NonStop DOM system, effectively shutting down the ORB on which your NonStop DOM application servers run. Once you run this script, you will need to restart the NonStop DOM system if you want your application servers to receive remote client requests.