Occasional failure to Submit UBE's from Citrix to AS400

[amwalshjde]

Occasional failure to Submit UBE\'s from Citrix to AS400

We have been on Xe for a long time, and within the past year have seen an increase in users not being able to submit a job from citrix. If they try it again, it will work. It doesnt occur in any pattern, and we have not been able to get detailed logs.

The user gets the popup, "remote Job" with the text "An error occured submitting batch R30812, Version to CSD2001PRD.

In the users jde.log we see:
2976/10360 Wed Mar 18 06:48:00 2009 lanchube.c648
Submitting R30812, CSD2001PRD to XXXXX (with Specs).

2976/10360 Wed Mar 18 06:48:38 2009 JDEKNUBE.C3328
KNT0000107 - Remote batch process could not be
submitted on XXXXX.


We dont keep Debug on so on the AS400 the JDEDEBUG logs are all blank. We could not find an JDEXXX.log for this, but our <B7333SYS/JDENET_N> logs show the following:

Wed Mar 18 08:24:44 2009 netrcv.c290
3426-Error from Host=<192.168.XXX.XX> in recv returned A connection with a remote socket was reset by that socket.

135 Wed Mar 18 09:32:58 2009 netrcv.c290
3426-Error from Host=<192.168.XXX.XX> in recv returned A connection with a remote socket was reset by that socket.

135 Wed Mar 18 09:38:51 2009 netrcv.c290
3426-Error from Host=<192.168.XXX.XX> in recv returned A connection with a remote socket was reset by that socket.


This only occurs about 3-4 times a month, and if they rerun all is good. So it isnt a show stopper, just trying to get to the bottom of this. Any Idea's on where I should look next?

Thanks
Aaron

 

[Sebastian Sajaroff]

Re: Occasional failure to Submit UBE\'s from Citrix to AS400

hi,

That message typically says that you have to check your
network (between your Citrix and your iSeries), could also
be related to ODBC bugs (are you on the latest CA PTF?)

 

[amwalshjde]

Re: Occasional failure to Submit UBE\'s from Citrix to AS400

We are running Client Access v5r4m0 Service pack SI26879 on the citrix box. Our network setup is as follows:

Citrix box <--->HP2610 switch<---->AS400

On the switch the citrix box is defined as 100FullDuplex, as is the as400. They are both on the same subnet. When I view the switch status (it's a HP procurve) I do see that there are some Drops Rx. (albeit not many) None of the ports on the switch get much above 10% utilized, nor is the switch CPU being hit hard.

Is there anywhere on the as400, citrix box, or switch that might give me more details as to the issue? Any help on where to look next would be great.

Thanks
Aaron

 

[AllisonD]

RE: Occasional failure to Submit UBE\'s from Citrix to AS400

We are running Client Access v5r4m0 Service pack SI26879 on the citrix box. Our network setup is as follows:

I think Sebastian is on it. Make sure you are in sync with the CA Service Pack on all your clients and Citrix. Make sure everyone is running on the same Service pack through the entire communication link.

From: [email protected] [mailto:[email protected]] On B ehalf Of amwalshjde
Sent: Wednesday, March 18, 2009 2:45 PM
To: [email protected]
Subject: Re: Occasional failure to Submit UBE's from Citrix to AS400 (14420 5)

We are running Client Access v5r4m0 Service pack SI26879 on the citrix box. Our network setup is as follows:

Citrix box <

 

[amwalshjde]

Re: RE: Occasional failure to Submit UBE\'s from Citrix to AS400

Darrell-

In this case is the "entire communication link" just the citrix server and the as400? or is it all citrix servers and all fat clients, and application servers that use JDE?

If it is the former, there is only one client / citrix box to consider.

If it is the latter, does this mean that if one client is configured with an older CA Service Pack that all other JDE machines could suffer? For exmaple, one Fat Client could impact a Citrix Farm.

Thanks,
Aaron

 

[jdeKrnl]

Re: Occasional failure to Submit UBE\'s from Citrix to AS400

Aaron,

Do you see any errors in the UBE kernel log?

Cheers,

 

[markdcci]

Re: Occasional failure to Submit UBE\'s from Citrix to AS400

This might be a longshot here, but sometimes when our users change their passwords as they are logging in, and then try to submit a UBE there is a mismatch between the cached password being passed in from the client and the password as it now exists on the AS400. They get the exact same error. Logging out and logging back in fixes it, as long as they haven't disabled themselves. May not be applicable to your case, but the error looks so familiar I had to mention it.

 

[AllisonD]

RE: RE: Occasional failure to Submit UBE\'s from Citrix to AS400

You communication link for a Citrix thin client is Desktop Client, Citrix S erver(s), Enterprise Server (AS400).
For a Fat Client its Desktop Client, and the Enterprise Server(AS400)

In either of these paths, if CA service packs are mismatched, it has the po tential for random acts of violence....otherwise known as Errors...

From: [email protected] [mailto:[email protected]] On B ehalf Of amwalshjde
Sent: Thursday, March 19, 2009 6:29 AM
To: [email protected]
Subject: Re: RE: Occasional failure to Submit UBE's from Citrix to AS400 (1 44223)

Darrell-

In this case is the "entire communication link" just the citrix server and the as400? or is it all citrix servers and all fat clients, and application servers that use JDE?

If it is the former, there is only one client / citrix box to consider.

If it is the latter, does this mean that if one client is configured with a n older CA Service Pack that all other JDE machines could suffer? For exmap le, one Fat Client could impact a Citrix Farm.

Thanks,
Aaron

OneWorld Xe SP22 AS/400 V5R2