DSXchange

Use the pxEreplace() function (which you can find on DSXchange) or upgrade to version 9.1 and use Ereplace() or Change() function.

One of the world's worst kept secrets emerged today, as InfoSphere Information Server v9.1 was announced to the world at IOD 2012.

The formal announcement will be on 23/10/2012 (US Pacific time) and expected GA date is in December 2012.

More news as it comes to hand.

There are also good examples in the IBM training class Advanced DataStage.

Note that the Data Rules stage is not for QualityStage rules. It is for data rules created in Information Analyzer (or within the Data Rules stage itself).

Note that versions 8.7 and later do not ship with full documentation; you have to download that separately if you require it. This is to reduce the overall size of the main software download. There is no extra fee for downloading the documentation.

Try using a project name rather than a project pathname.

Options -wait and -jobstatus are mutually exclusive, you can have one or the other or neither, not both.

When you ran the job did you enable collection of performance data? APT_PERFORMANCE_DATA only specifies where the files are to be put - you have to switch on the collection of those data.

Two left outer joins would seem to me to be a better solution, as inner joins return only those keys that occur in both sources. (Database 101)

A single full outer join may suffice for your requirement.

Or, there are several organizations who will do this for you for a fee. And you probably have to agree to your job designs being offshored.

atul9806 wrote:How can we get the jobs that were actually executed under a sequencer ?

I answered that question in my previous post. Get yourself a premium membership and you'll be able to read it.

If the jobs were generated from FastTrack the mapping is already in the repository.

How many links connect to the Transformer stage and what function does each perform (for example stream input, reference input, stream output, reject output)? A "pin" is a connection between a link and a stage. Pins are numbered from zero, so the problem is likely to be in the third link t...

You may take it as given that if people have anything to post here, they will. And that if they haven't, they won't.

I'm quite surprised to hear that the DB2 Connector cannot be used to connect to DB2 on iSeries. I understood that that was one of the features of the Connector over the Enterprise stage. And you definitely can use the DB2 API stage to connect to DB2 on iSeries, albeit only in sequential mode. (The D...