DSXchange

None. What you find with Search is all there is.

The word is "phantom", and it's nothing more than the DataStage term for a background process. Your job ran as a background process, so a "phantom" generated the message. Somewhere in your job a non-numeric value has been supplied when a numeric value was expected - for example in arithmetic or in s...

-jobstatus is valid for 7.x also.

There is an extraneous "/" in the pathname. Getting rid of it will probably fix the problem. DataStage does not resolve "//" in pathnames.

Is port #9080 blocked by a firewall on your client machine (or anywhere else)?

Last to first suggests that you're using "25R" rather than "25T".

On the Home page there's a link in the top-left panel to "Newsletter", with a link [archive] next to it. Click on that.

The errors appear to be coming from the IPC mechanism rather than from the Sort stage. Are you using row buffering or IPC, Link Collector or Link Partitioner stages? If so, try constructing the job without them, to see whether that cures the problem.

Specify a Sort Merge collector in Sequential_File_24 - which I assume to be the "output file" stage. This will preserve the sorting order. You will need to specify the sort key(s), of course.

CATEGORY is not a primary key field in the Repository, so theoretically it could be done with a simple UPDATE statement. But for safety, and for an approach that will continue to work into version 8.0 and beyond, continue to use the client - it's not that difficult!

Are you running on Windows XP and, if so, do you have the requisite patches (for DataStage) installed?

Whereas another school of thought might suggest text files or Data Sets for the staging areas, as they don't require a database server to be available (and can often be faster).

Experience is what you get when what you expected to happen doesn't.