DSXchange

I would guess that you installed DataStage in a different location than the old installation. Therefore to "reattach" the old projects a number of steps must be taken. 1. In the new engine insert entries into the UV.ACCOUNT table that match the entries in UV.ACCOUNT in the old installation. 2. Use V...

If it is enabled, you may be able to open the page on your server using a regular browser.

When you assert that the data are sorted, the Aggreagator stage must include a check for "row out of order" - and abort if one is found.

It is probably this check that accounts for the difference.

"Phantom" means background process.
22076 is that process's process ID.

That there's a problem in DSD.RUN suggests that there's a bug in the vendor's software. Contact your support provider.

6.0 to 7.5 is a transparent upgrade. Nothing needs to be changed. The jobs will be upgraded automatically. Of course, you won't have much of the new functionality in those jobs and job sequences. But these can be added in the usual maintenance cycle. Don't forget to export AND back up the version 6....

3) This will have no effect. The tables that govern run-time execution are not indexed, with the single exception of DS_JOBS, but its access uses the primary key (NAME) via its hashing algorithm, and therefore does not use any of the table's indexes. As noted earlier, I believe your delays are prima...

UTF-8 is not a standard - there are many variants of UTF-8. DataStage itself uses an idiosyncratic encoding called UV-UTF8. UTF = "Unicode transformation format" and the 8 means that it's an eight bit encoding (there are also 16-bit encodings). You might like to try ISO 8859-1 (sometimes erroneously...

In case you missed it, the part in square brackets goes ahead of the part in parentheses. The part in square brackets is the format string, the part in parentheses is the input column name.

A "regular" dimension is one - it doesn't really have a name - that is a parent table to a fact table. That is, the fact table has a foreign key that is resolved in the dimension table. Conformed dimensions are simply shared by more than one fact table. The time dimension is a typical case - every s...

You should be able simply to "promote" an older version.

How do you attempt to run the job, and what error message is generated?

You've specfied comma as the delimiter, and DataStage is finding \n character. You can not have the \n character here. Or have all \n characters; specify it as the delimiter, and use ls -1 to get the list of file names.

^M is not a space character. It is a carriage return, or Ctrl-M, or Char(13). It suggests that this file was generated on a Windows system.

Try using a filter command in the Sequential File stage that uses tr -d to remove the \r characters.

Leaving the reject link in place would also have yielded the desired result.

Time to mark this thread as resolved?

Whatever your job is doing is precisely what you have programmed it to do. Does the before-job subroutine exit cleanly? (You might like to include a DSLogInfo() call as the last executable statement of the routine.) You may not have an infinite loop, but a hang. In the former case, the job will eat ...