DSXchange

I guess the only exception is where the job can only process one row. For example SELECT MAX(keyvalue) FROM tablename.

Add the NO.PAGE keyword to the query.

Or redirect stdin from /dev/null. This provides the responses to "Press any key to continue . . ."

Same way you pass parameters to any shell script - on the command line and retrieve them within the script using shell variables.

Column Derivation DSFIELD1 : '-' : Str('0',2-len(DSFIELD2)):DSFIELD2 Overkill. Since WEEK will never have more than two digits, the original formulation will work. DSFIELD1 : "-" : Right("0" : DSFIELD2, 2) The expression "0" : DSFIELD2 can only ever return two or three...

1. UVwrite hashedfile keyvalue field1 field2 ... (warning: this is a destructive overwrite). 2. UVdelete hashedfile keyvalue 3. dssh "CREATE.INDEX hashedfile columnname" && dssh "BUILD.INDEX hashedfile columnname" 4. dssh "DELETE.INDEX hashedfile columnname" 5....

Good catch.

Must get the rest of the website back up (in my "copious free time"!).

Search (e.g. Fix Central) or ask your support provider whether this is a known issue for your exact version. I'm not aware of any such behaviour, but I'm not currently using Data Rules.

and you STILL don't have NAME in your INSERT statement.

Try removing all non-required columns from the output link of the Remove Duplicates stage and reverting to your original SQL statement.

Destructive read is the default mode of operation. If you need to you can move each message to a work queue pending the successful commit on the actual target queue, to give yourself a retry capability.

They are not converted to "native machine code instructions". They are dispatched (along with any following arguments) within the DataStage engine to an appropriate function that performs the task associated with that particular opcode.

Yes, read the message again carefully, then look at the INSERT statement (which fails to name the NAME column, and that's probably just the first column that it fails to name). You have configured the Connector to abort when this situation occurs. Can you please look on the Outputs (Columns) tab of ...

Columns never "show up" in the Connector stage reject link. What stage type is on the other end of that link, and what columns do you see there?

Yes.

dr.murthy wrote:... but these are not fetching data parallel.

How do you know that?

What style of funnel are you performing?