DSXchange

Not directly. You can use COMO or DIVERT.OUT commands to capture the results and to disable capture.

Use a job sequence that has a Start Loop activity with the list of file names.

Yes, I just thought I'd clarify that the rules for the engine (the server) are different.

This suggests that the export file from which you are trying to import has job executables only, not design-time information.

Create a new export, WITH design-time information, and import from that. This will override the run-only executable that you currently have imported.

DataStage server is not supported on any Windows XP platform but can be gotten to work on Windows XP Professional. It is not supported on any Windows Vista platform.

You don't (read in parallel) unless the Oracle table is a partitioned table.

Clean out the Registry as well, after uninstalling.

0002.0000 is the same as 2.0. You don't need anything different. Decimal data are stored in binary format, so how they are displayed is irrelevant. To get control over display, you must have a string data type of some kind.

There's nothing built in to DataStage other than the Director client.

Therefore you can use ETLstats (or something like it) or re-invent the wheel.

Please be more specific about which ODBC stage you are referring to - the ODBC Enterprise or the "ordinary" ODBC (API) stage. As far as I can recall, however, both have a property called something like transaction isolation level. In the ODBC Enterprise stage click on the Options folder in the Prope...

Only metadata are stored in the Repository. No data are stored there unless you have designed things thus (which is considered to be a Bad Thing to do).

How busy is the database server, or is it in the process of being shut down or quiesced when these messages appear?

Welcome aboard.

Look at RT_BP73/JOB.1872841101.DT.1479270838.TRANS2 on your server (in the project directory) around line #247, to see what might be causing this error.

"Load" is sqlldr - there is no concept of a transaction, therefore no concept of commit or rollback. Best is probably to identify the run from which rows were added to the target, so that you can selectively delete them.

Does it occur after you restart your client machine?

How long since your project Repository was re-indexed?