RSC/MP 7.3 Installation and Configuration Guide

Configuring and Managing the RSC/MP TDP
Process
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011
12-6
TERM Object
TERM Object
All RSC/MP connections and sessions terminate with a TERM object. While a TERM
generally corresponds to a workstation, a workstation can be configured to access
multiple TERM objects. The TERM object sets defaults for the sessions associated
with it. For example, a TERM object can enforce access through an ACS process
regardless of how individual workstations are configured.
PIPE Object
The PIPE object provides the TDP interface to the Piccolo transport system. Its name
is used as the listen (or passive open name) on connect requests from clients. This
name, along with the host system name, is used by RSC/MP clients in the RSC.INI file
as the value of HOST_PIPENAME.
Files Used to Configure RSC/MP
After you configure and start TDP objects, you can edit the following files to configure
and maintain the TDP.
Retaining Modifications
To retain modifications to the TDP configuration, place the modified values in a
command file (for example, TDPCFG) that is supplied to RSCCOM upon TDP start up.
TDP Logging
You can turn on TDP logging and view the messages by following the steps in the
following subsections.
Setting Up a Log File
The TDP sends critical RSC/MP event messages automatically to the Distributed
Systems Management (DSM) event collector, $0, and to a log file if the file has been
established using the RSCCOM LOGOPEN command. These critical events include
critical errors, logfile opens, and object state changes (such as start, stop, and abort).
This process does not require configuration. HP Global Customer Support Center
Table 12-2. Sample Configuration and Management Files
File Purpose
TDPCFG RSCCOM input configuration
STARTRSC Starts the
RSC/MP
host processes
STOPRSC Stops the
RSC/MP
host processes
PWYCFG Configures a Pathway/TS for the test server (TDDSVR)
PIPETXT Piccolo configuration