ClearCase Web supports the following new features:

For complete information, see the Help.

The Mainframe Connector Remote Build feature allows you to submit build requests from ClearCase client platforms to OS/390 (MVS and USS) and z/OS (MVS and USS). You can configure Remote Build to return the derived objects to the client platforms, where you can version them. In addition, you can audit the builds using clearmake. For more information, see the Mainframe Connectors User's Guide for Rational ClearCase, which is available from the Help and the section, Changes to Mainframe Connector Remote Builds.

The following is a summary of build-related enhancements. For more information, see Building Software.

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.

The ClearCase multiversion file system (MVFS) has been enhanced to reduce lock contention and to scale to large systems (that is, 8–way multiprocessors or greater) that are accessed by multiple users. This enhancement results in noticeably better performance.

New environment variables control the Mozilla browser, as follows:

These environment variables are comparable to the CCASE_NETSCAPE and CCASE_NETSCAPE_OPT environment variables that are described in the reference page for xcleardiff. The script display_url.sh treats them as follows:

This section describes miscellaneous enhancements in this release.

This release introduces feature level 4. Table 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 (or in the case of a replicated VOB, raising the VOB family to feature level 4), results in the following changes in the VOB:

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

For instructions about raising the feature level of replicated VOBs, see the Administrator's Guide for ClearCase MultiSite. Note that in a VOB family, the replica that masters the VOB object must master the element types xml, html, and rose.

At this release, Rational ClearCase Attache is no longer a supported product.

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

Beginning with this release, Perl 5.6.1 is distributed with ClearCase. Perl 4 has been removed from this release. For backward compatibility, this release also includes a modified version of Perl 5.002. To use 5.002 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 describes the modifications that were made to Perl 5.6.1.

Likewise, in conformance with the Artistic License Agreement Table 3 describes the modifications that were made to Perl 5.002.

This release is the last major release that includes 5.002. The unmodified sources for Perl versions 5.002 and 5.61, as well as the binaries built from them, may be downloaded from http://www-3.ibm.com/software/awdtools/clearcase/support/index.html.

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.

The sections that follow describe changes to the mainframe connector remote builds feature.

This release introduces no new commands.

Table 4 lists new options and arguments to commands.

All ClearCase Attache commands are obsolete at this release.

The clearexport_ffile command was announced as obsolete in 2002.05.00; at this release, it has been removed from the product.

All ClearCase command options and arguments that were specific to ClearCase Attache 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, getcache, getlog, lsactivity, lsbl, lsstream, lstype, man, mkbl, mkdir, mkelem, mkproject, mkstream, protectvob, rebase, rmdo, rmname, schedule, setcache. For details, see the corresponding reference pages.

Most Help, including reference pages, is HTML.

The following reference pages have been removed from the Command Reference:

The Administrator's Guide contains new information about backing up and restoring ClearCase 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/doc/hlp.

The apropos command no longer supports the –glossary option.

In previous releases, if syncreplica –import tried to import an oplog for an rmreplica operation, it could fail with the error There are still objects mastered by this replica. In this release, the replay of the oplog succeeds with a warning. This behavior was reported as CMBU00063297; RATLC00684693.

It is possible for the oplog for a rmreplica operation to be replayed at a sibling replica before the last packet from that replica is imported at the sibling replica. In previous releases, syncreplica –import could fail with the error Replica has been deleted if it tried to import the packet after replaying the rmreplica oplog. In this release, the import will succeed with a warning. This behavior was reported as CMBU00063321; RATLC00684707.

When you delete the second-to-last replica in a family, the rmreplica command uses a series of write transactions to delete oplog entries. This behavior prevents the VOB database control files from becoming too large.

When the oplog entry for an rmreplica operation is replayed, no mastership checking is done. This change improves performance during packet import. This behavior was reported as RATLC00691265.

The Shipping Server sends packets in order of their creation time. They do not necessarily arrive at a destination site in that order. This behavior was reported as CMBU00065543; RATLC00686620.

The following sections describe changes to command output.

Some German locales are obsolete, such as De, De_DE.646, De_DE.646@EU, and De_DE.646@TE. If the current locale is set to one of these obsolete versions, the install scripts may abort with a syntax error. If this occurs, you must select and set a new locale before rerunning the installation.

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.

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.

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 the following procedure:

The Rational ClearCase 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 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.

When assigning names to dbsets, follow these rules:

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

The information that follows was omitted from Building Software.

Standard compatibility mode supports the GNU make export and unexport statements as well as the .EXPORT_ALL_VARIABLES directive. You can use the export statement to pass variable or macro values to a sub-make environment. Use the unexport statement to prevent a variable or macro from being exported to a sub-make environment. Using .EXPORT_ALL_VARIABLES causes all variables in the makefile to be exported.

Standard compatibility mode support Sun pattern rules. You can use these patterns within your makefile to indicate matching targets. Any target matching the pattern will have a dependency on the same pattern and will use the same rule as in the following example:

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.