DSXchange

Well... technically there are no data types in a flat file other than string / varchar so you could certainly read it like that and then do an explicit conversion to whatever it needs to be. At least that way you have full control over it rather than letting the stage do an implicit conversion durin...

There's a whole dedicated forum for "QS" so let me get you over there...

wittyme wrote:The parameters do come from input. This Stored Procedure will be in middle of the job.

Bit of an incomplete job design posted, eh? Back to a type of "transform". I'll let others with practical DB2 experience handle the other questions.

Is that a typo in your posted code where there's no quotes around Benefit? If it is and there are quotes in your code, then you'd need to go into detail as to what "not working" means with some examples - input and output.

It would only be a "transform" type if it was in the middle of a job, meaning needing input and output links. Yours is just a source, so select that type.

Where will your input parameter(s) come from?

Why not start by letting us know which tabs you need help with? Also, I need Complete explanation on XML OUTPUT generation through the stage. That's usually called a "class" or "consulting" and not generally covered in a single bulletin board post. You might want to start by chec...

Short answer? Yes, you can certainly nest them.

Is your source field a string or a decimal? Your outer function should be a Right() not a Left(), btw.

Thanks Andy. My two second search for "WAVES DB" only turned up Oceanography sites, that or sites about sound wave and decibels or women in the Naval Reserve during WW2.

So, help me out here. You say your client did not purchase the "WAVES DB", by that do you mean they did not purchase QualityStage?

And the short answer to the question you asked me is: no.

This conversation should probably be taken over into their actual post on the XML processing they are trying to do: viewtopic.php?t=155792

Guessing you've not worked with XML before? High level: You need to generate the metadata from either a sample of the file itself or from an "xsd" you received from the source. That will generate the columns and "XPath Expressions" needed to parse the XML and you can then import ...

Do you want it to be a job parameter? If so, re-read Ray's question.

'XML file structure' IS a single string. Pass it along to your XML parsing stage of choice.