DSXchange

They haven't posted here in five years. Best if you start your own post and explain to us the issue that you are having.

Yes. You basically write to the file as you normally would but use the SEEK command first to move to the end of the file before writing. Lots of information to be found if you do an exact search for "OpenSequentialFile" here and then start at the bottom of the results with Ray's post from ...

You haven't answered my question. Simply passing back error text doesn't tell the caller there was a problem - raising an exception does. Can you ask the developer or check the code?

So you're wondering if DataStage or Java would be better for which portion - the XML or the SQL Server piece? Your original post suggested the former but now it seems you may have meant the latter. As to the native driver question, ODBC is a 'native driver' for that database so I imagine 'performanc...

Clarify for us what "throws an error message" means... does it use RAISE_APPLICATION_ERROR for that?

Two things. 1) "Datatype not presently supported" should have stopped you right there. If passing a BLOB to the SP isn't supported, this whole approach goes down the drain. You'll need to look into alternates like PL/SQL I would imagine. 2) I don't see the need to add the LF/CR between wha...

Then we're all the way back to your first post and the question you haven't answered yet - detail for us how you are combining the first 10 records and then what failure do you get with the procedure.

You need to verify what exactly it is you are passing in - is it a BLOB or a CLOB - and pass it appropriately. I don't see any circumstances where converting it to hex would be a good idea... unless you've been specifically told to do that by whomever created the stored procedure.

Then you'll need to go back to the original specifications and / or the source to target mapping for guidance.

Do the math in DataStage and then DecimalToString() as I wrote and then use the function as noted by vasudev_koti. That should be all there is to it and you can embed the functions together... or do them in steps via stage variables if desired. And I would drive that decision based on how valid your...

Do you mean what goes in the 'Command' v. 'Parameters' boxes in the Execute Command stage? Shouldn't really matter, put the whole thing in either one. If you really need something, try using CMD as the Command.

So, you are trying to do this in SQL rather than DataStage? If so, what database?

And you still haven't clarified if your target is an actual date datatype or a string.

And? Is that working for you?

... as noted, assuming a DATE is actually what is wanted. Many times when we see a 'date' shown with specific formats needed, what they're really looking for is a string.

That step is only an example ( OR rather simplest example) Usually the simplest example gets you the simplest response and that typically doesn't work out well for either side. Best to put all of your cards on the table right up front so we know what we're dealing with. IMHO. As Arnd noted, can you...