DSXchange

That would be the approach I would take also. Do you know all the possible fields that can occur in a jil file?

That's all fine. So to find out what went wrong you will need to consult the install.log file.

That's correct. However, if you had re-partitioned the data on the input to the Data Set, the data in the Data Set would almost certainly not be sorted.

There is no default Parameter Set in the way in which you describe.

Parameters that are not members of parameter sets exist only as job properties - they have no existence outside of the job in which they are defined.

Re-partitioning is almost guaranteed to destroy parallel-sorted data's sorted order. Partitioning of a sequential stream will tend to preserve sorted order.

Job interview leading to min sal ?

Are the sort keys the same as the remove duplicate keys?

Then you have not successfully installed the engine tier. Does the installation directory already exist? It should not exist, though its parent directory must exist. For example, if your installation directory is /opt/IBM/InformationServer, then /opt/IBM/InformationServer must not exist, but a direc...

Did you migrate the associated Parameter Set?

Welcome aboard.

Are the data partitioned on the "key used to determine duplicates"?

HariK wrote:Lookup is supposed to return only one row from the reference input. If there are more than one record that matches it will throw warning.

That's not true. One reference input to a Lookup stage is permitted to return multiple rows. There's a drop-down list that allows that link name to be selected.

Check that you do indeed have 2GB. One of the memory sticks may not be fully pushed home in its slot. Or your PC supplier may have robbed you!

sureshbabu wrote:friest filer basend on depno, then sort ase order on sal then the both depno and sal and using copy pass only one

Please replace your keyboard with one that can spell!

Search DSXchange for "vertical pivot". It's been discussed a number of times.

How do you construct Arg2?