DSXchange

Other than huge performance impact if you read/write a lot of files (sequential and hashed), which pretty much sums up ETL with DataStage. Sure a VM is cool if you're doing some lite development as a single person on a single machine, but if you're talking about running a production environment, don...

I've been reading and answering a lot of your posts lately. When doing an SCD, you transform a source row and compare it to the most recent existing row in your database. If there is no row, you insert it. If there exists a recent current row and your new row is different , you: Type 1: Update curre...

Why not put a row in the audit table for each source with a LastExtractDate of something like 1900-01-01? Then, the first time isn't an issue.

Sure, if you take the time. You have to parse your parameter file for values and pass them to the Job stages, but you'll probably think it's easier with a Batch job.

You can write a fancy .bat script, or use a perl script, or go as far as unix tools for Windoze, or a DS Batch job would work great.

Two things: 1. Test the environment of the engine by either creating a Batch job to CALL DSExecute("UNIX", "env", ScreenOutput, ReturnCode) CALL DSLogInfo("The environment shows :":ScreenOutput, "Msg") or whip up a Sequence w/Command stage to r...

I would always as a matter of practice track all job stream executions just from a process metadata standpoint. Leverage that to track processing "to-from" dates allows you to do the things you're talking about doing. Trusting a source system to tell you is not the same as knowing it yourself.

Look at this:
http://www.dsxchange.com/viewtopic.php?t=85578

It's a shell script that runs dsjob. You should be able to get the idea how some of us are using it.

Universe is something else entirely. If you need to reference DataStage hashed files in a PX job, then you should consider using a container and a hashed file stage reading the hashed file and then move it into a dataset of some kind. Using the ODBC stage to read a hashed file will work if you simpl...

You mean the command line program dsjob? It's fully documented in your DS manuals under the Start menu as well as having help just by typing in dsjob.

Undocumented and proprietary information, but you can glean it by looking around on this forum.

Place a sequential file stage under your DB2 UDB API stage and right-click draw a reject link to the sequential file stage. See the error message?

Sucks, don't it?

You should NOT use ODBC to connect to Universe. If you understand Universe technology, you would know that support for multi-value attributes exists within the Universe UV/ODBC stage. Even then, your efforts are not sufficient for connecting to Universe. You will need to setup clean dictionaries wit...

The surest and safest solution is to always track in an audit table the date of an extraction. This allows you to use this date in the next run, because it sets the point in time you will use for a forward looking query. Even though you run on the 1st of every month, it's safer this way because you ...

yes