DSXchange

There's no syntax that can magically change the source from non-nullable to nullable in a Modify stage. You can, however, specify that the target is nullable.

Are these entries identical to those on the production server?

You need to ensure that the value passed through $DS_PROJECT is correct: correctly spelled, correctly cased.

Notice that the property name is actually Number of Readers Per Node (emphasis mine).

In a word, NO.

DataStage is an ETL tool, it has no business in the presentation layer.

Can you take a look at the job log to see whether any particular process takes a very long time? Perhaps enable some of the reporting environment variables (especially APT_PLAYER_TIMING)?

Check the response file or install log to ascertain whether your site is using a non-default port number (that is, something other than 9080).

The table structures (and column names) have changed since version 7.x.

DSguru2B wrote:Use the following query at the uv account or admin command, once logged into your project.

This is not a suitable answer for version 7.x. Also it would not work in the UV account.

You have to find the previous run FOR THAT INVOCATION. If there have been many runs with different invocations that particular previous run may already have been purged.

What format of timestamp is your Teradata instance expecting?

If NLS is enabled, parallel jobs use UTF-16 internally.

UTF-16 shares code points 0 through 127 with ASCII. Most implementations of UTF-16 share code points 0 through 255 with "extended", or 8-bit, ASCII.

The story is different for server jobs.

That said, it is working as documented.

Specifically, the folder H:\Datastage_Projects\EIS_Ent/RT_STATUS1554 and its contents.

Looks like you just want to accumulate source columns into a single row until the key changes?

Is the number of source rows per key constant or variable?