DSXchange

How can we increment the surrogate key value for every insert in to target database? By adding one to the previous value, which you initialize from the target table. Or by using a sequence in the database. There are key management routines in the SDK, but no way to initialize these out of the box -...

Do you have the XP sp2 patch for DataStage installed on these clients?

There is a 7.5 version of QualityStage, so you definitely would not get version 6. Version 7.5 can be called from DataStage 8.0, but only via the plug-in stage in server jobs; you can not use the new DataStage/QualityStage Designer to design version 7.5 QualityStage jobs, nor benefit from the "autom...

OUTER join. It will work.

Why did you post this in the MetaData forum?

It means that you have not imported the routines - in this specific case the before/after subroutine InitialHashCreation - that the job calls when you imported the job.

Given the original request

venkat_kp wrote:What is the correct syntax for the modify stage.

I do not believe the OP was looking for the Transformer stage function.

That is easy. In Designer, instead of doing a regular compile, choose Force Compile from the File menu. It forces re-doing of the Transformer stage: generation of C++ source, plus compiling and linking thereof.

There are no such things as drivers from Microsoft that run on UNIX. That was my original point.

True, but the same restrictions apply. The function generating the error is BCI.Put - doesn't that ring any alarm bells?

Use a Filter command to bring in only the good rows. Use a second Sequential File stage with the logically inverse filter to capture the bad rows and deal with them separately. The Sequential File stage reject link won't help you in general, though it may for specific cases; it captures rows that do...

... and not possible on the UNIX command line in any case.

I understand that the ODBC stage supports only sequential mode for SELECT, but can execute in parallel for Upsert. It fakes this by establishing multiple connections. Ask yourself what would be the advantage of parallel select if there's only one table (non-partitioned). If it's any consolation, the...

Blank is not a valid timestamp, therefore you can not insert it in a timestamp field. If you are writing to a text file, you can replace NULL with a Null Field Value, but blank is not the same as NULL; you might need to convert blank to NULL in an upstream stage. If the text file is fixed width form...

In Modify stage functions can take only one argument.

In days_since_from_date() the source date must be a constant. It can not be an input column.

If you want to do transformations, you must supply the metadata for the columns involved, on both the input and output links. RCP only looks after the pass-through columns. (And destroys your ability to perform a meaningful lineage analysis.)