DSXchange

It's not an error.

It's an alert.

Not every decimal number, not every float number can be represented as an integer.

You need to be alerted to that fact, in case you don't know what you are doing.

Include a NOWARN specification in your Modify stage.

Record size is 1TB ?!!!

Rubbish. Both the starting value and the Limit can be job parameters.

Try here

Have you configured the account (project) for ODBC access using HS.ADMIN menu?

Details of this are to be found in the UniVerse ODBCmanual.

Ur was a city in ancient Babylon; any solutions Ur may have had perished with the city. We do not do ASAP or urgent; DSXchange is an all-volunteer site whose participants post as and when they can, if they have something to say and if they want to. If you need urgent support sign up with your suppor...

Use a Row Generator stage.

Your question is too vague. We don't know the size of a record. That said, ten million rows is not that many, so you should be able to run on the minimum configuration recommended by IBM for installing the products.

Why do you need them? If you Search DSXchange you will find a complete list that I posted some years back.

You might also investigate the Java PACK.

What problem? You assert that there is no problem in ds.

What do you mean by "performance" in an ETL context? Isn't being able to perform a task better than not being able to do so?

How about you tell us what you get on the reject link from the CFF stage?

Not really. You have no convenient mechanism from the command line to determine the name of the log table.

Also in version 8.1 you have no convenient mechanism from the command line to determine whether the log tables themselves are in a local repository or in the common repository.

When you upgrade to version 8.1 much of what you ask for is in the Information Server Manager.

To abort a job that is running issue a Stop request, perhaps from Director or dsjob command line interface.