DSXchange

The current XML importer does not support "import" for xsd's. The best solution is to ask for a complete "instance" document, or create one (there are lots of tools that will do that). Then import from the xml instance instead of the xsd. The only significant caveats to importing...

ok...then, if it always just two, then I would just grab the whole "Dates" element in your xmlInput Stage output link (have a column called "DateElement" as a varchar 100 or other similar large length and change the xpath in the Description to be /.../.../Dates/ (without the fina...

It's not a stupid question, but you do have a lot of reading and playing to do........here and in the standard documentation. As for the XML Metadata Importer, you can use either an XML doc or an xsd....assuming the window comes up properly, you can "open" your document or xsd...... You sh...

Please answer the second paragraph in my note above. How much more complex is it? That will help dictate the best solution. This is easy to handle in DataStage, but will require some additional steps.

Ernie

There was a patch early on in v8 for e-o-w, but it may have been prior to 8.0.1 ......are you sure you are on 8.0.1 and not 8.0 ? I agree with Arnd...it's been pretty clean for awhile now, and the early symptom was as you describe...it just didn't work at all.......

Ernie

It's a poorly designed xml document. Would have been nice if the second date was identified as such by its element name....or even better, if each "sequence" contained subelements (or subattributes) of "sequenceNumber" and "updateDate"..... Otherwise, what is represente...

More important is what are you trying to retrieve from XMETA? There are lots of good ways to get metadata out of Info Server without having to actually access XMETA directly --- it depends on what you are looking for....there are exports, APIs, and query tools that are part of Info Server.

Ernie

I haven't looked. v8 has Shared "Tables" and Shared "Files", among a few other things. The dialog to create them from DataStage changes based on that pull-down value. Shared Tables are the most common......people don't use or encounter the Shared Files very often (except when usi...

"usually"? That is an industry observation, not a DataStage one..... why do people choose unix or linux over windows (or vice versa) to run their critical systems? The question is far bigger than DataStage, and (regardless of the direction, windows/linux/unix) is about performance, confide...

....great! However....keep in mind for future reference that it is not necessarily the plugin you used for initial import that allowed things to work correctly......it is that very first pull down on the Locator tab.....it's value is what is critical for Shared Table creation --- (there are some val...

Look at your tables in DataStage. What is the value of the first pull down at the "locator" tab? It MUST ABSOLUTELY be RELATIONAL, or just set it to DB2 prior to creating the shared table. If not...save it as one of those, and then push it again to a Shared Table. Sounds to me like it is a...

ps. Let's get you up onto Release 8. !

Mmm. Tough call. I can't remember to what extent xmlpack2 was made available
For v6. Was this a working job till recently or a new development?

Folder was developed with xmlpack1, which had an xmlreader stage.

Ernie

When you get to 8.x, you will be able to use istool for this functionality. It is available server and client side....

Ernie

Hmm.... I have only one guess on that. Go back into DataStage and look at the Table Definition (any table defintion) that you'd like to turn into a Shared Table def....... open it and find the "locator" tab......click on that and look at the top level property. There are probably a variety...