Usually the starting point to modifying a data warehouse is
to add a column to target table. Job Metadata shows you all file names by
stage type. You can find which job reads a table or writes to a table. In this
example job "QaAutoRowHist" is the only job that reads hash file
"DWN_RT_ROW_COUNT_HIST". Now you know which job to add a column to.
Drill Down:
Project -> "Job Metadata" -> Stage Type -> Filename -> Job Name
Here is an example where the table name also shows up when you drill down into a job. If you are trying to figure out which job built a table so you can add a column to it then "Job Metadata" is your starting point.
This information is also displayed when drill down into the job derivation
rules. In this example job "DailyLuBuyStrategy" hash file "DM_LU_BUY_STRATEGY"
is read by this job but written by job "HshLuBuyStrategy". DwNav
display the job that does the opposite to this job to this hash file. So in
this case it displays the job that writes to the file because this job reads
it. The job "HshLuBuyStrategy" had to be run before this job
because we are reading the data that it wrote. To trace data from target to
source or source to target this is very important. DwNav uncovers the complex
business rules hidden in the GUI DataStage Designer.
Job Metadata information is also displayed when you drill down into a job.
Here is the same data displayed in the job drill down.
If you are in a Quality Assurance role then you can easily trace down naming conventions for job names and link names by browsing job metadata. You may also want to track how much work was done after the fact. "Job Stats" will show you how many objects were created by a developer. It should take a similar amount of time to add objects of a specific category like 30 minutes per each link or 4 hours for each job or whatever you need to try to project amount of work.
