COMTI/OTMA error occurs after application returns unbounded recordset in a single send (313137)
The information in this article applies to:
- Microsoft Host Integration Server 2000
This article was previously published under Q313137 SYMPTOMS
When a mainframe host application returns a recordset that contains
multiple records to a COM Transaction Integrator (COMTI) component that
is connected through TCP/IP to an IBM Information Management System
(IMS) region on a mainframe that uses IBM Open Transaction Management
Architecture (OTMA) or IBM IMS Connect, the following COMTI 102 event
may be logged in the Application Event Log:
Description: (102) COM Transaction Integrator reported the following
exception to the client:
Component: (Prog ID of Component)
Method: (Method Name)
Exception description:
(2135) The TCP transport detected that the socket was closed but has
not received the Complete-Status Message segment. Therefore, the
outcome of the IMS transaction is in an unknown state. IP Address: (IP
of Host), port: (port number), transid: (Trans ID).
CAUSE
The host application sends all rows of the unbounded record set within
a single IMS Insert command (ISRT), and this causes COMTI to return the
error message. If the host application sends an individual ISRT
command for each row of the unbounded recordset, no problem occurs.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
328152 How to Obtain the Latest Host Integration Server 2000 Service Pack
The English version of this fix should have the following file
attributes or later:
|
Trantcp.dll | 19-JUN-2001 | 12:00 midnight | NOTE: Because of file dependencies, the most recent fix that
contains the preceding files may also contain additional files.
WORKAROUND
To work around this problem, revise the program on the host so that it
uses individual ISRT statements to send each row of the unbounded
recordset.
STATUSMicrosoft has confirmed that this is a problem in Host Integration Server 2000. This problem was first corrected in Host Integration Server 2000 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 4/27/2005 |
---|
Keywords: | kbbug kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix KB313137 kbAudDeveloper |
---|
|