DSXchange

I think that the NLS may not have been enabled in the 7.1 installation and was enabled in the 7.5.1.

Also commit and transaction size.

As for abort, they will be the one in the top as they will be the last job run before failure.

You need to make sure that the format is correct. Also you need to verify the possibility of null values and / or incorrect date values in that field.

Do the sub-batches run in parallel?

If you perform an 'Add Job', it will automatically include the syntax to capture failure.

Can you describe on how you have designed and what happens when one (batch) job fail.

Take the job executables as part of your export.

Check whether your network traffic is high.

If you want to correct, try a convert or trim.

If you want to identify the char, try preparing various ascii chars and matching them with the char you obtain.

Check whether you have any IPC stage within that container.

Did you run the job as a different user last time? Maybe the temp file was created with the other user's permissions.

Check whether DataStage is installed and running in that machine. Also check whether you have any firewall preventing connections.

You can write a shell script to 'extract the list of invocations id and then reset them one by one'.

They will be in your proj dir from which you ran those jobs.

Check the stage variables and their default values.

The error can be located in the given line number on the BP dir TRANS file.

But you do not have a 'Before-SQL' tab in ODBC stage.