DSXchange

Could this be similar to the "not enough space" and remapping the object using "ldedit" (which I am not sure exists on your LINUX)?

If you are renaming from the Designer, make sure that you have the job closed there as well.

to reiterate:

dsusr wrote:...check the precision and scale...

(and post your settings as well)

The warning message means that DataStage detected a duplicate key while building up the lookup table and only stored the first key and it's corresponding data values. When doing the lookup with actual data, only that value is in the table and therefore only that value is returned.

Two options that immediately come to mind are: (a) Lock the table during the load process so that Cognos can't generate reports during that time. (b) Load to a different table name, then in a closed SQL block lock the original table and delete it, then rename the new table to the old name. I prefer ...

The definition of what a "complex" file contains is very loose. Many, if not most, COBOL structures can be read in sequential file stages. The CFF stages makes a lot of things easier to reqalize and has support for such things as "OCCURS DEPENDING ON" which the sequential file st...

Umm, if you had gone throught the thread it would have become clear that port 31358 is used as the default port for client communications and has nothing to do with database connectivity; that is controlled and defined by the database itself and not datastage.

This thread should contain what you are looking for.

$APT_CONFIG_FILE
$APT_DISABLE_COMBINATION

should be in every PX job. The latter can be removed once the job debugging is finished.

What are the DS_AUDIT permissions, are they RW for your user? Can you get to the TCL prompt or use the administrator and enter the command "COUNT DS_AUDIT" - that will show if there is an error in the file.

DataStage Server is fully recursive. You will need to declare your routine within the routine itself in order to call it, though: DEFFUN maxXmlLoopRoutine(Param1,Param2) CALLING "DSU.maxXmlLoopRoutine" should do the trick. edit/append I see you use "maxXmlLoopRoutine" and "m...

Either demote the warning message to "informational" or suppress the warning altogether; or sort your data and avoid generating the warnings in the first place. I prefer using the latter method, as that is more efficient.

What is the option at version 8, priyadarshikunal, if you post that the original poster might try to see if it works at 7

You cannot use the "view data" in DataStage to correctly view multibyte data, unfortunately.
Is your DB2 instance and/or table also set up to use UTF-8?

I don't think that the command-line option has an "append" switch so it might be better to just create 4 files and then "cat" them together.