DSXchange

I'm as sure as I can be that the columns are lined up correct. Perhaps you can verify my interpretation of the log extracts I put in a previous post? In the first log, I had deliberately set the data type of day_number to incorrect varchar. My interpretation of the message in the log is that "P...

Hi craig, very valid point.

But I am also interested in getting this UV stage to work as an academic exercise.

Which method would you guess to be the best performer?

Do I need a VOC pointer if the target hash file is "Use Account name", and the UV Stage datasource name = "localuv"? With or without the SQL terminator ";" the behaviour is the same. Could that mean that the SQL statement is not being processed? The Entire Job is Hashed...

Hi Guys, I now have mini-job as described, reads 1 row into a transform, the transform is then input to the UV stage. The UV stage user-SQL is: Update HF_COP_Process_#COP_PS.COP_DN#_#COP_PS.COP_PN# set Docs_Extracted = ? where Day_Number = ? and Partition_Number = ? and Container_ID = ? Docs_Extract...

Excellent News! Thank you very much for the confirmation.

Option 4 does also work - slightly slower than the routine version - and in my testing I was not successful in passing the path. i.e. the path must be set by a job parameter, and col 1 to the folder stage becomes filename, col 2, etc file content. Despite the theoretical likelihood that Parallel job...

Wasn't sure which Forum to post this to... Moderator, sorry, ir I got it wrong.

We have heard ugly rumours (coming out of a Benelux IBM training lab) that Server Jobs will, in a soon coming release, no longer be supported by IBM.

Does anyone know of any truth behind such rumours?

I have already carefully read the Posts: Hashed file update - only to *some* existing columns; Delete specific records from hashfile / hashed-file; Usage Of Universe Stage. I have managed to get the UV stage functioning to get to the hash file and show data. Where I'm struggling is understanding the...

in testing DataStage is happy to receive and process 40000 char as an arg to a routine. I haven't yet got test data for the threatened 4 MB, but it's looking good...

I'm slightly concerned I'll end up regretting this post... but who or what are Grognards?

hoping it will work with a 4MB char string?

does anyone know how big an argument passed to a datstage routine is allowed to be? (maximum size in chars)

I have table blobs, consisting of blob_id (char16) and blob_cont (char 4MB)

I need to create sequential files for each row in blobs, where filename = blob_id and file content = blob_cont

Is there a way of creating multiple differently named sequential files simultaneously in DataStage?