DSXchange

Hello,

How are encoded your input data ?

4 years later, sorry for the grave digging

I had the exact same issue. To solve it, I had to add a "copy" stage right before the database connector, enable RCP and delete all the output columns.

You could set the "OSH_PRINT_SCHEMAS" environment variable to "True" to see the schema of each stage in the job log.

We need to send the record to the output unless the row number is higher than the number of rows to generate, in my head, my logic is right.

Anyway, Siva will test it if he decides that is the right solution.

As for the original topic of this post - selecting rows from a table and using the results as parameters to a job, I think you have confirmed my lack of results from searching. That is, in a job sequence, it is not possible to read values from a database table, put those values into a list / array ...

I also execute those statements using the same job (in the "user defined SQL" section) : update THOMAS.DATA1 set INT02 = ORCHESTRATE.INT02 where INT01 = ORCHESTRATE.INT01; update THOMAS.DATA1 set INT03 = ORCHESTRATE.INT03 where INT01 = ORCHESTRATE.INT01; They both update the DATA1 table. I...

sriven786 wrote:Yes. Teradata connector write mode allows for User Defined but not the odbc connector (Only Insert/Update/Delete)

I am going a little off-topic here but you can definitely do it with an ODBC Connector, i just did it on DataStage 11.5 using Windows.

User Defined SQL is disable if we use ODBC Connector as Output. Are you sure about that? I often use the "user defined SQL" section to execute instructions using the input columns with the "Teradata Connector" stage (I did not try the ODBC stage). @neeraj Did you try to add a CO...

You didn't specify the password ? You could try to add it with the /P option.

Yes, you just need to disable it in the Sequential File and the Transformer stages, activate it in the Column Generator and the output will represent the schema file.

You could use the "Filter" option of the Sequential File stage to skip the first rows from a file, for example : will skip the first 3 rows.

JoeClark wrote:I didn't find the right solution from the internet.

The solution was right under the text you copy / paste from cnet.

Maybe you could take a look at John's posts on that topic :

It is possible to set a string defining a null value in the Column Import stage or directly in the schema. The easiest way is to add it to the schema, you can add the 'null field' property that way: record {final_delim='end', quote=none, delim=';'} ( C1:string[max=24] { null_field = '' }; ) To add t...

DataStage see that value as a 0 length string, not a null.
Did you try to use the "Null field value" option on the "Format" tab ?