DSXchange

Or you can convert them in DS internal format and then do the comparison.

If your volume is not that high, you can always write the records to HF, but make sure you sort them before writing.

HF will remove the duplicates for you.

The problem is not with the line terminator..its with column delimiter. View your data and see if you have this delimiter anywhere in the record as part of the data...

you can not rename the category..but you can get the same result by creating a new category with the name you want and move the jobs from the category you want to rename to this new category...and then delete that old category.

Or otherwise do search and replace in the dsx

If you are going to use same logic, in different jobs use routine, but if the logic is used specifically for some field in one job you are better off using Stage variable.

I had this problem arise in my job, due to Inter process or row buffering on...you might want to check there. Increase the timeout period for Interprocess (if you have that enabled)

johm73 wrote:Yes those are the fields I'm joining or looking up on

But I dont see that field in your input file.

Whats

bp_file_ques_num--------- bp_file_ques_num ?

Is that how you are doing a lookup?

What fields are you using to join the HF and Seq File..Can you please describe your input and hf metadata..

Do you have any constraints?

how did you put your condition..

Use trim ..may be there is a blank space

substring or []...

Use OCI stage as look up..but with high volume it will hurt performance.

Yes you can, but you will need a process that keeps the track of how many records read/written and can add a extra parameter for start point. Then you can put a constraint using @INROWNUM....and startpoint