DSXchange

You can use KeyMgmtGetNextValue if you're updating, but why would you want to? You're updating an existing row, so you don't need a new key value. You can view the source of KeyMgmtGetNextValue in your Repository using Manager or Designer. It's a Routine. The SDKSequences hashed file is created with...

I've got an AIX machine at home! :D

Best practice is to pre-load a lookup source (for example a hashed file) with the current values and to maintain this during the load process.

Search the forum for "Type 2", "lock for update" and "slowly changing dimension" for techniques.

I too give the "blank piece of paper" advice, but alas it seems that most of the folks are deaf. Or just want to play with their shiny new DS toy!

Anyway, I can make a living doing it right the second time!

Folks, it's GREAT advice!

... and the answer is exactly the same for PX jobs and server jobs. :D

You can not set a job's user status unless the job is running. If the job is running it has not failed.

You will have to find another mechanism.

Why not use a job sequence and test the jobs' exit status? Based on this you can set up a trigger to perform some action if either job has failed.

Probably your target rejected two of the four rows, maybe due to a primary key unique constraint violation. What do your four rows of data look like?

You WILL need to write a routine to use the DSGetLogEntry() function. The function can only retrieve the details of a single logged event. However, why are you using these functions at all in a DataStage job? Use a UV stage or hashed file stage to select from the log, and you automatically get every...

By "appropriate C++ compiler" I mean the one specified in the installation notes for DataStage EE or one with identical characteristics. In general, free or open-source compilers don't cut it.

You will also require an appropriate C++ compiler on the UNIX machine. Do you have this?

This error is being generated by the ODBC driver manager. Check to make sure that the database server is running, and that none of the connectivity requirements (including password) has changed. Test to verify whether you can connect to the database via ODBC using the test software in branded_odbc. ...

There's no documented limit on the number of hashed files that you can have in a job. You will have some issues using cache, which is a finite resource. You may have some hashed files unable to be cached for reading once the cache is full. Avoid having too many hashed files feeding the one Transform...

Then @INROWNUM is a good choice, because it is guaranteed to be unique.

If you have a constraint on the output link, all this means is that you will have gaps in your sequence. If all you're after is uniqueness this is not a problem.

If you don't want gaps in the sequence, prefer @OUTROWNUM.

@INROWNUM is a count of the rows entering the Transformer stage on its stream input link. It is incremented for every row processed. @OUTROWNUM is a count of the rows exiting the Transformer stage on an output link. Separate counts are maintained for every output link. It is incremented for every ro...

There are two easy ways to limit the number of rows processed by a Transformer stage. One is to add constraints to the output link(s), for example @INROWNUM < 100 The other is to open the Constraints editor grid. The rightmost column of this grid allows you to specify a number of rows on each output...