DSXchange

Zero.

You'll need to create a script for that as the WaitForFile stage does not support wildcards. The 'smaller id first' part is just a matter of ordering the list you process properly.

Well, that "load" option invokes sqlldr, so unless you can force it to do a conventional (DIRECT=FALSE) load you won't have any control over commits. If you've screened out any non-inserts then UPSERT may be an option as there are environment variables to control commits there.

It other words, do a lookup against the target table and only load those where the lookup fails.

That's not what was asked. Where/how exactly are you calling this stored procedure?

Actually, just the "split" command since the requirement is by row count. There's no need for the "context split" capability (based on file contents) that the csplit command brings to the table.

Hmmm... the External Source stage should be passing the file/pathname to the XML Input stage and the XML stage should be the one "reading" the file. What is yours doing, exactly?

If you go that route, the UNIX command "split" can be used to chunk up the full file into smaller files and then you may need to loop through the results and rename the files unless you can live with the naming convention the command uses.

Does "installed the datastage" mean both the client and the server? Or just the client?

I don't see how. And if anyone wants to help with the 'unable to save' issue, there's already a thread open for that:

viewtopic.php?t=125964

The OCI stage is definitely compatible with 9i and the OCI8 stage could interface with 9i via an 8i client. The 'dynamic' part of the DRS stage is the pro here with the ? parameter markers being the con. IMHO.

Signal = sign, yes?

That "50" is your count. Your first 'case' statement needs to be corrected, as you only declare the function call good if it returns a zero:

Case Temp = DSJE.NOERROR
Ans = Temp