DSXchange

Why not just SELECT from the materialized view?

Weights reflect the rarity of the value within its domain, and so can not be given as an example. Rarity (also called "information content") is calculated based on the frequency tables generated by QualityStage. You can read about m-probability and u-probability in the manual. The former i...

Ascential no longer exists; it was swallowed by IBM in 2005. However the patch is certain still to be available through your official support provider.

There is more in .uvconfig than in uvconfig. Since you don't have premium membership, you will just have to take my word for it.

That requirement is for a "horizontal pivot" and is precisely what the Pivot stage provides.

This environment variable simply disables the job monitor, so that row counts may not be available in Designer, for example. Changing or removing it ought not to affect the job logic, but you should attempt to ascertain from the job's author why it was included, for example to overcome a known bug.

Precisely as you have specified. However, there is no capacity to "select" columns from the calling job. The calling job should provide the error code and/or error message which IT has captured (for example on a reject link) and pass it to the shared container, which can enrich it with the...

You use the XMLOutput stage. Full details in the manuals or on-line help.

A moment's analytical thought will show that it is sufficient (always) to partition solely on the first sort key.

Do you want to execute the file once per job or once per row? In the first case you can use a before-job or after-job subroutine such as ExecSH.

I prefer Left(InLink.TheLargeField,2000) believing it to be better "self-documenting". It compiles to exactly the same code as Craig's substring suggestion.

Sequential File stage becomes an import operator; Column Export stage becomes an export operator. In your initial scenario the rows all matched the column definitions (record schema) for the Sequential File; in the second scenario they did not.

Good advice but wrong technique. The .uvconfig file will never be the same as uvconfig - for one thing it doesn't contain all the comments and, for another, it contains additional information, for example about the licensing. You can always regenerate the .uvconfig file using the uvregen command or ...

Repetition was not mentioned in the original question, which is what I answered.

ayan wrote:Is it possible to use a job parameter in the user defined query in OCI stage ?

Technically, no. You use a reference to the job parameter. The reference is the parameter name enclosed in sharp signs (#), as already observed.