DSXchange

You need to talk to your UNIX admin. /usr/lib/sendmail does not exist. Your email programs are not installed or setup in a non-standard place.

You can extract what I call ETL metadata from a UV Stage. Your source SQL would be the depend jobs in a sequence. Do a search for DEPEND_JOBS. I have posted this SQL before. The output would be a XML output stage. If you had EtlStats installed then you could get the order based on run time. I includ...

It does not show right after a compile.

Right click on the palette and show performance statistics.

OpenSeq is for sequential files. Open or OpenPath is for hashed files. Open "SDKSequences" to SDK else stop HashedKey = "Whatever" read HashedRec from SDK, HashedKey then * comment do something here end else * do something else here end Field1 = HashedRec<1> * change HashedRec wr...

EtlStats uses dsjob and works for parallel jobs. Vincent has modified the main job in EtlStats to aggregate all the row counts in one PX job run to get a true rows per second. I think I included this job. If not then I still have it so I can add it.

I have not used this job in a while but if I remember correctly this job needs to start at almost the same time as the job you want to monitor. You give it the job name to monitor. It will loop until the job finishes. It was designed to run EtlChkSeqJobsNotRun and send you the log file of any job th...

Why not download EtlStats which does all this for you? EtlStats is a group of jobs which extracts row counts for any or all jobs in a project. It can also get all row counts and start and end times for every job in a sequence. There are lots of jobs and routines to show you how to do wat you are ask...

We usually schedule these backups for 2am. You need to monitor the disk space. You can fill up a disk drive pretty fast with 100mb files.

You need to download DataStageBackup.bat from my links below my signature. Most people using this batch file backup development every weekday and production once a week. I usually do this from a client at work which is not portable. Needs to be at work every night. It also needs the DataStage client...

The only way to get the order is through run times. The order in job properties is the order input. The same would be true if you listed the repository. Run times are not consistent either. If you have more than one branch the order may change because the number of rows may make a job finish earlier...

Vincent, great job. I think the blogs are great too.

This document is version 10. The Universe that the DataStage engine is based on is version 9. I doubt if any of these extensions work with the DataStage engine.

Well the generic you is not happy.

It does not matter what I am on. I do not have the problem. It was just an example.