Windows Server

DPP · Guest

Hi,

I am calling a TP program from a .NET windows application using COM Client
Library HIS project deployed in HIS 2004.

I have selected RE properties, as TCP/IP, CICS, and TRM Link

and i created a new Object using TI Manager for that COM TLB created using
HIS 2004 project.

When i calling this COM TLB interface method from a .NET windows application,

I am getting the following exception,

An unhandled exception of type 'System.Runtime.InteropServices.COMException'
occurred in mscorlib.dll

Additional information: (2137) The TCP transport received a CICS TRM reply
length that is greater than the maximum allowed. Received length=1163548977,
maximum allowed=512. IP Address: xx.xxx.x.xxx, port: xxxx, transid: ,
Listener type: Standard. Make sure that the CICS Listener configuration
matches the RE settings.

Can somebody please let me know what is this exception and where can i check
for the HIS logs?

Thanks

--
Thanks,
DPP

DPP · Guest

Hi Neil,

Thanks for you response.

I followed the same procedure given in Cedar bank sample. But only
difference is i selected TRM Link instead of ELM link.

Created the TI object by selecting the TLB and COM+Application to host this
component and selected Remoting Environment that has the same settings.

I didn't find any TRM link option in Trace Utility. All it has is for SNA. I
am want to have the trace option for TCP/IP and TRM Link model.

How do i need to add these to the list bix in the first tab in Trace Utility?

Please let me know. Thanks,
--
Thanks,
DPP

"Neil Pike" wrote:

Neil Pike · Guest

DPP,

Have you followed the instructions in the below Kb article? (Reply from MS
for someone else getting a 2137 error)

In terms of logs, you need to start a HIS trace to see what's going in/coming
out to the mainframe, which may give you a clue as to what's going on.

It sounds like some sort of buffer overwrite though, as the length reported is
way too long to be real. Maybe a mis-configured variable datatype/length
somewhere?

-------

I would first recommend that you look at the following KB article as it may
prove helpful:

231862 Configuring COMTI to Use TCP/IP Link to CICS Using the Cedar Bank
Demo
http://support.microsoft.com/?id=231862

If you're still having trouble you may want to start a support case with us
so that we can have you capture some Network Monitor logs and we can examine
the traffic between COMTI and your host.

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Neil Pike · Guest

DPP - right click on the WIP node to get the tracing options for that node.
It's done differently in WIP/HIP applications because they don't necessarily
use APPC or any form of SNABase access. (They can run over pure tcp-ip).

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

DPP · Guest

Hi Neil,

Thanks for the information.

Here is the trace from WIP,

CStateMachObject::Invoke This is a Link or MSLink request.
CStateMachObject::Invoke Using MSLink.

CStateMachObject::Invoke Calling DistribLink with BufLen=959,
CommAreaLen=959, OptDataLen=107, TPName=Not used by TCP, TranID=ISHU.

TCP Transport Link entered, buffer length = 959, COMM Area = 107, optimized
send length = 959

TCP Transport FormatCICSTRM: Entry.

TCP Transport FormatCID: Entry.

TCP Transport FormatCID: Exit.

TCP Transport FormatCICSTRM data: Offset=0x0000 5c5c5c5c 5c5c5c5c
5c5c5c5c 5c5c5c5c

TCP Transport FormatCICSTRM data: Offset=0x0010 c9e2c8e4 40404040
03bf0000 006b0100

TCP Transport FormatCICSTRM data: Offset=0x0020 01000100 80

TCP Transport FormatCICSTRM: Exit.

TCP Transport DistribLink is sending the TRM, TRM length = 37

TCP Transport SendBuf entered, 37 bytes to send

TCP Transport SendBuf: Bytes sent=37.

TCP Transport SendBuf exited normally

TCP Transport CheckForListenerMsgs Entry.

TCP Transport CheckForListenerMsgs Checking for msg prefix of EZY.

TCP Transport CheckForListenerMsgs Three bytes of data was received but was
not a Listener message.

TCP Transport CheckForListenerMsgs No Listener message.

TCP Transport ReceiveTRMReplyMSLink entered for Listener type: Standard.
Make sure that the CICS Listener configuration matches the RE settings.

TCP Transport ReceiveBuf entered, maximum 4 bytes to receive

TCP Transport RecvBuf: Remaining=4, receive size=4.

TCP Transport RecvBuf: Bytes received=4, total received so far=4.

TCP Transport ReceiveBuf exited normally, 4 bytes rcvd, Data Complete = 0

TCP Transport ReceiveTRMReplyMSLink received the TRM reply length, TRM reply
length = 1163548977

TCP Transport Receive TRM Reply for MSLink exited abnormally at point=2,
hr=80040859

TCP Transport Link exited abnormally, HRESULT = 0000000f

BufferMgt Buffer being resized, requested size = 65535

BufferMgt Buffer being resized, allocated size = 32767

CStateMachObject (inst=00000000) state transition: Working -> WorkDone

00000000 1 2

CStateMachObject::Invoke failed at point=2, hr=0x80020009.

CSMDispObject::FreeStateMachine entered.

CStateMachObject::Unbind Entry.

CStateMachObject::Unbind eWorkDone.

CStateMachObject (inst=00000000) state transition: WorkDone -> Idle

00000000 2 0

TCP Transport Disconnect entered, type = 0

TCP Transport Disconnect exited normally because no socket existed.

CStateMachObject::Unbind Exit .

CSMDispObject::ResetResource entered.

CSMDispObject::ResetResource returns S_OK.

CSMDispObject::FreeStateMachine returns S_OK.

Client call to IDispatch::Invoke(ISHU), Elapsed time=2.603 seconds, returns
exception '(2137) The TCP transport received a CICS TRM reply length that is
greater than the maximum allowed. Received length=1163548977, maximum
allowed=512. IP Address: XXX.XXX.XXX.XXX, port: XXXX, transid: , Listener
type: Standard. Make sure that the CICS Listener configuration matches the RE
settings.
--

I think Listner not returned anything back. Can you please check and let me
know where it is wrong.

Thanks,
DPP

"Neil Pike" wrote:

DPP · Guest

Hi Rob,

Thanks for your response.

Both host IP address and port numbers are correct. Also, this is already
working in Production on HIS 2000 with the same host IP address and port
numbers. I am trying to migrate this application to HIS 2004 and so facing
this issue.

Please suggest.

--
Thanks,
DPP

"Rob Beardsworth [MSFT]" wrote:

Rob Beardsworth [MSFT] · Guest

Well someone on the host sent something back! Its first 4 bytes which we
were expecting to be the length of a TRM Reply were 1163548977 (decimal).
Are you sure that you have the right host/port and that our sample TRM
listener is listening on that port?

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
From: =?Utf-8?B?RFBQ?= <DPP@discussions.microsoft.com>
Subject: Re: COMexexption
Date: Wed, 2 Nov 2005 07:10:06 -0800
Lines: 125

Hi Neil,

Thanks for the information.

Here is the trace from WIP,

CStateMachObject::Invoke This is a Link or MSLink request.
CStateMachObject::Invoke Using MSLink.

CStateMachObject::Invoke Calling DistribLink with BufLen=959,
CommAreaLen=959, OptDataLen=107, TPName=Not used by TCP, TranID=ISHU.

TCP Transport Link entered, buffer length = 959, COMM Area = 107, optimized
send length = 959

TCP Transport FormatCICSTRM: Entry.

TCP Transport FormatCID: Entry.

TCP Transport FormatCID: Exit.

TCP Transport FormatCICSTRM data: Offset=0x0000 5c5c5c5c 5c5c5c5c
5c5c5c5c 5c5c5c5c

TCP Transport FormatCICSTRM data: Offset=0x0010 c9e2c8e4 40404040
03bf0000 006b0100

TCP Transport FormatCICSTRM data: Offset=0x0020 01000100 80

TCP Transport FormatCICSTRM: Exit.

TCP Transport DistribLink is sending the TRM, TRM length = 37

TCP Transport SendBuf entered, 37 bytes to send

TCP Transport SendBuf: Bytes sent=37.

TCP Transport SendBuf exited normally

TCP Transport CheckForListenerMsgs Entry.

TCP Transport CheckForListenerMsgs Checking for msg prefix of EZY.

TCP Transport CheckForListenerMsgs Three bytes of data was received but was
not a Listener message.

TCP Transport CheckForListenerMsgs No Listener message.

TCP Transport ReceiveTRMReplyMSLink entered for Listener type: Standard.
Make sure that the CICS Listener configuration matches the RE settings.

TCP Transport ReceiveBuf entered, maximum 4 bytes to receive

TCP Transport RecvBuf: Remaining=4, receive size=4.

TCP Transport RecvBuf: Bytes received=4, total received so far=4.

TCP Transport ReceiveBuf exited normally, 4 bytes rcvd, Data Complete = 0

TCP Transport ReceiveTRMReplyMSLink received the TRM reply length, TRM
reply
length = 1163548977

TCP Transport Receive TRM Reply for MSLink exited abnormally at point=2,
hr=80040859

TCP Transport Link exited abnormally, HRESULT = 0000000f

BufferMgt Buffer being resized, requested size = 65535

BufferMgt Buffer being resized, allocated size = 32767

CStateMachObject (inst=00000000) state transition: Working -> WorkDone

00000000 1 2

CStateMachObject::Invoke failed at point=2, hr=0x80020009.

CSMDispObject::FreeStateMachine entered.

CStateMachObject::Unbind Entry.

CStateMachObject::Unbind eWorkDone.

CStateMachObject (inst=00000000) state transition: WorkDone -> Idle

00000000 2 0

TCP Transport Disconnect entered, type = 0

TCP Transport Disconnect exited normally because no socket existed.

CStateMachObject::Unbind Exit .

CSMDispObject::ResetResource entered.

CSMDispObject::ResetResource returns S_OK.

CSMDispObject::FreeStateMachine returns S_OK.

Client call to IDispatch::Invoke(ISHU), Elapsed time=2.603 seconds, returns
exception '(2137) The TCP transport received a CICS TRM reply length that
is
greater than the maximum allowed. Received length=1163548977, maximum
allowed=512. IP Address: XXX.XXX.XXX.XXX, port: XXXX, transid: , Listener
type: Standard. Make sure that the CICS Listener configuration matches the
RE
settings.
--

I think Listner not returned anything back. Can you please check and let me
know where it is wrong.

Thanks,
DPP

"Neil Pike" wrote:

Terry Bullington [MSFT] · Guest

The problem you are seeing is due to HIS2004 not recognizing that the host
has returned an EZY message (encoded in ASCII). We only look for EZY in
EBCDIC. Is it possible that you have things defined so that the host is
expecting character strings in ASCII rather than EBCDIC?
--------------------
Thread-Topic: COMexexption
thread-index: AcXf31nDH924dK/MRH2hN9tNDgonqw==
X-WBNR-Posting-Host: 65.165.5.70
From: =?Utf-8?B?RFBQ?= <DPP@discussions.microsoft.com>
References: <D7F9B50C-50CC-4846-8E1D-10942EA3E970@microsoft.com>
<VA.00006368.1c03cc6e@compuserve.com>
<7A231B62-1A22-40FB-BFDB-27DE3495AF69@microsoft.com>
<VA.0000636a.1f097947@compuserve.com>
<C80B3A57-5253-41C2-AF89-B11743A0E0C9@microsoft.com>
<3WOImv93FHA.2904@TK2MSFTNGXA01.phx.gbl>
Subject: Re: COMexexption
Date: Wed, 2 Nov 2005 10:58:02 -0800
Lines: 166
Message-ID: <CA503664-E70E-498E-AB72-68E71F502687@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.hiserver.general:2269
X-Tomcat-NG: microsoft.public.hiserver.general

Hi Rob,

Thanks for your response.

Both host IP address and port numbers are correct. Also, this is already
working in Production on HIS 2000 with the same host IP address and port
numbers. I am trying to migrate this application to HIS 2004 and so facing
this issue.

Please suggest.

--
Thanks,
DPP

"Rob Beardsworth [MSFT]" wrote:

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1