DSXchange

Try using the Connector wizard and specify ODBC Connector. Make sure that the DSN is properly recorded in uvodbc.config.

Do you have "first line is column names" set in the Sequential File stage?

This information is stored in the DS_AUDIT.CREATOR column for the creator, and in the DS_AUDIT.MODIFIER column for the modifier. Note that MODIFIER is part of an association of multi-valued fields called MODS. I suggest you search DSXchange for examples of how to query DS_AUDIT.

You could perform the import (read) using a single VarChar column (which could be trimmed in a Modify stage) and then perform the parsing in a Column Import stage (which can use a schema file). An added benefit is that your parsing can be performed in parallel mode.

No. What error/warning messages appear in its log? What was being executed at the time? What message appear in ITS log?

Make sure, too, that your repository database is starting successfully.

"DataStage TX" is no longer part of DataStage, and is properly called WebSphere Transformation Extender, or WebSphere TX.

Your question properly belongs in the DataStage Enterprise Edition forum.

If you don't move it, Craig surely will.

The function in a Modify stage is string_trim() and requires that you specify which character you want trimmed and from where.

The problem is in your configuration file. It must properly mention the node on which the job is started (I'm assuming you're not in a grid configuration here).

My guess is that you do not have write permission to RT_BP545 directory or its parent (the project directory). Is your umask properly set to 002?

Is this question really related to WebSphere Transformation Extender?

Help us to help you. Answer our questions.

Otherwise we can only guess, and the answer is likely to be 42.

There's no need to do anything external if you use Arnd's solution.

The solution from srinivas.g requires that the file be pre-processed - it does not matter where.

Just click on its subject after you've opened the IBM DataStage Enterprise Edition forum.

Each instance of a multi-instance job has its own user status area.