In the ClearQuest Web interface, the format of dates and times is specified by the Web server's time zone instead of the browser's time zone.

You can change the regional options on the Web server to standardize both the time and date stamps by setting the time format to a 24-hour format.

When you create a query that lists users on a system and then select a record from the result set, the form displayed does not include information about the user privileges for that user or group. To display user profile information, use the User Administration Tool.

Queries do not return data correctly when double-byte characters are included when using ClearQuest with a SQL Anywhere Database.

If a double-byte character, including 5B, such as the character codes like Katakana-Hiragana Prolomged Sound Mark (0x815B) or Catatonia Be (0x835b), is specified in a filter of a query, ClearQuest does not return any data even if there is data matching the query. 5B represents '[' , a left square bracket for single-byte character.

If you add an ASP file as an attachment to a record and, using the ClearQuest Web client running on Internet Explorer, try to save the attachment to your local disk, the following error message appears:

Internet Explorer cannot download default.asp from <machine name>. Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.

You can save ASP file attachments by using the ClearQuest Web client running on Netscape Navigator.

When reports are generated on the Web, the column headings are not oriented vertically, as they are in the native client. This causes reports to be wider than they are on the client, and they may run off the right side of the screen.

The architecture to produce Web-based reports involves having Crystal Reports generate a Web page. ClearQuest displays the page in a separate browser window, which renders the HTML as generated by Crystal Reports.

The required disk space displayed by the Install Wizard in Custom Setup or the Space box is not correct. For disk space requirements, see the Server and Desktop System and Server Requirements in the Rational Suite installation guides.

The NOT operator does not work correctly when a reference list field is used as a filter. For example, if you use ClearQuest Web to do the following, the submitted defect is listed in the query result set, but this is incorrect:

On UNIX, Netscape versions earlier than 6.2 often do not display dependent list boxes in the ClearQuest Web client properly. A dependent list box is a list box whose content varies depending on a previous list box selection.

If a dependent list box contains a large list that cannot be fully displayed, More often does not appear as the last value.

If you use the ClearQuest Export Tool and accept the default error log file name, the tool creates the file, (c:\temp\cqexport_error.log). If you subsequently erase this file, or use the ClearQuest Export Tool again and enter an alternative name for the file, the ClearQuest Export Tool may display the message An unexpected error has occurred even though the export completed successfully.

It is never necessary to set the value of the server version. However, you must set the client version by using installutil because the client version information is saved in the database. If you are connecting to the database from a client whose version does not match the information saved in the database, you must update the client version.

Using the installutil tool, set the value of server_ver to 7. Even if there is a change in the host string server_ver, the connection is created.

ClearQuest allows you to delete a database even if it is associated to an existing Rational project through Rational Administrator. If you do this, you cannot delete the project using Rational Administrator because the attached ClearQuest database no longer exists.

You must delete the Rational project before you delete the associated ClearQuest database.

The discussion of enabling a schema to work with UCM in Managing Software Projects for Rational ClearCase omits an important step: mapping states to state types.

When you apply the BaseCMActivity package to a schema, ClearQuest adds the BaseCMActivity record type. When you apply the UnitedChangeManagement (UCM) packages to the schema, ClearQuest adds the UCMUtilityActivity record type. But when you attempt to check in the schema with these changes, ClearQuest displays a series of validation errors stating that you need to map BaseCMActivity states to the AMStates Types package.

You receive this error because, in applying the UCM package to the schema, ClearQuest also applied the AMState Types package. This behavior is not described in the Administrator's Guide for Rational ClearQuest or in Managing Software Projects.

Before you can check in the schema, you must map states to state types from the AMStates Types to the BaseCMActivity record type, as follows:

For more information about mapping states and state types, see the Administrator's Guide for Rational ClearQuest.

For more information about enabling the BaseCMActivity record type, consult the Rational Support Knowledge Database.

The cqload importintegration command does not upgrade package information in the target schema. All changes are imported correctly, but the package is not in the list of the associated packages for the target schema. Therefore, the package is not correctly installed and will not work.

This behavior may cause problems, for example, when integrating a Rational RequisitePro project with ClearQuest by using Rational Administrator. In this case, an error states that the package is missing.

One workaround is to load the entire schema, unless you have a user database associated with the schema at the target site. Do not export the entire schema or apply the package directly to the new schema before applying the import integration.

If you do this, the package is applied correctly, but the import integration fails because it tries to re-create the scripts and fields (which already exist).

The following steps provide a method for an export/import integration where packages are involved:

The following example uses the Common schema (which has no packages applied) for versions 2 to 4 but does include changes to it (such as adding fields, actions, and stateless records). Then, in version 5, the Repository package is added and in version 6, the RequisitePro package is added. In version 7, a new stateless record is added. The following procedure transfers all of these changes to a new schema:

By viewing the Schema Summary dialog box and looking at the Comments field of the checked in versions (for example, Enabled schema for 3.0 version of Repository package), you can determine which versions contained the addition of a package. The default comment on a schema check in, when you apply a package shows that the package was applied. You can also obtain this information by looking at different schema revisions and checking whether a package appears in one version but not the other.

CQString is the string type used by the ClearQuest Perl API. This type is used for the Perl API, so any Perl hooks or external Perl scripts use it to pass string data to and from the ClearQuest core.

CQString uses single-byte characters. To make it use wide characters, the core must be compiled with _UNICODE, but ClearQuest is compiled with _MBCS.

Using the ClearQuest Web client running on Netscape 7.0, when you submit or modify an E-mail Rule record and click OK, a confirmation dialog box opens. Submitting records for other record types does not open a confirmation dialog box.

To disable the confirmation dialog box, log off from the Netscape Password Manager. Note that this workaround applies only to the current logon session. Each time you log on to ClearQuest Web, you must log off from the Password Manager to disable the confirmation dialog box.

ClearQuest Web uses Java applets to display lists (such as Keywords and Symptoms in the SAMPL database) and to start the Advanced Query Editor.

This release, the applet window does not display any characters when you press ALT and an ASCII character on the Num Lock keypad.

The ClearQuest Web client Help running on Netscape 7 has the following display problems:

Creating a PERL and VBScript record hook, each with the same name, causes the following problems when a field has one of the hooks assigned to it on a form:

The workaround is to restart ClearQuest Designer and delete the script. When the scripts are parsed, the New1 script is added to the tree view and can then be deleted.

When you edit a script using ClearQuest Designer, the changes you make are saved even if you choose No or Cancel, when prompted to save the work.

Using the ClearQuest Web client running on Netscape 7 on Japanese Windows 2000 and Windows XP machines, when you create a shortcut by clicking Operations > Create a Shortcut, the error message Cannot find the record_type:folder_name appears. Nonetheless, the shortcut is saved in the Shortcuts folder in your Workspace. However, when you attempt to run it, the same error message appears again and the shortcut does not work.

When you add the name of a new state in the To column on the left side of the State Transition Matrix, that name should also appear in the From row at the top of the matrix. This allows you to enter the actions that lead from the new state to the existing states and from the existing states to the new state.

However, if you enter the name of a new state in the To column, and the new name does not appear in the From row, follow these steps in ClearQuest Designer:

When you use the ClearQuest Designer to create a new user database, there is no validation that the ClearQuest data code page of the new user database is compatible with the vendor database character set. To ensure data integrity in your ClearQuest environment all databases must be validated when they are created.

Workaround: After you create a new user database, re-run the installutil setdbcodepagetoplatformcodepage command on the schema repository to perform the code page validation on the new user database. You must run the command on a computer that uses the same system code page as the ClearQuest data code page.

For more information, see the Administrator's Guide for Rational ClearQuest.

When you use the ClearQuest Maintenance Tool to move, update, or upgrade a schema repository, there is no validation that the character set of the target database is compatible with the ClearQuest data code page of the source schema repository. To ensure data integrity in your ClearQuest environment all target databases must be validated when moving, updating, or upgrading a schema repository.

Workaround: Before you move or upgrade a schema repository, or use a vendor tool to copy a schema repository in preparation for an update, validate the code page compatibility of a target database.

Note: In the case of a schema repository update, you must validate the code page compatibility before you copy the schema repository using a third party tool.

For more information, see the Administrator's Guide for Rational ClearQuest.

When you use the ClearQuest Maintenance Tool to move a user database or update user database properties, there is no validation that the character set of the target database is compatible with the ClearQuest data code page of the schema repository. To ensure data integrity in your ClearQuest environment all target databases must be validated when moving a user database or updating user database properties.

Workaround: Before you move a user database, or copy the user database in preparation for updating its properties, validate the code page compatibility of a target database.

Note: In the case of a user database update, you must validate the code page compatibility before you copy the user database using a third party tool.

For more information, see the Administrator's Guide for Rational ClearQuest.

When the screen resolution is set to 800x600 or lower, you cannot access the Print button on the Print Record Reports window.

You also cannot access the Print Preview or Cancel buttons at the bottom of the window, nor can you resize the window to allow access to the buttons.

When an action is performed through a hook and an e-mail rule has been created to send a message when this action is executed, no e-mail is sent.

The workaround is to create use a session named-value to specify whether a notification hook should be triggered inside an action started by another hook. The variable name is CQHookExecute, and its value (set to 1) indicates the hook is fired in any circumstance.

Create a new base action in the affected record type, and in its ACTION_INITIALIZATION hook add the following code:

If an English ClearQuest client running on a Japanese operating system enters Japanese data into a database with the ClearQuest data code page set to 932, an English ClearQuest client running on an English operating system with Japanese fonts and locales set to 932 (installutil lscodepage shows the client code page setting as 932) that opens that record will correctly display the Japanese data in the details section but not in the Results Set grid.

This problem occurs when running English ClearQuest clients on an English Windows operating system whose fonts and locale have been set to Japanese.

The workaround is to right-click the record form, select the correct font, and run the query again. To enable the ClearQuest grid to display non-ASCII characters correctly:

If you submit a record through e-mail and the e-mail message contains the string "Content-Type: text/html" or "Content-Type: text/plain" anywhere in the Description field, the Rational E-Mail Reader rejects it and does not submit it to the ClearQuest database.

The workaround is to insert an additional space (or carriage return) after the colon.

To connect English ClearQuest clients to a system with more than one database that supports Japanese character sets, you must create all databases after the first one, as follows:

For more information about how to set the ClearQuest data code page for the schema repository, see the Adminstrator's Guide for Rational ClearQuest.

You can create only one schema repository on a system where you give it a name in Japanese characters during the initial creation process. For the second and subsequent databases, you must follow the procedure, giving an initial name in ASCII characters. If you do not, English ClearQuest clients get an error message when they try to connect to any of the Japanese character set databases on that system.

If, using ClearQuest Web, you change your user profile by entering excessive data (that is, more than 25 double-byte characters in the Name, Phone, or E-Mail text boxes), the changes are lost but no error appears.

If you use the native ClearQuest for Windows client to do this, when you change the contents of one of these user profile text boxes using more than 25 double-byte characters, an error message states that the text box limitation is 50 bytes.

Users with administrative privileges may get an error (HTTP 500.100 - Internal Server Error - ASP), when adding a new customer to a change request form by using any returned query result set.

The list view field cannot add a value from the query result, if the query returns a long list of records. Queries that return large numbers of rows cause the IIS Web Server to time out in 90 seconds, by default.

If you use the SMTP protocol for the Rational E-Mail Reader, text fields, such as the Headline field, may be truncated to 61 characters in some e-mail applications.

For example, if you submit or modify a change request and enter 120 characters into the Headline field (Short String 125) or into another 125–character text field that you created, 61 characters are entered and the rest are truncated.

Any text that is longer than the setting in your e-mail client for the number of characters to wrap is dumped into your default field (such as the Description field). For international users, for multibyte languages, the value of this setting is reduced by approximately half of the value set in the e-mail client.

One workaround is to shorten your Headline field or increase the number of characters allowed per line in your e-mail client. To modify the setting in Microsoft Outlook, click Tools > Options, click the Mail Format tab, and click the internet format button. There is an option in this dialog box to set this value up to 132 characters.

Truncation does not occur when you use the MAPI protocol to send e-mail or with Netscape and other e-mail clients that wrap lines with soft returns (linefeed characters) rather than hard returns (carriage return + linefeed characters).

If you run the Advanced Query Editor on Internet Explorer 5.5 or 6.0 with the Java Runtime Environment (JRE) 1.4.x, the ClearQuest Web client can suspend its operation.

During these instances, when you try to exit the Advanced Query Editor (AQE) by clicking File > Exit, the AQE minimizes but does not exit and the ClearQuest Web client stops.

If you run a query that includes a filter on a REFERENCE_LIST field that points to another record type, a stale list (that is, a list that does not include recently submitted entries) of values may be returned when you run a dynamic query.

After you run the query, whose results are displayed in a child window, if you submit some new records to the referred-to record type, go back to the query results, and click Run Query, the dynamic filter dialog box reopens, but the choice list includes the original values, not the new values.

The workaround is to close the query results window and rerun the query by double-clicking it in the Workspace. This retrieves the list of customers with the current values.

Using the ClearQuest Web client running on Japanese Windows XP with Netscape, you cannot display a customer record where the customer name consists of Japanese characters.

This is not an issue for customer names consisting of only ASCII characters.

When you upgrade from a previous release of ClearQuest, certain items on the ClearQuest form may not be translated automatically. Items include the Main tab, and any other tabs that have been manually changed. To correct this problem, manually translate those items that appear in English.

The association between ClearQuest and UCM does not work correctly if you have more than one connection to a schema repository. The UCM association works correctly if additional database connections are created after the first ClearQuest database is successfully associated, with only one connection.

To correct the problem, remove the extra database connections, set up the project, and then restore the connections.

If the ClearQuest install directory is in 5c Japanese and you use ClearQuest Designer to modify a schema, you cannot check in a new user database. You receive an error when you validate your changes.

You may see an error message about ClearQuest data code pages if you use the ClearQuest integration with ClearCase or ClearCase LT. The error message appears when you enter data into ClearCase or ClearCase LT using characters that are incompatible with the set of characters that a ClearQuest database accepts. If you see such error messages, consult your ClearQuest administrator or systems administrator to resolve the problem.

When you use the cqload exportintegration command to export specific versions of a schema in a form that can be used to modify an existing schema, old hooks are not always deleted.

The cqload exportintegration command does not cause ClearQuest Designer to delete old hook code.

There will be only one Commit hook in your source database, but there will be two Commit hooks in the target of the import integration. With this redundancy, if you have a session variable in the twin hooks, you may see an error referring to a change request, CQdatabasename00000001.

If you are upgrading a user database to which the UCM package has been applied to ClearQuest version 2003.06.00, under some circumstances the user database upgrade is only partially completed. Some queries from the UCM package are not reinstalled, and you see the following error message: User database was not completely successful.

To avoid this problem, raise the metaschema level of the schema repository associated with the user database to the latest level, which is 22, as follows:

You can then upgrade the user database in the normal way by using ClearQuest Designer and reinstall the missing queries from the UCM package.

First, increase the metaschema version number to 22 by upgrading the schema repository, as described above.

Second, force the reinstallation of the package queries:

When you upgrade the user database this way, ClearQuest reinstalls the missing queries, and the user database upgrade is complete.

For more information about upgrading from previous releases of ClearQuest, see the Upgrade Guide for Rational Suite and the Administrator's Guide for Rational ClearQuest.

When you close the Rational Purify or Rational Quantify application, you may get the following error message:

CQINTSVR10.exe Application Error The instruction at "0x77fcb9b3" referenced memory at "0x0101b793". The memory could not be "written" Click on OK to terminate the program.

To correct this error:

When you install ClearQuest, if you choose the ClearQuest Evaluation Databases option under custom install, the install does not create the evaluation databases. For the procedure to install ClearQuest for evaluation, see the Installation Guide for Rational Server Products.

The install program sometimes fails with the error 1607: Unable to install InstallShield Scripting Runtime. Consult http://www.installshield.com for information about resolving this problem.

Rational recommends that you avoid configuring any one host to run the Rational Shipping Server for both ClearCase and ClearQuest because uninstalling either product from such a host removes the Shipping Server that is used by both products and renders the remaining product inoperable. If you must install both ClearCase MultiSite and ClearQuest with the Rational Shipping Server on the same host, ensure that you do the following:

Note: Administrators must verify that site configuration files for typical host systems do not specify installation of the Rational Shipping Server. Any attempt to install ClearCase on a host where ClearQuest and the Rational Shipping Server is already installed will fail.

Sometimes, after ClearQuest Web is installed, you cannot log on because no database selection is available. Furthermore, if you click RefreshDBList on the Logon page, the error message GetRegistrySubkeys Registry Error appears.

Ask your ClearQuest administrator to run the ClearQuest Maintenance Tool to specify a database connection.

You cannot use any of the shortcut keys for the tabs of a record. None of the tabs, including Main, Notes, Resolution, Attachments, History and Customer, are accessible by the shortcut keys.

Also, the Run Query and New Defect buttons are not accessible, using shortcut keys.

The workaround is to use the TAB key to navigate to the tab, and then use the left and right arrow keys to navigate to each of the tabs.

When you open the ClearQuest API Reference (for example, using Start > Programs > Rational Software > Rational ClearQuest > ClearQuest API Reference), some browsers may indicate an Unterminated string constant error.

You can ignore this error. Click the error indicator to open an Internet Explorer dialog box, and click OK. The API documentation opens normally.

There is also a PDF format available at /doc/books/cq_api.pdf in the ClearQuest home directory.

If you are modifying the installation of any product available from the Rational Setup Wizard, a fatal error occurs when you click the Space button in the Custom Setup page. To prevent the Setup Wizard from failing, do not click the Space button.

If you are using a ClearQuest database based on DB2 8.1 and click File > Exit when no query window is open, the ClearQuest client fails.

To avoid this problem, click File > Close Database > Exit.

If you add an attachment when modifying a record while the record is editable, and then attempt to save that attachment under a new name (click Save As), you get the following error:

The string "" cannot be interpreted as an integer. Cannot convert an empty string to an integer value.

Save an attachment while the record is not in the editable state.

If you run a query with the UNIX client and delete it using the command line tool, cqtool, you find that the query is still valid. The deleted query remains in the machine's memory and is not fully deleted until you log off from ClearQuest.

FLEXlm 7.0f stores the .flexlmrc file in the user's home directory and if the license server is moved, the settings in the old .flexlmrc file are used instead of the LM_LICENSE_FILE environment variable.

If using a SQL Server database, ClearQuest displays an error when you create a record with an attached image or clip art.

When you are working in text mode in the client on UNIX and select any action, other than Modify, from the Actions field, ClearQuest changes the display to the forms mode. However, it does not make the form editable, so you cannot edit or update any of the fields in the record.

When you are in forms mode but the form is not editable, revert the action, access the forms mode, and perform the action again.

Using a UNIX client, if you connect to a schema and right-click a field that has a Perl context hook, the context hook is not listed.

A ClearQuest process, called cqintsvr, continues to run in the background even after you remove a previous version of ClearQuest and install a new version. After you install the new version, shut the cqintsvr process down before running the new version of ClearQuest.

When you try to add an attachment from a UNIX client that is connected to a SQL Server database, the attachment cannot be larger than 64 KB. This restriction is imposed by the OpenLink Request Broker.

If, when inserting an attachment larger than 64 KB, you try to save that attachment, you get an error that the attachment size does not match the retrieved size. The retrieved size is always 64 KB when the attachment is larger than 64 KB. Only 64 KB are saved.