DSXchange

Each repeating node needs its own "output link"....not its own stage. You can have one xmlInput Stage (or xml stage for anyone reading this that has 8.5+ and wants to use the xml stage) with as many output links as you want...... you want to parse the xml only once...but each separate repe...

Each repeating node needs its own "output link"....not its own stage. You can have one xmlInput Stage (or xml stage for anyone reading this that has 8.5+ and wants to use the xml stage) with as many output links as you want...... you want to parse the xml only once...but each separate repe...

the repeating node (accessory) is dictated by the number of "rows" that come in for that particular node. So....from a basic perspective, you would want to pivot each row so that you have "n" rows for each model, where each row contains the model and spec information and one inst...

I don't know if you can run it that way. You might be able to do, but I can't confirm. The xmlInput and xmlOutput Stages are not native Operators. They were written long before osh existed. As such, they may have different characteristics that prevent what you are trying to do, so I am not surprised...

it's all about your classpath(s) at development and compile time, the manner in which the import statements are set up...where you have jar files and other resources......all in all...java development things. Make sure you have a java resource available for the work. Most will have a java IDE alread...

It's a comparison that can't be made on pure speed or technology, regardless of which parser does it faster. Databases have had data types for xml for a long time....each has some very interesting and unique technology for it. Nice support for certain xml constructs, compression, etc. ...but many si...

you can change the text and the logo on the base search page, but that is about it, short of writing your own app.

As has been noted above in various replies, you need one or more of the following: a) someone at your company, who is responsible for LDAP, to research available (if any) ODBC drivers. You can't easily do this yourself--- it needs to be someone who is very close to the LDAP environment at your site,...

A good reminder and lesson for everyone.....if you are dealing with xml the content is nearly ALWAYS going to be 100 character data. Make everything varchar and you will be a lot more successful. Convert it later only if you need to.

Ernie

Does it matter? The key point throughout this thread is that "while it can be done", the management complexities about having two flows in the same Job vs two separate Jobs typically outweighs any benefit or reasons for multiples in a single Job. DataStage has allowed this since release 1,...

I am guessing here, but it sounds like you might be using filtering on the Connector import option.......The addition of more tables may depend on the filtering (if any) that you did the first time. If you selected a particular database, and not filter on specific things below it, then the same impo...

Missed this topic earlier. Yes...MWB can perform lineage thru an RCP job......but...it requires that you have some metadata in order to perform that lineage. Imagine you have a fully RCP enabled job with a relational source stage, a few other stages and then a target relational stage. No column info...

check something else in your job. sometimes it helps to tear it down and just have one single column on your output link...the PHONE_TYPE_CODE ......your xpath looks good. It should return 2 perfect rows for the content you have up above. something else might be limiting your extraction to a single ...

make sure that something in the MEMBER_PHONE node is marked as the only "key" on the output link.

Choose an element that is ALWAYS existing...maybe PHONE_TYPE_CODE. You should get 2 rows from the sample above.

Ernie

Just a guess, but try adding the windows box hostname to your service tier's hosts file if it isn't already.....