About the PATHMON Process
Using Scripts to Start and Stop NonStop TS/MP
Using the nsdstart Script
Using the nsdstop Script
This topic describes how to start and stop the NonStop DOM system and its application server processes using the scripts provided with the system.
NonStop DOM system server processes are configured using the services of NonStop TS/MP. Processes defined through NonStop TS/MP run under the control of a NonStop TS/MP monitor, the PATHMON process. PATHCOM provides the interface to the PATHMON process.
To configure and start processes running under NonStop TS/MP, you must follow a specific, sequential set of steps in the Guardian environment. The nsdstart script provided with NonStop DOM automates these steps. Although you run nsdstart from the OSS shell, the script executes the following set of Guardian commands from the OSS environment:
A NonStop TS/MP environment that is configured and started with the env.sh and nsdstart script files can be shut down in an orderly manner at any time after Step 5 above.
For details on the PATHMON process and the PATHCOM commands used in the scripts, refer to the NonStop TS/MP System Management Manual.
Note: NonStop DOM system processes are configured and deployed through the services of NonStop TS/MP. Tandem strongly recommends that you also configure and deploy your application server processes through the services of NonStop TS/MP.
NonStop DOM provides the nsdstart OSS shell script to execute a set of commands that create a NonStop TS/MP environment and start the NonStop DOM processes. Another shell script, nsdstop, terminates the NonStop TS/MP environment and any running processes. These scripts can be found in the bin directory of your NonStop DOM setup.
Some of the sample applications provided with NonStop DOM have custom scripts that create, start, and stop NonStop DOM application server processes under the control of a PATHMON process. These scripts are located in the subdirectories of the associated sample applications. If you wish, you can modify these scripts to configure, start, and stop your own application server processes.
Note: Separate sets of scripts are provided because it is strongly recommended that you create two unique NonStop TS/MP environments: one for your NonStop DOM system processes, and another one for any application processes you want to implement using NonStop TS/MP.
Each unique NonStop TS/MP environment is controlled by a unique PATHMON process. If your environment includes many complex applications, you may want to configure additional PATHMON processes in more NonStop TS/MP environments. See the NonStop TS/MP System Management Manual for guidelines.
Each time it is executed, the nsdstart script:
The nsdstop script:
Scripts enable you to start or stop an entire configuration by executing a single command. Thus, if you need to change the global parameters in your NonStop TS/MP configuration, you might edit them in the nsdstart file and then execute the script. (If your NonStop DOM system is running, you must execute the nsdstop script before restarting the system with the nsdstart script.)
On the other hand, if you need to restart a NonStop TS/MP configuration whose global configuration parameters have not changed, you can do so using PATHCOM, the interface to the PATHMON process. Similarly, if you need to change the attributes of a single server pool or server process, you do not need to shut down the entire NonStop TS/MP environment. You can modify one or more server processes more efficiently using the PATHCOM interface, as described in Using the PATHCOM Interface to Maintain NonStop TS/MP Processes.
Before running nsdstart, be sure that you have sourced the env.sh file, which loads the environment settings into your OSS shell environment.
If you source the env.sh file in your .profile file, the NonStop DOM environment settings will be automatically loaded each time you enter the shell.
Normally, the nsdstart script does not offer a display as it executes. However, by supplying the -v script option with the nsdstart command, you will get a verbose listing of the script commands as it executes. The following listing shows the execution of the nsdstart script when used with the -v option:
/nsdoms> nsdstart -v $Z06T: PATHCOM - T8344D42 - (03JUN96) COPYRIGHT TANDEM COMPUTERS INCORPORATED 1980 - 1985, 1987 - 1996 = = set pathway maxassigns 8 = set pathway maxparams 8 = set pathway maxserverclasses 4 = set pathway maxserverprocesses 40 = set pathway maxstartups 40 = set pathway maxtcps 0 = set pathway maxterms 0 = set pathway maxdefines 27 = set pathway maxpathcoms 8 = set pathway maxspi 8 = set pathway maxlinkmons 16 = set pathway maxexternaltcps 0 = set pathway maxprograms 4 = = start pathway cold ! PATHWAY CONTROL FILE DATED: 25 MAR 1998, 16:44:39 = =[ configure LSD = = reset server = = set server processtype oss = set server pri 150 = set server cwd /usr/tandem/nsdoms = set server program /usr/tandem/nsdoms/bin/lsd = = set server hometerm $ztnt.#pty000a = set server stdin /dev/null = set server stdout /usr/tandem/nsdoms/log/lsd.out = set server stderr /usr/tandem/nsdoms/log/lsd.out = = [ set server debug on = [ set server env NSDOM_CFG_TRACE_ORB=TRUE = [ set server env NSDOM_CFG_TRACE_GIOP_FW=TRUE = [ set server env NSDOM_CFG_TRACE_SOCKEH=TRUE = = set server env NSDOM_CFG_DBM=$SYSTEM.ZDOMSD20.NSDCFGDB = set server env MY_PREFIX=Z = set server define =_SRL_01, class map, file $SYSTEM.ZDOMSD20.NSDSRL = = set server createdelay 0 secs = set server deletedelay 0 secs = set server TIMEOUT 0 SECS = set server MAXLINKS 16 = set server LINKDEPTH 1 = = set server maxservers 1 = set server numstatic 1 = set server cpus (1,2) = = set server AUTORESTART 10 = set server arglist "-ORBprofile", "lsd1" = add server LSD = start server LSD $Z06T: SERVER LSD, STARTED = =[ configure comm server(s) = = reset server = = set server processtype oss = set server pri 150 = set server cwd /usr/tandem/nsdoms = set server program /usr/tandem/nsdoms/bin/cs = = set server hometerm $ztnt.#pty000a = set server stdin /dev/null = set server stdout /usr/tandem/nsdoms/log/cs.out = set server stderr /usr/tandem/nsdoms/log/cs.out = = [ set server debug on = [ set server env NSDOM_CFG_TRACE_CS=TRUE = [ set server env NSDOM_CFG_TRACE_SOCKEH=TRUE = [ set server env NSDOM_CFG_TRACE_GFSEH=TRUE = [ set server env NSDOM_CFG_TRACE_GCFEH=TRUE = = set server env NSDOM_CFG_DBM=$SYSTEM.ZDOMSD20.NSDCFGDB = set server define =_SRL_01, class map, file $SYSTEM.ZDOMSD20.NSDSRL = = set server createdelay 0 secs = set server deletedelay 0 secs = set server TIMEOUT 0 SECS = set server MAXLINKS 16 = set server LINKDEPTH 1 = = set server maxservers 2 = set server numstatic 2 = set server process $ZNCA (cpus 1:2) = set server process $ZNCB (cpus 2:1) = = set server AUTORESTART 10 = add server CS = start server CS $Z06T: SERVER CS, STARTED = =[ configure naming service = = reset server = = set server processtype oss = set server pri 150 = set server cwd /usr/tandem/nsdoms = set server program /usr/tandem/nsdoms/bin/name_servant = = set server hometerm $ztnt.#pty000a = set server stdin /dev/null = set server stdout /usr/tandem/nsdoms/log/ns.out = set server stderr /usr/tandem/nsdoms/log/ns.out = = [ set server debug on = [ set server env NSDOM_CFG_TRACE_POA=TRUE = [ set server env NSDOM_CFG_TRACE_PROXY=TRUE = [ set server env NSDOM_CFG_TRACE_ORB=TRUE = [ set server env NSDOM_CFG_TRACE_GIOP_FW=TRUE = [ set server env NSDOM_CFG_TRACE_GFSEH=TRUE = [ set server env NSDOM_CFG_TRACE_GCFEH=TRUE = = set server env NSDOM_CFG_DBM=$SYSTEM.ZDOMSD20.NSDCFGDB = set server define =_SRL_01, class map, file $SYSTEM.ZDOMSD20.NSDSRL = = set server createdelay 0 secs = set server deletedelay 15 secs = set server TIMEOUT 30 SECS = set server MAXLINKS 16 = set server LINKDEPTH 4 = = set server maxservers 4 = set server numstatic 2 =[ the following process 689111070NAME_SERVER will be used to support the file =[ system protocol access. = set server process $ZND0 (cpus 1:2) = set server cpus (2:1,3:2,2:3) = = set server AUTORESTART 10 = set server arglist "-ORBprofile", "NS" = add server NS = start server NS $Z06T: SERVER NS, STARTED = =[ configure Event Service = = reset server = = set server processtype oss = set server pri 150 = set server cwd /usr/tandem/nsdoms = set server program /usr/tandem/nsdoms/bin/EventService = = set server hometerm $ztnt.#pty000a = set server stdin /dev/null = set server stdout /usr/tandem/nsdoms/log/es.out = set server stderr /usr/tandem/nsdoms/log/es.out = = [ set server debug on = [ set server env NSDOM_CFG_TRACE_ES=TRUE = = set server env NSDOM_CFG_DBM=$SYSTEM.ZDOMSD20.NSDCFGDB = set server define =_SRL_01, class map, file $SYSTEM.ZDOMSD20.NSDSRL = = set server createdelay 0 secs = set server deletedelay 0 secs = set server MAXLINKS 16 = set server LINKDEPTH 1 = = set server maxservers 1 = set server numstatic 1 = set server cpus (1,2) = = set server AUTORESTART 10 = set server arglist "-ORBprofile", "event_service" = add server ES = start server ES $Z06T: SERVER ES, STARTED = |
Note: If you installed the Software Development Kit (SDK) version of NonStop DOM, your files are installed in the subdirectory ZDOMSD20. If you are using the runtime version of NonStop DOM, your NonStop DOM fileset is located in the subdirectory ZDOMRT20.
The system messages confirm that the Guardian name of the home terminal is $ztnt.#pty000a and that the $Z06T PATHMON process and the NonStop TS/MP environment are successfully started. PATHCOM also displays messages as each server pool is defined and started by the nsdstart script.
Although the LSD and Comm Server processes are the only system processes required to be configured as static servers, the default nsdstart script defines all the system processes as static servers and starts all the processes.
If you try to run nsdstart when the target NonStop TS/MP environment is already running, you will get an error message. The following example shows the result of executing the nsdstart file when the NonStop TS/MP environment for NonStop DOM is already running:
/nsdoms> nsdstart -v
gtacl[5]: unable to run $SYSTEM.SYSTEM.PATHMON, error (11, 12): \
process name error - The file is in use
$Z070: PATHCOM - T8344D42 - (03JUN96)
COPYRIGHT TANDEM COMPUTERS INCORPORATED 1980 - 1985, 1987 - 1996
=
= set pathway maxassigns 8
set pathway maxassigns 8
^
$Z070: ERROR - *1009* PATHWAY CONFIGURATION CAN'T BE CHANGED
|
In this example, the script attempts to open the PATHMON process for the NonStop DOM system processes in order to communicate the startup commands. However, the system returns an error message when it discovers the process is already in use.
Use nsdstop script to stop your NonStop DOM system after is has been configured and started. To confirm that the system is shutdown, you can run a status command on the NonStop DOM PATHMON process, which by default is $ZNDM.