DSXchange

By default no data are stored in DataStage, therefore data volumes do not affect sizing of DataStage itself. If you choose to use Data Sets for intermediate storage, then you need to allocate sufficient disk space for that. If you perform sorting, or lookups, etc., involving large data volumes then ...

You do get the iteration number in the log. And you could use a routine activity to log the value of startLoop.$Counter if you wish.

The UniData stage does connect to UniData 7.3.4. There should be no settings you need to make on the DataStage side (other than stage properties, of course). However, you do need to make the UniData account accessible through VSG.

Yes you do have to create a lot of PL/SQL scripts to use ODI.

Through Information Server Manager (or its command line interface istool) you can check-in and check-out DataStage and other components. For non-IBM source code control systems this is managed through the Eclipse download for the particular product. IBM source code control systems are directly suppo...

samarvind wrote:I wanted to reduce the usage of transformer wherever possible.

Why?

Faster? It depends. A normal lookup has to load the entire reference data set into memory before even the first lookup can occur. In some cases the reference data set must be read from a database. A sparse lookup has to go to the database for every single lookup. But for a sufficiently small number ...

We here are naturally biased towards DataStage, since this is a forum for that and related tools. And, yes, 100 million rows per day is certainly feasible using this tool. Information on planning and configuration can be found in the IBM Information Server Planning, Installation and Configuration Gu...

Had you searched more diligently you would have found that the parallel Sequential File stage is really bad at this whereas the server Sequential File stage is brilliant with these and other aberrations (such as missing columns). Therefore best advice is to use a server Sequential File stage, either...

As a first step, create a server job to read ./Quality/ruleset.CLS (using a single VarChar column) and test whether the line has a valid format. InLink.Line Matches "1A0A' '1A0A' '1A" Or InLink.Line Matches "1A0A' '1A0A' '1A' '3N" View the output and ignore the comment and format...

I'm pretty sure that the second argument to handle_null() must be a constant.

As a more general rule Modify stage functions can only operate on one input field.

It's "a" right approach, but not the only one. For example, one might pass the link names as arguments to a generic subroutine.

System variable @PARTITIONNUM, available in Transformer stage.

"Phantom" is just another word for background process. When a server job is run, it runs an instance of the DataStage engine (dssh, also known as uvsh) as a background process executing the DataStage BASIC program DSD.RUN. If you have a Transformer stage it, too, will create a background i...