Filter
Top Products
Appendix C 347
Configuring an Invokable TP Using snaptpinstall
File Format for snaptpinstall
The TP is a queued TP. Any incoming Allocate requests
arriving while the TP is running are queued until the
TP issues another Receive_Allocate, or until it finishes
running and can be restarted. An incoming Allocate
request is routed to this TP only if it is received by an
LU that is configured to route incoming Allocate
requests to this computer.
QUEUED-BROADCAST
The TP is a broadcast queued TP. Any incoming
Allocate requests arriving while the TP is running are
queued until the TP issues another Receive_Allocate,
or until it finishes running and can be restarted. When
the TP is started, information about the TP is
broadcast to all servers on the LAN; if an LU on
another computer receives an incoming Allocate
request and has no routing information configured, it
can dynamically locate the TP and route the Allocate
request to it.
Using QUEUED-BROADCAST instead of QUEUED avoids
having to configure explicit routing information for
LUs, and enables load-balancing by running more than
one copy of the same TP on different computers.
However, if you want to avoid broadcasting information
in order to reduce LAN traffic, or if you need to ensure
that incoming Allocate requests arriving at a particular
LU are always routed to the same copy of the TP, you
should use QUEUED.
NON-QUEUED
The TP is a nonqueued TP. SNAplus2 starts a new copy
of the TP each time an incoming Allocate request
arrives for it. Do not specify the TIMEOUT parameter
for a nonqueued TP.
A TP defined as nonqueued cannot be started by an
operator; it is always started automatically by
SNAplus2. Do not specify NON-QUEUED if the TP is to
be operator-started. If a user attempts to start a
nonqueued TP, SNAplus2 rejects the
RECEIVE_ALLOCATE verb because no incoming
Allocate request is waiting for it.