May 2017
Version: 3.12
- Entering of keys for record selection when submitting to batch is now allowed.
March 2017
Version: 3.11
- 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.
August 2016
Version: 3.10
- 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.
July 2015
Version 3.09
- 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.
June 2014
Version: 3.08
- 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).
February 2014
Version: 3.07
- 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.
June 2013
Version: 3.06
-
75-character licensing has been added.
February 2013
Version: 3.05
- 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.