 |
» |
|
|
|
This
section explains how to define an APPC TP. In most cases, you do not need to define TPs that run on the
SNAplus2 system; but you do need to configure a TP definition in
the following cases: - APPC
Characteristics
If the TP on the SNAplus2 computer is the invoking
TP
(or
source
TP—the TP that starts the APPC conversation) and you do
not need to restrict access to the TP, you do not need to define
the TP. You can, however, define an APPC TP, as described in “TP Definition Parameters”,
to specify the following characteristics: To define conversation security for
the TP. To indicate whether the TP uses basic or mapped
conversations. To specify sync point processing. To specify handling of PIP data.
- Invokable TPs
To enable a TP to be started automatically in response
to an incoming allocation request, define it as an invokable TP
as described in “TP Invocation Parameters”. An
invokable TP (or target TP)
is one that is started in response to an incoming allocation request.
You must create a TP definition for an invokable TP. An invokable
TP can be an APPC TP that issues RECEIVE_ALLOCATE, or a CPI-C application
that issues Accept_Conversation or Accept_Incoming. | | | |  | NOTE: In this section, the phrase “Receive_Allocate”
is used to indicate any of these three API calls. | | | | |
You can also define an invokable TP to route incoming allocation
requests to a running TP. For an invokable TP, you can also specify a timeout value,
to limit the wait for an allocation request. (You can only configure
this option using command-line administration.) SNAplus2 uses the invokable TP definition for the following
purposes: When a TP issues Receive_Allocate,
SNAplus2 searches for an invokable TP definition with the appropriate
TP name. If the definition exists, and includes a value for the
Receive_Allocate timeout, SNAplus2 uses this value when processing
the Receive_Allocate; otherwise it uses the default (no timeout,
which causes the TP to wait indefinitely). When an incoming Allocate request arrives at the
target system, and the requested TP is not already running with
a Receive_Allocate outstanding, SNAplus2 searches for a TP definition
with the TP name specified on the incoming Allocate. If the definition
exists, SNAplus2 uses the information in this definition to start
the TP (if multiple instances are permitted or the TP is not already
running), or to determine that it should queue the incoming Allocate
(if the TP is already running and multiple instances are not permitted
).
If necessary, you can configure both types of definitions
for the same TP (for example, to define conversation security for
an invokable TP). To configure a TP definition, use one of the following methods: - To define
APPC characteristics:
Use either of the following methods: - Motif
administration program
Select APPC
and Transaction
Programs from the Services menu on the Node window.
When SNAplus2 displays the TP window, select the bottom pane and
click on the Add
button, or select an existing TP definition and click on the Zoom button. - Command-line administration program
Issue the snapadmin define_tp
command.
- To define an invocable TP:
The configuration methods for servers and clients
are different: On a server, use either of the following
methods: - Motif
administration program
Select APPC
and Transaction
Programs from the Services menu on the Node window.
When SNAplus2 displays the TP window, select the top pane and click
on the Add
button, or select an existing invokable TP definition and click
on the Zoom
button. - Command-line administration program
Issue the snaptpinstall
command.
On a client, issue the snaptpinstall
command.
For information about using the snaptpinstall
command, see Appendix C “Configuring an Invokable TP
Using snaptpinstall” TP Invocation Parameters | |
The following parameters are required for a TP that can be
invoked on the local node: - TP name
A TP name in one of the following forms: - Application TP
If the remote TP is a user application, supply the
name as normal characters (up to 64 characters in length). - Service TP
If the remote TP is an SNA service transaction program,
enter the name in hexadecimal (up to eight hexadecimal digits, representing
4 bytes).
You can define multiple TPs that have the same TP name, provided
each TP definition specifies a different LU alias. - Parameters are for invocation on any LU/on specific LU
Whether to make the TP invokable
on any LU or only on a specific LU. By default, the TP can be invoked
on any LU. - LU alias
The
local LU alias from which the TP is to accept incoming Attaches.
This name must match the name of a local APPC LU on the SNAplus2
node. If you do not specify an LU alias, the TP accepts incoming
Attaches from any local LU. This field applies only if you specify that the parameters
for this TP definition are for invocation on any LU. You can define multiple TPs that have the same TP name, provided
each TP definition specifies a different LU alias. - Multiple instances supported
If
you do not select this option, 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, or if it is received
by an LU on this computer that has no routing information configured. If you select this option, the TP is a nonqueued TP. SNAplus2
starts a new copy of the TP each time an incoming Allocate request
arrives for it. A nonqueued TP cannot be started by an operator;
it is always started automatically by SNAplus2. For a nonqueued
TP, SNAplus2 permits more than one copy of the TP to be running
at a time. All copies run with the same user and group IDs and the
same working directory, as defined by the User ID
and Group ID parameters.
If the TP writes to files on the local system, you need to ensure
that different copies of the TP do not overwrite each other's files. - Route incoming Allocates to running TP
This option applies only if multiple instances
are not supported. Select this option if 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 this option avoids having to configure explicit routing
information on 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,
do not select this option. - Full path to TP executable
The
path and file name of the executable file for this TP. If you do
not provide the file name, SNAplus2 assumes that the executable
file name is the same as the TP name
parameter. If no path is specified, the default path for HP-UX systems
is /etc/TPname,
where TPname is the TP name
parameter. For a Windows system, the system uses the usual Windows
mechanism to locate the executable file. The file must have execute permission for the user specified
by the User ID parameter.
In addition, if the executable file is to be run with User ID
set to root, the file must be owned by root and must have setuid and setgid
permission in order to be started automatically by SNAplus2. - Arguments
Any
command-line arguments to be passed to the TP, separated by spaces.
The arguments are passed to the TP in the same order as they appear
here. This value is optional. If it is not included, the TP is invoked
without any command-line arguments. - User ID
The
user ID that SNAplus2 uses to start the TP. This line is required,
and must be specified. The ID must be a valid HP-UX login ID on
the SNAplus2 computer. The TP is started in the home directory associated with this
user ID. This home directory is also the default path for trace
files and any other files accessed by the TP (unless the application
overrides it by specifying a full path). If the application specifies
a file name without a path, SNAplus2 searches for the file in this
home directory; if the application specifies a file name with a
relative path, SNAplus2 searches for the file in the specified directory
relative to this home directory. The executable file for the TP, specified by the Full path to TP executable
parameter, must have execute permission for the specified user.
In addition, if User ID
is set to root, the file must be owned by root and must have setuid and setgid
permission in order to be started automatically by SNAplus2. - Group ID
The
group ID that SNAplus2 uses to start the TP. This must be a valid
HP-UX group ID on the SNAplus2 computer. This line is optional. If it is not included, the default
is sna.
TP Definition Parameters | |
You can configure an APPC TP to specify conversation type,
sync level, and handling of PIP data. The following parameters are
also required to define a TP for APPC communication: - TP name
A TP name in one of the following forms: - Application TP
If the remote TP is a user application, supply the
name as normal characters (up to 64 characters in length). - Service TP
If the remote TP is an SNA service transaction program,
supply the name in hexadecimal (up to eight hexadecimal digits,
representing 4 bytes).
- Conversation level security required
Select this option if an allocation
request must include a valid user name and password (or an indicator
that the password has already been verified). If you do not select
this option, no verification is required. - Restrict access
Select
this option if the user name must be included on a security access
list. This field applies only if the Conversation level security required
option is selected. - Security access list
Name
of a security access list that contains user IDs permitted to access
this TP. If the Restrict access
option is selected, you must provide this value.
|
Printable version
