DSXchange

Two stages, one handling the inserts and one handling the updates. The logic is determined upstream in the job design.

It might, if there are lots of indexes and constraints to be checked on the target table.

But that's not a DataStage problem.

Welcome aboard. :D

What is your timeout setting? How do you know it doesn't time out?

Temporarily change the name of the "read from" hashed file to one that exists (for example VOCLIB). Validate the job, which will create the hashed file in the Hashed File stage that has the input link. Then change the name of the "read from" hashed file back to what it needs to be (the one you have ...

I don't believe that's correct, but will need to check. There is another possible value, for mainframe jobs. Will post back once I've checked.

This simply means that you have not installed any plug-in (= optionally installed) stage types that support the View Data capability.

Except on Windows, which doesn't use the ds.rc scripts.

However, you do need to verify the inheritable permissions on the folder into which you are trying to write the file.

pmadhavi wrote:I am not able to use Ereplace or Convert or any other similar function in the transformer.

Why not?

You need to pass parameter values to a shared container via its Properties once the shared container has been painted onto the design canvas. This is done from the Repository view, but otherwise is an identical process to painting a stage onto the design canvas. It's good practice to click the comma...

... because JOBCONTROL.H contains the DEFFUN declaration for DSGetJobInfo()

$INCLUDE DSINCLUDE JOBCONTROL.H not required sleep 20 strFileName = 'Directory name' : "/" : File Name' mismatched quotes Call DSLogInfo(strFileName, "Job Control") OpenSeq strFileName To objFileVar Else Create objFileVar Else ErrorCode = 1 End End WeofSeq objFileVar Call DSExecute ("UV", "SELECT N...

One job sequence to rule them all.

But only on the documented versions of Red Hat. AS 3.0 is one of them.

I do not believe that there is.

It is DS_AUDIT. "DS.AUDIT" was a typo, which has since been corrected via the edit facility. Clearly this is an example of a Type 1 SCD. These things happen occasionally. "Table" and "hashed file" are interchangeable terms in this particular context.