For TPs that you will start many times or that will be started by a user, arrange for the TP to be started easily. That is, for graphical interfaces, create a program icon for starting the TP; for nongraphical interfaces, make sure the TP is in the path.
For information about how to set up LU-LU pairs to support TPs, see Using Invoking and Invokable TPs and the Microsoft SNA Server Administration Guide. For information about symbolic destination names and side information, see Side Information and the Microsoft SNA Server Administration Guide.
For autostarted invokable TPs, it is recommended that you use the sample TP configuration program, TPSETUP, for this step. When you write an installation program for autostarted invokable TPs, it is recommended that you include code similar to TPSETUP.
For information about registry or environment variables, see Configuring Invokable TPs and Invoking TPs. For information about TPSETUP, see Sample CPI-C TPs in the SDK.
If the invokable TP is autostarted, SNA Server will start it when needed.