DSXchange

In that case it does sound like the patch listed by Kryt0n is your most likely solution.

I would still do a full export, remove the old, install the new and then re-import on the new.

It isn't that easy to identify all those processes. One way would be to do a "ps -ef | grep phantom" which will show the parent processes of started jobs.

This could be done by using a transform stage and stage variables. Store the last Col1 value in a stage variable, when it changes for a new row then output a string "{NewValue}:CHAR(13):Char(10):{Col2}" otherwise just output the contents of Col2. The output of the transform stage must go t...

It sounds like you have 2 separate machines; in that case a simple export from the old and subsequent import into the new project should not cause any problems.

Take a look at this DataStage Wiki page for some history on DataStage and it's nomenclature.

While I haven't experimented with version 8 configurations as much, at Versions 7 and before the critical issue was not the actual IP address but the hostname of the DataStage server, which could not be changed after installation, since that name is hardcoded at installation time in several places. ...

Only one person can edit a job at time and be able to save it. You will need to wait for the other person to close their copy before you can make any changes to it.

While I don't have a Windows 8.1 installation, it might speed things up if you could post your DSParams values for the compiler switches to this thread, that way anyone with the same software version can compare to see if the error might lie there.

After the file has been loaded with data, do a "ANALYZE.FILE {YourHashedFile}" from either TCL or from the admin client. Add 10% to your current number of groups and using "PRIME {YourNumber}" to get the next higher prime number and choose that as your MINIMUM.MODULUS value used ...

Is this a warning message or an error message causing the job to abort? One option you have is to sort your incoming data according to your aggregation group(s).

Also, could the file be in a remotely mounted location? You can also try to locate what is happening at line 553 by going into TCL or issuing the following command from the admin tool : VLIST DSD_BP DSD_SEQOpen.B the first column is the source line number. Sometimes one can decode the action from th...

It is clear that your actual data format and metadata don't match. Start off with the first field, what is it called, what is the PIC clause for it and have you used a binary or similar editor to compare the actual file contents with your picture clause?

How about partitioning your database according to this key, then a delete operation could involve just removing one or more database partitions.

What happens when you choose a dataset in the window; doesn't it open up the dataset details window?