Windows Server

Ellen Deak · Guest

I have a BizTalk orchestration that receives a file, FTPs it to an AS400 and
then calls an HIS TI component which executes a CL that processes the data.

When I run the process, all of the commands in the CL execute and process
the data successfully. But, the call to the TI Component always generates an
error.

The following is the error from the Event Log on the BizTalk/HIS Server.

(102) Transaction Integrator reported the following exception to the client:

Component: IFADJDECHN.COOPERSOFT.1
Method: IFADJDECHN

Exception description:
(1588) Exception returned from host: "IFADJDECHN"
An AS400 DPC request returned a server program error, return code = 1281.

--------------------------------------
Our AS400 System Adminstrator is seeing the following errors on the AS400.

CPE3426 Diagnostic 10 10/03/05 11:18:21.795440 QZBSCOMM
QSYS *STMT QZBSCOMM QSYS *STMT

From module . . . . . . . . :
QZBSCOMM

From procedure . . . . . . :
SndErrnoMsg__FPc

Statement . . . . . . . . . : 3099

To module . . . . . . . . . :
QZBSCOMM

To procedure . . . . . . . :
SndErrnoMsg__FPc

Statement . . . . . . . . . : 3099

Message . . . . : A connection with a
remote socket was reset by that

socket.

CPIAD08 Diagnostic 40 10/03/05 11:18:21.795488 QZBSCOMM
QSYS *STMT QZBSCOMM QSYS *STMT

From module . . . . . . . . :
QZBSCOMM

From procedure . . . . . . :
SndCPIAD08__FiN21

Statement . . . . . . . . . : 3064

To module . . . . . . . . . :
QZBSCOMM

To procedure . . . . . . . :
SndCPIAD08__FiN21

Statement . . . . . . . . . : 3064

Message . . . . : Host server
communications error occurred on recv() -

length - TCP .

Cause . . . . . : Error code 3426 was
received while processing the recv() -

length - TCP function for the host
server communications. Recovery . . . :

See any previously listed message(s)
to determine the cause of the error;

if necessary, correct the error and
issue the request again.

---------------------------------------------------

Has anybody else run into this issue with the AS400?

--
Ellen Deak

Terry Bullington [MSFT] · Guest

The error code stipulates that "An error occurred when calling the
program". I suggest that you contact Microsoft support so that they can
have you gather traces so that we can see if the request is properly
formatted when delivered to the host and if anything wierd is occurring
with the connection.
--------------------
Thread-Topic: remote socket reset
thread-index: AcXI6/uLWBztRubvTFqxja+zPxLVRw==
X-WBNR-Posting-Host: 208.10.131.8
From: "=?Utf-8?B?RWxsZW4gRGVhaw==?=" <EllenDeak@discussions.microsoft.com>
Subject: remote socket reset
Date: Tue, 4 Oct 2005 07:00:31 -0700
Lines: 93
Message-ID: <6F7E3B91-2EE3-4FAF-B9B5-A6675C511DC1@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:2085
X-Tomcat-NG: microsoft.public.hiserver.general

I have a BizTalk orchestration that receives a file, FTPs it to an AS400
and
then calls an HIS TI component which executes a CL that processes the data.

When I run the process, all of the commands in the CL execute and process
the data successfully. But, the call to the TI Component always generates
an
error.

The following is the error from the Event Log on the BizTalk/HIS Server.

(102) Transaction Integrator reported the following exception to the client:

Component: IFADJDECHN.COOPERSOFT.1
Method: IFADJDECHN

Exception description:
(1588) Exception returned from host: "IFADJDECHN"
An AS400 DPC request returned a server program error, return code = 1281.

--------------------------------------
Our AS400 System Adminstrator is seeing the following errors on the AS400.

CPE3426 Diagnostic 10 10/03/05 11:18:21.795440 QZBSCOMM

QSYS *STMT QZBSCOMM QSYS *STMT

From module . . . . . . . . :
QZBSCOMM

From procedure . . . . . . :
SndErrnoMsg__FPc

Statement . . . . . . . . . : 3099

To module . . . . . . . . . :
QZBSCOMM

To procedure . . . . . . . :
SndErrnoMsg__FPc

Statement . . . . . . . . . : 3099

Message . . . . : A connection with
a
remote socket was reset by that

socket.

CPIAD08 Diagnostic 40 10/03/05 11:18:21.795488 QZBSCOMM

QSYS *STMT QZBSCOMM QSYS *STMT

From module . . . . . . . . :
QZBSCOMM

From procedure . . . . . . :
SndCPIAD08__FiN21

Statement . . . . . . . . . : 3064

To module . . . . . . . . . :
QZBSCOMM

To procedure . . . . . . . :
SndCPIAD08__FiN21

Statement . . . . . . . . . : 3064

Message . . . . : Host server
communications error occurred on recv() -

length - TCP .

Cause . . . . . : Error code 3426 was
received while processing the recv() -

length - TCP function for the host
server communications. Recovery . . . :

See any previously listed
message(s)
to determine the cause of the error;

if necessary, correct the error and
issue the request again.

---------------------------------------------------

Has anybody else run into this issue with the AS400?

--
Ellen Deak

Neil Pike · Guest

Ellen,

I'm guessing, but how long does the CL process take to run? I'm thinking
about something timing out. i.e. does it work with a minimal size file?

A network trace would be useful to see what is going on at the tcp level.

Are both the server(s) and the AS/400 ethernet connected, or is one of them
token-ring connected? It shouldn't matter as MTU/PMTU processing should give a
working packet size automatically, but the error message is going on about a
length error on receive.

If you can get a sniffer (network) trace I'd be happy to take a look.

p.s. Do your AS/400 folks use a product called "Connect:Direct"? If they do
then there would be another way to achieve this without using FTP/HIS/TI.

p.p.s. Do you actually need the output from the CL back? If not then the
AS/400 job scheduler can always be configured to wait on a file arriving and
then processing it without you kicking anything off at all.

Neil Pike · Guest

Excellent - I was rather clutching straws, but glad it provoked investigation
that led to the resolution.

Possibly you could have made some tweaks at the TI "client" parameter end to
handle those messages, but getting rid of them is just as good!

The error messages were pretty unhelpful on both ends though. Don't know if
MS could have handled it better - a more meaningful error message would be
nice. Something to look at for HIS2006 perhaps Terry?

Ellen Deak · Guest

Hi Neil,

Your suggestions gave my AS400 SysAdmin some ideas.

The problems ended up being caused by some message commands in the CL. Once
they were removed, we stopped getting the error back in BizTalk and it was
able to finish processing normally.

Thanks,
--
Ellen Deak

Terry Bullington [MSFT] · Guest

The documentation for Distributed Program Call is all licensed material so
we can't reprint it so that the customer can look it up themselves.
--------------------
Date: Tue, 04 Oct 2005 22:39:46 +0100
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: Virtual Access by Atlantic Coast PLC,
http://www.atlantic-coast.com/va
Organization: Protech Computing Ltd
Message-ID: <VA.00006331.070690d9@compuserve.com>
Subject: Re: remote socket reset
From: Neil Pike <neilpike@compuserve.com>
Reply-To: neilpike@compuserve.com
References: <6F7E3B91-2EE3-4FAF-B9B5-A6675C511DC1@microsoft.com>
<VA.00006330.061879f6@compuserve.com>
<26A03E0E-9A87-4C22-B4AC-79B8487DC345@microsoft.com>
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: cpc2-cmbg4-4-0-cust221.cmbg.cable.ntl.com 81.96.71.221
Lines: 1
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.hiserver.general:2093
X-Tomcat-NG: microsoft.public.hiserver.general

Excellent - I was rather clutching straws, but glad it provoked
investigation
that led to the resolution.

Possibly you could have made some tweaks at the TI "client" parameter end
to
handle those messages, but getting rid of them is just as good!

The error messages were pretty unhelpful on both ends though. Don't know
if
MS could have handled it better - a more meaningful error message would be
nice. Something to look at for HIS2006 perhaps Terry?

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