DSXchange

This code is a part of EtlStats. There is a job included which will take any SQL statement and turn it into html document and email it as an attachment. Kind of poor man's reporting tool. There are bunch of reports which included in folder called SqlScripts. They have :1, :2 as parameters. One of th...

There was one on the ADN. It would take a while and each each job's log file. It might be on my tips page. If not then I could post it.

Tips and Tricks page call DataStageBackup.bat.

Next time I would use XML.

Unless your server name is the same name as the one you are replacing then you may have issues. The server name is buried down in these files. You need to reinstall DataStage. You should design your DR recovery around full export and imports. SDK sequences should have a job which can rebuild them. I...

Besides you cannot use an ODBC stage to read a hashed file. You need a UV stage.

You have $ in your hashed file name? I would rename it. Not sure if " is the proper quote character for a hashed file. Remove the $ and " should not be needed. I think your issue is in the name.

I don't think that is possible. Never heard of the logs making any difference in the jobs performance except when it writes a warning on every record. The XML files are created in the before job command which runs dsjob. It has to either not write the XML files or write them to the wrong place. Mayb...

I think your parameter values are different for each run. That is where I would start to look.

We were trying to calculate a weight based on amount RAM used by each job. We were paging so we wanted to run just enough jobs not to page.

Just to figure out what processes are tied to one job is very difficult. I tried to do this in UNIX with a shell script. It is very hard. Some processes have the job name in them. Not all do though. I would bet this is lots harder to do in Windows.

There is only one type of sequence job. It runs both server jobs and parallel jobs. A sequence job just happens to be a server job. You can mix and match server and parallel jobs. You also run server or parallel jobs from command line with dsjob. I see no big deal. Once a job is started it makes no ...

A sequence job can run parallel jobs. No problem. It does not effect the parallel execution in any way. A sequence job is to run jobs in a specific order whether they are parallel or server jobs.

There are many facets to being a good DataStage developer. There are architect roles in some sites to not only move data around but design target tables. There are DBA roles in connecting and tuning databases and SQL. There are admin roles in installing and maintaining DataStage itself. Good knowled...

Each dsx file has a header. This would work if you stripped the header off. Not sure if it can ignore multiple headers in one file. Try it. Let us know.