DSXchange

FIND OUT what has changed.

Welcome aboard.

The best first step is Search - DSXchange has been around for a long time and you are not the first to ask this question. This may get you going faster than waiting for someone to answer your specific post.

Clearly this approach, as you have implemented it, is not a good one. You must design any restart capability, and this involves keeping accurate records of (at least the count of) which rows were sent to the target table and, indeed, which ones failed. One way is to tag the target records with a uni...

You MUST design that as two jobs.

The operating system will not permit reading from a file that is being written to.

IsNull() returns a TinyInt, and Trim() can only be applied to a string. This is why it won't compile. Trim() won't like NULL so you have to convert this null before the Trim() function is applied. IsNull() does not convert; it only reports. You need something such as Trim(If IsNull(InLink.Th...

kirankota79 wrote:i am connecting to oracle, i was working with the database since past 10 days and never faced the problem..suddenly it happened.....i am checking it now but still getting hanged.

What changed?

"Nothing" clearly is not the correct answer.

You will not get any support from IBM if you do, even though you can get it to work.

Windows XP is simply not a supported platform for DataStage Server.

TimestampFromString(), surely?

Because, by definition, any Outer Join returns NULL in all columns defined on its unmatched input.

This is regular SQL, not just DataStage.

Or, perhaps more meaningful to read:

There is no DSTOOLS command, on either platform.

However, the DS.TOOLS menu is available - and identical - on all platforms.

The *.trx file is the C++ source code generated when the Transformer stage is compiled.

Your diagnosis of the Field function is incorrect. Field("A|B","|",2,1) will return "B". I suspect you don't have "B" alone as the second field, that it is followed by a field mark (@FM). Therefore you may need Field(Trim(XYZ.$CommandOutput,@FM,"A"),"|",2, 1)

Yes, you do need to specify how the Row Splitter stage is to parse the input field. How have you done this? It is usually done with metadata definitions.