DSXchange

Of course, but it can be unlocked and the RESIZE can be restarted - unless INPLACE of course!

The Manager Guide can. It's completely up to you whether or not you use node pools and how you specify them. Best practice is that the default node pool (the one whose name is "") contains all nodes.

In an SMP environment the fastname is the same for every node.
In an MPP environment more than one fastname is used.

I don't mind private email, provided it is a request to engage my professional services - in this case as a paid consultant.

Cleanup on the Administrator client runs DS_CHECKER on the server. Deleted files (which were recognized as orphaned) are not recoverable except through restoration from export or backup. I suspect that the cleanup process was incomplete. On the server look in the &COMO& subdirectory in the p...

RESIZE is actually restartable these days. And the USING clause means you get two I/O channels rather than one. If you're really worried about locked, use CONCURRENT as well - that is also very robust. (Still avoid INPLACE though - that's a leftover from the days when 80MB was a lot of disk space an...

First it means you're in the wrong forum. This is a question about a parallel job. Second it means that you've hijacked someone else's thread, with a totally unrelated question. That behaviour is severely frowned upon here. Third, you don't seem to realize that a wat is a Buddhist temple. Fourth, it...

Only the obvious one - don't call a stored procedure for every row. In addition to being slow, and depending upon what the stored procedure actually does, you risk the possibility of self-deadlock.

You've managed to feed DateGenericToTimestamp an internal format date rather than an SDK generic date format.

ALL members are volunteers, as it happens. No-one gets paid anything for posting.

There's even a forum for TX'ers !

You should be able to get the Tutorial CD for the asking from your support provider. Indeed, they should have a copy for their own purposes. Even to borrow it would suffice.

If your client is running on Windows XP sp2 you probably need the DataStage xpsp2 patch. This behaviour is one of those addressed by the patch. Ask your support provider to provide the patch.

You can use the Package Installer (on the server) to install the Pivot stage without installing the whole server again. The Package Installer is a script called DSPACKINST.

Read the manual about Package Installer, and go for it.

Probably time to re-install DataStage client. One of the DLLs seems to have been fried on your machine.

Just did the hashed file solution. It's pretty slick, though a really interesting exercise in tuning the hashed file. With GROUP.SIZE 2, LARGE.RECORD 1024, SEQ.NUM it did up to 1000! in 0.120 CPU seconds and 0.000 elapsed seconds (including creating the hashed file). Even stage tracing (microseconds...