Invokable Transaction Program registry locations that Tpsetup.exe creates (316787)
The information in this article applies to:
- Microsoft Host Integration Server 2000
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft SNA Server 4.0 SP3
- Microsoft SNA Server 4.0 SP4
This article was previously published under Q316787 SUMMARY A Transaction Program (TP) that can be invoked (called upon
to start a conversation) by another TP is known as an Invokable TP. Invokable
TPs are generally server-type applications. A TP that is
automatically started when invoked is known as an autostarted TP.
Tpsetup.exe is a utility that is included with Host Integration Server 2000 and
with the SNA Server 4.0 Software Development Kit (SDK). You can use Tpsetup.exe
to install autostarted invokable TPs. Autostarted invokable TPs can be either queued or nonqueued. Queued and nonqueued TPs function differently:
- When a queued TP is invoked multiple times, it loads one
time and then queues up requests after that to be dealt with one at a
time.
- When a nonqueued TP is invoked multiple times, it loads
multiple times, one time for every time that it is invoked.
REFERENCES For more information, see the online books on this subject,
and the SDKs for both Host Integration Server and SNA Server 4.0.
For more information about TPs and related
topics, click the following article numbers to view the articles in the Microsoft Knowledge Base:
182576
PRB: NT client does not support dynamic definition of invokable TPs
158515 Auto started TP is not invoked if TP has mixed-case TP name
118382 Making and running AREXEC/AREXECD samples
118381 Making and running APING/APINGD samples
Modification Type: | Major | Last Reviewed: | 2/24/2006 |
---|
Keywords: | kbinfo KB316787 kbAudDeveloper |
---|
|