Also, folks, this is DS 8.0.1, who the heck knows what's going on with the new repository and how much resources are being hogged down on the DS Server. Is the DS repository, probably DB2/UDB, on the same server as DS? In addition, this is a PX post, so how many processes are firing?
Until you watch the DS server CPU and disk load, you can't really troubleshoot your "slow" performance.
Jobs Executing slower when called from Job sequence
Moderators: chulett, rschirm, roy
Glad we could amuse you, Ken. 
Point taken on the 8.x repository and something I'd been wondering about but didn't want to muddy the waters with quite yet. If all this communication is service based, that probably adds a little 'lag' that wasn't there before, let alone if the repository can now be 'remote'...
Point taken on the 8.x repository and something I'd been wondering about but didn't want to muddy the waters with quite yet. If all this communication is service based, that probably adds a little 'lag' that wasn't there before, let alone if the repository can now be 'remote'...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
There's lag, then there's putting the database on the same server as DS, and then running PX on that same server. How much clocktime are you going to devote to all of those activities? Your DS Director update is going to take a long time. But, if the measurement is job runtime, you have to know what's going on w/r/t server resources.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle