DSXchange

You can't, except by providing all partial key values as lookup keys.

If the report already exists (created by QualityStage) why not just try viewing it?

Know where the files are, and which files they are, and either copy them (for example uvodbc.config, default.apt, etc.) for subsequent editing, or copy only pertinent lines (for example DSParams file). Do you have any server jobs in your mix? If so, you might also want to think about re-creating has...

7.1 at a guess, maybe even a minor 7.0 release.

Obviously it's more difficult with delimited data, but it's certainly possible (locate the percentage point then scan forward for a line terminator).

That's the best answer.

If you get warnings during design, isolate and eliminate the cause.

Not solely by a lookup table, but certainly by a lookup table followed by upstream pivoting and downstream processing (including vertical pivot).

This is your first mention of partial replacement, and with no amplification. The short answer is yes, provided that all partial key combinations are accounted for in the lookup. Or you could effect a non-equi join in a database. You do any conversion in a Transformer stage downstream of the Lookup ...

Welcome aboard, and a good tip to check.

The trailing space would not, of course, be a problem for Upsert, because SQL is free format (unless the table name had to be quoted because it contained unusual characters).

Read the man page for rsh and learn about the different ways that the remote host will allow access. One of these authentication things must be done in order for rsh to work (and therefore for multi-machine parallel jobs, which rely upon rsh, to work).

What does this function do?

It does not appear to be mentioned in the DataStage BASIC or Parallel Job Advanced Developer Guide manual (version 8.0).

There can be many parameter sets in a project.

Each data set consists of at least N+1 structured binary files, where N is the number of partitions. You can not expect anything sensible from concatenating the contents of the control files that record the existence and location of the data files.

Not true any more. Multiple readers per node will work with delimited formats.

The answer is no. Parameters are job properties, not stage properties. The only way to get the parameters named in a given stage is to interrogate the stage metadata, and that's non-trivial, particularly for stage types that use references to parameters inside expressions, where they are not surroun...

Data Sets preserve partitioning. Data Sets preserve sorting. Data are moved between persistent Data Sets and virtual Data Sets using the copy operator, which is hugely efficient compared to any other mechanism. Those alone argue the case for using Data Sets for staging data between parallel jobs. It...