We are having this exact same issue. We opened up a case with IBM and didn't get any useful or valuable information from them - they couldn't tell me why they were different. This is extremely problematic because it causes certain items to not appear in the job monitor, which then makes us unable to search for them using any of the filtering in the UI.
If these items abort in Datacap for any reason, we are unable to troubleshoot them because they don't appear in the UI. I had to build in custom queries in Maintenance Manager to be able to find the items that are not appearing in the UI. We are calling them "orphaned" because they don't appear to be tied together in the tables properly due to the way the table joins are being done for the JobMonitor view.
I would urge anyone that relies on the Job Monitor and uses those queries to be aware that you could potentially have data missing from your view.
The issues appears to be related to how the QUEUE.QU_TASK = QSTATS.QS_TASKID are being compared. One of the views will not return results for mismatched TaskIDs and the other one will. We are not sure how the TaskIds are getting mismatched in the table, but it has happened several times over the last few months.
------------------------------
Samuel Neville
------------------------------
Original Message:
Sent: Wed July 27, 2022 08:04 AM
From: Tom Grisham
Subject: issue with Datacap
I am looking into an issue with Datacap and it looks as if some items are not appearing properly in the Job Monitor. After taking a look closer at the Job Monitor view and the JMView, they appear to be ever so slightly different.
My question is, why are they different and what are they used for? Does one load the the results for the Datacap Navigator screen, and another load something else? Are they both used?
Thanks
Tom L. Grisham
------------------------------
Tom Grisham
CEO
Homebuyers Of Kansas
Wichita KS
13164615313
https://homebuyersofks.com
------------------------------