RSC/MP Installation and Configuration Guide

Configuring and Managing the RSC/MP TDP
Process
Editing the STARTRSC File
Editing the STARTRSC File
STARTRSC is a sample TDP startup TACL macro and can be used as it is; however,
you can make the following changes:
If yo u are not going to pass the volume and subvolume names as an argument
when yo u run the macro, change all the [RSCWORK] references in the
STARTRSC file to indicate the volume and subvolume in the format $vol.subvol.
If yo u chose a name for the Piccolo configuration file other than PIPEINI, then you
must change the following line setting the PIPEINI environment variable to the
actual name of your Piccolo configuration file name.
PARAM PIPEINI [RSCWORK].pipeini
Determine if you will need to access your host applications as Pathway
serverclasses. The following lines start a Pathmon process and configure it to run
the RSC/MP test echo server as a Pathway serverclass (TDDSVR). You will need
to edit the Pathway configuration file, PWYCFG, adding server configurations for
your applications. If yo u do not need your applications to run in a Pathway
environment and you don‘t wish to run RSCTEST to TDDSVR via Pathsend, you
can comment out (by preceding each line with the TACL COMMENT ==) or delete
the following lines:
PATHMON /NAME $pathmon-process-name, NOWAIT/
PATHCOM /IN [RSCWORK].pathway-configuration-file/
$pathmon-process-name
Run the TDP. This command starts the TDP process and optionally specifies,
among other things, the CPU its backup will run in, the home terminal, and the
standard input and output devices. The general syntax to run the TDP process is:
TDP /NAME $process-name, NOWAIT, IN in-file, OUT out-file, &
TERM home-term, PRI priority, CPU cpu-num/backup-cpu
The OUT and TERM parameters should refer to a permanently configured terminal
with a paused TACL. If not specified, these options will default to the terminal ID of
the starting TACL. If this OBEY file is run from a Telnet session or other temporary
terminal, then the IN, OUT, and TERM options must be added to the command
shown below. Failure to do this can cause the TDP process to fail because the
assumed device is inaccessible.
The CPU in which the backup process will run can either be supplied with the RUN
command or via RSCCOM with the CONTROL command.
The following steps assume that the TDP and RSCCOM objects are installed in
$SYSTEM.SYSTEM.
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration G uide — 52235 8- 013
10-2