FIX: A Session Level Interface (SLI) application that sends a Request Recovery (RQR) command does not receive a response to the RQR in Host Integration Server 2006

Article translations Article translations
Article ID: 971983 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

A Session Level Interface (SLI) application that issues an SLI_SEND verb to send a Request Recovery (RQR) command does not receive any further data from an IBM mainframe application in Host Integration Server 2006. The symptoms that you experience vary, depending on the SLI application. In some cases, the SLI application stops responding if the application is designed to wait for an expected response from the IBM mainframe application. In addition, HIS administrators may notice that the Logical Unit Application (LUA) LUs defined in SNA Manager show an In Session status until the LUs are manually stopped by SNA Manager or by an IBM mainframe administrator.

This problem is related to the issue described in the following Knowledge base article:
971669 FIX: A Session Level Interface (SLI) application may stop responding after starting session recovery by issuing a SNA Request Recovery (RQR) command in Host Integration Server 2006

CAUSE

The SLI library (Winsli32.dll) does not set the correct flags in the SNA Request Header (RH) when the SLI application sends the RQR command. Namely, the RQR command that is sent by the SLI application does not have the definite response requested flag set. Therefore, the IBM mainframe does not respond to the RQR command. The session recovery requested by the RQR command cannot continue without a response to the RQR command. This prevents any further processing of the LU being used by the SLI application.

RESOLUTION

Host Integration Server 2006

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:
979497 How to obtain the latest Host Integration Server 2006 service pack

Hotfix Information

A 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 the problem described in this article. 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=support
Note 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.

Prerequisites

You must have Host Integration Server 2006 installed to apply this hotfix.

Restart Requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
32-bit (x86) version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Winsli32.dll7.0.2924.0105,29602-Jun-200902:10x86

64-bit (x64) version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Winsli32.dll7.0.2924.0135,49602-Jun-200902:11x64SP1Not Applicable
Winsli32.dll7.0.2924.0105,29602-Jun-200902:10x86SP1SYSWOW

WORKAROUND

The SLI application uses an SLI_SEND verb to issue the RQR command. The SLI_SEND verb can be defined to set the flags in the RH to correctly format the RQR command to request a definite response. The following fields in the lua_rh parameter of the SLI_SEND verb should be set to 1 to correctly format the RQR command:
  • lua_rh.fi
  • lua_rh.bci
  • lua_rh.eci
  • lua_rh.dr1i

For more information about the SLI_SEND verb and the lua_rh parameter, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/aa745656.aspx

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

After you apply this update, the SLI library (Winsli32.dll) correctly formats the RQR command to indicate that a response is required.

The update that is described here also includes the update that is described in Microsoft Knowledge Base (KB) article 971669.

The following is an example of the RQR command that is sent before you apply this update. The following command was captured in a data link control message trace in Host Integration Server:
DLC 01020101->04160000 DLC DATA 
DLC DAF:01 OAF:03 ODAI:off Exp. 
DLC RQR RQN SC MC 
DLC 
DLC ---- Header at address 01195424, 1 elements ----
DLC 01010100 00012D00 01030001 0100A40A <......-.......u.>
DLC 
DLC ---- Element at address 01B8B688, start 10, end 13 ----
DLC 600000A3 <`..t > 


The Request Header (RH) in this Request Unit (RU) is 0X’600000’. The RQR command is 0X’A3’.

The following is an example of the RQR command that is sent after you apply this update:
DLC 01020101->04160000 DLC DATA 
DLC DAF:01 OAF:02 ODAI:off Exp. 
DLC RQR RQD SC FI BC EC DR1 
DLC 
DLC ---- Header at address 01194D70, 1 elements ----
DLC 01010100 00012D00 01020001 0100C402 <......-.......D.>
DLC 
DLC ---- Element at address 01B81DB0, start 10, end 13 ----
DLC 6B8000A3 <k..t >


In this case, the RH is 0X’6B8000’. The difference is that the following fields in the Request Header are set to 1:
  • Format Indicator (FI)
  • Begin Chain Indicator (BCI)
  • End Chain Indicator (ECI)
  • Definite Response 1 Indicator (DR1I)

For more information about the Request Header, refer to the IBM SNA Formats (GA27-3136).

For additional 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

Properties

Article ID: 971983 - Last Review: October 7, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft Host Integration Server 2006 Enterprise Edition
  • Microsoft Host Integration Server 2006
Keywords: 
kbautohotfix kbexpertiseinter kbsurveynew kbbug kbfix kbqfe KB971983

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com