Hi,
the fact that the general line is 256kbps means nothing if the network cards on the computers you try to connect has less thruput, so check with your system people to check the thruput between the machines.
you'll probably find that somehwere along the way you have a bottle neck that slows you down.
can you try to ftp, to your client pc, a file from the DS server and see your connection speed?
also you might not be getting the full band width anyway so check it.
IHTH
Roy R.
Time is money but when you don't have money time is all you can afford.
Hi,
was wondering, usually kbps stand for kilo bits per second and not bytes so take that in concideration as well when you think it should run faster then what you get (if that is the case).
IHTH
Roy R.
Time is money but when you don't have money time is all you can afford.
The other problem with a WAN is that there are many potential points of failure, any one of which can lead to a "connection is broken" (81002) error occurring and your having to re-start the client.
Sometimes a dedicated dialup line may prove to be a more viable solution even if notionally slower. Don't forget there's an awful lot of other traffic on that WAN. You've not necessarily got all that bandwidth - you're sharing it with all the other users.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
If only used for development: export all jobs, put them in your favored version control tool and erase all DataStage jobs you don't currently need for development. DataStage gets remarkably slower with a higher number of jobs in a project.
Other tricks are to use DataStage Manager instead of Director to navigate your job designs...
Also, make sure that all your jobs are in categories.
At one site I worked at there were hundreds of jobs not in categories. They all had to be loaded every time the Jobs part of the repository tree view was selected.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.