ClearCase LT Web supports the following new features:

For complete information, see the Help.

This section describes integrations that are new or enhanced in this release.

This release includes the following enhancements to UCM:

For more information, see Managing Software Projects, the reference pages cited in this section, and the Help.

This section describes miscellaneous enhancements in this release.

This release introduces feature level 4. Table 2.1 shows all supported feature levels and the versions at which they were introduced.

Feature level 3 placed constraints on client/server compatibility in UCM environments. Feature level 4 introduces no additional constraint; it is equivalent to feature level 3 in terms of PVOB client/server compatibility. For information on feature level 3, see the Version 2002.05.00 Release Notes for your product. Also note that read-only streams and single-stream projects are restricted to PVOBs at feature levels 3 and higher (see the reference page for mkstream).

Raising the feature level to 4 results in the following changes in the VOB:

For instructions about raising the feature level of a VOB, see the chflevel reference page.

ClearCase::CtCmd is a Perl extension that takes cleartool–like arguments. ClearCase::CtCmd takes a string or an array as an input argument and returns a three-element Perl array, as follows: a status bit, a scalar string corresponding to stdout, and any error message corresponding to stderr. This Perl extension and its documentation are available from www.cpan.org.

Note: After upgrading to Version 2003.06.00, you must rebuild ClearCase::CtCmd to account for the addition of new libraries and symbols to ClearCase LT

Beginning with this release, Perl 5.6.1 is distributed with ClearCase LT. Perl 4 has been removed from this release. For backward compatibility, this release also includes a modified version of Perl 5.001m. To use 5.001m instead of Perl 5.6.1, set CCASE_USEPERL5 to a nonempty string (see the env_ccase reference page). To verify the version that is being invoked, type ccperl –ver.

In conformance with the Artistic License Agreement under the terms of which Perl is distributed,Table 2.2 describes the modifications that were made to Perl 5.6.1.

Likewise, in conformance with the Artistic License Agreement Table 2.3 describes the modifications that were made to Perl 5.001m.

This release is the last major release that includes 5.001m. The unmodified sources for Perl versions 5.001m and 5.61, as well as the binaries built from them, are archived at ftp.rational.com. A link to the archive can be found at www.rational.com/support/downloadcenter/index.jsp.

In the Project Properties and New Project Wizard GUIs, the ClearQuest page displays the policies that are appropriate for the UCM level of the ClearQuest user database associated with the project. If the ClearQuest user database uses the revision 5.0 UCM package (corresponding to Version 2003.06.00), the available policies are as documented in the Help and in Managing Software Projects.

If the ClearQuest user database uses an earlier UCM package, the available policies are as follows:

This section contains miscellaneous announcements about this release.

This release introduces no new commands.

Table 2.4 lists new options and arguments to commands.

No commands are obsolete at this release.

The dir argument to annotate and the –glossary option for apropos are obsolete.

Significant changes to command output are as follows:

Commands that have changed in one or more respects are as follows: annotate, apropos, chactivity, checkvob, chproject, chstream, deliver, describe, diff, diffbl, find, lsactivity, lsbl, lsstream, lstype, man, mkbl, mkdir, mkelem, mkproject, mkstream, protectvob, rebase, rmname, schedule. For details, see the corresponding reference pages.

Most Help, including reference pages, is HTML.

The following reference page has been removed from the Command Reference:

The Administrator's Guide contains new information about backing up and restoring ClearCase LT and ClearQuest data together.

The script-driven tutorial has been replaced with an HTML tutorial without scripts.

A platform-independent edition of Managing Software Projects replaces the separate UNIX and Windows editions that were published at earlier releases.

Manuals in Portable Document Format (PDF) are installed in ccase-home-dir\doc\books. In previous releases, they were installed in ccase-home-dir\bin.

Most Help files are installed in ccase-home-dir\doc\help. In previous releases, they were installed in ccase-home-dir\bin.

File system corruption can result from installing ClearCase LT on Windows 2000 to an NTFS partition that has the Windows Change Journal log enabled on it. Accordingly, the installer checks for and does not install to such partitions. We are working with Microsoft to repair the problem or provide a workaround for it.

Before installing ClearCase LT onto a computer running Windows 2000, read Rational Solution 182435434 at http://solutions.rational.com/solutions/display.jsp?solutionId=182435434. Alternatively, you can search for the text change journal in the Rational Solutions Knowledge Base at http://solutions.rational.com/solutions.

The ClearCase LT Web product requires Netscape 7. However, the rest of the Rational Suite products require Netscape 4.78, and are not guaranteed to work correctly on Netscape 7. If you use ClearCase LT Web and another Rational Suite product, use Netscape 7 as your ClearCase LT Web browser, but do not modify your PATH.

For a Unicode file to be processed correctly when using the compare operation across multilanguage platforms, the file needs a byte-order mark, as follows:

For the Web interface, snapshot view config spec load rules are specified differently from the way they are specified for the native interface. The keyword load is not needed in the Load rule scopes portion of the config spec for the Web client.

The Compare and Merge operations are limited to elements of type text_file. Attempts to perform these operations on other types will fail.

Using special characters on non-ASCII operating systems can cause server output to be corrupted or the server to crash.

For example, the Shift-JIS double-byte tilde character (FULLWIDTH TILDE), which is used to indicate “Copy of” in the Japanese Windows environment, can cause this problem. The problem originates in differences between the Unicode conversion tables used by ICU (the publicly available Unicode software currently used by the Web interface) and the base operating system. The ICU Shift-JIS conversion table maps FULLWIDTH TILDE to WAVE DASH.

The server-side CGI process needs access to a directory in which it can create temporary files. The default on Windows is c:\. If the permissions on this directory do not allow everybody to create files in it, obscure failures occur, often with the error message, Operation "fileutl_tmpfile_ext_binary" failed: Permission denied. To avoid this problem, create a directory on the server with permssions that are set to allow everybody access to create files there. Then add a directive like the following to the RWP configuration file: SetEnv TMP d:\temp. The RWP configuration file is normally stored at c:\Program Files\Rational\common\rwp\conf\rwp.conf.

Pathnames that refer to files in your Web view are normally presented as hyperlinks. However, the Netscape 7 and Mozilla browsers enforce more stringent security restrictions than do other browsers. In these browsers, pathnames are not presented as hyperlinks because they cannot be traversed.

For best performance, we recommend running the Web interface on Windows 2000, Windows XP, or Windows NT.

When running the Web interface under SSL, the browser displays warning messages such as You are leaving a secure site. For example, in the VOB View, this may happen when you click a file name to view the file. The reason for the warning message is that a new window is launched to view the local file under the file protocol rather than under https. However, if you choose to view the same file by clicking View on the Properties page, a new window is launched under https, returning to the server, and the warning message does not appear.

You can safely ignore these warning messages because all client-server communications in the Web interface are encrypted. To disable the warning messages, use one of the following procedures:

On Mozilla and Netscape 7

On Internet Explorer

Note that when running Internet Explorer 6 on Windows XP, you cannot disable these warning messages when the displayed page has content from both secure and insecure sources.

The Rational ClearCase LT Web client can be very slow when browsing large directories, especially when your client PC has a slow CPU or limited RAM. For example, on an 800 MHz PC with sufficient RAM, a 1500 entry directory can take approximately 2 minutes to render.

To work around this situation, use one of the following workarounds:

When using the ClearCase LT Web client, display of pop-up windows must be enabled in your browser.

When a ClearCase activity in a project enabled for ClearQuest is linked to a ClearQuest record, the Name of the ClearCase activity is set to match the ClearQuest record's ID. This allows you to access the corresponding activity when you are working on a defect by using the current defect number. For example, you can use the command, cleartool setactivity ClearQuest-record-ID.

We recommend that you do not change the name of a ClearCase activity, although ClearCase does not prevent that. If you change an activity name, you cannot use the setactivity command as already described.

Note that the Headline field for a ClearCase activity is synchronized with the corresponding field in a ClearQuest record. That is, if you change this field from within either ClearCase or ClearQuest, the corresponding field in the ClearQuest record or ClearCase activity is modified as well.

The original Windows version of the Base ClearCase-ClearQuest integration ("V1") may on occasion fail to see the expected ClearQuest database because of outdated or incorrect description information that is maintained in the Registry. The error message that results is

"Error trying to logon to the ClearQuest database"

If this occurs, do the following:

A problem that is believed to originate in a Microsoft service pack can cause the Base ClearCase LT–ClearQuest integration to fail when a user logs on to a computer with an identity other than Administrator. The symptoms may include error messages such as This program can only be run within a ClearQuest trigger or Automation error...library not registered. To repair the problem:

On Windows 2000 and Windows XP systems

On Windows NT 4.0 systems

When assigning names to dbsets, follow these rules:

If you use Netscape to browse HTML documentation, we recommend Netscape 7.

The diffbl reference page does not describe the -nmerge option. The correct syntax for the first two usage modes of diffbl is as follows:

The -nmerge option is used to compare two baselines on the same stream and reports only activity and version changes made on that stream.

The protectvob reference page does not describe the pname-in-vob argument. The correct syntax for this command is as follows:

pname-in-vob can be the pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted). It cannot be the pathname of the VOB storage directory.

The checkvob –ucm command supports a –verbose option, which directs the command to generate more detailed output.

The information that follows was omitted from the Administrator's Guide.

If you install Rational Web Platform (RWP) on a host that was previously using a different HTTP server to support version 4.2 or version 2002.05.00 of the ClearCase Web interface and if that HTTP server must continue to run on that host to support other applications, you must do the following:

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.