DSXchange

If we're referring to their content, they represent the underlying datastore for DataStage metadata, run time information, table definitions, etc. etc. etc. etc..... XMETA is the 8.x implementation, which uses a hybrid, as there are some functions that were better kept in the pre-8.x storage model. ...

...or use alternatives to ereplace.... Field() might work well, with <surrogate> as a delimiter.

Ernie

Too much there for a first attempt. Start with your odbc table, going to a flat file. Dump a few rows. Make sure it works. Make sure you can see the xml content. Make sure you are comfortable with the xml content. Cut/paste that content into its own flat file. Play with it. Be sure you can read it f...

Something is still strange here.... Can you confirm two questions? a) Is the message oroginally created and written to a queue by an MQ application, or by a Java JMS application? b) Is there ONE xml document per MQ message, or many? (ie...is this a whole "file" of XML messages, or one sing...

Well...first lets assume you can get the column FICXML into your Job. People have reported success using longvarchar, varchar, etc. for CLOB datatypes (search thru the forum here)........assuming you can get it "out" of the database using normal stages, send that column down a link to the ...

Don't use the Sequential Stage....use the External Source stage...go to the table of contents at my blog url below...there is a section on reading xml documents...... you pass the full qualified filename of your xml into the xmlinput stage...

Ernie

What sort of lineage are you looking for? If you are looking for lineage "thru the jobs" to identify transformations and jobs called one after the other, then you do not need to do anything...... that lineage works regardless of the tables. Export the jobs and the lineage will work the sam...

You are (probably) simply observing the difference between "Table Definitions" and "Shared Table Definitions". In 8.x a new object, called a Shared Table and also known as a Physical Data Resource, was created to provide a "collection" of columns that is used among Data...

Keep in mind that being "always on" is a way to reconcile the start up overhead of ETL in the real-time space. ETL tools do a lot of work for you....they initialize connnections, they preload lookup tables into memory, they prepare and validate SQL, they authenticate connections, they init...

Not sure...as noted above, I can only guess that it's an install issue. Support may have seen something like this.

Ernie

It may depend on the complexity of the document, but this may not be that difficult.... Can we assume that the xml content you want to split is coming from disk, database or message queue? (I was thrown by the thoughts on "trigger" which is generally associated with "writing" xml...

No...you still may be able to do lineage....it depends on what artifacts you were successful in importing. The Import/Export Manager does support earlier releases of Cognos...... Let's take a look. At the home page of the workbench, on the left, there's a pull down. You will see an entry for BI Repo...

...you don't. I was thrown off course by a comment in your third entry above.... "My first goal is now to export the data from the SQL-Server and than import it to the "Infosphere Information Server" installed on a "Windows 2003" with a DB2." If you want to review the m...

What is the final goal? As lstsaur has said, you can use xslt inside of DataStage, but there are some caveats. Typically you are still catering to the DataStage engine and relational model, and ultimately sending rows and columns to the output. It sounds like your desired result is something differe...

It's been a long time....I think it was included by then, but it may still have been a separately installed entity called Message Pack. Either way, it won't cost you anything...if it's not in your palette, call your provider and find out where you can get the "Message Pack" for your releas...