HP-UX SNAplus2 Upgrade Guide (June 2003)

Changes in SNAplus2 Functions in R6.0 and later releases
Invokable TPs
Chapter 466
Invokable TPs
In SNAplus, all invokable TPs (both auto-started and operator-started)
must be defined in the configuration file; this definition includes the
computer where the TP runs, and whether the TP is queued or
nonqueued. Information on a queued TP is broadcast to servers when the
TP starts, so that incoming Allocate requests arriving at LUs on servers
elsewhere in the LAN can be routed to it.
This model is changed as follows:
• TPs no longer need to be defined in the central configuration file
(except when they require certain advanced configuration
parameters). Auto-started TPs are defined in a separate file on the
computer where they run; operator-started TPs do not generally
need to be defined except to override certain default settings. For
more information, refer to the chapter that defines invokable TPs in
the HP-UX SNAplus2 Administration Guide.
• A queued TP can be defined to be broadcast queued, which means
that information about a TP is broadcast to servers when it starts so
that it can be located dynamically. The default is nonbroadcast,
which means that it only receives incoming Allocate requests
explicitly targeted at the computer where it runs.
• The configuration of a local LU specifies whether to route incoming
Allocate requests to a particular target computer, or to attempt to
locate a broadcast copy of the TP. For more information, refer to the
description of the define_local_lu command in the HP-UX
SNAplus2 Administration Guide.
• When an incoming Allocate request arrives for a TP that is not
defined in the invokable TP data file and so cannot be auto-started,
SNAplus2 rejects the request if the TP has not already been started
by an operator. It does not provide either a timeout during which the
TP must be started or a console message requesting the operator to
start the TP, as it did in SNAplus.