DSXchange

What about letting both jobs use a different range of keys?

Resolved. I changed the key and recompiled with not problem. I changed it back to the exact same key and range. It compiled an ran fine. No idea why.

I get a compile error in a range lookup. Does any one have any ideas? ################################################################## #### STAGE: Lookup_3 ## Operator transform ## Operator options -table -range "StartItem <= Item AND EndItem > Item" -keep -allow_dups -flag run -name 'V0...

Can you post the SQL that got generated?

Ok, I agree. Without doing some kind of transformation, I doubt that the performance would be much different on any of the nodes.

Even with more rows, I think you will get the same behavior. The file is read in order, and sent down the random partitions. The auto collector eagerly reads any row that is ready from any partition. Since they are read in order, they will be ready in order.

Isn't the sequential file read in order if you do not use multiple readers?

Why wouldn't you export and import the project?

Ray is correct. You can get it through the partnership program. You will need to purchase either the Software Option or Value Pack.

Can you provide more detail about the data sets. How are they related? In business terms, how do you wish to join them.

Did you try changing it on the Job Properties NLS tab to see what happens?

I also like Craigs advise about sourcing the dsenv file in the script. You could get this error if you don't: error while loading shared libraries: libvmdsapi.so: cannot open shared object file: No such file or directory By the way, the return code is 127 when you get this error. Someone also sugges...

Where are you trying to use it?

No, I can not send you my code.

Yes it did work. I called DSJOB directly from the Application Engine Program. I also used a run control table to store the parms, project and job name. The app engine parsed the parms and formatted the dsrun job command. I did not use a script.