Pathway/XM System Management Manual

Configuring Clients and Requesters
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
5-9
Configuring TERM and PROGRAM Objects
•
NONSTOP specifies whether the router process runs as a process pair.
•
INSPECT specifies whether you can use the Inspect program to examine the
SCREEN COBOL programs running on the terminals handled by the router process.
The SET TCP INSPECT attribute also must be set to ON.
•
PRINTER specifies the name of the print device for each temporary TERM object
associated with this ROUTER object.
For example, suppose you want to define and add a ROUTER object named RESERVE.
ENABLE ROUTER
RESET ROUTER
SET ROUTER PROTOCOL SOCKET
SET ROUTER
TCP TCP_TEMPLATE2
SET ROUTER PORT 5000
SET ROUTER INITIAL SCOBOL-RUN-UNIT
SET ROUTER HANDLER $ZTC0
SET ROUTER CONNECTIONS 100
SET ROUTER
GROUP RESERVATIONS
SET ROUTER GROUP WEB_CLIENT
SET ROUTER WEIGHT 10
SET ROUTER NONSTOP ON
SET ROUTER INSPECT OFF
SET ROUTER PRINTER $S.#LPT1
ADD ROUTER RESERVE
Configuring TERM and PROGRAM Objects
Terminal objects represent tasks controlling the input-output devices and processes that
allow users to interact directly or programmatically with a Pathway application. There
are two types of these objects: configured terminal (TERM) objects and temporary
terminal (PROGRAM) objects.
Configured TERM objects are those you define and add to the PATHMON
configuration file. Temporary TERM objects are created for you (and automatically
deleted) by the PATHMON process in response to a RUN PROGRAM command, using
a template you configure as a PROGRAM object. The names you specify for configured
TERM objects must begin with a letter; the PATHMON process assigns names
beginning with numbers to temporary TERM objects.
Temporary TERM objects can be easier to use than configured TERM objects. Because
more default attributes are supplied for a PROGRAM object than for a TERM object, it
is easier to use a PROGRAM object. And because temporary TERM objects are deleted
automatically when the user completes a session and exits the program, PROGRAM
objects can be easier to manage from an operations standpoint.
On the other hand, a Pathway application can support just 100 concurrent waited RUN
PROGRAM requests from PATHCOM processes and SPI processes. Thus, it may be
appropriate to use temporary TERM objects to control input-output devices and
processes only in a low-volume, low-terminal-count, multiple-application environment.
An appropriate environment, for example, might be a system management area in which