DSXchange

Here's one for our UV experts on board.... am trying to figure out how to insert multiple rows on an input link to the UV Stage, where each row is really just a new value to a multivalued column. Here's a simplified example: CREATE TABLE FRED (col1 char(10) not null primary key, col2 char(10) multva...

Yes. I suggest that you separate the two technologies and learn each one separately before trying to combine them. Get your MQ Connector working, sending your xml to disk. Once you are comfortable with the way you are reading the queue, start working on xml. Write and test separate jobs that read th...

RCP works via Metadata Workbench just fine....but it's important to understand the definition of what "works" means. If this is a 100% RCP job (ie...one that has absolutely zero column information), then there simply isn't any column metadata in the job. It doesn't exist. So --- what Metad...

don't put anything in that data element for the output link, unless it is one of the WMQ type of data elements. The xml data element has very special purpose, usually for use in an xmlOutput Stage, and is beyond the scope of this discussion. Leave it blank. The message from MQ at this point is nothi...

That's certainly one way to do it, but the other (as noted above) would have populated the "namespace" box with the particular namespace value for the soapenv prefix....which probably would have looked something like: xmlns:soapenv="http://www.w3c.org..../.../..." That would have...

....you have to pass the xml content thru one of the xml stages first....xmlInput or xmlStage (you will have to learn how to use those stages)....but if you are getting the xml content in your target, whit its tags, then it sounds like you are using the MQ Connector perfectly!

Ernie

The most critical thing about Metadata Workbench is it's ability to trace data and illustrate data lineage. "Where does this value come from?" is a problem that plagues every enterprise. Metadata Workbench provides the opportunity to answer that question in minutes...instead of days. The ...

how did you create your metaadata? did us use the xml metadata importer? if so, "load" the tabledef into the namespace property of the trsnaformation settings.

The Connector can handle * both * the MQ Client API and the MQ Server API......the Stage has to be installed with the desire to use one or the other.... ...the Connector is set up to be coordinated with the DTS stage for distributed transactions and work queues.... ...the Connector supports end of w...

DataStage and QualityStage Jobs are automatically "in" Metadata Workbench. Unless you knowingly used istool export from some other instance of Information Server, to create an .isx file, then there will be no reason at this time to use istool import. Where is the metadata that you are tryi...

istool imports metadata from .isx files that were created by "exporting" the metadata assets from "another" Information Server.

Use Metadata Asset Manager (among other things, such as DataStage), to import your assets from the database.

Ernie

...probably a good idea to open a new thread for this discussion, with a new more specific subject, as it may help others.

You need to import it again if there are changes, and decide if you want/need to keep those changes. If you are in 8.7, the history of imports is kept in great detail when using the Metadata Asset Manager. In earlier releases, you will need to keep greater administrative track of your metadata, wher...

There is no better place to start than with the documentation....and then threads here in the forum...there are also articles at my blog (below) and others.

isnt there a direct wire protocol driver for odbc on sql server?

Otherwise, javapack is well documented, and with lots of posts here in dsxchgange and check out the url in my signature -- the TOC has a section on using java with DataStage