DSXchange

Yeah....hard to say. Namespaces can be very confusing. Technically speaking, those sub-elements are "in" that particular namespace....but I'm not sure what it (xslt, what the stage is using under the covers) does with the xpath in this particular case. I usually figure out what is needed a...

Not sure why you received the ??? ...that's one I haven't seen before. I'd have to try it.

....but in the meantime just edit them out of the Description and try it. It will probably work just fine.

Ernie

I didn't have time to look thru yours, but compare to my source code at www.dsrealtime.com (go to the table of contents...scroll to find some posts on java, and then download the code that is there -- it isn't named "java" [I think it had to be uploaded there as "pdf", so you wil...

It depends....are each of those independent nodes repeating on their own? If so, then it's no different than reading multiple relational tables and making decisions on how they should be combined downstream. Grab your common "keys", whatever they are (higher level node element and attribut...

I would agree.....there's more than just truncation going on here.

It's by design, Ray (the "all must be approved before publish" issue)....so we have to deal with it for now...though I agree with your sentiment.

Ernie

I haven't tried it, but "in theory" I suspect it will work, using the xmlInput Stage....of course, the details of namespaces and elements/attributes will have to be fully populated on each of the output links, and you won't be able to send the details down the "same" link, even i...

This assumes that these two Jobs are indeed designed to be "always on".....not every ISD enabled Job will be "running".....if it begins with an ISDInput Stage, then yes, it should end up running. ...check again the deployments and the log, as suggested by other posters. ...what i...

How are you reading in your xml. Be sure you read it in as a filename via external source stage.

Ernie

There are several ways you can approach this.... The first is to try and find an element at the lowest level (the lowest level for which you want "rows" retrieved for each repeating element) that is not optional..... ...but if there isn't one, work with the setting called "Repetition ...

As Ray notes in another thread, you use a bridge to bring in Cognos metadata. Via the Import/Export Manager, or via the InfoSphere Metadata Asset Manager if this is 8.7.

They both have their own Project conventions. They are on this user interface together, but really are separate purposed offerings. Create a project for each one when you are using that particular technology.

Sounds like a perfectly normal message --- it possibly has nothing to do with the queue......but it could be getting truncated or something. Do this: Write the single message from the MQ Connector to a Sequential Stage. Use Format options of Delimiter=NONE and Quote Character= NONE. Be sure that you...

cool. Thanks Ray. I'll try them later today..... much appreciated.

Ernie

I should have noted that I've tried a variety of INSERT statements on the input link, at one point adding an association to the CREATE to see if I could insert to the association.....

Ernie