DSXchange

Did you see my reply in your original post re: the wsdl you used?

Also note that if the web service already returns something to you in XML, that you don't need the XML Output stage - just write it out using a Sequential File stage. Or I guess an XML Ouput stage in pass-through mode would be ok...

If you are writing a true 'csv' as in a 'comma separated value' file with a .csv extension, then Excel should load it up properly. What does the file look like when you open it in Notepad?

So, not RTI at all but rather you're utilizing the Web Services PACK. It's hard to tell if the server you are trying to connect to is down or if your metadata is incorrect.

Did you have any issues when you imported the wsdl?

And it's apparently not an RTI job but one utilizing the Web Services PACK.

I'd worry more about the 'system error 998' than the tns issue. And since this has happened post-patch, I'd suggest you contact IBM support and open a case.

Ok, so you've got a problem with an RTI Enabled job. First off, there's a specific forum for the RTI / SOA Edition, you need to repost your question there. Secondly, you need to explain how you are 'running' the job, if you've deployed it using the RTI Console, if your environments are all set up, e...

Are you sure that's all that is going on in your job? Those aren't messages I'd expect to see if all you had were XML Input and XML Output stages, hence the question.

Is this an RTI Enabled job perhaps? Or also include a Web Services Client or Web Services Transformer stage?

Oh my, the flamboyant Mr Humphries.

That was me. My apologies. Hard to know gender in all cases, even with English names - and don't get me started on 'handles'... like 'DSGuru2B'. For all I know 'he' is a very clever PHP script.

At a very high level, a Sequence job is the same as a Batch job. It's just that you have a GUI to generate the Sequence job and you need to hand-code the 'Batch' job. Other than that, they're both 'job control' code. Of course, when you write it yourself, you can extend the functionality considerabl...

Actually, according to the docs, any child job is supposed to inherit the warning limit of the job that calls it. Which means it all goes back to the limit on the 'main' top level Sequence.

If that's not happening, report it to your Support provider as a bug and let us know the outcome.

Thank you, thank you very much. I'm here all week. Try the veal.

The only reason you'd need to use 'custom sql' is if you were using an ODBC stage as it doesn't have that update action for some silly reason. The OCI stage does.

Why are you even considering a 'basic' approach for this? The functionality is built into the stage - the update action of 'Delete existing rows' for example. You just need to send it the proper keys.

What is CurrentDate() and what does it's output look like? I'll wager it is not the proper format, gets 'converted' to null by Oracle and then fails the constraint.