DSXchange

The number of uvsh processes has no effect whatsoever on the transaction size, which is a property in the stage that actuallky loads the database table. The number of uvsh processes is solely a function of the number of active stages in the job and how these are connected to each other (and, perhaps...

Whatever you specify on the input links of downstream stages.

Odd. Most databases allow VarChar out to at least 1024, if not longer. Did you try Long VarChar? (I presume you made the schema data type match what you're generating in the CAST expression.) The ":" character being complained about comes from the generated OSH used for View Data. Unfortunately I do...

/usr/lib is definitely not enough. You also need the DataStage lib directory, the branded ODBC drivers' lib directory, any other operating system library directories and, in particular, the directory containing the "missing" V0S1_testjobtrans_Transformer_1.so. You need to adjust LD_LIBRARY_PATH in $...

Welcome aboard! :D In the job control routine, immediately after DSAttachJob, add another innocuous function call that uses the job handle. For example RealName = DSGetJobInfo(hJob, DSJ.JOBNAME) Replace the DSWaitForJob call with a "busy wait" - a loop that periodically checks the job's stat...

Looks like there's a problem with your use of the REJECTEDCODE link variable.
Try recreating the expression(s) in which it's used using the expression editor.

Seek filevariable, offset, position Then * statements if Seek successful End Else * statements if Seek failed End The position argument is 0 for current position, 1 for beginning of file, 2 for end of file. Therefore, to position to beginning of file you need Seek filevariable,0,1 ...

If that's true then you have got major problems in your project. Try (with administrator privilege) executing the command UPDATE.ACCOUNT This should refresh your VOC file with necessary entries. Note also that the hashed file name is case sensitive, and that you must have a pointer in the VOC file t...

Do you want to build separate indices on the three columns? You do not need an index on the combined key (which is called @ID), since this is already taken care of by the hashing algorithm. When the three key values are put together, they are assembled into a character string with a text mark (@TM, ...

Yes, mine was only an example, showing how you would do it with a CLOB. Trying to CAST a LONG as VARCHAR is not appropriate, so it's good to see that you worked out that a large enough VARBINARY was an appropriate cast.

You can let the stage generate the SQL based on the columns (SELECT clause), table(s) (FROM clause) and other information you supply.
Or you can specify user-defined SQL and do anything that's legal for DB2.

Please do not post URGENT Answers on this forum all come from volunteers, in their own unpaid time. If you want urgent answers, sign up for premium support from your support provider, and learn the true cost of urgent. And posting the same question twice in quick succession isn't going to win you a...

Please do not post URGENT

Answers on this forum all come from volunteers, in their own unpaid time. If you want urgent answers, sign up for premium support from your support provider, and learn the true cost of urgent.

If you are searching for the primary key, the row will be returned instantly irrespective of its location. Why? The key value is processed by a hashing algorithm that returns the address of the page on which the key and its record are stored. One I/O operation is required to retrieve that page. If y...

Please don't post the same question on more than one forum Lots of grey areas and overlaps - one of the dangers of applying labels. Validation is ensuring that values are valid; this might include data type and range checking, might include "exists on file" checking too. Cleaning is applying algori...