Microsoft KB Archive/924770
Article ID: 924770
Article Last Modified on 12/4/2007
- Microsoft Host Integration Server 2004 Enterprise Edition
- Microsoft Host Integration Server 2004 Standard Edition
This article discusses a software update that adds Virtual Routing Node (VRN) support to the IP-DLC link service in Microsoft Host Integration Server 2004.
A VRN is a virtual node that exists in an Advanced Peer-to-Peer Networking (APPN) topology database. APPN nodes that operate in a VRN can create dynamic connections to other APPN nodes in the same VRN. VRNs provide the following benefits in an Advanced Program-to-Program Communication (APPC) network:
- If direct connectivity between APPN nodes is required, VRNs reduce the number of APPN link definitions that must be manually defined.
- VRNs remove potential bottlenecks that are caused when session traffic is routed through intermediate network nodes (NNs) and when direct APPN links between APPN nodes do not exist.
- Fewer topology database updates (TDUs) are sent across the APPC network when VRNs are used. The number of TDUs is more when you manually define direct APPC link definitions between APPN nodes.
Service pack information
To resolve this problem, obtain the latest service pack for Host Integration Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
940313 How to obtain the latest Host Integration Server 2004 service pack
A supported feature that modifies the default behavior of the product is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if you are not severely affected by the lack of this feature, we recommend that you wait for the next Microsoft Host Integration Server 2004 service pack that contains this feature.
To obtain this feature immediately, download the feature by following the instructions later in this article or contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|File name||File version||File size||Date||Time||Platform|
|Wmisnalinkservicems.mof||Not Applicable||3,090||12-Feb-2007||23:41||Not Applicable|
|Wmisnalinkservicems_xp.mof||Not Applicable||3,133||12-Feb-2007||23:41||Not Applicable|
After you apply this update, the IP-DLC link service can be configured to use VRNs by using SNA Manager, the Linkcfg.exe command, or the Host Integration Server Windows Management Instrumentation (WMI) provider.
- Click Start, point to All Programs, point to Microsoft Host Integration Server 2004, and then click SNA Manager.
- In SNA Manager, expand the Host Integration Server subdomain.
- Expand the Servers node, and then expand the Host Integration Server name for which the IP-DLC connection will be configured.
- Click the Link Services node. If an IP-DLC link service is not installed, right-click the Link Services node, point to New, and then click Link Service to add a new link service.
- Right-click the IP-DLC link service that will be configured, and then click Properties.
- Click Configure.
- Click the VRN tab.
- Click Add.
- Enter a VRN name in the Enter the name of Virtual Routing Node box. For example, the VRN name can be APPN1.ROUTE1.
Note The VRN name consists of two names that are separated by a period (.). Each name can be 1 to 8 characters long. The total length of a VRN name cannot exceed 17 characters.
A maximum of 16 VRN names can be added for each IP-DLC link service that is installed on a Host Integration Server 2004 computer.
The VRN names that are configured for an IP-DLC link service are written to the following registry subkey:
x is replaced with the name of the IP-DLC link service. For example, SNAIP
x can be SNAIP1, SNAIP2, and so on. VRN
x is replaced with the VRN name. For example, VRN
x can be VRN0, VRN1, and so on.
The following is a sample Linkcfg.exe command that can be used to add a new IP-DLC link service that has a VRN name.
LINKCFG LINKSVC "SNAIP1" /SERVER:HIS Server Name /LSTYPE:"IP-DLC Link Service" /PRIMARYNNS:NNS1 /NETWORKNAME:APPN1 /CPNAME:HISSERV1 /NODEID:05D.FFFFF /LENNODE:"SNA Service" /ADAPTER:AdapterName /VRNNAMES:APPN1.ROUTE1, APPN1.ROUTE2 /DOMAIN:<DomainName> /USERID:UserName /PASSWORD:Password
For more information about the Linckcfg.exe command, see the Host Integration Server 2004 documentation.
For more information about the VRNs and the connection networks, see the "Networks and Virtual Routing" section in Chapter 4 of Inside APPN - The Essential Guide to the Next-Generation SNA. To see this documentation, visit the following IBM Web site:
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
For more information about how to specify the network adapter name when you use the Linkcfg.exe command in Windows 2000 Server and in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
262807 How to use the SNA server Linkcfg.exe on Windows 2000
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbfix kbqfe kbpubtypekc kbhotfixserver KB924770