DSXchange

You can not be 100% certain that what is in the product is accurately documented in the manuals, particularly for components that came from Torrent Systems.

I wonder why the sudden interest in Cartesian products? I recall that one Cartesian product test was not included in the QA test suite for Prime INFORMATION because it was estimated that it would take in the order of 110 years to complete. (It was a ten-way cross join.) The essence of performance is...

1. Because it's a JOB status report. 2. Alas, that's how it works. Submit an enhancement request. If the job fails, then one can have no confidence about stage start and end times, link row counts, etc., so they are simply not reported. 3. Any such change to default behaviour is a DIY exercise. Suit...

With no V in the PIC, and fewer than 10 digits specified, it should correctly choose Integer. If there is a V in the PIC, such as 9(9)V99, or ten or more unmasked digits specified, then it should choose Decimal (or Numeric).

Do it in an upstream activity such as a Job or a Routine activity, and use the job's user status or the routine's return value as a parameter in the Addressee field of your Notification activity.

So the algorithm, in English, is something like "for each distinct combination_number generate a new row containing a pk_id one larger than the current largest pk_id value for that combination_number and set elements to 'd'". Is that correct? If the source is a table you could select max(pk_id&#...

There's a whole seperate forum here for DataStage TX. You could also look on the [url=http//ibm.ascential.com]IBM Ascential web site[/url] for general product information.

Exactly as Craig stated; ActivityName.$ReturnValue where ActivityName is the name of your Execute Command activity. If you're on 7.x you can select these "activity variables" from the "Add Parameter" button's dialog. In earlier releases (5.2 and later) they had to be entered manually, but could stil...

Extract using SQL (select DISTINCT column...).
Aggregator stage, selecting First or Last of grouping column.

Find the "rows per transaction" setting. This configures a value N which causes DataStage to issue a COMMIT request for each N rows that have been sent to the database server.

Unless you can specify the rules under which 'd' will need to be generated we won't be able to be much help.

You can also use a Merge stage if both sources are text files and there exists a common key.

There is a relationship between rows-per-transaction and parameter array size that must be maintained.

Check (in dsenv) that your shared library search path includes $DSHOME/../branded_odbc/lib, which is where libodbc.so resides.

When you review/enhance this, handle the case yyyy-12-31 23:59:59.998 + 0.003