Powertech Database Monitor for IBM i
NOTE: Prior to versions 3.16, Database Monitor for IBM i was called Data Thread.
- The new product name, Powertech Database Monitor for IBM i, is now used throughout the software and accompanying documentation. (Prior to version 3.17, the product was called "Data Thread.")
- An issue causing Notify Only users (non-signers) to be displayed on the Workflow History screen has been resolved.
- Message CPF950A 'Storage limit exceeded for data queue IDTINDXQ in DataThread' is no longer sent many times (which can result in filling up job logs).
- An issue causing the incorrect program to be reported as having made a change to a monitored file on IBM i 7.2 and 7.3 has been resolved. (QDZXDBI is no longer reported as QDBUDR.)
- A typo has been fixed in the REFMON description.
- An issue regarding the selection of fields to be tracked has been resolved.
- An issue reporting the correct program to have made a change to a monitored file in the Inquiry screen has been resolved (affected systems running IBM i V7R2 and V7R3 only).
- A performance issue that could result in slow processing has been resolved.
- The number of Job Exclusion entries allowed has been increased from 250 to 999.
- Workflow signatures were added to Data Thread reports, including XML output.
- Data Thread no longer fails improperly when the DATATHREAD user profile can not be created.
- Duplicated transaction IDs are no longer created under certain scenarios.
- Entering of keys for record selection when submitting to batch is now allowed.
- The DT_DUPPROC job no longer loops occasionally while attempting to fix duplicate Transaction ID's.
- An error during the product update relating to the EVFEVENT file has been resolved.
- Incomplete CSV output has been corrected.
- A new System Parameter has been added to opt 12, EM-DTFMT, that allows the email date format to be customized.
- Data Thread is now delivered with new deployment functionality, including the ability to stage the product installation.
- Issues with IDTINDXQ overflowing have been resolved.
- Date range handling and general performance issues in Transaction Inquiry have been fixed.
- A license code issue has been resolved.
- A problem causing the User Journal Monitor job to stop processing and loop has been resolved.
- Failed updates from version 3.2 have been resolved.
- IDTLOD/ITDLOH are no longer converted during an update, decreasing the time required for updating.
- Validation checks have been added when retrieving Code Type EMAILMBR, remedying the error MCH1210.
- *NOTRACK errors have been resolved.
- Path name comparisons in IDTAUDxx files have been fixed to allow for filtering by path/object.
- Messages accompanying signature requests are now for the current change (rather than the previous change).
- Code was changed to allow the journal reader to continue reading the next journal sequence number.
- A Workflow issue whereby the program call will not call the program after the first event has occurred has been resolved.
- Multiple possible failures due to changes to the OVRDBF command’s default settings have been resolved.
- 75-character licensing has been added.
- In older versions setting up a Job Exclusion using 400JOBEXCL from Option 13 in DataThread only worked with triggers, not journals. This change adds job exclusion functionality to journal monitors.
- New message is displayed when a field being monitored that is greater than 1024 is selected (field length surpasses allowed length).
- When the system manager is already running ( IDTALO ) DataThread now suppresses "Unable to allocate IDTALO.." messages to reduce message volume.
- Fix issue with CSV files w/commas in fields in a report issued from the DTPRT command or Option 27 in DataThread.
- Remove RUNSQL command so the program will not use the incorrect version of RUNSQL during installation.
- Allow for fields longer than 9,999 for a Key or Field when setting up a file to be monitored within Option 11 of DataThread.
- Now show error messages at the bottom of the menu screens that have not been there since R03M03 because of Powertech copyright being added to the screen.
- Update the journal monitor program to recognize the correct amount of data from the journal entry. The journal monitor was not grabbing the correct amount of data from the journal entry causing an error.
- Monitor jobs were causing a new instance of the programs to be created each time they are called, which was slowing down processing and requires additional CPU This fix changes the activation group on monitor jobs to current ‘named’ groups rather than ‘New’ to improve performance.
Back to Product Index