DSXchange

I have a question.

1. What do most of you use to build your mapping documents?

2. How do you track database changes?

3. How do track the relationship between jobs and tables?

4. How do you do impact analysis when a table changes?

You work for Bush now or just watch The Daily Show?

Arnd is correct. Do not do this with running jobs. It is possible to save off \\PURGE.SETTINGS and clear everything else in the log. Look at Ken Bland's routine. In an emergency like a filesystem filling up then clear it. We have developers which get a warning for every row. They can fill up a files...

If you run dsjob -report XML on a job then there are multiple repeating groups in this file. So all of us can create examples. The parameter values are one set. The row counts with link names is a second set.

The main job in EtlStats uses dsjob -report XML to load these stats into tables. The DDL for ETL_JOB_HIST, ETL_ROW_HIST and ETL_PARAM_HIST is included in the zip file. The bugs in XML forced me to process the XML file 3 times. This main job is called DSJobReportDb. If you call job DSJobReportDbDrive...

Do search for EtlStats. It is a bunch of jobs I give away on my tips page.

The job that can extract row counts from old log records is written in BASIC. You might be able to use dsjob -logsum or -logdetail to get what you want. If you want the last run only then dsjob -report will give you that.

You guys are both nuts. See you at IOD. Registered today.

NAME is not the job name. NAME is link name and stage name. The job name is stored in DS_JOBS.

This is one of the jobs included in EtlStats.

EtlStats is a bunch of jobs which have been discussed a lot in this forum so you can search on it. These jobs are free. Download them on the link Craig provided. They do exactly what you want, load row counts into tables.

A job can be dependent because it is run by this sequence or batch job. Another way is one job creates a hashed file or sequential file that the other job reads. Which are these are you looking for?

You can switch it to a routine stage which will use the parameter values.

I agree Ray. What does Peter know. Besides it is mandatory nowadays to remind me how it works.

DataStage wrapper is a shell script. It reads all parameters from text file in a directory below the project called JobParams. This script is a combination of 3 scripts developed be me and a couple other people. Best features of all three combined into one huge script. We wanted parameters to defaul...