DSXchange

The compiler needs to know about processing node allocation too.

You will find it there. The best bits are Chapters 1 and 2 of parjdev.pdf.

A white paper on PX, differences from server and related issues got written almost two years ago by BigPoppa (since departed from the DataStage world) and me. Its publication on the then Tools4DataStage site was blocked by Ascential on "legal grounds".

What exactly do you want to convert? For example, what would you expect to get by trying to convert a character string like "The Source" into a DECIMAL(10) data type? No database would let you load the raw data, but what kind of number would you expect to see? There is a rich set of conversion funct...

DSSetVar is a function. You are trying to invoke it as a subroutine, using the CALL statement. Curiously, this is possible. The first argument must be the name of the variable that is to hold the result. The following two statements are equivalent, provided that a DEFFUN declaration has been made. R...

You will never be able to squeeze a DECIMAL(18) number into a DECIMAL(4) column, unless the value of the number happens to be sufficiently small (good luck rather than good management). You have two, and only two, choices if you want to prevent the warnings.. The target column must be made capable o...

There's probably an adjacent message in the log showing you the values that were sent to replace the parameter markers in the INSERT statement. Using your knowledge of the metadata, identify which numeric value was out of range. For example: TinyInt can not be larger than 127. SmallInt can not be la...

If you're using ODBC protocols, make sure that the data source name (ICPC) is defined in .odbc.ini and in uvodbc.config.

Otherwise, the name may need to be configured explicitly within the DB2 client software.

A more general solution, that handles weird things that people might do (like use Q pointers or distributed files) is to use the FileInfo() function. This is able to return lots of different information about an open file, including its pathname.
Read all about it in the DataStage BASIC manual.

You create it. If the other person already has one, certainly use their work, but ultimately you need the collection of column definitions in your job design. Best practice is to create it in the Repository first, then load it into your job design. It must have exactly the same number of columns as ...

That was my workaround ( ls -l | awk '{print $6,$7,$8}' ). Problem is on 01 Jan, when the time ($8) suddenly contains the year number of the previous year, which is not desirable in the current context. The problem still occurs if I don't invoke the function, so I think my initial diagnosis was wron...

Have you declared any column to be the key? The key expression is only enabled when you have a key column selected.

Please advise what has changed on the server since the time when you could run jobs. "Nothing" is not the correct answer. Ask the UNIX administrator, the network administrator, the database administrator(s). Check that the various tables (e.g. process table, inode table) have not become full. Has an...

Usually, when that kind of error occurs, the More button is enabled and you can determine what failure has happened. But not always.

Always be alert for the More button becoming enabled.

I've just received that same error on DataStage 7.1 on AIX 5.2. Very simple job design; Folder stage retrieving file names only, Transformer stage, sequential file output. Transformer stage adds a second column which invokes a routine that calculates the file's date/time modified using OpenSeq and S...