SNA APPC Event 93 Should Log Fully Qualified PLU Name

• Microsoft SNA Server, versions 3.0, 3.0 SP1, 3.0 SP2, 4.0

SYMPTOMS

If a CPIC or APPC application attempts to allocate a conversation and specifies a fully qualified Primary (that is, Remote) APPC LU name (instead of the Remote LU alias), and the allocation attempt fails, the SNA Server APPC interface logs Event 93, but does not indicate the fully qualified PLU name in the event. For example:

   Event ID: 93
   Source:   SNA APPC Application
   Description:
   APPC local conversation start failed:
   Primary_rc   = <Return code>
   Secondary_rc = <Return code>
   TP_ID        = <Transaction program ID>
   Dest TP name = <Destination TP name>
   LU alias     = <Local APPC LU alias>
   PLU alias    = <Remote APPC LU alias>
   Mode name    = <APPC mode name>

   EXPLANATION%
   An attempt to start an APPC conversation locally using the verb
   [MC_]ALLOCATE failed. 

CAUSE

The SNA Server Event 93 was not originally designed to log the fully qualified PLU name.

STATUS

Microsoft has confirmed this to be a problem in SNA Server 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0. We are researching this problem in SNA Server version 3.0 and will post more information here in the Microsoft Knowledge Base as it becomes available.

This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

MORE INFORMATION

With this update applied, the SNA Server APPC DLL (Wappc32.dll) logs the fully qualified PLU name, in addition to the other fields noted above.

Additional query words:

Keywords : kbbug4.00 kbfix4.00.sp1 snaappc snacpic kbbug3.00 kbbug3.00.sp2 kbbug3.00.sp1 snatp
Version : WINDOWS:3.0,3.0 SP1,3.0 SP2,4.0
Platform : WINDOWS
Issue type : kbbug