DSXchange

You are asking the question on a DataStage forum so people will tend to favour DataStage over Ab Initio. Both ETL tools have a robust parallel processing engine that is better then any other data integration tool on the market. They both have data quality plugins and metadata management. We cannot t...

You could have a flag for each job set to Y or N. You have a nested condition that has four links, three links go straight to jobs A, C and D. The second trigger goes to a sequencer stage set ANY. Job A has a link to this same sequencer stage. The three direct links have a trigger of FLAGA='Y' FLAGC...

This can be done using a full outer join stage however with a large number of columns you may find it much easier to use the Change Capture stage.

Isn't this a straight forward remove duplicates problem? Sort the data by case and date and then send it through the remove duplicates stage with case as key keeping the FIRST record. The stage variable approach is good if you need to output all records and set a flag field indicating the earliest r...

Just do a forum search for "Version Control" and you will see quite a few threads on using the DataStage version control tool to move components between dev, test and prod. This tool is free with DataStage and you will find it in a sub directory on your DataStage CD or on your DataStage install menu.

Have managed to get encrypted environment variable passwords working in version 7.1 of DataStage. Created a database password environment variable using Administrator as a project level user defined environment variable of type Encrypted. This appears in the Administrator as ****** and in the DSPara...

I think in the very latest version they have fixed the handling of encrypted environment variables so you can set a project level environment variable as encrypted, add it as a job parameter, set it to $PROJDEF to always pick up the latest setting and use it in your job. Previous versions did not wo...

Those look familiar, the old Y and X records again! Just use a stage variable to maintain a counter that is incremented each time you get a Y record and reset to 0 each time you get an X record. StageVar - svRecType : left(InputField, 1) StageVar - svRecCounter : IF svRecType = 'X' THEN 0 ELSE IF sv...

It works. The DRS is designed to let you choose the RDBMS at run time. As long as you haven't put in any RDBMS specific code in your user-defined SQL or generated WHERE clause such as functions or database optimisation hints. You can set the database type to a job parameter to change it at run time ...

You would do this in DataStage. Installing DataStage and not using it for a standard database load job like this is like buying a train ticket and then walking between stations. You can do a lookup directly against the lookup table by joining it into a transformer. This will perform a database looku...

If you have installed the XML Pack then it should be in your "Profile Files/Ascential/DataStage/Docs" directory and it's called XMLPACK_20_Designer.PDF. If it's not there you will find it on the DataStage install CD in the XML Pack folder.

I think your fastest and easiest design will be stage variables. Looking at your original post you have a transaction group delimited by two X records. Between these X records you have one or more Y records and you want to make sure they are not duplicates. What I recommend is several stage variable...

Consider using the new Set Variables stage in your sequence job to retrieve your parameters from the file. Write a routine that opens a file and retrieves a named parameter. Call this routine from your Variables stage for each parameter you need to retrieve. Insert these Variables into your Command ...

This is excellent stuff! I ran it on our project. There was some minor adjustments as it was a Unix server and I had to run the dsjob commands manually on unix to get the project and job lists before running the create bitmap command back on the Windows client.

Well done Kim and Tony!

In my experience if a company has either Informatica or DataStage and is thinking of switching to the other then they are experiencing current pain with the production jobs. The problem is usually not with the tool but with the way it was implemented. Since the grass is always greener they hope that...