Hello Shannan,
without the indexer definition and the data itself it is difficult to help.
But from what you show, it says that it couldn't create the output file and the index file needed to make the load in CMOD.
In order to debug that, you might try to use arsload with the following options:
-i to run only the indexer, and thus keep all the work files
-L 7 to receive more info for the trace (1=errors, 2=warnings, 4=info)
-T <tracefile> to activate and save the trace file for debugging
so for example:
arsload -nv -i -L 7 -T e:\od\arsload\trace.log -g APPG -a APP -u login -p password e:\od\arsload\wi.x.EFTReversalStatusRpt.EFTReversalStatusRpt.20091118.1111.ard
In that example you will see more messages on the screen, and you will also have the e:\od\arsload\trace.log file with all the info.
If that does not help, you could try to use -L 15, it will add more messages on what does arsload, but maybe that would be too much non useful informations...
Let us know if you could find something interesting, or need help.
For your info, here are the full explanation of the options of arsload (
http://publib.boulder.ibm.com/infocenter/cmod/v8r4m1/topic/com.ibm.ondemand.administeringmp.doc/dodlo003.htm).
Cheers,
Alessandro