Microsoft KB Archive/247340

From BetaArchive Wiki
Knowledge Base


SymDestName Incorrect in SDK Documentation for CPI-C Samples

Article ID: 247340

Article Last Modified on 6/28/2004



APPLIES TO

  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 3.0 Service Pack 2
  • Microsoft SNA Server 3.0 Service Pack 3
  • Microsoft SNA Server 3.0 Service Pack 4
  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 4.0 Service Pack 1
  • Microsoft SNA Server 4.0 Service Pack 2
  • Microsoft SNA Server 4.0 Service Pack 3



This article was previously published under Q247340

SYMPTOMS

There is an error in the SDK documentation for the CPI-C send and receive sample Transaction Programs (TPs). An incorrect name is listed for the SymDestName.

The exact location of the sample documentation in the Software Development Kit (SDK) is under Appendixes\Sample CPI-C TPs in the SDK\Sample CPI-C TPs.

The Setup section states the following:

For example, use SENDLU-RECVLU-#INTER as your LU-LU-mode triplet. Then create a CPI-C symbolic destination name CPICRECV containing the application TP name CPICRECV...


However, under the Input and Output section, the CPI-C symbolic destination name (SymDestName) is listed as CPICSEND:

ResultFile = C:\CPICSEND.OUT File name to print timings to.
NumSends = 2 Number of Send_Data calls per conversation.
SendSize = 1024 Size in bytes of data sent each time.
ConfirmEvery = 1 Number of Send_Data calls between Confirm calls.
SymDestName = CPICSEND Symbolic destination name.


The SymDestName name should actually be CPICRECV.

STATUS

Microsoft has confirmed that this is a problem in SNA Server versions 3.0 (all SP), 4.0, 4.0SP1, 4.0SP2, and 4.0SP3.

Keywords: KB247340