DSXchange

The OP was on version 6. Is this true for all of you?

Is NLS enabled? You are using a code page on your Windows client that does not correspond to that used on the DataStage server. Try setting each to 1252 and working from there.

You need to mark columns A, B and C as Key in your job design. "Key" in this context does not mean primary key - it means "search key" and gets the parameter markers to bind to the WHERE clause.

The DS.AUDIT table keeps track of the most recent time that an object was deleted, and by whom. Of course, it may be that nothing has been deleted and you can't see them because the indexing needs rebuilding.

Why do you want to do "other than"? It's a perfectly valid approach. Anyway, one "other than" approach is to decompose your source date using substring techniques then re-assemble it with concatenation, adding the time portion.

Filter stage has limited regexp capability.

DataStage can be configured to support real-time applications, by exposing a job as a web service through ISD. An always-running, multi-instance job is capable of quickly processing the data sent to it by the caller (and sending data back to the caller). There is probably insufficient "encryption in...

There's only one output but it contains three fields: the first input row (as a subrecord), the second input (as a subrecord) and the difference result.

So use Compare stage, which outputs both inputs.

You can't. Each node operates independently. You need to re-think your design and/or your parallelism.

Check in Information Server Web Console. You can find out on the Licensing screen what products you have licensed.

Maybe yes. Randomly. Depends on the number of rows and the seed used for generating the "random" numbers.

Why aren't you using one of the change detection stages (Change Capture, Difference or Compare stage)?

You need to run DS.CHECKER to tidy up the partially-removed job before you can proceed with an override-import. And you will need exclusive access to the project to do so.

1. Get the file provider to guarantee fixed width. What you have isn't.

2. Read as single VarChar(400) field and parse inside your job.