DSXchange

You can use an ODBC stage (driver for text files). You can use a Hashed File stage to remove the duplicates, as Craig suggested. You can use stage variables in a Transformer stage, but will need to have the data sorted on the SAL field, as Craig also suggested. You can achieve that via a Filter comm...

You can check the condition in the "rules" part of the Lookup stage. If the lookup fails there are four possibilities; Continue, Drop, Fail or Reject. If the condition to undertake the lookup in the first place is not met, the same four possibilities obtain.

Are your Information Server (repository database), WebSphere Application Server and DataStage Server on the one machine or separate machines? If the latter, you're now doing stuff over the network that you used to do locally, which might explain some or all of the increased time. In addition, the re...

The record is discarded in the read stage, so the transform stage would never see it. That's not entirely correct in a server job. If the "contains line terminators" property is set, the line can still be read "successfully" if that field contains line terminators. Methinks you've been too long in ...

Adding one to the year portion always works unless the starting date is Feb 29, in which case you also need to subtract one from the day number. Or you could download a function from here where you will find both AddYears (to date) and AddYearsToTimestamp functions among others. Each has its own doc...

Could you identify the rotten apples in a barrel without inspecting every one?

Then use a left outer join.

pagerakesh wrote:this job takes only 10 min in one server but takes 12 hrs in other server..

What's different between the servers?

Welcome aboard. Is the line terminator legitimately in the data? If so, there is a "contains line terminator" rule that will allow DataStage to handle the field gracefully when reading. Downstream a Transformer stage can use the Index() function to determine whether there is a line terminator in the...

No. All you need is an inner join. Nothing else is required. Inner join will give the correct number of rows.

Left outer join will give additional rows with only NULLs from the right input. This is not what you require, according to the specification you have posted here.

Dollars to donuts the place it doesn't work is in a different project.

Can be achieved in the metadata.

That's the point I've been making.

I think that post refers to a DSX file, meaning a DataStage export file. These are stored on the client machine wherever you specify when you perform an export. What seems to have happened here is that you have imported the job but not a routine (called AggGetRowCount) that it calls. Both of these ...

What you seek to do is a common or garden variety inner join, on the join key column whose value is 123 in your example. Where are you experiencing difficulty?