Slow record count on AS400

Good point, Ryan.

However, the client already HAD spend all that money before we first got
there. IBM did the sizing. The machine seems quite big to me. Now telling
them that they could have gotten a better (quicker?) solution cheaper could
possibly make them upset.
I can still do a lot of tuning to bring down the package build time from
presently 14 hours to ??? hours. There are a lot of good suggestions about
this on the LIST.

Actually when I first posted this question it was not primarily the time
spend during builds, it was more a question of understanding what was going
on. Still, I appreciate your comment.

Thanks, Gerd



B732 - ERP8, Unix, a little AS400, Windows, Oracle, SQL, WTS, JAS
 
Re: RE: Slow record count on AS400

Gerd,

We have CO on the as400 and our package build time for a complete client and server package lays between the 5 and 6 hours depending when we start this. So yes 14 hours is a long time. Our first package build on XE took use approx. 2.5 days!!

Have you checked the indexes use for the central objects?
have you changed that odbc block size?
what kind of dep.server do you use? (cpu)
are there running other programs on it?
 
Gerd, is this still an issue for you? We came across the same problem recently on one of our client sites that had just loaded 5 european languages. We found a fix by disabling the sqlpkg support on the central objects odbc of the build machine - in our case it's always the deployment server. Build times went back to normal.
 
Yes, kind off. The client got used to the long build-times, they went live and will not create to many full packages. Still, it's great news for all other As400 clients we have, all got language loaded.
Just curious, what was the build-time difference for you ?
Thanks a lot, Gerd
 
Back
Top