DSXchange

Usually it means that your xml contains namespaces (the xs: is actually in your xml document, in front of the element and attribute names), and is in your xpath (look at the description property of each column on your xmlInput Stage output link), but you don't have the namespace declared in the name...

I think the lookup is the simplest, and also the most consistent (it's doing exactly what your "real" lookup is doing), but perhaps there are other ways to more easily detect that the database is up and available.

Ernie

I was referring to the "programmatic" reason for losing the connection....ie...the dba of the database where you are doing the lookup establishes a timeout rule that disconnects all threads without activity after 15 minutes (I see this all the time).... in that case, set the max time to li...

I've seen this before. Too bad the job doesn't abort. One solution is to lengthen the timeout from your rdbms, and another is to make adjustments to the maximum runtime, so that the job recycles more often. A solution that I've thought about but have never tested is to have a "heartbeat" t...

That and much more.

The first simple test is to make sure you can just open it in IE.

Also, it might be a code set issue also [you will need to do some research on the settings that are available in the header of an xml document as to things like UTF-8 or UTF-16, etc.].

Ernie

What exactly are you sending on the input link to MQ? The best practice I've used is to have one single column.....call it "myXMLmessage" with longvarchar and long length and put a single "/" in the Description property. ...then look carefully at the maximum length that you are s...

Yes...it can be done...it's not "easy", but it is definitely do-able. A Server Transformer can send multiple links into an ODBC target.... one link (say) for an insert to Parent table, another link for (say) the insert to a child.... depending on what is happening in each row upstream, the...

Interesting pattern..... I doubt seriously if it was designed to be used in that fashion, especially within an EE Job.... In fact, I'm entirely surprised it didn't generate an error. Such "passive" (classic source/target) type Stages are not usually designed to support "flow thru"...

...and also describe what your incoming records look like.... (where are they coming from and what is their organization)..... Also, it would seem as though customer2 is a sub-element of customer (inside the first customer element?).....show us the structure of the xml you need to create for your we...

try storing it in a longvarchar....you "may" have success with your rdbms clob or xml columns, but DataStage's support for such columns is not consistent across all stage types and protocols. Do some testing trying to get inserts to work with each of those datatypes until you find one that...

Yeah.....you still see this sort of thing every once in awhile.....usually it's with tools that were written when XML was new --- someone insisted back then on having xml in the "model", but formal xml api's weren't used in the code, or the skills weren't there, etc. ....if the xml node is...

bravo. Absolutely.

Ernie

First, we need to know a few things... a) do you need to parse the xml into individual columns (break out the elements), or are you just keeping them intact as whole xml docs? b) if so, you'll need to separate them "before" xmlInput, because it's two separate documents. Once the two questi...

It's not easy to do, but it can be done....you have to build the header separately in an upstream stage (Transformer, or xmlOutput if it is really large and complex). As to your ultimate goal, if your service requires that you first "sign in" and then respond back with "another call&q...