DSXchange

Think of DataStage Jobs and Extension Mappings as equals.....(if you are in 8.1.1 or above).... they both connect resources. If you are on 8.1 prior to 8.1.1, then yes, only DataStage Jobs can paint lineage. Lineage is for Shared Tables and Files (and their columns), and Report assets, and for a few...

Hi Doug....tell us a bit more about the patterns you are looking at.....your title is Jobs as SOA (which often is a request/response pattern that rarely has a persistent store), but your initial question is regarding DataSets.... all good questions and thoughts --- just want to get an idea of what y...

Search thru the doc and in the forum for entries on Web Services Pack. It is designed to invoke simple web services from within DataStage. If these are services that provide a limited number of rows at the source, and the same at the target, you can use Web Services Pack for that, usually the WS Cli...

Start here.... since we were discussing it, I decided to put an entry into my blog.... http://dsrealtime.wordpress.com/2010/06/24/data-lineage-vs-business-lineage/ You'll need to at least be on 8.1.1, which came out in June of 2009. This release allows you to create what we call Extension Mappings.....

a) We assume that you have 8.1.2 of BG and Metadata Workbench installed. b) We assume you have working "data" lineage that goes from, perhaps, a Shared Table as a source...thru a DataStage Job...and into another Shared Table as a target. [if not, let's start another thread on that topic......

In 8.1.2 there is a feature called Business Lineage.... it is primarily designed for Business Glossary, but is visible also in Workbench if you also have the BG user role. It's a "higher" level view of lineage...one that includes only the data resources (sources, targetst, reports) in the ...

Nothing in particular.....the MQ Connector can do a lot more things, but most of them have specific purposes......If your job is "working", there should be no reason to change it. Here are some of the more significant reasons someone might move to the connector: It can do both MQ client an...

They become critical for data lineage when you want to connect DataStage Jobs to "other" software, other artifacts and other information....such as profiling details uncovered by Information Analyzer and Discovery, Cognos reports and Packages, or models imported from a variety of design to...

I'm talking here about "Shared Tables"...these are the formal tables that we see inside of xmeta --- the ones created today by using the little wizard inside of DataStage ("Create Shared Table from Table Definition") or via Import/Export Manager, or when you import via a Connecto...

Exacly...it's a leftover from/during the metadata import process....and since <non> "happens" to look like xml, it makes sense that it had a problem. The current xml pack "overloads" the description as a place to carry xpath. Unfortunately it wasn't caught in 7.x. Ernie

It should be just "bytes". What problems are you having? I wouldn't try to view the data anywhere within ds, but if you write it to a sequential file, and open that with an editor that can see hex, I would expect the data to still exist as it was in the original queue..... how you "vi...

Ok...some things to try....

What happens if you just go from a Transformer into MQ? (skip your java stage).
Are you using MQ Connector or MQ Plugin?
What happens when you try the other?
Are you using MQClient or MQ Server mode?

Ernie

I didn't find it at fix central, but maybe I missed it..... maybe it has to be requested specifically....anyway, I've been told that it's number if JR33537, if that helps. Let support qualify the requirement for you --- it's possible that the fix does other things also, or maybe it's rolled up somew...

Hi all... Our engineering team has built a utility that allows the creation of Shared Tables and Shared Files directly from the command line via a .csv structure. Ultimately it will be posted in a DeveloperWorks article, and I will make it available at my blog. Will this be useful? Wanted to get an ...

Do you want that column on your XML? If so, it needs xpath on the input link. If not, I would delete it from the link.

Why did it work before? Chalk it up to "code tightening." I am surprised it didn't get an error.

Good debugging work!

Ernie