DSXchange

Akash I am sure this is covered in numerous previous posts. However, it is always worth repeating. In addition to what has already been mentioned, a table is usually copied to a hash file for performance advantages when doing lookups. If a large number of look ups are required on a dataset that is s...

One of the most useful features of a UV table is that it can be used to return mutiple records from a single look up record. Hash files can only return single rows from a lookup. When using larger UV tables remember to index columns as needed with the CREATE INDEX command.

Under the DSEngine directory on unix you should find a directory called unishared.load/uojsdk/lib and this should be included in your classpath for java. There are sample programs and some documentation in the subdirectories of unishared.load. There are java equivalent methods for most of the Basic ...

Kim I agree with all you say, and also with the substance of what Ken was saying. I certainly don't judge all Americans by the few. I have met some bad examples but I have also met loads of Americans that are great folk. Some of my comments and examples were meant light heartedly. Certainly in the U...

[America is the most creative country on the planet. I have seen a lot of very smart Indians and other nationalities struggle to compete in this environment. ] True America is creative. True many jobs from America and Europe (where I work) are going to India and other places. That's the democratic f...

To get the most from a 4 CPU box it is worth switching on inter process row buffering from the Performance tab of the Job Properties. This can provide dramatic performance improvements depending on the job design. If you use this option be careful to check that your job still works as expected; glob...

Yes the proposal of inter5566 seems very good. However, for multi row lookup to work you have to use either an ODBC stage or a universe table.

On Solaris platform there is a master uvodbc.config file in the datastage home directory and there are also project level copies in each project directory. Make sure the correct uvodbc.config is gettign picked up. Also double check that the dirver specified really does exist and is readable. Paul Pr...

Indeed the double slash does not what you hoped. We do not have tags coming out of our UV tables any more. We let the XML writer generate all the tag information. Tags may repeat several dozen times in our output XML files but we separate invoice rows, invoice addresses and other relationships out t...

Petri firstly a general point about producing XML. We went down the route of using a table join to produce XML tags as part of the data. This was efficient but ran into trouble when certain characters such as & occurred legitimately in our data. Also it was hard to get the indentation correct to...

Some columns after invoice rows are optional. As I said in the first post, invoice rows are already in XML-mode and I read them from UV-stage with multi row result set. We also use a UV table with multi row select, and we have similar output. I will check the definition later this afternoon and tel...

Hi Petri are you using the XML 2 pack or the standard XML 1 writer? It would be nice if you could post a section of how yuou want the output to appear. Are there any optional fields that are sometimes missing? We put most of our data including invoice data ito XML and it works very well so post up a...

Craig

I'm probably culturally deficient in my knowledge but why does it always say "Bunnies, bunnies, it must be bunnies after your name" ?

Try using the syntax:

CALL APPL_TOOLS.ANALYZE_TABLE('RGILMORE','b_acct_tran_eod');

That should work.

Paul.

Hi you mention that this query is in a lookup. With no bind variables (:1,:2 etc) the same query will be executed for every row in your source data. Lookups with user written queries usually include bind variables. If you have a user defined query with no bind variables and you expect that the recor...