UBEs take too long on 400

[Eastwood]

We are on XE (SP22), DB2 400, co-existence. I need help to make UBEs run faster on the server. The same UBE that runs approximately in 50 seconds locally takes about 3.5 minutes on the AS400 server. We are trying to go live and this is critical to go live.
In order to solve this we have tried the following but could not improve the performance.
1. Deleted the *SQLPKG
2. Checked the value for *PURGE of the QSYS/QPWFSERVER job class which is set to *NO (as recommended)
3. Checked the value of RequestedService=NONE in JDE.ini on server
4. Checked the TCP/IP configuration
5. Checked the mapping for BSFN objects in the OCM which is disabled.

Did anyone ever ecounter this problem?

Thanks-

 

[DBohner-(db)]

Re: UBE takes too long on 400

Is the issue all ube(s) or specific ube(s)?

I logging enabled on the 400?

db

 

[Eastwood]

Re: UBEs takes too long on 400

This is with all the UBEs and I checked logging is disabled.

 

[Larry_Jones]

Clint,

We have always observed that most PCs can run UBEs faster than our HP DS-390 box. Given that the E.S. has a lot more tasks to perform simultaneously than a PC its not so surprising. Think of an Enterprise Server as a powerful Budweiser Clydesdale rather than an Arabian race horse. The Clydesdale may not run as fast but it can haul a heck of a lot more beer than the race horse. Your ratio of run times does make the ES box look particularly slow - but what else is it doing and what is it's configuration?

Cheers,

 

[scottw]

Re: UBEs takes too long on 400

I suggest setting a jobq and have your ubes go to the new jobq so that there is no chance of other jobs getting in the queue ahead of your UBEs. See if this works. If not then start going back through your setup which can be found in your AS400 installation guide. Where are your central objects located? Are they on the server or on your deployment server? Check your
Look at the debug

0003.00
0004.00 [DEBUG]
0005.00 Output=NONE
0006.00 Trace=TRUE
0007.00 DebugFile=JDEB7333/jdedebug
0008.00 JobFile=JDEB7333/jde.log
0009.00 JDETSFile=JDEB7333/JDETS.LOG
0010.00 ClientLog=1
0011.00 LogErrors=1
0012.00 KeepLogs=1
0013.00 RunBatchDelay=0
0014.00 TAMTraceLevel=0
0015.00 RepTrace=0
0016.00

UBE kernel in the JDE.INI
[JDENET_KERNEL_DEF2]
krnlName=UBE KERNEL
dispatchDLLName=JDEKRNL
dispatchDLLFunction=JDEK_DispatchUBEMessage
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

Is your database on the AS400 or is it somewhere else?

Is the speed of you card on the as400 set to 100 and full duplex?

Look at the ube debug level
0208.00 [UBE]
0209.00 UBEDebugLevel=0
0210.00

Hope this helps?!
--
Senior Technical Consultant
17611 E. Tennessee Pl.
Aurora, CO 80017
Work 303-337-1906
Cell 303-885-1405
Fax 303-306-1800

 

[Eastwood]

Re: UBEs takes too long on 400

This issue is with all the UBEs. All the UBEs take way too long on the 400 server.
I just checked the JDE.ini under B7334SYS library and found that Output=FILE under debug section but the UBEDEBUGLEVEL=0. I am going change the value of OUTPUT to NONE and then I will shutdown and restart the services once all the users leave today.

The AS400 we are on is model 820 single processor with 2 gig memory. Full Duplex. My client is a very small shop on co-existence. We are trying to go live asap. And when we are testing these UBEs there is no one else running any jobs because we are still testing.
Hope I have all the answers which will help us solve this performance issue.

thanks-

 

[Eastwood]

Changing OUTPUT=FILE -> NONE in INI did it guys. Thanks for all your responses.

 

[scottw]

Good Job!

--
Senior Technical Consultant
17611 E. Tennessee Pl.
Aurora, CO 80017
Work 303-337-1906
Cell 303-885-1405
Fax 303-306-1800

 

[scottw]

Be sure to clean up your jdedebug.log on the server; they can be rather large.

--
Senior Technical Consultant
17611 E. Tennessee Pl.
Aurora, CO 80017
Work 303-337-1906
Cell 303-885-1405
Fax 303-306-1800