Select the product you need help with

A software update is available that enables Virtual Routing Node (VRN) links to be configured as non-limited resource links in Microsoft Host Integration Server 2009 and Microsoft Host Integration Server 2006 SP1

Article ID: 977899 - View products that this article applies to.

Bug #: 465806 (VSTS) Bug #: 3660 (EBizSE)

INTRODUCTION

This article describes a software update that enables Virtual Routing Node (VRN) links to be configured as non-limited resource links in Microsoft Host Integration Server 2009 and Microsoft Host Integration Server 2006 Service Pack 1 (SP1).

Back to the top | Give Feedback

MORE INFORMATION

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.

Limited resource links such as High Performance Routing (HPR) are automatically deactivated when no traffic flows over the link for a specified time-out period. Historically, the APPN architecture specified that all dynamic links, such as VRN links, would be set up as limited resource links. Over time, most implementations of APPN enabled dynamic links to be configured as either limited or as non-limited resources.

By default, the IP-DLC link service treats all dynamic incoming links as non-limited links, except for VRN links.

Software Update Information

A supported feature that changes the product's default behavior is now available from Microsoft. However, this feature is only intended to change the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if your system is not severely affected by the lack of this feature, we recommend that you wait for the next Host Integration Server 2009 or Microsoft Host Integration Server 2006 service pack that contains this feature.

To obtain this feature immediately, 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:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

File information

The English version of this hotfix 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.

32-bit versions of Host Integration Server 2009

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Snaipdlc.dll	8.0.3749.2	1,003,344	04-Dec-2009	20:03	x86	SP1
Trcipdlc.dll	8.0.3749.2	3,023,696	04-Dec-2009	20:03	x86	SP1

64-bit versions of Host Integration Server 2009

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Snaipdlc.dll	8.0.3749.2	1,397,072	04-Dec-2009	20:05	x64	SP1	Not Applicable
Trcipdlc.dll	8.0.3749.2	3,782,992	04-Dec-2009	20:05	x64	SP1	Not Applicable
Snaipdlc.dll	8.0.3749.2	1,003,344	04-Dec-2009	20:03	x86	None	SYSWOW
Trcipdlc.dll	8.0.3749.2	3,023,696	04-Dec-2009	20:03	x86	None	SYSWOW

32-bit versions of Host Integration Server 2006 SP1

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Snaipdlc.dll	7.0.4205.0	990,544	11-May-2010	18:39	x86	SP2
Trcipdlc.dll	7.0.4205.0	2,961,744	12-May-2009	21:50	x86	SP2

64-bit versions of Host Integration Server 2006 SP1

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Snaipdlc.dll	7.0.4205.0	1,462,096	11-May-2010	18:39	x64	SP2
Trcipdlc.dll	7.0.4205.0	3,954,512	12-May-2009	21:51	x64	SP2

Note Because of file dependencies, the most recent software update that contains these files may also contain additional files.

After you apply this update, the IP-DLC link service can be configured to treat VRN links as non-limited links. In this manner, the links stay active even when there is no traffic flowing over the link.

How to configure VRN links as non-limited resource links

To configure VRN links as non-limited resource links, follow the steps:

Click Start, click Run, type regedit, and then click OK.
Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNAIPx\Parameters\ExtraParameters
Note Replace x with the number that matches the IP-DLC link service that you want to change. For example, assume that you have one IP-DLC link service installed on your Host Integration Server 2009 or Host Integration Server 2006 SP1 system. In this case, you should replace x with 1.
Right-click ExtraParameters, point to New, and then click DWORD Value.
TypeVRNnotLimitedResource , and then press ENTER.
Double-click VRNnotLimitedResource, and enter 1 as the Value data.
Exit Registry Editor.
Restart the IP-DLC link service so that the change takes effect. The easiest way to do this is to restart the SNA Server service or the SnaBase service. When you restart these services, users who are connected to the Host Integration Server are disconnected.

In addition, the other end of the VRN link must also be configured so that the VRN link is treated as a non-limited resource link. If the other end of the VRN link is an IBM mainframe, you should configure LIMRES=NO in Virtual Telecommunications Access Method (VTAM) to enable the link to be treated as a non-limited resource link. If either end of the VRN link treats the link as a limited resource link, the link will be deactivated as soon as the specified aliveness timer expires.

For more information about limited resources, about advanced peer-to-peer networking (APPN), about high performance routing (HPR), and about rapid transport protocol (RTP) connections in APPN/HPR networks, see "Inside APPN and HPR - The Essential Guide to New SNA" at the following IBM Web site:

http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg243669.html

(http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg243669.html)

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.

Back to the top | Give Feedback