HP-UX SNAplus2 R7 APPC Programmer's Guide

Writing Transaction Programs
Starting TPs
• Partial network name
• Whole network name
• Partial network name followed by CP name
• Fully qualified partner LU name
Only a single TP server application can register for a given TP and LU combination, including wildcards.
For example, one TP server application can register TPNAME1 and *, while the same TP or another TP server
application registers TPNAME1 and LUNAME1. Registration of this type is legal, but two TP server applications
cannot both register TPNAME1 and LUNAME1. The second registration attempt will fail.
2. When an Attach arrives at SNAplus2, SNAplus2 attempts to find the TP server application whose registration
most closely matches the TP name, LU alias and fully qualified LU name received on the Attach. The matches
are examined for greatest closeness in the following order:
a. TP name match
b. LU alias match
c. Exact fully qualified partner LU name match
d. Wildcard fully qualified partner LU name match
When SNAplus2 finds a match, it delivers the Attach to the TP server application. The TP server has the
following options:
• Reject the Attach, in which case SNAplus2 returns the Attach to the invoking TP and includes an error code
provided by the TP server application
• Accept the Attach, in which case SNAplus2 informs the invoking TP that the Attach has been accepted
3. If no matches are found after trying all combinations above search criteria, SNAplus2 rejects the Attach and
returns the Attach to the invoking TP with the appropriate error code.
2.9.6 Timeout Values for Invoked TPs
The SNAplus2 configuration specifies two timeout values that define how long APPC waits to establish a conversation
between two TPs, as follows:
Timeout for Starting TP
This value defines how long an Attach is queued waiting for the invoked TP to be started and to
issue the RECEIVE_ALLOCATE verb. If RECEIVE_ALLOCATE is not issued within this time, the
[MC_]ALLOCATE verb in the invoking TP fails. This timeout is defined in the configuration of the local
LU that the TP uses.
Timeout for Servicing TP
This value defines how long a RECEIVE_ALLOCATE verb issued by the invoked TP waits for an Attach
from the invoking TP. If an Attach is not received within this time, the RECEIVE_ALLOCATE verb in the
invoked TP fails. The configuration can specify one of the following:
Infinite timeout
RECEIVE_ALLOCATE waits indefinitely
Zero timeout
RECEIVE_ALLOCATE fails unless the Attach has already been received
Finite timeout
A specific timeout value is provided
72