Extracting Description from each Stage

rbk · Post by **rbk** » Sat Dec 17, 2016 1:57 am

Hey everybody,
Hope everyone is doing good..
Request your expertise in helping me with this query.

Currently we are trying to reverse engineer a few projects and extract the functionality.

This is to be done with DataStage 7.5 and 11.5.

Is it possible to extract the description from the columns tab of the source stage ?
(Description from the columns tab inside each stage)

Currently we generate the reports using the "Generate Report" option but the descriptions do not seem to be available in them.

With 11.5 I think Xmeta might have this information. We do not have access to XMETA..But if XMETA access were available, it would be great to have some pointers regarding the extraction.

Thank you.

ray.wurlod · Post by **ray.wurlod** » Sat Dec 17, 2016 6:49 pm

These can also be retrieved from DS_JOBOBJECTS in the local repository. The Columns collection is a set of associated multi-valued fields, amongst which are the column name and description.

Since it's the weekend, I don't have access to DataStage to check the actual field numbers right now. Someone else may like to chip in with these.

UCDI · Post by **UCDI** » Mon Dec 19, 2016 8:10 am

I have C that can pull an 11.x table export into an excel csv file. From memory it pulls column name, data type, description, length, maybe one other field. If that is useful.

chulett · Post by **chulett** » Mon Dec 19, 2016 8:27 am

Of course you do.

eostic · Post by **eostic** » Mon Dec 19, 2016 8:39 am

The Description of a Stage is easily retrieved using the Query tool in IGC.

Ernie

UCDI · Post by **UCDI** » Mon Dec 19, 2016 10:20 am

chulett wrote:Of course you do.

Heh this is one of the most useless programs I wrote. Every once in a blue moon, maybe 2, 3 times a year, someone who does not have any access to datastage or the suite wants a table def from us. When we first got datastage (and I had just been hired) these requests were common so I cranked out something to make it simple and quick.

Given that the table defs that people want are invariably a mirror of actual database tables that can be looked at in any tool, its was a total waste of time, in hindsight. I just didn't realize the loop at the time (database imported to datastage exported and given back to database admin/modeler is a circle).

And of course its triply useless for anyone with the tool suite.
But its here if someone wants it, for whatever reason!