DSXchange

Import the two table definitions into DataStage and use the comparison tool within DataStage.

Why do you want to find it?

It is probably better (safer) if it remains "invisible".

You CAN add environment variables to parameter lists in a Parameter Set.

And you CAN set the default value of these using the special tokens $PROJDEF, $ENV and $UNSET.

I've done both in the past (version 8.5).

If there is no indication that the inputs of a Join stage are sorted, then a tsort operator will be inserted. There is no requirement for this to be sequential; each node is managed independently. It is vital, of course, that the data are correctly partitioned (on at least the first join key).

8.5 and higher offers looping in the Transformer stage. Out of curiousity, is that true for Server jobs? For some reason I though just Parallel ones supported that. Version 8.7 server Transformer stage does not have looping (I just checked). On that basis I'll assert that version 8.5 server Transfo...

Splitting credit and debit can be done in a Transformer stage, and you could take an additional output on each to an Aggregator stage to calculate the minimum (oldest) debit and credit, dumping those results into hashed files. That should be enough to join everything back together, and use a final T...

Please write out the required logic in English. In that explanation, show us how six rows in come to be eight rows out, and under what circumstances that will occur. This is called a "specification". Writing out the logic may even allow YOU to solve the DataStage logic!

You can put it into a server Shared Container and use that in a parallel job. Details in Chapter 2 of Parallel Job Developer's Guide.

The control file name itself is embedded (at the beginning of) all the segment files that make up that Data Set. Therefore, from your example, the control file name for the segment file datadata_analysis.txt.dsadm.cs-uat-etl02.0000.0001.0000.f1c2.cfdf2027.0001.e69caf04 is datadata_analysis.txt

If CSV file was created on Windows the line terminator is \r\n (DOS style). The overrun might simply be the Ctrl-M characters (\r). Try changing from Record Delimiter to Record Delimiter String and setting its value as "DOS style".

Please verify that you're performing the installation as root. This is mandatory.

Does a file called DSParams exist in the project directory?

If an environment variable has been used in a job it must be declared in the job parameters list, so that should be your first cut; extracting the parameter information from the ROOT record in the DS_JOBOBJECTS table. If you need to know every stage in which an environment variable has been used the...

Some of the InfoSphere marketing material covers this well. It can be accessed on the IBM web site.

There are not. But contact your local IBM training centre and they'll tell you the next time it's scheduled to be run. Tell them I "sent" you.