DSXchange

The two are equivalent, assuming you mean <element> </element>

Reviewing this thread. A truly frustrating situation when the mainframe folks aren't communicating. It has probably been said in earlier parts of this thread, but be ABSOLUTELY CERTAIN you are working with a quality editor that allows you optionally to see every row in its full HEX format. That's cr...

That's the best approach due to the fact that there is no formal standard for JSON schemas. Note --- Be careful when completing your document to fully represent your arrays...meaning...if you have a truly repeating subnode, then put more than one value in that node array. I haven't checked carefully...

JSON Schema has seen some success, but is not widespread --- not like xml schema and its formality. The Hierarchical Stage uses a formal JSON document --- best suggestion is to find a "complete" one that has at least one instance of each element, and preferably, two or more instances of an...

Wow. Missed this one. Sorry! For validation, even though it may be overkill in this case, I would still choose the Hierarchical Stage, if only because it provides a LOT more options for control of the validation of your schema.....it's also faster, and can more easily (if and when you need it in the...

"The moment it is defined as list, it needs a separate output link even though it is a child for company." Not true. You can go "as many nested lists deep" on a single link as you want. ...meaning that "Company" and "Department" elements and attribute values c...

The Hierarchical Stage is many times faster as it uses a different methodology to more intelligently parse the xml. Multiple output links? ...that's simply the nature of a hierarchy if you are putting the data into relational tables. Of course, if you are just doing this to back up "chunks"...

...misread your original email...I see you are "reading" the xml. ...and yes, you would aim for a single output link for each complete "path". ...and 100 output links? Perhaps...but that is normal....especially because typical "normalization" of such a hierarchy would m...

You dont necessarily need one link for every list (actually, it is generally one link per complete "path", where a path might have many nested lists) but it is the most typical.....because those independent paths are frequently coming from many different sources, such as multiple relationa...

yeah.. a lot of it depends though, on "how dynamic"? For example, if it can be one of (say) 8 xsds...then just have 8 instances of the xmlOutput Stage or the Hierarchical Stage (actually, you could probably do it in one big hierarchical stage instance, but I would prefer multiples, just fo...

Not really possible, because an xsd could mean structure change, different groupings, different hierarchy, multiple leafs, etc. It's not like a "schema" change in a relational environment. ....and the Stages take that into account and their metadata isnt dynamic on the links or in the asse...

Indeed...they are used extensively for many functions and operations, especially now with the IA thin client. I am not an expert on IA, but I suspect that the issue you are having may be due to some latency in the index. This might not be the exact issues, but the re-indexing process may offer you s...

I happen to like XML, so I would probably research doing this via a stylesheet. I've only touched stylesheets lightly, but found it very easy to create attractive displays of xml content without too much difficulty or having to dive really deep (it is a very attractive way, for example, for those wh...

...that output looks like a trace of some kind. Please describe what you are doing inside the REST Step, the options you chose, etc.

Ernie

Depending on the size of the document, one thought is to just pre-process it....put the entire xml document into a single longvarchar, and then pass it thru a Transformer and hit it with something like ereplace(), and zap all of the x123: namespace prefixes to q999: or similar scenario. ...basically...