DSXchange

Iconv() and Oconv() work properly whether or not NLS is enabled. Some conversions behave differently, but it is proper in each case. You can disable/enable NLS via the NLSMODE configuration parameter in the uvconfig file. To change you must shut down DataStage, edit the file, regenerate, and start D...

How about DaysFromDateSince() function?

Monitor can show %CPU (percentage of clock time spent using the CPU). If this is high, then the job is CPU intensive.

You can monitor your system with tools like vmstat and iostat and match the process IDs with those of the DataStage processes.

abhay10 wrote:

ray.wurlod wrote:The job design I posted will give you what you want. ...

no it doesnt hold good for more than 2 same duplicate records...

Yes it does. Because every row from source appears on the left input of the Join stage.

rahul123 wrote:Even If i don't use reject link all records are going to output stream

Yes, that's what "Continue" means.

Something is preventing matching. It's hard to judge what might be causing this, since we don't know what your job design is.

Read my post again. Carefully.

For less than 30c per day (approx Rs12) you can purchase premium membership that will allow you to read the entire posts of the five premium posters. Revenue from premium memberships is 100% allocated to the hosting and bandwidth costs of DSXchange; like all other posters the premium posters are un...

The job design I posted will give you what you want.

They are going down the reject link because they are NOT matched.

Does one lot have trailing space characters and the other not? Incompatible data types? Incorrect/incompatible partitioning on the two input links?

Welcome aboard.

No, you don't need Condition - this allows you to attempt the lookup only if the condition is true (for example IsNotNull(Qtr) And IsNotNull(Year)).

Your Lookup Failed rule will need to be set so that failed lookup input rows are directed to the rejects link.

Without the code it's going to be difficult to determine. Improper data type usually arises from an attempt to use a file variable or subroutine variable that have not been properly assigned or which have subsequently been overwritten. However, there are other possible causes. Please post the routin...

In an SMP environment the fastname is the same for every node mentioned in the configuration file. In an MPP environment more than one fastname is used. If you have only one machine you are necessarily SMP. (DataStage treats NUMA (non-uniform memory architecture) as SMP for its purposes.) If you hav...

Do a lookup first to see whether the record exists. A sparse lookup would suffice.

All the Orchestrate operators are documented in a manual called Orchestrate Operators Orchestrate manuals do not automatically ship with DataStage but can be had for the asking from your support provider. They are also handed out (in electronic form) on most DataStage Enterprise Edition classes run ...