DSXchange

The relationship between the status number used in the API and what actually shows up in Director was hard for me to figure out. I needed it for DsWebMon a product I sell. I had to reproduce each status if possible to see what the verbage was in Director. Try to make a job fail in every way possible...

Just maybe if I answer every post I can get 4,000 posts in.

Geez, I did not get to enjoy my 3,000th long. Between you and Ken I look lazy.

By the way your error message is telling you that it cannot create file

/u02/XML/etlExtractGXStudent.xml

The directory /u02/XML needs to exist ahead of time. This directory was changed because my version writes to KimD in the project directory.

I posted EtlStats in June of 2004. Second version was posted in Feb of 2005.

JobStatus.txt was a text file I created.

What is your problem? All the values printed. If you print a dynamic by sending it to the log then it prints one value per line. It looks just like this.

I would use Reporting Assistant and do like Vincent suggested. Most of what changes is in DSProperties. Do a select where all the fields are equal except JobName and PropValue not equal. Should get you a much more readable difference.

I think MetaStage has a job compare report built in.

They aren't touchy. That is why you can make them all varchar and ignore what type they really are.

I agree with Kris. I would create this column as a varchar and not a date. In fact I would create all the columns as varchar unless you need to sort this file.

try it as char.

Is there a trim() in your lookup.

I would think when you load hashed files into memory that would consume more memory than most other stages.

Not true. It can connect to anything in TNSNAMES. DataStage uses only one ORACLE_HOME at a time normally.

Just download EtlStats from the links below my signature. That is what it is designed to do. It updates several tables. Just change it to update a sequential file. You need to modify the job GenHtmlJobLog to get the log file records. The job DSJobReportDbDriver runs the job DSJobReportDb which is th...

Never ever kill with a -9. This can corrupt repository tables. use kill -15 or just kill. If you have a tightly wound loop then you may not be able to kill it. I do not see an option to stop a job otherwise. You can do it from a routine. If you knew enough about BASIC then you could create a TCL com...