DSXchange

Welcome aboard.

Usually this message means that the DSN has not been mentioned in the project's uvodbc.config file. But you say you updated this. Did you create the DSN as a system or file DSN? DataStage can not use user DSNs.

Inspecting the value of the TZ environment variable will help, particularly if you need a more generic solution.

When someone says "installed" I assume that that includes setting up and testing database connectivity (perhaps even installing, configuring and testing database client software on the new DataStage server if applicable), because there would be no point in proceeding unless this had been d...

Note, however, that there are some small errors in Appendix B. For example, handle_null() should be SetNull().

Is it possible to have one of the jobs update a temporary table and move these updates to the main table at a convenient time?

It's reasonable (to use Change Capture stage), and you only need one pass.

Be very careful with these numbers, particularly for short-running jobs. The CPU is sampled only at the indicated refresh interval in the monitor. Whether one is larger than the other does not really reveal much. Maybe the ODBC driver does more processing than the Oracle client software - highly lik...

1) Yes, for some value of "reliable" and if you have sufficient resources on the server.
2) Yes - any load will "affect performance" (whatever "performance" means)
3) Who told you that?

Where do the reject links go?

To create the file use a job that has a Surrogate Key Generator stage with no input and no output.

To initialize the file use a job that has a Surrogate Key Generator stage with an input link.

What operating system is your DataStage client installed on?

Remember back at school, when they taught you about the number line? As Craig observed, -89.62 is less than -88.02. Therefore the Max() function is yielding the correct result. You need to consider what you really want. It sounds like you want the number with the larger absolute value. (If you can b...

You can not read a block at a time in DataStage.

You must read a line at a time and process a block at a time.

This is not difficult, but your mindset is.

Please advise what the precise compiler error is.

Could anyone else in the organization be monitoring the job or have it open ? Just because you close the Director does not preclude that possibility. The locks are on the server.

If this is a parallel job with a Transformer stage, try a Force Compile.