DSXchange

Return is a valid statement. It will always give you a warning. It causes all kinds of problems. Try to avoid it. If you want to know how to use it then let us know.

Delete the line with "Return"

You are a morning person, right?

You are correct I am a night owl.

I wrote some simple VB code to extract some sequence information like the job dependencies into Reporting Assistant tables. This is part of DwNav. I posted most of the code on this forum a long time ago. There are several jobs in EtlStats which I give away on my tips page which extract job metadata ...

I have seen more than 10 but I put sleeps in between because you can overwhelm the CPU with all 20 starting one after another. 10 to 30 seconds on the sleeps. I would bet 20 jobs is easily possible.

It runs Dwn_ExecTCL.exe which is a VB program I wrote. It will run any TCL command from the client. So it is programmed in my script to run UNLOCK ALL in the UV account. It writes to a log file. It has a debug mode which writes the output to a GUI screen like DataStage Administor.

My script has a way to unlock all jobs too. Not wise in the daytime but at 2 in the morning it is safe.

I hope so.

Scalability and stability. How many more do you need?

You need to export your with the scripts on my tips page. Do it every night. I do PROD once a week.

If you use Reporting Assistant then you can write SQL to compare the 2 jobs.

Sounds like you still need EtlStats to load this into a table. Not good.

This is not uncommon to create an ODS as a buffer between your source and your data warehouse. I am sure Ken can give the long answer why this is important.

It looks like it did what it was supposed to do. You told it not to worry about job3. So it will always rerun it.

Another http://www.dsxchange.com/viewtopic.php? ... shedOutput