CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.7+)

How the nsdstart Script Works

Each time it is executed, the nsdstart script does the following:

Sets the script variables that specify the NonStop CORBA process names, such as the process names for

the Comm Server and Naming Server.

Determines the home terminal (hometerm) on which server output messages are displayed.2.

Starts the PATHMON process that manages the server processes.3.

Creates a new Pathway configuration file using the server pool settings contained in the script. Some

process names are defined using the script variables from Step 1.

Starts all the defined server processes.5.

The configuration settings defined by the script are stored in a pathway control file (PATHCTL). This file is

created in the directory given by the _DEFAULTS define in effect when the script is executed. For details about

the PATHMON process and the PATHCOM commands used in the scripts, see the NonStop TS/MP System

Management Manual.

Troubleshooting: Problems Starting NonStop Services for CORBA

Process Name in Use●

Pathctl File in Use●

Process Name in Use

If you try to execute nsdstart when the target TS/MP environment is already running, you get an error

message. The following example shows the result of executing the nsdstart file when the TS/MP environment

for NonStop CORBA is already running.

Issuing the nsdstart Command: Error Condition

/usr/tandem/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)

= set pathway maxassigns 8

set pathway maxassigns 8

$Z070: ERROR - *1009* PATHWAY CONFIGURATION CAN'T BE CHANGED

Pathctl File in Use

If the Pathway control file is in use, you see an error similar to this:

$Z1XY: ERROR - *1017* PATHCTL FILE (012)

To remedy this error, define an alternate location for the pathway control file by entering the following command

at the OSS command prompt: