HP-UX SNAplus2 R7 Administration Guide

Appendix CConfiguring an Invokable TP from the Command Line
combination of the two (for example, [<3f>"TP1"]). In this example, the first character is the unprintable
character 0x3f, and the following characters are "TP1".
SNAplus2 converts a supplied ASCII string to EBCDIC, but does not perform any conversion on a hexadecimal
string (which is assumed to be in EBCDIC already). It then pads the name with EBCDIC spaces on the right
(to a total of 64 characters) before matching against the specified TP name.
PAT H
The path and file name of the executable file for this TP.
This line is optional. If it is not included, SNAplus2 assumes that the executable file name is the same as the
TP name. If you specify a file name with no path, the default path for HP-UX systems is /etc/opt/sna;
for a Windows client, SNAplus2 uses the normal Windows mechanisms for locating the executable file.
ARGUMENTS
Any command-line arguments to be passed to the TP, separated by spaces. These arguments are passed to
the TP in the same order as they appear on the command line.
This line is optional. If it is not included, the TP is invoked without any command-line arguments.
TYPE
Specify one of the following values:
QUEUED
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 informa-
tion 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.
ATPdefined 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 because no incoming Allocate request is
waiting for it.
After a nonqueued TP has ended a conversation, it may terminate, or it may issue another
Receive_Allocate. For frequently-used programs, this provides a way of avoiding the performance
overhead of starting a new instance of the program for each conversation. Each time an Attach
is received for a nonqueued, automatically started TP, SNAplus2 checks whether there is already a
Receive_Allocate outstanding from an instance of this TP. If so, this TP is used for the incoming
conversation; otherwise, SNAplus2 starts a new instance of the program.
If you use NON-QUEUED, more than one copy of the TP can be running at a time. If the TP writes to
files, you need to ensure that different copies of the TP do not overwrite each other’s files. To do this,
use one of the following methods:
201