DSXchange

If it is a join with more columns, you can let it pass through and do an index on the LIKE column after the join.

So add a transformer after the join to constraint rows which satisfy the index.

If the match is complicated - something like '%A%B%C%', then you can write your own function.

Does the reference INTO WHICH you are doing the LIKE come from any database table? If yes, you can push LIKE in the stage linking the table rather than using the dataset which is the result of its extraction. Alternatively you can write a buildop to look for pattern. Btw, how big is this LIKE table?...

Try
and use the output as a lookup to identify duplicates.

Are you asking the framework or solution to identify whether to reject or not?

What is the source? If db, you can do in SQL.

'uniq -c' on second column and a 'grep -c' on 3rd and 4th column (combined) can do.

Alternatively, an 'awk' through the data must solve your issue.

There may be multiple records for the month+year combination. something like one for each day. So you may be getting different values.

What are you key links to lookup? Does the mentioned sql returns more than one row?

Do you have any parameter near the case structure?

Via webconsole.

Search.

Search "lparams"

Does the SQL run successfully outside DS ?

Did you search?

Try webconsole

Get a row generator / seq file with pattern and associated value.

Do an inverted pattern match using index - i.e. locate pattern in word rather than word of a pattern.

If it matches, then set it to the associated value.

Cross it with a generated list of values like below

Installments,InstallmentMonthNo,Days
0,0,0
1,1,30
2,1,30
2,2,60
3,1,30
3,2,60
3,3,90
..........
........
50,1,30
..........
50,50,1500

This will give you both months and days.

You will have to configure you reference, but I will leave that to you.

That is because you are using the os level single user authorisation rather than individual ones.