ClearDDTS 3.4 is a port of the ClearDDTS 3.3 release to support the DEC Alpha Digital UNIX platform. ClearDDTS 3.4 does not contain new enhancements or bug fixes from the 3.3 release.
This release is fully backwards compatible with 3.2 and 3.3. In addition, it supports all the 3.1 commands and is fully interoperable with 3.x sites. This means your 3.4 server can be connected via adminbug conn to any 3.x server.
Customers running versions of ClearDDTS earlier than 3.1.0 should NOT use this release to upgrade directly. Instead, please contact Rational Software Corporation Technical Support at (408) 863-4000 for special instructions. You can determine which version of ClearDDTS you are running by executing the command: whichddts.
ClearDDTS release 3.3 formally supports the following platform:
The ClearDDTS SQL server does not have the capability to perform parallel SELECT and UPDATE statements. This means that updates to the database would have to wait until all queries have been processed. During busy times updates could take a while. For this reason so we have added a timeout that blocks all new queries until the update is completed which takes effect 2 minutes after an update has been queued.
During normal operation users should not be aware of this timeout feature. However, if the system has many users and is busy and someone makes a very long query (over two minutes) and then someone else commits a defect record to the database, there is a possibility that all other users will have to wait for the first user's query to complete before their query is processed. This can cause the appearance of a lockup but is in fact due to action queuing.
There are two workarounds. First you can make users aware of this limitation and make sure they cancel queries running longer than two minutes or do them at non peak hours. Alternatively you can use a commercial database like Oracle with the ability for parallel actions.
The ClearDDTS SQL database server allows the user to search unlimited length enclosures in queries. However, please note that this new feature is not available if you use Oracle as the ClearDDTS SQL server. A workaround is to use fixed length text of 1 or 2 Kbytes to store the enclosure fields. This will allow you to search the first 1 or 2 Kbytes of enclosure text in your searches.
In order to use the ClearDDTS read access control you need to have the fields View (defects.ddts_view) and Security-token (defects.security_token) in your database config files. Please refer to the Administration Manual Appendix F for details on how to add these fields.
ClearDDTS supports SQL statements like INSERT, DELETE, and UPDATE. This is how our database daemons update the online database. However since all data is also kept in the flat files all data changes must happen in both places. All of the ClearDDTS programs do this by using the above statements and then updating the flat files automatically.
Please be advised that if you use the INSERT, DELETE, and UPDATE statements directly without also updating the flat files, all your changes will eventually be lost. As a general rule you should use our client programs (xddts, bugs, batchbug) for database updates and limit your use of the ddtssql program to the SELECT statement only.
Part #: 310-00001-02