DSXchange

Of course... but the problem seemed simpler than that. I guess we'll see.

Well... in this example you left off the "./" from the front, that would cause it to fail on most systems as the current directory (represented by the ".") is not typically in the PATH. Nor is your "cli" directory... or it would have worked. Lastly you are in the Korn s...

Then it would seem your "cd" is failing. If you were actually in that directory and issuing the command you've shown us, there's no reason for it to throw the error you posted that I can see. Does it work if you issue it manually and not "in code"?

Hard to say being on this side of the glass but I'd guess you're not being selective enough updating the columns. Only update the column for the record you have received. When it says "xref" only update the xref column. When it says "alt_id" only update the alt_id column. All oth...

I honestly doubt you have any kind of a "select statement" in your target.

You don't need to explain anything again, we all get the requirement. What's not happening is you are not understanding the solution which has been provided. Perhaps this revolves around the concept of "processing" the records after the "*". If in your mind that means "read&...

What happened when you tried? What datatype did you get for those fields when you imported the metadata? For your first question, I would ask that of your official support provider. I'd also be curious what exact 8.x version you have.

First thought - in your derivation check for null not an empty string as they are not the same thing. Other than that, you'd have to explain to us what it is doing, what kind of output you are seeing so we can provide cogent help. Right now all you've basically said is "it doesn't work".

He wants you to show us. Do a listing of the files in that directory and post the results here. We want to see what you are seeing.

It might be the spaces in the pathname, as a test can you try again from a location that doesn't use the "long" filenames? Meaning, no directory longer than 8 characters.

Why would you struggle with something for 10 days when the error message specifically says to contact support? To me that means it is not a 'expected' or common error and that it will require help from the vendor to resolve.

And no, it's not something I've ever seen or had to deal with.

sanygup wrote:Please contact your support provider if you encounter problems.

Did you?

That SET command may need to be in the Open / Before-SQL section rather than in there with the DML. It would for Oracle if it is of the "alter session" variety, no clue about DB2.

No, I don't mean a connection password but rather the "password" that is the encryption key. Check your syntax.

So... short answer? No.