DSXchange

Or what I will do is, create a small server job with just a transformer and a hashed file and update the status of each job sequence by calling this job in each of the 4 job sequences at success or failure ends and use UtilityHashLookUp in my 5th job sequence to see the status of the other 4.

What is the error message you get when your job aborts?

Basically the transformer will perform a Left outer join, so the columns from your reference table will be NULL if there isn't any match.

If you want inner join, you should specify a constraint to filter out the unmatched records like below.

Not(ReferenceLinkName.NOTFOUND)

In your db stage, did you give the parameter within quotes? If not, I would suggest trying it out...

Not sure about the maximum but 75 should not be a problem... I have used in 100s...

SandhyaShetty21 wrote:If I am directly importing the code without making any changes to read-only parameter what problems can i expect.

I don't think that will give you a problem but all you can do is, view or run the job. You will not be able to edit it.

Did you mean to say UPDLOCK?

Did you try with a user variable activity in between, passing your command output to a variable and then using your user variable in the email subject?

Why dont you just write all the different records to different datasets and create 3 separate jobs to do your insert, update and delete and run them in the sequence you want?

So this is your problem. You create the chunk with full XPath twice so its obvious that you get your root element for every record. And the exact same way should work. From my best knowledge, that is the only way to do it. Just to make sure, you just defined the XPath with '/' or did you even mentio...

From what I see in your sample XML, it seems you're not just creating this XML in one step. If you are creating your repeating XML tags in a separate step and appending that XML chunk in some columns like <store>. If so, don't define XPath for those tags, just put a '/' and specify it as XML in data...

What is the NLS map you were using for your original file? I guess this can be handled by using a proper NLS setting.

Unfortunately, yes, the data contains *. How will you, even manually differentiate the '*' in the delimiter and the data? We have had a similar file once but we never got '*' in the data. Maybe you can check with your source system and confirm if the delimiter can be changed to something which will...

'|' is your field delimiter and not record delimiter.

Then I believe, you should use the same NLS map while reading it as well. Did you try that already?