Batch aborts running NENU actions in Taskmaster Client with IBM Datacap Taskmaster Capture

Batch aborts running NENU actions in Taskmaster Client

with IBM Datacap Taskmaster Capture

Abstract

When attempting to run the NENU ProcessChangeBatchStatus, ProcessChangeBatchStatusOrder, or ProcessChangeBatchStatusTaskOrder actions in Taskmaster Client along with the actions required prior to these, the batch finishes with a status of aborted, even though no reasons are provided in any of the logs

Cause

Although it is allowable in general to run NENU actions with Taskmaster Client, they were designed and tested to be run by the NENU application. Some NENU actions that manipulate batch properties interfere with Taskmaster Client's manipulation of those properties

Resolving the problem

Only run the ProcessChangeBatchStatus, ProcessChangeBatchStatusOrder, or ProcessChangeBatchStatusTaskOrder actions with NENU