Article ID: 947858 - View products that this article applies to.
When an Advanced Program-to-Program (APPC) application that is running on an IBM mainframe tries to invoke an APPC application that is running on a Host Integration Server 2006 system, the SNA Server service logs an event 17 warning message that resembles the following:
Event ID: 17
Note The last two bytes of the sense data vary depending on the BIND request unit that the IBM mainframe sends. The last two bytes of the sense data point to the hexadecimal offset of the fully qualified primary logical unit (PLU) name.
The SNA Server service also sends a BIND –RSP response unit to the IBM mainframe that contains the IBM sense data that appears in the event 17 warning.
When you are using an IP-DLC connection, you must define remote APPC LUs on a Peer connection, as described in the following Microsoft Knowledge Base article:
939193The SNA Server service cannot associate the remote APPC LU that is defined on the Peer IP-DLC connection with a dependent APPC LU that is defined on a Host IP-DLC connection when the SNA Server service processes an incoming BIND request. The SNA Server service rejects the incoming BIND request because an association between the local APPC LU and the remote APPC LU cannot be established. Therefore, the BIND –RSP response and the event 17 warning occur.
(http://support.microsoft.com/kb/939193/ )How to set up the connection and the logical units for an APPC application when you use the IP-DLC link service in Host Integration Server 2006 together with dependent APPC logical units
To resolve this problem, obtain the latest service pack for Host Integration Server 2006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/979497/ )How to obtain the latest Host Integration Server 2006 service pack
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must have Host Integration Server 2006 installed to apply this hotfix.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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.
Host Integration Server 2006 32-bit (x86) version
Collapse this tableExpand this table
Host Integration Server 2006 64-bit (x64) version
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you apply this hotfix, you can use the Snacfg.exe command-line configuration utility to associate the remote APPC LU with the Host IP-DLC connection. When the remote APPC LU is associated with the Host IP-DLC connection, the SNA Server service can successfully process incoming BIND requests over IP-DLC connections by using dependent APPC LUs.
Commands in the Snacfg.exe command prompt utilityThe following is a list of the commands in the Snacfg.exe command prompt utility. You can use these commands to create and to assign connections to remote LUs.
(http://support.microsoft.com/kb/824684/LN/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 947858 - Last Review: October 8, 2011 - Revision: 3.0
Contact us for more help