DSXchange

The import warning is probably "first line is column headers" not being correctly set.

The export warning is specifically "output file full" - could be a full disk or a quota being exceeded.

Round Robin will preserve the generated order. However, they will be spread over the nodes mentioned in your configuration file. For example if you have four nodes your Data Set will receive: node #0: 1 5 9 13 ... node #1: 2 6 10 14 ... node #2: 3 7 11 15 ... node #3: 4 8 12 16 ... When you use View...

Welcome aboard.

The rule for Hashed File stage is "destructive overwrite" - last one in wins.

Therefore your "obviously" statement is incorrect.

But your job logic is dangerous - why not use two separate hashed files?

Wrong. UniVerse is gone. It went away in 2000.

You have DataStage Engine database for storage within the DataStage server as well as a more "open" common Repository for which the choices, in version 8.0, are DB2, Oracle or SQL Server.

Things may change in future.

Not easily. You can certainly test Rule Sets independently. You can also include Peek stages (or compile in trace mode) so that you can record what goes into and comes out of the QS stages, but that's about all there is.

Premium membership costs less than 30c (Rs12) per day, so is a very inexpensive way to enhance your knowledge about DataStage by being able to read the entirety of the five premium posters' contributions, as well as other benefits that, although slow in arriving, will be announced shortly (let's sa...

Currently Java is not used by the DataStage Engine. Java is only used by the stages that work with Java - essentially those in the Java PACK (and maybe deep within some of the XML stages, I'm unsure about those). Ernie may have more to say on that. Looking forward, and given that IBM has decided tha...

So you want to do in code what you do manually in Director log view?

Look at the Help for DSGetNewestLogID() and DSGetLogEvent() functions.

Verify that the SQL being sent from DataStage is exactly the same as what you executed through QTODBC. You may need to involve your DBA to monitor the connection to establish what query is actually being received by the database server. Also, please report whether you received any warnings or errors...

I posted as "other" because I was an employee of VMark Software then Ardent Software then Informix then IBM. I learned DataStage by preparing to teach classes and by providing technical support for the product.

Based on your other post, I'd suggest you come up with a detailed specification of what you wish to achieve first. Otherwise you and we will be wasting time.

DataStage will never report "number of records inserted in table". DataStage reports "number of rows sent to table" - whether or not they are successfully inserted depends upon the database server. If it generates error messages, these are returned to DataStage and logged. Thus, if you want to calcu...

It's not an error. "Is empty" means that your query returns 0 rows. Try the same query using any other client (not DataStage) - you will get the same result.

If that's not what you require, you will need to review the constraints in your SELECT statement (or stored procedure).

Read the Oracle table using a job - probably a server job if the number of rows is small. The target of this can be a file (which you can read using an Execute Command activity in the job sequence), or you can put a value into the server job's "user status" area and recall it from there. Once you ha...