DSXchange

Which column name were you trying to analyse? Does that column name occur in the error message?

Q.If i import a table def its meta data in datastage, it is stored in common repository... That is not correct except, perhaps, if you use the Connector import wizard. Conventionally table definitions imported using DataStage are stored in the local (project) repository. There are utilities for con...

Possibly that the user name, password or schema is wrong in that particular stage.

You run a column analysis from the INVESTIGATE pillar menu, having selected the column(s) that you wish to analyse, which I am sure is what you are doing.

What do you understand that this error message is telling you?

The key to good diagnosis is understanding the message in the error message.

What's wrong with writing three separate jobs each with correct metadata?

Otherwise investigate an approach that uses Runtime Column Propagation.

Use Nested Condition activities to decide whether to execute jobs. Trigger these based on a job parameter value indicating the region.

Transaction size is not related to ODBC - it is an option that specifies when DataStage will send a COMMIT to the database server. This is true whether using ODBC or a native database API stage.

There is only one active process in this job, so it will be in that process's memory. A hash file is a file for shaping a block of hash. Assuming you meant "hashed" file, and assuming further that you are referring to the read cache or write cache, these may be in the private memory of the...

In version 8 the database used for the repository is whichever one was allocated to the task by whoever installed Information Server. The scripts that create the database, which are run by the installer, configure the database to have auto-incrementing table spaces. Yes it is possible to run queries...

Just Date()

You can also use @DATE system variable, though it is initialized when the job starts and does not change its value while the job is running.

You can also use the System() function. This is useful if you need milliseconds.

They are the same in server jobs. They are different in parallel jobs, where they report per-partition information differently. System variables have already been evaluated, so there's no overhead of calling a function. Therefore system variables should be slightly faster. Macros invoke DataStage AP...

Leave DataStage out of the equation. It's best to regard DataStage as simply another client application to the database server, which uses ODBC in exactly the same way as any other clicnt, typically by calling functions that form part of the ODBC API, which has been documented by Microsoft Corporati...

In the manuals, particularly administration and installation manuals. There is no single physical architecture, though arguably there is a single logical architecture.

You can also garner some information by attending IBM classes, particularly DX437 (Information Server Administration).

In the manuals, particularly the Information Server Administration and Installation manuals.

Use a server job (or a server Sequential File stage in a server shared container). This is much better at handling delimiter character inside quoted text than is its parallel equivalent.