DSXchange

1) So, is DataSet the best equivalent of Hashed File in parallel Jobs to do a lookup? 2) Okay, here is the kind of situation that we are into, because of which we were thinking of making use of Hashed Files. We are planning to load a table's data into Hashed File. Then, in another job, call a routin...

Hi, We know that there is a possibility of making use of Server routines in Parallel Jobs. We are planning to write a server routine where we would be reading data in a Hashed File. If this is possible, then using this server routine, we should be able to read through the data in a Hashed File in a ...

Hi, We are currently working on Server Edition and are planning to move to Enterprise Edition in the near future. Recently we tried to ftp a file from Mainframes using the FTP stage. It turned out to be a bit pretty slow. It processed at about 120 rows/sec as shown in the performance statistics. We ...

Thank you DSguru2B and Craig.

I haven't had any problem (in terms of performance) so far on making use of this technique.

Hi, Here, this is our scenario. We have a lookup logic to be done. We use a first Job just to load a Hashed file. And then in the second Job, we use this Hashed File through a UniVerse stage to do the lookup. There are 2 reason for using UniVerse stage here - 1) To do a range lookup and 2) To get mu...

Yes, you are correct. I would tell you the scenario. I create the Hashed File using key X. Key X is the primary key in the source table and so there is no any rows that are missed while writing in the Hashed File. Then I do a condition < Y in UV stage (where Y is a date field). Here is all that I do...

Hi, Case1 : We had designed a lookup logic where the data for the reference link is fetched using ODBC stage from an Oracle table. We had used ODBC stage because we wanted to make use of the property "Reference link with multi row result set". Case2 : Then we decided to make use of Hashed ...

I had this issue resolved.

While writing to the Hashed File stage, I checked the option "UniVerse Stage Compatibility" in the Stage properties. Then, when I read it using a UniVerse stage, it reads the Decimal fields correctly.

Thanks.

2) If your whole hashed file will not fit in 128mb then it will put it in cache. Also when you are writing to a hashed file in cache then it will take it out of cache when it exceeds 128mb. As per the point you have mentioned above, if I try to write around 1 million records into the Hashed file, t...

Hi, We are using the Hashed Files for doing the lookup. We just like to get certain informations clarified on this. 1) Does Hashed files have good performance only till the number of records that are loaded into it is less? We would have around 5,000 to 10,000 records as of now that needs to be load...

I write the value using a Hashed File stage and read it through a UniVerse stage. So, you mean that in this kind of scenario, we will be getting this warning message whenever we make use of a Decimal column. So, does it mean that I should try avoiding making use of Decimal datatype wherever I write ...

Hi, We are working in version 7.1 on Windows. We would like to know if there are any known compatibility issue of 'Decimal' values between Hashed File stage and UniVerse stage. We write data to a Hashed File where the metadata for a column is Decimal(9,6). A sample value written to this column is 75...

Yes, I do get the same identical output in both cases. Ok, here is a sample of the column values that is in a particular sorted order, 001ZQ 002ZQ 001ZR 001ZT E4400 E4400 If I specify this as to be 'Ascending' in sort order, then I get an error as DataStage expects the 3rd row to be in the 2nd posit...

The incoming data is already sorted on the column that I want it to be aggregated. The source is from a flat file. The column on which it is sorted contains a combination of alpha-numeric values. So it is not in an ascending or descending order that DataStage expects but it is groups based on a part...

Hi, I did a sample test and found this, a bit strange result. I did a comparison run using Aggregator 'without' and 'with' asserting that the incoming rows are sorted. I tested it for about 1 million incoming rows with data being in a sorted order. I expected that the Job should perform better if we...