DSXchange

There have been a few thoughts on this topic in the forum....search around....but for a few other considerations... QualityStage is totally integrated now, into DataStage. This is one of the most significant reasons, outside of new stage type functionality that is here or coming on top of the 8.x pl...

I would suggest that you first research each of these topics as a separate unit, and apply that also to your testing and learning curve. Search extensively thru the forum here on each of the thre major pieces....review the doc for each....write simple jobs that explore and test each separately befor...

Hard to say... most likely a typo or other error in the Description property. Check all the columns. Be sure that the columns parsed by a prior XMLInput Stage have NOTHING in the Description property.

Ernie

Putting together multiple independent nodes requires that you build it in pieces... search thru the forum to find references to Kim Duke's website and a document he keeps there called Best Practices for XML.....a document written by one of our developers several years ago. Nice document that describ...

I think I see the issue. Sorry I didn't notice it before. In order to get DataStage XMLOutput to treat these as separate elements (whether in a greater parent or not, which you still may need to do), you need to get them truly into two rows. I failed to notice first time around that the columns are ...

You may need to group those together, as they probably should be in their xsd..... for the sake of testing, try wrapping those three elements in a larger element, such as "detail": .../detail/add1/text() .../detail/add2/text() .../detail/city/text() Make one of them the repeating element a...

there is a specification in the root of the document for the name of the xsd. If specified there, and if available to the DataStage engine, you can check the validate box and it will validate the current document against that particular schema..... lookup "xml schema validation" on the web...

Have an xsd that defines the formal elements....then check for validation..... "new" or "strange" elements will result in a rejection that can be captured down a separate link.

Ernie

You still should try having "multiple" XMLInput Stage instances.... not just multiple links coming from one. Get the XML to be processed in separate processes and see what impact that has...

Ernie

Hard to say what to advise you here, except that you need to start breaking things down to find out where it works and where it blows up. Reduce it dramatically. Follow your XML stage with a transformer and exclude all but maybe 3 columns and maybe 1 row. Be certain that they are 100% character. See...

have you tried sending the data from the flat file, thru a transformer to many XMLStages? If it's such a painful XML document to parse, perhaps you will have gains by using interprocess and having those xml documents work concurrently. This might cause you bottlenecks later on, but its worth looking...

...but it's hard to tell here, because Nicole is seeing "some" of the signs that it would have been licensed.... still, better safe than sorry. Find out the formal licensing and then look at options for configure/install/re-install, etc.

Ernie

absolutely.

First, contact your rep and find out exactly what licenses you have. Then its probably time for a support call to determine the best steps to take. It would seem that you could run the install again and be certain to choose Information Services Director, but there may be other particulars.

Ernie

Without knowing things about your machine, it's not possible to be sure that this will help, but consider that there may be some benefit to using Inter-process row buffering in combination with manual parallelism to send the rows to independent XMLInput Stages....and then re-collect them later. If t...