DSXchange

1. Yes. 2. Not quite. Perhaps: WISD Input --> XML Transformer --> Transformer --> XML Transformer --> WISD Output Now, maybe XML Input / Output in place of the XML Transformers but for whatever reason I ended up using them (the XML Transformers) instead. And you many not need the XML Output if you'd...

Nagaraj wrote:i saw wisd input stage, it cannot import or do anything with tibco message file.

What makes you say that?

Ray, for 'nuances' I mean how they are used. There is a misconception out there that you always need to use both in a job and Ernie has popped in here in the past and explained that that is not true. Or at least that's what I'm remembering. My search skills aren't turning up the post(s) I think I'm ...

What in that requirement says 'expose the job as a web service'? Doesn't really sound necessary for what you are looking to do unless that's how this message 'file' is delivered to you.

Again, if you have the product you have the dang documentation. It ships on the CDROM in pdf format, surely you can get your hands on that, yes?

Hemant_Kulkarni wrote:After installed the XML patch we got the following warnings could you please guide us to resolve this problem.

Shouldn't you be asking this of whomever provided you the patch? Your support peoples?

If you have the software then you have the documentation. And it would be a violation of their license to send things willy-nilly out to anyone that asked for it.

It's not about Windows versus UNIX. Your first example is the equivalent of a 'get' while the second is a 'put', both in reference to the remote server.

Ok. Is your connection information parameterized? Do those parameters reference environment variables? Does the view data work if those values are hard-coded in the stage?

They allow an 'RTI Enabled' DataStage job to be exposed as a web service and serve as the start and/or end points of the service. If Ernie comes along, I'm sure he can do a better job of explaining the nuances of their use or non-use.

Ok, it doesn't sound like you have configured DataStage for Oracle yet. There are specific changes you need to make to your dsenv file that are documented in the configuration guides. Have you done so? Do you have an Oracle client installed on the DataStage server?

Probably. Or, as Ray noted, include a stage to check the value and when empty bypass whatever is in the loop.

Yup, that would be the first suggestion.

How are you creating the text file? The loop is doing the right thing as the trailing comma denotes a null or empty field at the end. Best to not generate one there in the first place.

Aiieee, the corn daemon! Run for your lives!