Modifying the nsdstart Script

Previous Topic | Next Topic | Contents | Index
Getting Started Guide | Programmer's Guide | Reference Guide

Subtopics

To add a NonStop DOM application server pool to an existing PATHMON process, you can follow the procedures you use to add a server pool to the PATHMON process that's running the NonStop DOM system. Removing a server pool process is similar in nature.

With the NonStop DOM system, you add and remove sever pool processes by editing the nsdstart script. This is described in the following subtopics using the Comm Server as an example server pool process. Follow similar procedures to add and remove server pools from other PATHMON processes, such as the ones running your application servers.

Note: Changing the settings of the NonStop DOM PATHMON process requires that you make a parallel change to the NonStop DOM system configuration database.

Also be aware that you cannot alter the server pool settings in a running PATHMON process; you must first shut down the process.

Adding a Server Pool Process by Editing nsdstart

Assume that the currently running NonStop DOM system includes two Comm Servers named $ZC01 and $ZC02, and you want to add a third Comm Server process named $ZC03.

Note: The examples in this section assume that you have set MY_PREFIX in the env.sh script equal to the value Z.

1. If NonStop DOM system processes are running, stop them by executing the nsdstop script from OSS:

   > nsdstop

2. Locate the Comm Server specification section in the nsdstart script. The following example shows the section of nsdstart that configures the Comm Servers with two processes:

   Configuring Two Comm Servers

   #... COM_SERVER1="$MY_PREFIX"c01 COM_SERVER2="$MY_PREFIX"c02 #... set server maxservers 2 set server numstatic 2 set server process \$$COM_SERVER1 (cpus 1) set server process \$$COM_SERVER2 (cpus 0) set server AUTORESTART 10 add server CS start server CS #...

   
   
3. Edit this section to add another server process, $ZC03, as follows:

   Adding a Comm Server to the nsdstart Script

   #... COM_SERVER1="$MY_PREFIX"c01 COM_SERVER2="$MY_PREFIX"c02 #... set server maxservers 3 set server numstatic 3 set server process \$$COM_SERVER1 (cpus 1) set server process \$$COM_SERVER2 (cpus 0) set server process $ZC03 (2:3) set server AUTORESTART 10 add server CS start server CS #...

   
   
4. Be sure you add the new Comm Server process $ZC03 to the configuration database. See Configuring NonStop DOM and Using the Configuration Tool for details.
5. Restart NonStop DOM system processes by executing the nsdstart script from OSS:

   > nsdstart

Removing a Comm Server by Editing nsdstart

Assume that the current NonStop DOM system is configured to include two Comm Servers, named $ZC01 and $ZC02, and you want to remove the $ZC02 process.

1. If NonStop DOM system processes are running, stop them by executing the nsdstop script from OSS:

   > ndsstop

2. Locate the Comm Server specification section in nsdstart. The following example shows the section of nsdstart that configures the Comm Server, including two processes:

   Configuring Two Comm Servers

   #... COM_SERVER1="$MY_PREFIX"c01 COM_SERVER2="$MY_PREFIX"c02 #... set server maxservers 2 set server numstatic 2 set server process \$$COM_SERVER1 (cpus 0:1) set server process \$$COM_SERVER2 (cpus 1:0) set server AUTORESTART 10 add server CS start server CS #...

   
   
3. Edit this section to remove the $ZC02 server process, as follows:

   Removing a Comm Server From nsdstart

   #... COM_SERVER1="$MY_PREFIX"c01 #... set server maxservers 2 set server numstatic 2 set server process \$$COM_SERVER1 (cpus 0:1) set server AUTORESTART 10 add server CS start server CS #...

   
   
4. Remove $ZC02 from the configuration database using the Configuration Tool. If you expect to continue to receive requests from these hosts, you must either associate them with the remaining Comm Server process or rely on the dynamic association function to assign a server to the requests.
5. Restart the NonStop DOM system processes by executing the nsdstart script from OSS:

   > nsdstart

Previous Topic | Next Topic | Contents | Top
Getting Started Guide | Programmer's Guide | Reference Guide
Bibliography | Glossary | Index

© Tandem, a division of Compaq. All rights reserved. Legal notices.