Pathway/iTS System Management Manual (G06.24+)

Configuring Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
2-11
Configuring TERM Objects
For Pathway/iTS web clients and sockets IDS requesters, you must use configured
TERM objects. However, for other intelligent devices and for terminals, 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 10 to 15 operator terminals monitor the system using several different
information-gathering Pathway applications.
A Pathway application can support up to 4095 configured TERM objects. Thus, it is
often appropriate to use TERM objects for large networks of terminals dedicated to a
single application. A high-volume application that includes many non-dedicated
devices must be coded to dynamically add and delete TERM objects as needed when
the non-dedicated devices access the application.
Configuring TERM Objects
For each input-output device or process you want to configure explicitly, you must
define and add a TERM object using the SET and ADD commands. A TERM object
runs as a thread in the TCP, which can handle many such TERM objects concurrently.
For example, consider a PATHMON environment that runs a single order-processing
application on 100 application workstations or terminals. Whenever users begin to use
the application, their web browsers or terminals typically display the logon or menu
page or screen for the application, as presented by the initial screen program. The
users can use only this application; they cannot access other software. To support this
system, you would need to configure 100 TERM objects—one for each workstation or
terminal.
To configure a TERM object, you must specify these attributes with the SET TERM
command:
•
FILE specifies the name of the input-output device or process that the TERM
controls.
This can be the name recognized by TACL for a terminal or other physical device.
Alternatively, it can be the name of a process that handles work such as front-end
processing or terminal emulation. For TERM objects supporting web clients and
sockets IDS requesters, it must be the name of the associated router process.
•
INITIAL specifies the name of the first screen program that runs on the device or
process when the TERM object is started. For TERM objects supporting web