Usage analysis in Datastage

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
dr.murthy
Participant
Posts: 224
Joined: Sun Dec 07, 2008 8:47 am
Location: delhi

Usage analysis in Datastage

Post by dr.murthy »

Hi,

I have an requirement like to identify the list of tables and sequential files that used in a datastage jobs across the project.
for example TableA was used in a five jobs out of five this table was used as a source in two jobs , used as a target in one job , used as reference in two jobs.

Is there any technology to identify this info.

Thanks advance
D.N .MURTHY
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Since table names can be parameters there isn't an easy generic way to do this. If you always use the same table column definitions then you can see where that has been used (but it won't tell you whether as source or target).

I would think about doing an export of the project into either .dsx or .xml and then parse that file looking for the keywords and table names.

You could program part this using the API calls.
- Select all jobs
- For each job,
- get the list of passive stages of type sequential and <your datbase>

This list could be used to scan the export file.
dr.murthy
Participant
Posts: 224
Joined: Sun Dec 07, 2008 8:47 am
Location: delhi

Post by dr.murthy »

Thanks Arndw, my table names were not hardcorded .
can i find this information from metadata work bench
D.N .MURTHY
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

I'm not sure about the metadata workbench in this case; if your table names are not hardcoded but parameterized, then you could get the table names from the runtime job logs.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

IF you have been diligent with handling your metadata, only ever loading table definitions from the Repository, then you can quite simply perform a usage analysis on the table definition and learn from that when jobs have loaded it (and therefore, presumably, are using it).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply