DSXchange

You have at least a couple fact tables to worry about. I would say premiums and claims would be the first fact tables. If you can get with underwriting and figure out how they rate then your fact tables need to track the data elements to validate the rating formulas. I would say some dimension would...

Maybe you are running out of connections on the database.

Ernie We have a DataStage admin team. We scripted a solution using DOS batch files which do almost all of what VC does. You create a list of jobs to migrate. These are stored in a folder with the same name as the project. You edit one batch file to pick the command line options of from and to server...

You are welcome.

Rolling your own is complicated. You need to store when a job finishes successfully either in a table, sequential file or maybe a hashed file. You need to compare this last completion to the start of the current run even if this run has been stopped. If you run once a day then you can compare to tod...

Used to be a bug in that DataStage could not process 2 repeating groups in one stage. You should be able create a lookup out of one repeating group from the other to combine them.

RCP can make a job a lot more readable. If you use shared containers then you can feed in only the columns needed. Lot less columns mean less mistakes, cleaner more readable design. Metadata management within DataStage is one of the weakess parts of the product. I do not consider this more valuable ...

If you are talking about load balancing then you need to measure the load on the system during your ETL job runs. EtlStats will get you part the way there. You still need to know the load on the system. Are you paging? Are you waiting on disk IO? What jobs are running during peak load times on the s...

We use Zeke on our mainframes and Zena on our UNIX servers with DataStage. We have a shell script we call datastage_wrapper.ksh which runs our jobs. If you are part of a BlueCross then we might be able to share ours otherwise I doubt it. Most of us have many hours invested in these scripts. Ours is ...

I think some are set in the ROOT record in DS_JOBOBJECTS as well. Update statement looks similar.

Search for EtlStats.

You probably need a -wait option to wait on the reset to finish as well.

Edit the generated html.

EtlGetRowCountsFromLog is designed to get row counts from the log files for previous job runs. It works like DSJobReportDb in where it writes the results.