Windows Server

Andrée Laliberté · Guest

Hi,

I configured CedarBank Sample HIP connection with a CICS and test it with
the CICS Mainframe CedarBank Client but the call failed with Event ID error
803 (see error below). I also traced the listener and here is the error
reported in the trace
"Transport Receive exited abnormally at point 1, HRESULT = 0x00002746"

Is there a list of common errors solutions reported in the traces?

Event Type: Error
Event Source: HIP Service
Event Category: Network
Event ID: 803
Date: 2005-04-28
Time: 11:24:48
User: BUILTIN\Administrators
Computer: XXXXXXX
Description:
(803) A Transaction Integrator flow control module is reporting a failure.
HIP Application: CedarBank

Module: WorkFlowTRM

Progress: 90

HRESULT: 80020009

EXPLANATION
An error has occurred in the flow control Module identified above. The
error occurred at the point identified by the Progress code identified
above.
ACTION
Make sure that the Transaction Integrator service has been properly
deployed and administered and that the HIP runtime environment has been
installed on the system on which the failure occurred. If the problem
persists contact Microsoft support.

Rob Beardsworth [MSFT] · Guest

Hi Andre,
this error is a socket error, "socket forcibly closed by remote host",
which tends to indicate that the host end is dying on us :-). Just before
the trace entry you mention, is there a "Calling MSLink TRM Handler"? If
that is the case, are you driving the CICS Client correctly to use the Link
model?

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: "Andrée Laliberté" <alaliberte@globetrotter.net>
Subject: HIP failed
Date: Thu, 28 Apr 2005 14:19:29 -0400
Lines: 41

Hi,

I configured CedarBank Sample HIP connection with a CICS and test it with
the CICS Mainframe CedarBank Client but the call failed with Event ID error
803 (see error below). I also traced the listener and here is the error
reported in the trace
"Transport Receive exited abnormally at point 1, HRESULT = 0x00002746"

Is there a list of common errors solutions reported in the traces?

Event Type: Error
Event Source: HIP Service
Event Category: Network
Event ID: 803
Date: 2005-04-28
Time: 11:24:48
User: BUILTIN\Administrators
Computer: XXXXXXX
Description:
(803) A Transaction Integrator flow control module is reporting a failure.
HIP Application: CedarBank

Module: WorkFlowTRM

Progress: 90

HRESULT: 80020009

EXPLANATION
An error has occurred in the flow control Module identified above. The
error occurred at the point identified by the Progress code identified
above.
ACTION
Make sure that the Transaction Integrator service has been properly
deployed and administered and that the HIP runtime environment has been
installed on the system on which the failure occurred. If the problem
persists contact Microsoft support.

Sachin · Guest

Rob,

Even i seem to be facing the problem as mentioned by Andre. I checked
through our traces and found the statement "WorkFlow is Calling MSLink TRM
Handler". Is this what you mentioned about?

The Cedarbank works perfectly, but another sample i am trying out just does
not work. Can you give details on how to check if i am "driving the CICS
Client correctly to use the Link model".

Sachin

"Rob Beardsworth [MSFT]" wrote:

Rob Beardsworth [MSFT] · Guest

HI Sachin,
if I understand you correctly you are getting exactly the same error
message as Andre (803 and the progress 90 etc). You say that you have
CedarBank working, i.e. you are using the sample client (contained in
tcpcedrcli.cbl) and the supplied "ms link driver" (in tcpmshiplnk.cbl). The
"other sample" that does not work is based in the sample client, and has
not in any way changed the "ms link driver" correct? Its not impossible
that there is a bug in that code :-). Could you give us a netmon trace or
your client source code to see if there is something we can obviously spot?

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
--------------------
Thread-Topic: HIP failed
From: =?Utf-8?B?U2FjaGlu?= <Sachin@discussions.microsoft.com>
Subject: RE: HIP failed
Date: Wed, 17 Aug 2005 02:15:02 -0700

Rob,

Even i seem to be facing the problem as mentioned by Andre. I checked
through our traces and found the statement "WorkFlow is Calling MSLink TRM
Handler". Is this what you mentioned about?

The Cedarbank works perfectly, but another sample i am trying out just does
not work. Can you give details on how to check if i am "driving the CICS
Client correctly to use the Link model".

Sachin

"Rob Beardsworth [MSFT]" wrote:

Sachin · Guest

Yes, I am receiving the same error as Andre (803 and Progress code 90). After
trying out Cedrbank sample (compiling and placing the tcpmship), i ahve not
modified the code there. Instead i have placed another cobol file to include
the below code and am trying to execute tcpmship.
And, yes, of course there could be some bug in the code.

Here's the source code of the prog
WORKING-STORAGE SECTION.
01 IO-AREA.
05 MSHIPLNK-CONTROL-AREA.
10 IP-ADDRESS PIC X(15).
10 PORT PIC S9(4) COMP.
10 TIME-OUT-SECS PIC S9(4) COMP.
10 RESOLUTION-TYPE PIC X(3).
10 TRANSACTION-REQUEST-MESSAGE.
15 TRANS-ID PIC X(4).
15 CLIENT-IN-DATA PIC X(35).
15 OPTIONAL-USER-DATA REDEFINES CLIENT-IN-DATA.
20 CID-USERID PIC X(8).
20 CID-PASSWORD PIC X(8).
20 CID-LINK-TO-PROG PIC X(8).
20 CID-COMMAREA-LEN PIC S9(4) COMP.
20 CID-DATA-LEN PIC S9(9) COMP.
20 CID-VERSION PIC X.
88 CID-VERSION-1 VALUE X'00'.
88 CID-VERSION-2 VALUE X'01'.
20 CID-FLAG-1 PIC X.
20 CID-FLAG-2 PIC X.
88 CID-PC-NONE VALUE X'01'.
88 CID-PC-OPEN VALUE X'02'.
88 CID-PC-USE VALUE X'04'.
88 CID-PC-CLOSE VALUE X'08'.
20 CID-RESERVED PIC X(2).
15 REPLY-MSG PIC X(80).
10 RET-CODE PIC S9(9) COMP VALUE 0.
10 ERR-NO PIC S9(9) COMP.
10 ERROR-MESSAGE PIC X(80).
10 DATA-LENGTH PIC S9(4) COMP.
10 ENABLE-LOGGING PIC X.
88 LOGGING-IS-ENABLED VALUE 'Y'.
88 LOGGING-IS-DISABLED VALUE 'N'.
05 COMMAREA-USER-DATA.
10 DATA-RETRIEVED PIC X(3000).

PROCEDURE DIVISION.
MOVE 'xxx.xx.xx.xxx' TO IP-ADDRESS.
MOVE xxxx TO PORT.
MOVE 200 TO TIME-OUT-SECS.
MOVE 'TRM' TO RESOLUTION-TYPE.
MOVE SPACES TO TRANSACTION-REQUEST-MESSAGE.
MOVE 'HSTP' TO TRANS-ID.
MOVE SPACES TO CLIENT-IN-DATA.
MOVE SPACES TO OPTIONAL-USER-DATA.
MOVE SPACES TO CID-USERID.
MOVE SPACES TO CID-PASSWORD.
MOVE 'HOSTPROC' TO CID-LINK-TO-PROG.
MOVE LENGTH OF COMMAREA-USER-DATA TO CID-COMMAREA-LEN.
MOVE LENGTH OF COMMAREA-USER-DATA TO CID-DATA-LEN.
MOVE X'00' TO CID-VERSION.
MOVE LOW-VALUES TO CID-FLAG-1.
MOVE X'01' TO CID-FLAG-2.
MOVE LOW-VALUES TO CID-RESERVED.
MOVE SPACES TO REPLY-MSG.
MOVE 0 TO RET-CODE.
MOVE 0 TO ERR-NO.
MOVE SPACES TO ERROR-MESSAGE.
MOVE LENGTH OF COMMAREA-USER-DATA TO DATA-LENGTH.
MOVE 'Y' TO ENABLE-LOGGING.
EXEC CICS LINK PROGRAM('MSHIPLNK')
COMMAREA(IO-AREA) END-EXEC.

On the HIS server side i have configured the HIS to use TRMHandlerMSLink
with the link prog name as HOSTPROC. On turning on tracing on HIS, no error
is mentioned at any point in the trace files except:

1756 00000e50 Aug 17 11:48:50.256 22028 (22028) Transport Receive entered,
maximum 2 bytes to receive

1756 00000e50 Aug 17 11:48:50.256 22036 (22036) Correlation information =
0x00000314 and 0x0000096a for receive operation.

1756 00000e50 Aug 17 11:48:50.256 22030 (22030) Transport Receive exited
normally, 0 bytes rcvd, Data Complete = 1

This last statement i guess is incorrect, cos Cedarbank seems to retrieve
more data from the mainframe.

I get the error "Write Failed" logged on the mainframe end.

Thank you,
Sachin

"Rob Beardsworth [MSFT]" wrote:

Terry Bullington [MSFT] · Guest

The HIP Receive trace entry seems to indicate that the socket was closed
without any data being received which appears likely as you state that a
WRITE FAILED message was logged in CICS. There should be additional
information available in the CICS log containing the WRITE FAILED message.
It should contain additional TCP error information that can help with
problem determination.
--------------------
Thread-Topic: HIP failed
thread-index: AcWoX+xipOU5Ql9tQJeCShpFS5i9Pg==
X-WBNR-Posting-Host: 220.227.179.6
From: =?Utf-8?B?U2FjaGlu?= <Sachin@discussions.microsoft.com>
References: <OvzwS7BTFHA.3332@TK2MSFTNGP15.phx.gbl>
<2cLWTnCTFHA.2184@TK2MSFTNGXA01.phx.gbl>
<E5BB3E55-6722-41DE-B6A4-F9B7000284C6@microsoft.com>
<NyaFX$3pFHA.1204@TK2MSFTNGXA01.phx.gbl>
Subject: RE: HIP failed
Date: Tue, 23 Aug 2005 20:57:19 -0700
Lines: 194
Message-ID: <89093D2C-CACD-4E84-ACF5-FC3D522B1E96@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
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!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.hiserver.general:1917
X-Tomcat-NG: microsoft.public.hiserver.general

Yes, I am receiving the same error as Andre (803 and Progress code 90).
After
trying out Cedrbank sample (compiling and placing the tcpmship), i ahve not
modified the code there. Instead i have placed another cobol file to
include
the below code and am trying to execute tcpmship.
And, yes, of course there could be some bug in the code.

Here's the source code of the prog
WORKING-STORAGE SECTION.
01 IO-AREA.
05 MSHIPLNK-CONTROL-AREA.
10 IP-ADDRESS PIC X(15).
10 PORT PIC S9(4) COMP.
10 TIME-OUT-SECS PIC S9(4) COMP.
10 RESOLUTION-TYPE PIC X(3).
10 TRANSACTION-REQUEST-MESSAGE.
15 TRANS-ID PIC X(4).
15 CLIENT-IN-DATA PIC X(35).
15 OPTIONAL-USER-DATA REDEFINES CLIENT-IN-DATA.
20 CID-USERID PIC X(8).
20 CID-PASSWORD PIC X(8).
20 CID-LINK-TO-PROG PIC X(8).
20 CID-COMMAREA-LEN PIC S9(4) COMP.
20 CID-DATA-LEN PIC S9(9) COMP.
20 CID-VERSION PIC X.
88 CID-VERSION-1 VALUE X'00'.
88 CID-VERSION-2 VALUE X'01'.
20 CID-FLAG-1 PIC X.
20 CID-FLAG-2 PIC X.
88 CID-PC-NONE VALUE X'01'.
88 CID-PC-OPEN VALUE X'02'.
88 CID-PC-USE VALUE X'04'.
88 CID-PC-CLOSE VALUE X'08'.
20 CID-RESERVED PIC X(2).
15 REPLY-MSG PIC X(80).
10 RET-CODE PIC S9(9) COMP VALUE 0.
10 ERR-NO PIC S9(9) COMP.
10 ERROR-MESSAGE PIC X(80).
10 DATA-LENGTH PIC S9(4) COMP.
10 ENABLE-LOGGING PIC X.
88 LOGGING-IS-ENABLED VALUE 'Y'.
88 LOGGING-IS-DISABLED VALUE 'N'.
05 COMMAREA-USER-DATA.
10 DATA-RETRIEVED PIC X(3000).

PROCEDURE DIVISION.
MOVE 'xxx.xx.xx.xxx' TO IP-ADDRESS.
MOVE xxxx TO PORT.
MOVE 200 TO TIME-OUT-SECS.
MOVE 'TRM' TO RESOLUTION-TYPE.
MOVE SPACES TO TRANSACTION-REQUEST-MESSAGE.
MOVE 'HSTP' TO TRANS-ID.
MOVE SPACES TO CLIENT-IN-DATA.
MOVE SPACES TO OPTIONAL-USER-DATA.
MOVE SPACES TO CID-USERID.
MOVE SPACES TO CID-PASSWORD.
MOVE 'HOSTPROC' TO CID-LINK-TO-PROG.
MOVE LENGTH OF COMMAREA-USER-DATA TO CID-COMMAREA-LEN.
MOVE LENGTH OF COMMAREA-USER-DATA TO CID-DATA-LEN.
MOVE X'00' TO CID-VERSION.
MOVE LOW-VALUES TO CID-FLAG-1.
MOVE X'01' TO CID-FLAG-2.
MOVE LOW-VALUES TO CID-RESERVED.
MOVE SPACES TO REPLY-MSG.
MOVE 0 TO RET-CODE.
MOVE 0 TO ERR-NO.
MOVE SPACES TO ERROR-MESSAGE.
MOVE LENGTH OF COMMAREA-USER-DATA TO DATA-LENGTH.
MOVE 'Y' TO ENABLE-LOGGING.
EXEC CICS LINK PROGRAM('MSHIPLNK')
COMMAREA(IO-AREA) END-EXEC.

On the HIS server side i have configured the HIS to use TRMHandlerMSLink
with the link prog name as HOSTPROC. On turning on tracing on HIS, no error
is mentioned at any point in the trace files except:

1756 00000e50 Aug 17 11:48:50.256 22028 (22028) Transport Receive entered,
maximum 2 bytes to receive

1756 00000e50 Aug 17 11:48:50.256 22036 (22036) Correlation information =
0x00000314 and 0x0000096a for receive operation.

1756 00000e50 Aug 17 11:48:50.256 22030 (22030) Transport Receive exited
normally, 0 bytes rcvd, Data Complete = 1

This last statement i guess is incorrect, cos Cedarbank seems to retrieve
more data from the mainframe.

I get the error "Write Failed" logged on the mainframe end.

Thank you,
Sachin

"Rob Beardsworth [MSFT]" wrote:

Sachin · Guest

Terry,
The CICS log dump contains the following trace:
TASK # 0000863 NEW SOCKET=+00001
TASK # 0000863 ENTER CONNECT
TASK # 0000863 IP ADDRESS=xxx.xx.xx.xxx
TASK # 0000863 IP CHARACTERS=xxx xx xxxxx
TASK # 0000863 IP DECIMALS=xxxxxxxxxxxxxx
TASK # 0000863 CONNECT RETURNED EINPROGRESS
TASK # 0000863 ENTER WRITE-TRM
TASK # 0000863 WRITE DATA TO SOCKET
TASK # 0000863 WRITE FAILED RETCODE=-00000001 ERRNO=+00000057
TASK # 0000863 ENTER EXIT-THE-PROGRAM.
TASK # 0000863 ENTER CLOSE-THE-SOCKET.
TASK # 0000863 END OF MSHIPLNK PROGRAM

Does the ERRNO indicate anything? I was checking some files where it
mentioned that 57 error number indicated socket not connected. Is this any
indication what the possible error can be?

Sachin

"Terry Bullington [MSFT]" wrote:

Terry Bullington [MSFT] · Guest

From looking at the code for MSHIPLNK it appears the we are getting a
connect failure and it is being masked by the call to WAIT-FOR-WRITE-EVENT.
This would explain the "not connected" error returned by the write call.

Do you have any firewalls in place and did you have to go through some
administrative process to get CedarBank working? If you did then maybe
with the new client you are using a different port that may not be set up
completely to pass through your firewalls.
--------------------
Thread-Topic: HIP failed
thread-index: AcWpID/NtEleEblfQbucpCcW6v39CQ==
X-WBNR-Posting-Host: 220.227.179.6
From: =?Utf-8?B?U2FjaGlu?= <Sachin@discussions.microsoft.com>
References: <OvzwS7BTFHA.3332@TK2MSFTNGP15.phx.gbl>
<2cLWTnCTFHA.2184@TK2MSFTNGXA01.phx.gbl>
<E5BB3E55-6722-41DE-B6A4-F9B7000284C6@microsoft.com>
<NyaFX$3pFHA.1204@TK2MSFTNGXA01.phx.gbl>
<89093D2C-CACD-4E84-ACF5-FC3D522B1E96@microsoft.com>
<moNMjvMqFHA.472@TK2MSFTNGXA01.phx.gbl>
Subject: RE: HIP failed
Date: Wed, 24 Aug 2005 19:54:02 -0700
Lines: 267
Message-ID: <C8942782-29CF-4A83-BB4B-B13D9739753F@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
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!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.hiserver.general:1922
X-Tomcat-NG: microsoft.public.hiserver.general

Terry,
The CICS log dump contains the following trace:
TASK # 0000863 NEW SOCKET=+00001
TASK # 0000863 ENTER CONNECT
TASK # 0000863 IP ADDRESS=xxx.xx.xx.xxx
TASK # 0000863 IP CHARACTERS=xxx xx xxxxx
TASK # 0000863 IP DECIMALS=xxxxxxxxxxxxxx
TASK # 0000863 CONNECT RETURNED EINPROGRESS
TASK # 0000863 ENTER WRITE-TRM
TASK # 0000863 WRITE DATA TO SOCKET
TASK # 0000863 WRITE FAILED RETCODE=-00000001 ERRNO=+00000057
TASK # 0000863 ENTER EXIT-THE-PROGRAM.
TASK # 0000863 ENTER CLOSE-THE-SOCKET.
TASK # 0000863 END OF MSHIPLNK PROGRAM

Does the ERRNO indicate anything? I was checking some files where it
mentioned that 57 error number indicated socket not connected. Is this any
indication what the possible error can be?

Sachin

"Terry Bullington [MSFT]" wrote:

Sachin · Guest

Terry,
We have no firewall in between our HIS server and the mainframe. We did not
require any administrative process except for defining program ids and
transaction ids.

What are the other reasons possible for not receiving the
WAIT-FOR-WRITE-EVENT? Can it be any problem with the set up on the HIS side?

Sachin

"Terry Bullington [MSFT]" wrote:

Terry Bullington [MSFT] · Guest

I can't think of anything that might be wrong on the HIS side as you appear
to be getting there via a valid port number and are getting the correct
flow control processor invoked (TRMHandlerMSLink). Give this a try change
you client so that you use the same port number that you have mapped to
CedarBank. This should lead to a failure at a different point as you will
not be sending the correct data.

Also at some point you should consider using ELM rather than TRM, it is
more efficient and has no effect on your server or client code (other than
calling for ELM rather than TRM). Don't do it now because we don't want to
muddy the waters any more than they already are.
--------------------
Thread-Topic: HIP failed
thread-index: AcWp6P5jSRkzeGXISQeaW664sANV4Q==
X-WBNR-Posting-Host: 220.227.179.6
From: =?Utf-8?B?U2FjaGlu?= <Sachin@discussions.microsoft.com>
References: <OvzwS7BTFHA.3332@TK2MSFTNGP15.phx.gbl>
<2cLWTnCTFHA.2184@TK2MSFTNGXA01.phx.gbl>
<E5BB3E55-6722-41DE-B6A4-F9B7000284C6@microsoft.com>
<NyaFX$3pFHA.1204@TK2MSFTNGXA01.phx.gbl>
<89093D2C-CACD-4E84-ACF5-FC3D522B1E96@microsoft.com>
<moNMjvMqFHA.472@TK2MSFTNGXA01.phx.gbl>
<C8942782-29CF-4A83-BB4B-B13D9739753F@microsoft.com>
<6vDtdyZqFHA.472@TK2MSFTNGXA01.phx.gbl>
Subject: RE: HIP failed
Date: Thu, 25 Aug 2005 19:51:01 -0700
Lines: 312
Message-ID: <7FE273CD-9FBE-44D4-93DA-7DC854B7B963@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
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:1927
X-Tomcat-NG: microsoft.public.hiserver.general

Terry,
We have no firewall in between our HIS server and the mainframe. We did not
require any administrative process except for defining program ids and
transaction ids.

What are the other reasons possible for not receiving the
WAIT-FOR-WRITE-EVENT? Can it be any problem with the set up on the HIS side?

Sachin

"Terry Bullington [MSFT]" wrote:

Sachin · Guest

Terry,

Sorry for the late reply.
But i did try this out. What i did was:

Deleted the CEDRBANK listener on the HIS.
Placed my listener using the same port. (local environment).
Executed the CICS program.

But i still get the same log in event viewer and retrieve the same "Write
failed" error.

Also, just asking, i am doing a WIP call to this cobol program, which will
do a HIP to retrieve the data (this is just a showcase demonstration). Will
this scenario cause the problem?

Sachin

"Terry Bullington [MSFT]" wrote: