Testing the CPI-C Sample Programs (282877)

MORE INFORMATION

The source files for the CPI-C Send and Receive TPs can be found in the following folders: For Host Integration Server, the sample programs must be compiled before use. For SNA Server 4.0, the already compiled executable files for the CPI-C Send and Receive TPs can be found in the following folder: The documentation for the CPI-C Send and Receive TPs can be found in the following locations in the SDK Help files:

Testing the TP

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Define two local logical units (LUs), one called "CPICSEND" and one called "CPICRECV".
2. Define a CPI-C symbolic destination name called "CPICRECV" with the following values:

   Mode Name: QPCSUPP
   TP Name: CPICRECV
   Partner LU: CPICRECV

3. Because CPI-C does not provide a way to specify a local LU, use one of the following three methods to make the local LU default to CPICSEND:
   • In the Advanced Properties for the CPICSEND LU, select the checkbox to make it a Member of Default Outgoing Local APPC LU Pool.
   • Under Configured Users, go to the Properties of your user or group account. On the APPC Defaults tab, set the default local LU to CPICSEND.
   • Configure a registry entry to specify CPICSEND as the local LU.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

     132720 SNA Server CPIC Allocate Error 20 (CM_PRODUCT_SPECIFIC_ERROR)

4. Save the changes to the configuration file, and then stop and restart the SNA Service.
5. Start the CPICRECV program (CPICRECV.exe), which will appear in the task bar as a running application and wait for the CPICSEND program to be started.
6. Start CPICSEND (CPICSEND.exe). It will very briefly appear in the task bar. If the two applications successfully communicate with each other, both will then shut down.

Successful execution of the applications will result in creation of a CPICRECV.out file and a CPICSEND.out file. The CPICRECV.out file should contain data similar to the following:

     CPICRECV Results
     ----------------

     Local TP Name           = CPICRECV
     Number of conversations = 1
     Wait mode               = No

     Conversation number 0, time = 0.020 seconds
				

The CPICSEND.out file should contain data similar to the following:

     CPICSEND Results
     ----------------

     Symbolic destination name = CPICRECV
     Number of conversations = 1
     Sends per conversation  = 2
     Sends between confirms  = 1
     Bytes per send          = 1024
     Wait mode               = No
     Blocking                = No

     Conversation number 0, time = 0.203 seconds
				

You can also modify the behavior of the CPICSEND and CPICRECV programs through the use of initialization files. See the SDK documentation for further information.