Thursday, April 12, 2012

AutoDelete does not contain a 'suspended' batch status filter in IBM Datacap Taskmaster Capture

Auto Delete does not contain a 'suspended'


batch status filter in Datacap Taskmaster Capture


Abstract


AutoDelete does not contain a 'suspended' batch status filter in IBM Datacap Taskmaster Capture

Resolving the problem




The "suspended" status is normally not used, but batches can be set to the status using the rrunner library action SetTaskStatus or some equivalent. In AutoDelete there is no filter for the batch status; this limitation is removed in IBM Datacap Taskmaster Capture 8.0.0 and later through NENU, the replacement for AutoDelete.

In Taskmaster 7.6 and earlier, batches with the "suspended" status can be deleted manually through the Job Monitor. In IBM Datacap Taskmaster Capture Client the Job Monitor Filter menu has a SQL button where a customized filter can be inserted -- the value qu_status IN ('suspended') can be used to show only batch records with the suspended status. Similar functionality exists in Taskmaster Web with the Monitor's Filter button screen.

No comments:

Post a Comment