DSXchange

floor and ceil are giving correct results (assuming you're applying that before removing the sign).

From memory, the behaviour of rounding is determined additionally by whether the preceding digit is odd or even when the least significant digit is 5. Try it with 10690164.345.

naveen.p wrote:Hi Ray,

Kindly Help me out in arriving the solution with aggregator.

Naveen.

Group by item, sum the other three columns.

Table name should be $mappings as I observed earlier.

To do that your configuration file will need to name node pools. Once node pools exist, your stages can each be restricted to run in a particular node pool.

Maximum and minimum functions in the Aggregator stage work happily with decimal data types, or you can use stage variables in a Transformer. In a Transformer you can use IsValid() functions to test whether the string (an implicit conversion) is valid as a date.

It's still not a pivot - it's an aggregation. Use an Aggregator stage (or stage variables in a Transformer stage if you must). It's not a pivot. You won't solve it with a Pivot stage.

But if it's the output value surely the job is finished?

If one job writes a file another job can read that file.

If one job writes a value into its user status area, its controlling sequence can access that value and pass it to another job as a parameter value.

The main trick is that Excel worksheets present as "system tables". Therefore, you need to import the table definitions with "include system tables" option checked. It is also a requirement (of the ODBC driver for Excel, not particularly of DataStage) that the worksheets have the...

Document your expectations, run sequence to determine actual behaviour, document/explain any anomalies. Standard stuff.

A common technique for causing abort situations is to provide invalid values for job parameters.

That method will only work for newly-created jobs. For existing jobs go to Director client, select the job in question. and choose Clear Logs from the Job menu. This will open a dialog in which you can set the auto-purge options for that job only. Logs are stored in a database table, either in the l...

The easy way would be to change all the permissions on the server to read-only for the project directory and its contents. Exporting from that project will not cause any logs to disappear.

Change your auto-purge settings for that job to be either more than 32 runs or days-based.

Testing DataStage is not especially different from any other software, in that you are looking to compare actual with expected results. The main difference is that your expected result may be success/failure of a run, graceful handling and reporting of exceptions, or maybe number of records processe...

The document could still benefit from some rigorous proofreading.