Ok, I (actually, a certain awesome lady at IBM support) was able to pinpoint the problem. Occasionally, if an absolute path is not specified when calling the application, the batch adapter "hicups" and failes to call it. So, simply specifying the path name in the batch file cured the problem.