Article ID: 841063 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
A TN3270E emulator may stop responding when you log off a mainframe application. When the problem occurs, the TN3270E emulator may display a message that indicates that the previous command completed or that the logoff is in progress. The exact symptoms vary depending upon the mainframe applications that are used. The TN3270E emulator cannot send or receive any data after this problem occurs.
When the user logs off the mainframe application, the expected behavior is that the TN3270E emulator will display a previous mainframe application menu.
The TN3270 service does not reset a stored Request Unit (RU) when the TN3270 service receives a CLEAR command from a mainframe application.
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft Host Integration Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/328152/ )How to obtain the latest service pack for Host Integration Server 2000
Hotfix informationThe 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.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Date Time Version Size File name ------------------------------------------------------ 23-Apr-2004 18:12 184.108.40.2068 258,320 Tn3servr.exe
To work around this problem, make sure that the emulator is configured to connect to the TN3270 server in TN3270 only mode.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in Microsoft Host Integration Server 2000 Service Pack 2.
The following is an example of the data flow that causes the problem that this article describes: