Rational ClearQuest 2000 Patch 1 Release Notes

Please read this document to learn about known product issues, important tips, and other Rational ClearQuest product information.

Release Notes, version 9.3.00

1.0 Supported Platforms and System Requirements

1.1 List of Supported Platforms and Operating Systems
1.2 Upgrading from Previous ClearQuest Releases
1.3 What's New in ClearQuest 2000 Patch 1
1.4 What's New in ClearQuest UNIX
1.5 Defects Fixed in ClearQuest 2000 Patch 1
1.6 Oracle Database Connection Options

2.0 Known Defects

2.1 Installation
2.2 CQ Client
2.3 CQ Designer
2.4 CQ Web
2.5 CQ Import and Export
2.6 User Documentation
2.7 UCM Integration

3.0 Troubleshooting Web Services

3.1 Basic Troubleshooting Tips
3.2 Advanced Troubleshooting Tips

4.0 The Rational Web Site

5.0 Subscribing to the ClearQuest User Group

6.0 Accessing the Sample Hooks Database

7.0 Contacting Technical Support

1.0 Supported Platforms and System Requirements

1.1 List of Supported Platforms and Operating Systems

1.1.1 Windows Operating Systems:

Windows 2000
NT 4.0 SP5 and SP6a
Windows 95 SR2
Windows 98 Second Edition

Supported Languages:

Dutch
English
French
German
Italian
Japanese
Simplified Chinese
Traditional Chinese
Swedish

Browsers and Other Packages:

Internet Explorer 4.01 (4.72.3110.8 is recommended) and 5.x.
Netscape Navigator 4.0.4, and Communicator 4.5, and 4.7.
Internet Information Server (IIS) 4.0 and IIS 5.0 (on Windows 2000).
MDAC 2.1.2
Visual Studio 6 SP3, Visual Studio 5 SP3
Office 2000, Office 97 SR2
Crystal Reports 6.0 and 8.0 (see section 1.3 as well as defect 12965 in section 2.2)

Databases:

Oracle 7, Oracle 8.0.5, and Oracle 8i/8.1.x Client and Server (see sections 1.3 and 1.6)
SQL Server 6.5 Service Pack 5
SQL Server 7 Service Pack 2
SQL Anywhere 5.5.04
MS Access

Disk Space Requirements:

Drive containing system files: 43 MB (default is drive C)
Drive where ClearQuest is installed: 141 MB

1.1.2 Unix Operating Systems (see also section 1.4):

Solaris 2.5.1, 2.6, and 7 (2.7)
HP-UX 10.2 and 11.0

Supported Language: English Browsers and Other Packages:

Netscape Navigator 4.7 (see also defect 12444 in section 2.4).

Databases:

Oracle 7, Oracle 8.0.5, and Oracle 8i/8.1.x (UNIX Server only)

1.2 Upgrading from Previous ClearQuest Releases

Upgrading from CQ 2000
Customers upgrading from CQ 2000 to CQ 2000 Patch 1 should be aware of the following:

No database upgrade is required when going from CQ 2000 to CQ 2000 Patch 1.
It is possible to interoperate between CQ 2000 and CQ 2000 Patch 1 (i.e. for some workstations to have 2000 installed, while others have CQ 2000 Patch 1 installed) with the following caveats:

Clients running 2000 will not be able to modify reports that were created under 2000 Patch 1, if Crystal Reports 8 was used in the 2000 Patch 1 installations.
CQ 2000 Patch 1 Clients can use reports and report formats that were created in 2000 with Crystal Reports 6, but Crystal Reports 8 must be used with 2000 Patch 1 when creating and modifying new report formats (see also defect 12965 in section 2.2).
CQ 2000 Patch 1 users must download the Patch 1.1 fix in order to utilize the capabilities seen in the following integrations: VSS-CQ; Robot and the Rational Administrator; CC-CQ; UCM; CQ-RequisitePro (see also defect 13293 in section 2.2).

Because of these caveats, Rational recommends that you upgrade the software on all workstations at the same time. If you have installed ClearQuest 2000 in a Rational Suite, you may install ClearQuest 2000 Patch 1 on top of that Suite.

To upgrade the software from CQ 2000 to CQ 2000 Patch 1, follow these steps:

Step 1: Run the CQ 2000 Patch 1 setup executable and select "Install Rational Product" in the first installer pane.

Step 2: In the next installer pane, select, "Install Product before Licensing," then proceed to install ClearQuest as you did with the CQ 2000 installation.

Please note that:

When 2000 Patch 1 is installed over a 2000 Suite, you'll get an additional entry, for CQ only, on the Start menu.
Upon invoking ClearQuest for the first time, you will need to connect to the ClearQuest databases again. Get the database location and connection information from your CQ Administrator, and enter it, when prompted.
If you use CQ 2000 Patch 1 and set the Oracle DB connect options to either 8.0 or 8.1, you won't be able to run CQ from a 2000 installation. See also defect 12405 in section 2.2.

To upgrade the software from CQ 2000 to CQ 2000 Patch 1 as well as upgrade from Crystal Reports 6 to Crystal Reports 8, follow these steps:

Step 1: Uninstall Crystal Reports 6.

Step 2: Run the CQ 2000 Patch 1 setup executable and select "Install Rational Product" in the first installer pane.

Step 3: In the next installer pane, select, "Install Product before Licensing," then proceed to install ClearQuest as you did with the CQ 2000 installation.

Step 4: Install Crystal Reports 8.

To set up CQ 2000 Patch 1 with Crystal Reports 8 in a standalone mode, but not over a CQ 2000 Suite, follow these steps:

Step 1: Run the CQ 2000 Patch 1 setup executable and select "Install Rational Product" in the first installer pane.

Step 2: In the next installer pane, select, "Install Product before Licensing," then proceed to install ClearQuest.

Step 3: Once the patch installation is complete and the Rational License Key Administrator form appears, licensing can be established for the new installation.

Step 4: Install Crystal Reports 8.

Upgrading from CQ 2.0
Customers upgrading from CQ 2.0 to CQ 2000 (or CQ 2000 Patch 1) should be aware of the following:

No database upgrade is required when going from CQ 2.0 to CQ 2000 (or CQ 2000 Patch 1).
It is possible to interoperate between releases 2.0 and 2000 (i.e. for some workstations to have 2.0 installed, while others have 2000, or 2000 Patch 1, installed) with the following caveats:

Clients running 2.0 will not be able to run queries that were created or modified under 2000 (or 2000 Patch 1).
CQ 2000 Patch 1 Clients can use reports and report formats that were created in 2.0 with Crystal Reports 6, but Crystal Reports 8 must be used with 2000 Patch 1 when creating new report formats (see also defect 12965 in section 2.2).
CQ 2000 Patch 1 users must download the Patch 1.1 fix in order to utilize the capabilities seen in the following integrations: VSS-CQ; Robot and the Rational Administrator; CC-CQ; UCM; CQ-RequisitePro (see also defect 13293 in section 2.2).
When using Oracle databases, any operation involving exporting the schema or schema repository will not work if the export is done from 2000 Patch 1 and the import is done on 2.0; this is because the specification for Oracle databases has changed from "Oracle7" to "Oracle" in the text files created by these tools. 2000 Patch 1 supports either format, but 2.0 does not.

Because of these caveats, Rational recommends that you upgrade the software on all workstations at the same time. If you have installed ClearQuest 2.0 in a Rational Suite, you may install ClearQuest 2000 Patch 1 on top of that Suite. To upgrade the software:

Install the new (2000 Patch 1) software on top of the existing installation (as an "upgrade" in the Rational Installer; this is selected for you by default in the installer).
If the patch is installed over the Suite then youll get an entry for CQ on the Start menu.
Upon invoking ClearQuest for the first time, you will need to connect to the ClearQuest databases again. Get the database location and connection information from your CQ Administrator, and enter it, when prompted.

Upgrading from CQ 1.0, 1.1, or 1.1 SP1

Customers upgrading from 1.0, 1.1, or 1.1 Service Pack 1 should refer to the documentation in Chapter 7 of the manual, Installing Rational ClearQuest.

Please be especially aware of the following:

If you have applied any of the ClearQuest add-ins from version 1.1 to your schemas (or if you used certain functionality that was supplied as part of the provided sample schemas like TeamTest or Enterprise), you must use the Package Wizard to apply the equivalent upgrade packages to these schemas. For more information see "Working with schema packages" in the ClearQuest Designer Help. Specifically:

If you have installed the Email Rules functionality (either by using the add-in or by using the TeamTest schema, which has this functionality installed by default), then you must apply the Email package (Upgrade 2.0 version).
If you installed the Visual SourceSafe or the ClearQuest/ClearCase integration add-in, apply the Visual SourceSafe package (Upgrade 2.0 version) or ClearCase package (Upgrade 1.0 version) respectively.
If you are using the integration with TeamTest, Test Studio, or the Rational Administrator, you must install both the "TeamTest" and the "Repository" upgrade packages. If you do not install both of these packages, you will get errors creating the ClearQuest project records when trying to connect the ClearQuest database to the Rational Repository.

If you do not apply the needed upgrade packages after upgrading the ClearQuest software and databases, the existing functionality (notification mail, integration with your source code management system, etc.) will be inoperative.

NOTE: Be careful when selecting the packages to install. Some packages (such as Email and Visual SourceSafe) have a version for first-time installations (for example, version '1.0') and a version for upgrades (for example, version 'Upgrade 1.0'). Be sure to select the correct version.

As a general rule of thumb, when installing upgrade packages, if there is more than one version, always apply the highest-numbered version. Record types, fields, and actions that were added by the add-ins are modified by the packages. The package takes "ownership" of these entities (record types, fields, and actions) so that in some cases they become readonly in the ClearQuest Designer.

1.3 What's New in ClearQuest 2000 Patch 1

Introduction

ClearQuest 2000 Patch 1 includes support for new platforms, enhanced documentation and improvements in a number of areas that may be critical to your deployment. It provides support for these new platforms:

Oracle 8.0.5 and 8i Client and Server
Oracle 8i Context Server
Crystal Reports 8
SQL Server 7 Patch 2

ClearQuest 2000 Patch 1 also provides an update to ClearQuest 2000, offering a variety of fixes problems in a number of areas that may be critical to deploying ClearQuest in certain configurations. These include:

Web Stability and Performance
Handling of Date/Time
Other issues

Support for Oracle 8.0.5 and 8i Client and Server

Rational ClearQuest now includes support for Oracle 8.0.5 and Oracle 8i client and server. This alleviates the need for Oracle 7.3.4 network protocols on the client side. Users can install Oracle 7.3.4, 8.0.5 or Oracle 8i. For further details, please refer to section 1.6 and the Installing Rational ClearQuest guide.

Support for Crystal Reports 8

ClearQuest now supports the latest release of Crystal Reports. You can now use the features provided in Crystal Reports 8.0 in your ClearQuest reports. (Please note that CQ 2000 Patch 1 Clients can use reports and report formats that were created in 2000 with Crystal Reports 6, but Crystal Reports 8 must be used with 2000 Patch 1 when creating new report formats. See also defect 12965 in section 2.2).

SQL Server 7 Patch 2 Update

Support for SQL Server 7.0 SP2 is included in this release.

Documentation

The API guide now has more Perl examples, including code for:

Getting and setting attachment information
Updating duplicate records to match the parent record
Managing records that are stateless and stateful
Extracting data about a record type
Showing changes to a record
Running a query and reporting on its result set
Getting session and database information
Running a query against more than one record type
Triggering a task with the destination state
Extracting data about a field in a record

Web Stability and Performance

ClearQuest 2000 Patch 1 includes one enhancement and fixes several memory leaks that may have caused the deployment of ClearQuest for the Web to have stability problems. The typical symptom that would have been seen is an ASP115 error from IIS or web server hangs . You should also check the version of MDAC that is installed on your web server. For improved stability of the web server, you should run the virtual directory in the same memory space.

1. Shared Metadata - ClearQuest has been enhanced to share metadata among multiple sessions.. The metadata is the description of the record types, forms, and hook scripts for a ClearQuest database. Previously, ClearQuest kept a copy of the metadata for each user's session now copies of the meta-data are automatically shared by multiple sessions. This can result in a significant reduction in memory usage depending on the complexity of the underlying schema.

2. Memory leaks - ClearQuest 2000 Patch 1 fixes a number of memory leaks that have been found with registry handles, history records, etc. These changes should decrease the amount of memory used by ClearQuest in a web environment. For example, in a 50 user test scenario involving a typical schema ClearQuest 2000 Patch 1 uses approximately 400 MB of memory and can be run indefinitely on a machine with 1GB of RAM. Previously, this same stress test would have eventually exhausted memory. Please see item 7 for more information on recommended configurations.

3. Deadlock on Simultaneous Commits - ClearQuest 2000 Patch 1 fixes a problem with deploying the CQ Web against SQL Server (6.5 and 7.0) where two users committing a defect at exactly the same time would encounter a deadlock situation. The symptom encountered here is one of the following:

SQL Server error message is generated when a record is committed: "[Microsoft][ODBC SQL Server Driver][SQL Server] Your transaction (process ID #19) was deadlocked with another process and has been chosen as the deadlock victim."
Another symptom is that a query appears to hang waiting on a record table lock and/or the SQL Server error log would contain entries for "sp_cursorfetch" errors; hanging problem goes away when the hung SQL Server user process that has the lock to the record table is killed.

4. Oracle multi-threading - ClearQuest 2000 Patch 1 protects the web server against a number of problems where the ODBC drivers for Oracle do not appear to work correctly in a multi-threading environment.

5. MDAC version - We have discovered that the combination of the Rational install and installation of IIS can cause a version mismatch in the Microsoft Database Access (MDAC) libraries. You should check your installation to ensure that you have MDAC version 2.1, SP2 (2.1.2.4202.3) or above on your machine. If you don't have it, you can download it from Microsoft site, http://www.microsoft.com/data/download.htm. You can download the Component Checker from the above location to determine the installed version information of your MDAC libraries. One other way to make sure you have the appropriate version of MDAC is to check the version of SQL Server ODBC driver shown in the ODBC control applet - it should read at least 3.70.06.90.

6. IIS performance tuning - In order to ensure top performance from CQ Web in a multi-user environment, please be sure the following IIS tuning is completed:

On the Internet Service Manager->host_name->Properties->Internet Information Server tab, check "Enable Bandwidth Throttling" and use the default of 1024 kb/s for maximum network use.
On the Internet Service Manager->Default Web Site->Properties->Web Site tab, uncheck the "Enable Logging" option.
On the Internet Service Manager->Default Web Site->Properties->Performance tab, set the performance tuning scale to the maximum (more than 100,000).
On the Internet Service Manager->Default Web Site->Properties->Performance tab, make sure the "Enable Bandwidth Throttling" option is unchecked.
On the Internet Service Manager->Default Web Site->Properties->Performance tab, uncheck the "http Keep-Alives Enabled" option (this option is in the Web Site tab for IIS5).

7. In order to ensure web stability under high loads, Rational is performing load testing involving 50 simultaneous users performing normal operations (e.g.,, submit, modify, query) which is equivalent to a typical user community of approximately 300 users per web server. Based on this load testing Rational recommends the following configurations for best performance and stability under high loads:

Windows NT 4.0 SP6a, IIS 4.0, SQL Server 7.0 SP1

Windows NT 4.0 SP6a, IIS 4.0, Oracle 8.0.5 Server, Oracle 7 Client

Date/Time

ClearQuest 2.0 changed the internal storage of dates and time to use GMT as the way that dates and time were stored in the CQ user database and display dates and time in the locale used at a particular client. However, the upgrade process did not change existing dates and times in CQ 1.1 databases to use GMT. This resulted in databases that stored times in a combination of GMT and local time, which would lead to minor inaccuracies in displayed dates. ClearQuest 2000 Patch 1 fixes this upgrade issue by converting the existing local times stored to GMT in an existing CQ 1.1 database. If you decide to upgrade from CQ 1.1 to CQ 2000 Patch 1, we recommend that you install ClearQuest 2000 Patch 1 on the machine where the upgrade process will occur. If you already upgraded to ClearQuest 2.0, or 2000 Patch 1, and you wish to convert your 1.1 data to GMT, please contact Rational Technical Support.

Other Issues

The following lists a number of other defects that have been addressed in ClearQuest 2000 Patch 1. See section 1.5 for a more complete list.

Hook editing is now possible for the action access control hook.
Using Queries with dynamic filters as the query in a Report now executes correctly using Crystal Reports.
Setting a filter date field equal to "Today" represents the entire range of the current date. In previous releases, "Today" represented an exact time (midnight) and returned non-intuitive results.
As deployed for ClearCase Unix, the ClearCase/ClearQuest integration performance has been improved significantly by employing some simple caching techniques to give significantly better performance.
Hook scripts written in Perl can execute nested actions. This limitation has been removed.

1.4 What's New in ClearQuest UNIX

Introduction
This release of ClearQuest also provides increased support for ClearQuest's "design once, deploy anywhere" capabilities through the introduction of native UNIX clients. ClearQuest UNIX includes both a motif-based and command-line interface that enables UNIX users to use a native interface in addition to ClearQuest Web. The ClearQuest UNIX interface was designed to resemble the Windows client both in functionality and look and feel, and enables UNIX users to submit records, create, edit and run queries and create text-based reports. Support for ClearCase integration, including UCM, is provided on the new UNIX platform.

Customizations designed once using the ClearQuest Designer on Windows are deployed automatically to all client platforms, including Windows, UNIX and the Web.

ClearQuest UNIX is supported on the following platforms:

Solaris 2.5, 2.6. and 7 (2.7), HP-UX 10.20 and 11.0

ClearQuest UNIX is supported with the following database servers:

Oracle 7, Oracle 8.0.5, and Oracle 8i/8.1.x (UNIX Server only)

Please contact Technical Support for more information on the general availability of ClearQuest UNIX.

Using CQ Unix with Existing ClearQuest Databases

ClearQuest UNIX requires supported database servers to be on UNIX platforms. Even though you can have multiple databases using a mixture of database vendors, ClearQuest UNIX will only access those databases that use Oracle on UNIX. In order to enable your Oracle databases for use with ClearQuest Unix, you must change the "Connect Options" on your master and user databases. For the user databases, this property can be changed from the ClearQuest Designer, in the Database Properties dialog on the Database menu. However, changing properties of the schema respository cannot be done from that dialog.

Contact Rational Technical Support for assistance with this process.

1.5 Defects Fixed in ClearQuest 2000 Patch 1

Web Stability Issues:

Defect 7930: System internal error: invalid use of shared metadata session.
Defect 9295: Deadlock happens when simultaneous query or commits are attempted.
Defect 10493: Web service fails after 10 users (an issue with OpenLink drivers).
Defect 10662: CQ Core memory leaks.
Defect 10760: Java Script Error when clicking on Browser page after generating a Report.
Defect 10858: Web list_callback performance for web dependent fields sub-optimal.
Defect 10902: CC/CQIntegration is too slow on Web.
Defect 10907: Trace.inc Trace enhancements did not get implemented.
Defect 11335: Microsoft Transaction Server hogging CPU on CQWeb machine.
Defect 11416: Long delay after associating a defect with ClearCase/ClearQuest integration.

Other Issues:

Defect 2327: Setting filter date field equal to "Today" doesn't work.
Defect 6992: CQ Web field not in group box, but should be.
Defect 7934: Package name lookup not working for user sessions.
Defect 8524: CQWeb submission form fails to display all tabs.
Defect 9079: Push buttons do not work as expected in CQ Web 2.0.
Defect 9316: Web-enabled buttons not actually enabled.
Defect 9625: Group box contents do not show correctly in CQ Web.
Defect 9679: Hook edition not possible for the action access control hook.
Defect 9792: Can't save query from ClearQuest web 2.0.
Defect 9930: Bogus date result when the NT time setup is set to GMT +1 (or +x).
Defect 9954: Queries using dynamic filters are not displayed within Crystal Reports.
Defect 10073: Notification doesn't work after applying 2.0 Patch 1.
Defect 10301: Openlink Oracle8 drivers truncate constant numbers like 16777822.
Defect 10317: Problem with a mandatory field on the Submit EnhancementRequest form.
Defect 10512: Need to convert local time to GMT time when upgrading from 1.1 to 2.0 or 2000.
Defect 10554: VSS checkin is deleting entry in CQ VSS Change Set.
Defect 10649: Perl $entity points to wrong record type after creating a child record.
Defect 10672: No status in the installer when creating CQ evaluation databases.
Defect 10765: Internal error occurred displaying tabs on certain customer-specific forms.
Defect 10779: Wrong display in the web when two fields are placed in a group box.
Defect 10849: Need to have web track and be able to report logon usage.
Defect 10909: Cannot move databases from SQL Server to Oracle.
Defect 10924: Form layout problem with a group of radiobuttons.
Defect 10925: Incorrect form layout seen with certain schemas when the new layout method is applied.
Defect 10945: RECORD_SCRIPT_ALIAS actions don't work from Perl.
Defect 11014: CQWeb Not Displaying Date Fields Correctly in Form.
Defect 11046: ReferenceList (listctrl) not showing button labels correctly in web.
Defect 11071: Setfieldchoicelist on entity missing in cqperlext.pm.
Defect 11096: After Cancel in New Child, Apply of Modify State in Parent causes Error.
Defect 11257: Predefined schemas have the Submit action greyed out.
Defect 11273: Fix to Web CC/CQ Integration not handling DbName Change Properly.
Defect 11282: Web Dependent Fields not working on SSL Web Site.
Defect 11336: Improve the information provided on ClearQuest version numbers in the About Box.
Defect 11366: Need to Show Database Description in DB Selection Field at Login.
Defect 11417: Error when building & unbuilding CQ session against Oracle user db.
Defect 11518: Rational Installer doesn't upgrade OpenLink driver.
Defect 11533: Copy & paste operation into Global Scripts problem.
Defect 11601: Base action hook called twice.
Defect 11643: Email Rule using Source State in Action Controls does not work in CQ 2000.

1.6 Oracle Database Connection Options

Oracle Connection Options

The connect_options database property has been expanded to support Oracle 8 clients. This option is a site-wide setting per database. The CQ user sees these options as a string in the Connect Options field in the CQ Maintenance tool when attempting to connect to an Oracle database. The permissible values are:

host=<host>;sid=<sid>;server_ver=<ver>;client_ver=<ver>;lob_type=LONG

where,
<host> is the network hostname of the Oracle database server;
<sid> is the instance ID of the Oracle database server;
<ver> is the Oracle version number, either, 7, 8.0 or 8.1;
server_ver is the Oracle database server version number;
client_ver is the Oracle client version number;
lob_type is the Oracle data type used for text fields; currently, this must be of type LONG.

You can override each, or all, of the connect options values per machine by using installutil registeroracleoptions command-line utility. This will not change the setting in the master database, only the way a specified client will connect to the database. A sample registry entry looks like:

[HKEY_CURRENT_USER\Software\Rational Software\ClearQuest\2000.02.10\Core] "OverrideOracleConnectOptions"="client_ver=8.0"

For Unix, the client-based connect override can be achieved by setting the environment variable:
CQ_OVERRIDE_ORACLE_CONNECT_OPTIONS

The Oracle client connect options are also described in the guide, Installing ClearQuest. Please refer to the section, "Creating ClearQuest Databases."

Also note that, while not all the Oracle connect values are required, it's a good practice to set all the values to avoid any undesirable default behavior.

What Does This Mean to the ClearQuest User?

Oracle 7 and 8x Servers; Oracle 7 Clients:

This is the supported configuration prior to CQ 2000 patch 1 and customers don't have to set any Oracle connect options in order to continue using this Oracle client/server configuration.

Oracle 7 and 8x Servers; Oracle 8 and 8i Clients:

Customers should use the appropriate Oracle connect options for their configuration. For example, if they can connect to an Oracle 8.0.5 server via an Oracle 8i client, they should use: server_ver=8.0;client_ver=8.1.

Oracle 7 and 8x Servers; Oracle 7, 8, and 8i Clients:

This configuration will require setting the Oracle connect options for the site, as well as on machines that deviate from the site setting. If most of the CQ clients are using Oracle 8.0.5 client, they should set connect options with client_ver=8.0 in the master database. Then, for the CQ client machines that have Oracle 7 or Oracle 8i clients, those users will need to use the installutil registeroracleoptions command-line utility in order to override the 8.0-client master DB setting.

Setting Connect Options for New Databases:

You should set the appropriate connect options using the guidelines above.

Setting Connect Options for Existing Databases:

To set the connect options for an existing schema repository (i.e. not newly- created with the CQ Maintenance tool), use the installutil registeroracleoptions command-line utility to set the connect options for existing user databases. After that, use CQ Designer and execute the "Database Property" dialog and enter the connect options there. Make sure to answer "NO" when it asks whether you want to physically move the database. Another way is to run the installutil relocateuserdb command-line utility.

An Example: the server is an Oracle 8i instance; and there are existing CQ 2000 Patch 1 clients with Oracle 7 client software; as well as new CQ 2000 Patch 1 clients with Oracle 8i client software.

There are two methods to set up this site:

Method 1: Set the client 8 option per CQ client machine.

Step 1 For each new CQ client machine where the Oracle 8i client is also installed, run the command line: installutil registeroracleoptions "server_ver=8.1;client_ver=8.1"

Method 2: Set the client 8 option for all CQ clients.

Step 1 Run the following command-line utility in order to change the properties of the schema repository: installutil relocateschemarepo ORACLE <dbo_login> <dbo_password> <rw_login> <rw_password> <ro_login> <ro_password> "server_ver=8.1;client_ver=8.1"

Step 2 Run the Designer and change the connect_options property of all user databases to "server_ver=8.1;client_ver=8.1".

Step 3 On existing CQ client machines where the Oracle 7 client is installed, run the command line: installutil registeroracleoptions "client_ver=7"

Please note that, if your existing CQ client machine is still using a non-patched 2000.02.10 version of CQ, the only option is to use method 1 above (See also defect 12405 in section 2.1).

2.0 Known Defects

NOTE: All defect numbers listed here are "RAMBU" database defect numbers.

2.1 Installation

Defect ID	Description
5607	Minimal client install looks for an .ini file in the target install directory. During a minimal client installation, if cqprofile.ini exists in the source directory, it is not copied to the client's local destination directory. The workaround is to copy the cqprofile.ini file manually to the local destination directory.
6533	Unable to do defect association with SQL Server that is configured for case sensitivity. When installing SQL server, make sure you set the dictionary sort order to case insensitive. Otherwise, VSS integration will work, but you will get a "cqvssmgr:Error:GetVSSEntityByItem" error. If the admin installs SQL Server with the wrong sort order, the user databases will have to be removed before any reinstallations of CQ with a different sort order.
8097	Schema list is missing with minimal/evaluation install. The set of out-of-the box schemas are not available in the pull-down list box for Schema Setup after installing a minimal evaluation configuration of ClearQuest. By copying the sample_dbs directory from the network directory to the local drive, the schema list can be populated by ClearQuest Maintenance Tool and you'll be able to create a sample db.
9963	Cannot build a SQL/Anywhere schema repo for CQ on Win2000. When creating a SQL Anywhere schema repository for CQ, an error dialog will appear. Currently, creation of SQL/Anywhere schema repos on the Windows 2000 isn't supported. A patch provided by Sybase, SQL Anywhere patch 5.5.05ebf build 2734, is recommended.
10675	SQL Anywhere setup clarified. Sybase SQL/Anywhere has limitations with respect to its ability to smoothly cross IP subnet and Windows/NT domain boundaries. To successfully create and use SQL/Anywhere databases, if any of the relevant machines (the one on which the database server is running, the web server, or your client workstation) are in separate IP subnets or Windows/NT domains you should be aware of certain precautions and limitations. These are spelled out at length in Rational Technical Support TechNote 10773. To summarize the information in the TechNote: The safest and most reliable method is to create all ClearQuest SQL/Anywhere databases while running the ClearQuest Maintenance Tool or ClearQuest Designer programs on the same machine as the SQL/Anywhere database server. All ClearQuest client machines (including the web server) should be in the same IP subnet and Windows/NT domain as the Sybase SQL/Anywhere database server. These suggestions are quite restrictive. The TechNote spells out additional techniques that can be used to work around SQL/Anywhere's limitations and enable usage with fewer restrictions; see the TechNote for details.
11079	ClearQuest release notes cannot be accessed from the RS Release Notes link on a minimal install. After doing a minimal install of Rational Suite Enterprise, if you launch the Readme for all products, and click on the ClearQuest release notes link, it points to the network location from where the install took place. However, the Readme file is installed onto the local machine. Look inside the ClearQuest directory under the installation directory and look for the readme.htm file.
11989	Connection error when upgrading from 1.1 Oracle 8 DB to CQ 2000 Patch 1 with an Oracle 8 client. If you use a machine, which has the Oracle 8 client installed on it, to perform a CQ upgrade, the CQ Maintenance Tool ignores the client_ver option and you will get a connection rejected error. Workaround: use either the *installutil registeroracleoptions* command or use an Oracle 7 client machine.
12405	Oracle 8 client version setting doesn't work with previous CQ releases. If the connect option, client_ver (set either to 8.0 or 8.1), is set for any of the databases, CQ2000 and earlier releases will not be able to run. Workaround: set the registry: [HKEY_CURRENT_USER\Software\Rational Software\ClearQuest\2000.02.10\Core] "SupportOracle8Client"="DWORD=1" Please note that this doesn't address the problem where the server_ver connect option is set (to 8.0 or 8.1). Also, this registry setting is only enforced in CQ 2000 Suites (not patched) releases and up. For further details and examples, see section 1.6.
12445	Netscape and Acrobat links are broken in the CQ Unix installation. The symbolic links for Netscape and Acrobat created in the [Rational_dir] by the rs_install process point to non-existent files in the releases directory. Those products are actually installed in the base/cots directory. Note that ClearQuest explicitly looks in the /base/cots/netscape.4.7 for a Netscape executable, so these links do not affect whether or not the help system functions. For further details and examples, see section 1.6.
12470	Should save Oracle Connect options in profile file. The Oracle database connection options, client_ver, server_ver, host, and SID are not saved in the profile file. There isn't a workaround at this time.

2.2 CQ Client

Defect ID	Description
5924	Multi-line fields losing last line via OLE. In multi-line text fields, like Description, sometimes the last line of text gets dropped off of field values before it's stored in the database.
6421	ClearQuest crashes when changing styles for an empty report. If you run a chart that does not return any data, then open the property box, and select either the "Display Type" or "Style" tab, CQ will crash.
7344	Run report, click Export icon gives GPF. This appears on Windows 95 with no service packs. After starting CQ, run a report, then click on the Export button from the toolbar and an error dialog will appear. The error does not occur on other platforms.
7421	Crash occurs while changing Form fonts in CQ client. An access violation error message will appear. The workaround is to use the default Windows font in CQ client forms.
7780	Query on Groups causes crash when no default is given for filter item. The access violation will follow when you click Run. It appears that a lack of a default value causes the violation here. A suitable workaround is to provide a value for the query to run with.
10899	Database timeout ignored on Windows 95/98. There was a problem with the database timeouts on the Windows 95 and 98 platforms, so database timeouts on these platforms have been disabled in the 2000 Patch 1 Final release.
11895	CR8 can't author reports with Attachments and History fields. Crystal Reports 8 users: The CQ Client user cannot create a new report format if either the Attachments or History fields have been selected to be displayed as a part of the report. After such a query has been created in the Client, the Author Reports button does not function.
12965	ClearQuest 2000 Patch 1 support for CR6 limited. Crystal Reports 6 users: The CQ 2000 Patch 1 Client user cannot create a new report format with Crystal Reports 6. However, formats generated in CQ 2000 installations with Crystal Reports 6 can be utilized to create new reports. Also recommended is an upgrade to Crystal Reports 8.
13298	CQ 2000 Patch 1 integrations broken. The following integrations with ClearQuest 2000 Patch 1 were broken: VSS; Rational Administrator; Robot; Team Test; CC; UCM; and, RequisitePro. Download the file found in the "K2.1.1" folder in the ClearQuestPatches ftp site. In that K2.1.1 ftp folder, find and read the accompanying K2.1.1 Readme file on how to utilize the downloaded file.

2.3 CQ Designer

Defect ID	Description
4517	Option buttons will exhibit unexpected runtime behavior if the option button value attribute is not set during form authoring.
5745	After importing a form you lose the form data if you don't modify the form. If you just import a form into the Designer, close the form window, and then re-open it, the form will be empty. The work- around is to modify the form after importing it.
7436	Perl Scripting support should allow global variables. There are variables local to a routine and variables available to an entire Perl script. However, the Perl editor only allows variables to be declared within a routine and not outside. Use session vars name-value pairs as a workaround.
10887	Crash when exiting ClearQuest on Windows 95/98 after adding Perl hook. On the windows 95 and 98 platforms, when you've created a new record type in Designer without creating a default form, and you've launched the Client, followed by the selection of the "New Defect" command, you may see an error dialog after exiting the client.
10910	Problem using Perl on the CQ Web server. If you are using the ClearQuest Web client, you must use VBScript to write your hooks. ClearQuest Web 2000 Patch 1 doesn't support the use of Perl.
10852, 11934	Error message appears when a UCM-enabled schema is applied without a UCM install. The error message happens only when a UCM-enabled schema is used, but UCM has not been installed. The message appears in the terminal window where the ClearQuest was started, each time a form is displayed that needs to show the UCM information. Due to this error, the area in the form is simply blank. However, the error has no other effect and can be ignored.
11994	Client GUI controls have max character value of 50; if exceeded app crash may occur. There is a real limit of 50 for various GUI items, such as tab names and labels, but the Designer does not enforce this limit. If the limit is exceeded, the Windows client may crash.
12240	Hooks dependent upon "::new" API may experience a run-time error. A "bus error" or Client application crash may appear when Perl hooks fire which are looking for "::new" PAI methods, CQEmailRules::new and CQWorkSpace::new. The workaround is to replace "::new" with "::Build".

2.4 CQ Web

Defect ID	Description
NA	User edits are not allowed during DUPLICATE and UN- DUPLICATE type actions. There is no workaround for this.
5919	Controls for the second tab using the same name of a prior tab do not appear on the form. Using Internet Explorer version 4.72.3110.8 as the CQ Web browser and, if a form has two tabs with the same name, the 2nd tab with the same name doesn't show the field controls - just the title bar. An error dialog will appear saying, "Error getting form items". For multi-tab display: In addition, since the name is no longer unique, all subsequent "tab link rows" have the 2nd same name tab selectable, and when you click on it, it brings you to the first tab with that name. Netscape Navigator v4.05 displays similar symptoms, except that when you go to Single Tab Display in view mode, when you click on the link to go to the 2nd same name tab, you'll get a blank screen. Here, the workaround is to log off and log back on, and you'll see the first tab.
8244	Resizing and reloading after setting a presentation while Web Setting dialog is open crashes CQ Web. This problem appears when using CQWeb using a Netscape browser. If you load a presentation set or use the Apply button in the Web Settings dialog in Netscape and then resize the window, Netscape suggests that you use the reload button to refresh the page. This leads to a state that will cause you to restart Netscape. The work- around is to click the web-settings menu item to refresh rather than the reload button. IE does not have this problem.
9137	Identifying the anonymous IIS user when "Run in Separate Memory Space" is used Chapter 6 of Installing Rational ClearQuest describes setting up ClearQuest/Web. One detail it does not mention is that the identity of the anonymous NT userid which effectively "runs" the ClearQuest/Web application varies depending on whether the "Run in Separate Memory Space" option is chosen on the IIS configuration dialogs. For details, see Rational Technical Support Technotes 8597 (setting up/troubleshooting ClearQuest/Web) and 7975 (setting up email notification).
10819	On IIS5, no dbwin32 log when the anonymous user is not a local admin. When using IIS5 (a component of Windows/2000), if you need to run the debugging utility 'dbwin32' you must make the anonymous IIS user a member of the local machine's "Administrators" group. If you do not, no output will be logged to the dbwin32 window due to tighter security restrictions in Windows/2000.
10982	Using Back button will crash the browser. Using Netscape Communicator 4.7 on a UNIX platform, using the Back button while viewing a defect record can sometimes cause the browser to hang or crash.
12444	Netscape 4.7 or later required for CQ Unix. The CQ The CQ/Unix help system requires Netscape version 4.7 or later.Unix help system requires Netscape version 4.7 or later.

2.5 CQ Import and Export

Defect ID	Description
5988	Two versions of cqimport running on the same machine causes one to crash. While running two cqimport processes on just one machine, the first process may crash after the second cqimport process is started.
10912	Using CQEXPORT on a schema with no default record type gets runtime error '91' Workaround: Define a default record type in your schema.

2.6 User Documentation

Defect ID	Description
8695	Unified Change Management (UCM) not documented in the Introducing Rational ClearQuest guide. The information on available schemas in the Introducing Rational ClearQuest guide is incomplete; it does not mention the UnifiedChangeManagement schema. For information on that schema and using UCM with ClearQuest see, "Appendix A, ClearQuest schemas and packages," and "Appendix B, Enabling ClearQuest for Unified Change Management," in the Administering Rational ClearQuest guide.
10961	Packages replace the add-ins used in previous versions of ClearQuest. If you are upgrading from a previous version of ClearQuest and your schemas use add-ins, install the upgrade version of the package(s). Upgrade packages contain the word "upgrade" in their version string. To install an upgrade version of a package, your schema must contain metadata for the upgrade package to modify. For example, installing a package that modifies the Email_Rule record type will succeed only with a schema that already includes the Email_Rule record type. See section 1.2 of this readme file for additional information.
12487	ClearQuest 2000 Patch 1 Installation guide needs further details on setting up Oracle 8i Context/interMedia text server. (Errata to Chapter 2, the two sections for enhancing search capabilities for Oracle 7.X and Oracle 8.0.x, as well as Oracle 8.1.x.) In addition to Step 1 shown in the Install Guide, perform the Post-Installation Setup procedures seen in the guide, Oracle InterMedia Text 8.1.5 Technical Overview. You can find this at: http://www.oracle.com/support/ Step 2 as shown in the Install Guide is incorrect. You should run the following command: ctxsrv -user ctxsys/ctxsys -personality M -logfile $ORACLE_HOME/ctx/log/ctxsrv.log where ctxsys/ctxsys is the default username/password. You may have to create that ctx/log directory. You'll also want to run this in the background. Oracle doesn't provide anything to start this automatically, say at boot time, so you'll either have to run these processes manually or develop a shell script for that purpose. Step 3 as shown in the Install Guide, for the section entitled, "For Oracle 7.X and Oracle 8.0.X", is incorrect. You should, instead, use the following steps: The Oracle user must have these priviledges: CTXAPP role, select on ctxsys.ctx_servers, execute on ctxsys.ctx_ddl The SQL script, setup_cq_ora_user.sql, can be used to grant the necessary priviledges. setup_cq_ora_user.sql can be found in the ClearQuest installation directory, \\Rational Software\ClearQuest\. This script must be run with Oracle's SQL interface, sqlplus, program as the Oracle ctxsys user, via: sqlplus ctxsys/ctxsys@<tnsname> @setup_cq_ora_user.sql <cq_user> where, <cq_user> is the Oracle user name assigned to CQ dbo. Note: Oracle's SQL interface can be "plus33" or "plus80" and is also accessible via the Windows start menu. Step 3 as shown in the Install Guide, for the section entitled, "For Oracle 8.1.X", is incorrect. You should, instead, use the following steps: The Oracle user must have these priviledges: CTXAPP role, select on ctxsys.ctx_servers, execute on ctxsys.ctx_ddl The SQL script, setup_cq_ora_user.sql, can be used to grant the necessary priviledges. setup_cq_ora_user.sql can be found in the ClearQuest installation directory, \\Rational Software\ClearQuest\. This script must be run with Oracle's SQL interface, sqlplus, program as the Oracle ctxsys user, via: sqlplus ctxsys/ctxsys@<tnsname> @setup_cq_ora_user.sql <cq_user> where, <cq_user> is the Oracle user name assigned to CQ dbo. Note: Oracle's SQL interface can be "plus33" or "plus80" and is also accessible via the Windows start menu.

2.7 UCM Integration

Defect ID	Description
8669	With UCM integration, file check in only works with Access database. If you are using the UCM/ClearQuest integration with a ClearQuest database other than Microsoft Access, you will see the following problem: In ClearQuest: Go to the UnifiedChangeManagement tab of a form. Right click on a version in the Change Set and from the context menu, choose Check In... Clicking OK on the Check In dialog box produces this error: "CoInitialize has been called. Unable to logon to ClearQuest database". Likewise, in ClearCase, opening the Activity Properties dialog opens a ClearQuest form and the same problem holds true. The workaround is to do the check in from outside of the integration. Operating the Check In dialog box from other places like the Windows NT Explorer, or the Find Checkouts dialog box works correctly.
8670	Unclear Error message after trying to select Activity without UCM info. After running a CQ query on activity items (like defects) defined via the UCM integration, and then selecting an activity which lacks project info from check-in/-out, a misleading error dialog may appear like, "IDispath error ... ACException occurred", after selecting a member of the query. When this error dialog appears, close the dialog then fill out the UCM Project field and a more useful info box will appear.
8678	RunTime Error after trying to delete Activity with non-empty change set. If, in the UCM tab, the Change Set field is not empty and the user tries to delete an activity, a run-time error will appear. Close this error dialog, then a more useful CQ dialog box will appear.
NA	In order to use Rational ClearQuest 2000 Patch 1 with the UCM/ClearQuest Integration in ClearCase 4.0, you must do the following: All ClearCase clients which are using the UCM/ClearQuest Integration must install the ClearCase "clearcase_p4.0.NT-7" patch or equivalent. All ClearQuest databases which are accessed by the UCM/ClearQuest Integration must be associated with a ClearQuest schema version that has version 2.0 of the "UCMPolicyScripts" and "UnifiedChangeManagement" packages installed. If you created your UCM-enabled schema with ClearQuest 2.0 or used the pre-defined "UnifiedChangeManagement" or "Enterprise" schemas, your schema will only have version 1.0 of the "UCMPolicyScripts" and "UnifiedChangeManagement" packages installed. This means you must: Use the Package Wizard in the ClearQuest Designer to upgrade the "UCMPolicyScripts" and "UnifiedChangeManagement" packages in your schema to version 2.0. Upgrade your ClearQuest database to use the new schema version that has the new package versions installed. NOTE: If you have customized the global scripts UCM_ChkBeforeDeliver, UCM_ChkBeforeWorkOn, or UCM_CQActAfterDeliver in your schema and wish to avoid losing your customizations when upgrading the "UCMPolicyScripts" package to version 2.0, you must do the following before upgrading the package: Open the schema for viewing and save the text of the modified global script(s) in a temporary text file. Use the Package Wizard to upgrade the schema with version 2.0 of the "UCMPolicyScripts" and "UnifiedChangeManagement" packages. Edit the schema and replace the upgraded text of the global script(s) with your customized text that you saved in the temporary file.

3.0 Troubleshooting Web Services

3.1 Basic Troubleshooting Tips

The IIS Server (inetinfo.exe) may crash when you stop the service from the Microsoft Internet Service Manager application. If this happens, you must stop and restart the Internet Service Manager before restarting the WWW service. If FTP or Gopher services are provided by this machine, you must restart them too.
If you are using Microsoft Internet Explorer version 4.72.2106.8 or 4.71.1712.6, you will need to upgrade to a newer version, such as 4.72.3110.8. Otherwise, you will run into a JavaScript error when selecting Help, About or attempting to view an attachment.
Users of Netscape Communicator 4.0x browsers should have the following options set:

In the browser, selectEdit>Preferences.

Select"Advanced->Cache" Category.

Set "Document in cache is compared to Document on network" to "everytime" and press OK.

Users of Netscape Navigator 3.x browsers should have the following options set:

In the browser, selectOptions>Preferences.

Select "Connections" tab and set "Number of Connections" to 1 and press OK.

3.2 Advanced Troubleshooting Tips

There is detailed documentation on the configuration of IIS 4.0 and IIS 5.0 in the Installing Rational ClearQuest guide that may help you troubleshoot installing Web services.

If you have not granted proper permissions on the CQ registry keys you may get the following error while attempting to access ClearQuest Web:

        Failed condition: disposition == (0x00000001L) 
        Location: ClearQuest Core:adregistry.cpp:569occurred 
        in BBOLEI~1

See the printed document, Installing Rational ClearQuest, to set the proper permissions.

If you haven't granted proper permissions in the cache directory, you will not be able to logon and you will see the following error:

        Logon Error 80020009
        Could not create directory
        occurred in ClearQuest.FileCache.1

See the printed document, Installing Rational ClearQuest, to set the proper permissions.

If you see the error:

Logon Error 
Unable to logon to the MS_ACCESS database
"\\\\.mdb".
The vendor error message was: 
SQLConnect: RETCODE=-1, State=S1000, Native Error=-1032
[Microsoft][ODBC Microsoft Access 97 Driver]The Microsoft Jet database engine cannot open the
file '(unknown)'. It is already opened exclusively by another user, or you need permission to
view its data.
This indicates a permissions problem regarding an Access Database. Try the following steps:

If this database is local to your machine, make sure that the Anonymous User has "Access this machine from network" rights, and Full Control Permissions on the .mdb file.

If the above steps don't fix the problem, consult the Microsoft KnowledgeBase Article Q166029, Cannot Open File Unknown Using Access. To locate the article, go to the Microsoft web site at www.Microsoft.com, click the Search button at the top of the page, and enter the article number. The article describes the problems of accessing an Microsoft Access database via a network share with IIS. There is also a bug in the 3.51 version of the Access Jet ODBC driver that causes this problem. There is a Knowledge Base article (Q180815) that addresses this issue.

If you run your Web server and SQL Server database on different machines, you may encounter an error if the user ID the Web server uses to establish a network connection is not recognized by the computer hosting the SQL Server database. Consult the Microsoft KnowledgeBase Article Q152828, IIS Queries to SQL Server Generate Error 1326. To locate the article, go to the Microsoft web site at www.Microsoft.com, click the Search button at the top of the page, and enter the article number. You should now be able to access the ClearQuest database using the Anonymous Internet connection. This issue is described in more detail in Rational Tech Support TechNote 8184, "How do I access a SQL Server database in another domain?"
Occasionally you may have your script time out. If this happens, you'll see a message that looks like

                            error 'ASP 0113'
                            Script timed out

The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.Script.Timeout or by changing the value for ScriptTimeout in the Registry. error '800a041d'
By default Active Server Pages Scripts (which are the providers of the CQ Web pages) are given 90 seconds to complete. If they do not complete in 90 seconds the IIS Server terminates them and presents the user with an error message similar to the above. You may increase the value from the default 90 seconds by editing the following registry key value with regedit.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
      W3SVC\ASP\Parameters\ScriptTimeout

If you decide to change the database that ClearQuest is serving on your web machine, do the following first before running the ClearQuest Maintenance Tool (cqdbsetup.exe) to update the web server machine to point to the new schema repository. You may have to remove the following registry keys and their subordinate values, if they exist.

  HKEY_USERS\.DEFAULT\Software\Rational
       Software\ClearQuest\2000.02.10\Core
  HKEY_USERS\.DEFAULT\Software\Rational
       Software\ClearQuest\2000.02.10\Install

If you have used cqdbsetup to change the schema repository characteristics, it might change the values under these keys in HKEY_CURRENT_USER, and HKEY_LOCAL_MACHINE but these settings will be overridden because the web server uses keys from HKEY_USERS\.DEFAULT instead of HKEY_CURRENT_USER. To make it see the right values, delete the values as described above; then, the ones from HKEY_LOCAL_MACHINE will be used.

4.0 The Rational Web Site

Please visit the Rational Web site for latest Release Notes, patches and information:

http://www.rational.com/

5.0 Subscribing to the ClearQuest User Group.

The ClearQuest User Group is an e-mail forum where you can share your experiences, pose questions, or obtain useful information from other ClearQuest users. To subscribe to the group, visit the Rational web site at:

http://www.rational.com/support/usergroups/

Your e-mail address will not be given out to anyone.

6.0 Accessing the Sample Hooks Database

The ClearQuest Sample Hooks Repository provides a place for users to trade hook scripts with one another. The Repository is located at:

http://clearquest.rational.com/cqhooks

To gain access enter:

username: user
password: password

You can browse the existing hook scripts for ideas, or add a script you would like to share with others.

7.0 Contacting Technical Support

If you have any problems with the software or documentation, please contact Rational Technical Support via telephone or electronic mail as described below. For information regarding support hours, languages spoken, and other Rational Software information, visit the Rational web site, http://www.rational.com/support.

Rational's web site contains an extensive library of Technical Notes. To access the Technical Notes, go to http://solutions.rational.com/solutions/.

Rational maintains Support Centers in different geographic regions. To contact the center nearest you, consult the chart below. If you are contacting Technical Support by phone, dial the phone number shown below and follow the voice prompts to select ClearQuest Technical Support.

Contacts and Information

For questions regarding current versions of products, please contact us by e mail or phone
Region	E mail contacts	Telephone Contacts
US and Canada	support@rational.com	1-800-728-1212 or 408-863-4000
Europe	support@europe.rational.com	+31 (0)20 4546 400
Asia/Pacific	support@apac.rational.com	+61-2-9419-0125

©2000 Rational Software Corporation and its subsidiaries. All rights reserved. Rational Software Corporation and its subsidiaries ("Rational") claim copyright in this Program and documentation as an unpublished work, versions of which were first licensed on the date indicated in the foregoing notice. Claim of copyright does not imply waiver of Rational's other rights. See Notice of Proprietary Rights.

NOTICE OF PROPRIETARY RIGHTS

This computer program and documentation are confidential trade secrets and the property of Rational Software Corporation and its subsidiaries. Use, examination, reproduction, copying, disassembly, decompilation, transfer and/or disclosure to others, in whole or in part, are strictly prohibited except with the express prior written consent of Rational Software Corporation and its subsidiaries.

Rational ClearQuest 2000 Patch 1 Release Notes

Contents

1.0 Supported Platforms and System Requirements

1.1 List of Supported Platforms and Operating Systems

1.2 Upgrading from Previous ClearQuest Releases

1.3 What's New in ClearQuest 2000 Patch 1

1.4 What's New in ClearQuest UNIX

1.5 Defects Fixed in ClearQuest 2000 Patch 1

1.6 Oracle Database Connection Options

2.0 Known Defects

2.1 Installation

2.2 CQ Client

2.3 CQ Designer

2.4 CQ Web

2.5 CQ Import and Export

2.6 User Documentation

2.7 UCM Integration

3.0 Troubleshooting Web Services

3.1 Basic Troubleshooting Tips

3.2 Advanced Troubleshooting Tips

4.0 The Rational Web Site

5.0 Subscribing to the ClearQuest User Group.

6.0 Accessing the Sample Hooks Database

7.0 Contacting Technical Support

Contacts and Information