DSXchange

Hi jweir It appears that the second and third rows are being set to the default value, which in my example I did not set a default, this the second and third rows having blank. But why would it take the default value? we experienced the same bug - by the way already in DS 8.5. Contact IBM support.

Hi chulett

it was DataStage 8.5

Hi tedsimon

specially check the part of the BIND commands in the faxpack docs and make sure the db2profile is sourced on the DataStage client.
A connect and select should work as dsadm - this is a good test.

Hi harikhk

the dump file will be created on the database server

Hi harikhk A dump file will be created by the load if you specify the "Dump file" under "File type modifiers" The documentation for the exeption tables can be found here http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/index.jsp?topic=%2Fcom.ibm.db2.luw.sql.ref.doc%2Fdoc%2Fr0001111...

Hi harikhk, it is about how a load in DB2 works. are you loading to DB2 z/OS or DB2 LUW? You already talked to your DBA you wrote - which is good - and he should be able to explain a little more. The exception table is to capture unique key violations - the use is to get the violations caught in a t...

Hi anu123,

Ray is right it is DB2 issuing the error and I suggest you talk to your DB2 z/OS DBA as he is the person who could help you here.
The problem can occur when you cross a ressource limitation on the host in cases where your SQL is too expensive (which can happen handling LOBs)

Hi SIHM

I think I did not full understand what you are trying to do but
you can use Parameter Sets like any other job paramter in the job control.
The parameter is the name of the parameter set and the value can be a specific one or - much more important - a name of a value file.

Hi times29 the problem is that you used "after sql" in db2 stage but export is a utility and so a DB2 command and not SQL. Two things you could do 1. use a OS script and call that 2. use admin_cmd stored procedure to wrap the export command and call the stored procedure (the call statement...

Hi
well yes you mentioned it but you mentioned as well that you have set it at some point in time - and my experience on UNIX is that DataStage keeps it cached untill it gets restarted.
So you might still suffer from the one test where you had it set.

Hi

.. I forgot to mention - in your case you should leave it blank
This is always the best solution in my eyes.

But this means the DataStage Admin user has to have the DB2 environment set (sourcing the db2profile - on UNIX systems)

Hi Klaus Schaefer the instance property is missleading in the DB2 Connector. It actually means the name of the CLIENT instance - the one on the DataStage Server. Additionally there could be another problem - check out: http://pic.dhe.ibm.com/infocenter/iisinfsv/v9r1/index.jsp?topic=%2Fcom.ibm.swg.im...

Hi william.wang_GMA, here are my two cents: I think the question is not quite right - if I got you right you are asking how to do the sparse lookup and how you get the data from the WS input into your SQL statement (and not necessarily the Parameter Set). In asparse lookup you can reference the data...

Hi callmatkarna, make sure the data modell really corresponds to the test environmnts - specially check if all indexes are available. Check and compare the data size between your environments - things can be dramatically different when you have much more data in production compared to test and this ...

Hi Ray right - I use the variable WHERE condition in many other situations and my feeling about the problem is similar to yours - it SEEMS not to be supported because of the data type change but I really do not know it. In this situation I need the IN-List for the multi-row lookup as a can not use t...