DSXchange

pravin1581 wrote: Can you please elaborate your answer , sorry I didn't get you.

There's more on upserts in thisthread

You can get the rows with too many commas as follows: sed -e '/\(.*,\)\{25\}/ p' -e 'd' myfile.csv > toomany.csv Replace the "25" with a number that is 1 more than the "correct" number of commas. You can get the rows with the right number of commas as follows: sed -e '/\(.*,\)\{2...

Even if you don't want to use the bulk loading capabilities of an Enterprise stage, there are still advantages to be had from separating your inserts and updates. If you use an UPSERT with an array size of (say) 500 with Insert set to try first, then DS will attempt to insert all 500 rows in one sta...

Sounds like you are reading a Packed Decimal, which - from memory - uses the first nybble to designate the sign. What datatype have you specified in the DataStage source stage? Have you retained that datatype all the way through the other stages? Have you used the correct conversion function to conv...

What do you get when you type "groups" at the Unix prompt?

Also worth noting: A routine call entails a small performance overhead - possibly a context-switch - but I'm no expert. My bechmarking reveals that native BASIC functions can be executed orders of magnitude faster than routines that encapsulate the very same functions. With relatively simple logic l...

An inferior solution (but possible) is use a user-defined SQL that calls a stored procedure, which in turn generates dynamic SQL in PL/SQL.

If you want to see the correct syntax for using those commands, you can create a Job Sequence that does nearly - or a part of - what you want, and then view the generated code in the Jon Control of the Parameters dialog.

There are probably a couple of ways, but all of them are a bit tricky. From DataStage shell ($DSHOME/bin/dssh) you could write a SQL that joins the appropriate tables. That would require a detailed knowlege of the unpublished UniVerse table structure and an even more detailed knowlege of UniVerse. I...

Don't know how the OP went (a year ago!) but I had the same problem reinstalling today and this fix worked for me.

Don't know how the OP went (a year ago!) but I had the same problem reinstalling today and this fix worked for me.

I don't know about the DB2 stage, but the Dynamic RDBMS stage works fine with Environment Variables in Server but fails in Parallel. It seems likely to me that DB2 is the same. We raised the Dynamic RDBMS problem with IBM - demonstrating how it worked with the VIEW DATA button but not at runtime - a...

Looks like the same problem as this thread - ie. its not translating your environment variable. As I said to other poster (who hasn't replied yet): Instead of running the job, try View Data from the DB2 stage in the designer window. There is a bug in the Dynamic RDBMS stage (at least in v whereby it...

Are you trying to use NextSurrogateKey() in a Stage Variable?

If so, I don't believe that you can. You can only use it in an output link column derivation.

Instead of running the job, try View Data from the DB2 stage in the designer window.

There is a bug in the Dynamic RDBMS stage (at least in v8) whereby it DOES recognise environment variables when you View Data, but does NOT when you run the job.

Possibly the same bug exists in the DB2 stage