| Version: | 2003.06.00 |
| Edition: | Windows Edition |
Table of Contents
This chapter describes new features and other changes in Version 2003.06.00 of Rational ClearCase, as follows:
The following is a summary of the new features that are introduced in this release of ClearCase:
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, 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.
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.
ClearCase is integrated more fully with Microsoft VS.NET than with its predecessor product, Visual Studio. This integration supports the UCM and base ClearCase process models that use either dynamic and snapshot views, with and without Rational ClearQuest.
The ClearCase-ClearQuest integration is also available in VS.NET. You can use these products separately or link them through UCM. With the UCM configuration, you can work on activities and manage change requests concurrently within the VS.NET IDE.2.
Highlights of the integration include the following:
For more information, see the Help for CC.NET.
This release introduces the integration of ClearCase with WebSphere Studio. The integration supports WebSphere Studio versions 4 and 5.0 running on versions 1.0, 2.0, and 2.1 of the Eclipse shell. For more information, see the Help.
This release adds support for PowerBuilder 8.0. The integration has also been enhanced to make the application path persist across sessions. For more information, see the Help.
This release introduces the integration of ClearCase with Forte for Java version 3.0. For more information, see the Help.
This release provides support for Borland JBuilder versions 5, 6, and 7. For more information, see the Help.
This release includes the following enhancements to the UCM-ClearQuest integration:
This release includes the following enhancements to UCM:
For integration activities in projects enabled for ClearQuest, you can click Actions > Contributors on the ClearQuest record form to display the activities that were included in the deliver operation.
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 section contains announcements, as follows:
This release introduces feature level 4. Table 1.1 shows all supported feature levels and the versions at which they were introduced.
Table 1.1. Feature Levels and ClearCase Versions
| Feature level | Introduced in version |
|---|---|
| 2 | 4.0 |
| 3 | 2002.05.00 |
| 4 | 2003.06.00 |
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.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 1.2 describes the modifications that were made to Perl 5.6.1.
Table 1.2. Modifications to 5.6.1 Perl Distribution
| Reason for modification | |
|---|---|
| Modification | Source file modified |
| Changes to accommodate Rational installation structure | |
| Customize install path | win32/config.vc, win32/cinfig.bc, win32/config.gc |
| Customize @INC | win32/win32.c |
| Use Rational naming conventions | |
| Specify ratperl in .def | makedef.pl |
| Use “ratl” name and Rational install path | win32/Makefile, win32/config.bc |
Likewise, in conformance with the Artistic License Agreement Table 1.3 describes the modifications that were made to Perl 5.001m.
Table 1.3. Modifications to 5.001m Perl Distribution
| Reason for modification | |
|---|---|
| Modification | Source file modified |
| Accommodation of underlying C library changes or other OS changes | |
| Use tempnam instead of mktemp | perlexe.cpp |
| Building with DLL version of C library | perl.h |
| Use open_osfhandle, so we don't need to rely on libc | perlexe.cpp |
| Changes to accommodate Rational installation structure | |
| Have NtGetSiteLib use CLEARCASE_HOME | ntxs.cpp |
| Use Rational naming conventions | |
| perl.exe, perlglob.exe become ccperl.exe, ccperlglob.exe | pp_hot.cpp |
| New functions and other changes needed by the embedded ClearGuide interpreter | |
| PerlRequire, PerlClearAv, PerlPushAv, PerlUnshiftAv, PerlCreateSv | perllib.cpp, perlexe.cpp, perllib.h |
| Changes related to ClearGuide modules | |
| Fix for load_process_family_source | Getopt/Long.pm |
| Inclusion of changes/upgrades from public domain to sources | |
| 5.002 PerlEval | perllib.cpp |
| Defect fixes independent of public domain | |
| Fix of crash in catch in PerlRequire | perllib.cpp |
| Not getting $@ or return value | perllib.cpp |
| Change in build or test environment to Perl modules as shipped | |
| Fix autoloading | ParseWords.pm |
| Version related changes | |
| Remove v5.004 test | HTML.pm, Entities.pm |
| Remove use strict for use by Perl 5.001m | HTML.pm, Parser.pm |
| Remove use strict for use by Perl 5.001m | Date.pm, Parse.pm |
| Changes to NT modules | |
| Incorporate Net::SMTP | Mail.pm, Mailer.pm |
| Make it work with NT Perl 5.001m | Net.pm, SMTP.pm |
| Make it work with NT Perl 5.001m | Time.pm, Zone.pm |
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.
In previous releases, the name of the installation destination directory that you specified included the name of the product, “ClearCase.” In this release, you should specify only the name of the directory in which the ClearCaseClearCase LT directory is to be created. The standard location for this directory is drive\Program Files\Rational. If you specify ClearCase in this path, the product is installed in drive\Program Files\Rational\ClearCase\ClearCase.
In previous releases, one sitedef file held default values for both servers and clients. In this release, you create separate sitedef files for servers and clients.
The environment variable, CLEARCASE_OBSO_SYN, is not supported in this release.
The following change was made to remove the term "atria":
The name of the dll install file has been changed from CCWordIntegration.dll to ccmsoaddin.dll, and the integration has been expanded to include Microsoft Excel and PowerPoint.
The ClearQuest Configuration tool (cqconfig) offers the administrator a choice of the V1 (previous) integration or the V2 (new) integration implementation allowing administrators to migrate to the new integration as appropriate. The default values were set to V2 on UNIX (because V2 was a superset of the V1 implementation) and to V1 on Windows (because the V1 integration had a GUI interface that V2 initially lacked). In this release, the V2 GUI is now available in all circumstances making it as functionally complete as the V1 Windows integration. Accordingly, the default for Windows is now set to V2. Administrators can still select V1.
This section describes changes to the ClearCase command set.
Table 1.4 lists new options and arguments to commands.
Table 1.4. New Options and Arguments
| Command | New option/argument | Use |
|---|---|---|
| chactivity | –viewview-tag | Transitions an activity in the specified view. |
| –cqaction { –cact | activity-selector ... } | In a single-stream project, checks in the versions in the change set of an activity and closes the activity if the relevant ClearQuest policies have been set. | |
| checkvob | –ucm | Runs checkvob in UCM mode. |
| –view view-tag | Uses the view specified in view-tag. | |
| –log log-dir-pname | Specifies an alternative directory for the log file directory. | |
| –fix [ –force ] | Directs checkvob to try to correct any problems it finds. Without –force, –fix prompts you before fixing any problem object. | |
| –verbose | Specifies verbose output. | |
| –crm_only | Examines only references to records in a ClearQuest database | |
| –vob_only | Examines only references to objects in components. | |
| –component component-selector | Further restricts a –vob_only check to the component specified by component-selector | |
| object-selector... | Specifies the object types that are to be checked. | |
| –crm_dbname user-database-name | Checks the references held in the ClearQuest database specified by user-database-name. | |
| –activity cq-display-name | Checks the references held by the activity record specified in cq-display-name. | |
| –project cq-display-name | Checks the references held by the project record specified in cq-display-name. | |
| chproject | –blname_templatebaseline-naming-template | Defines the baseline name template for a project. |
| chstream | –cview | Specifies the stream connected to the current view to be modified. |
| deliver | –reset–tointegration-view-tag | Resets a new integration view so you can cancel, resume, or complete a deliver operation after the integration view is lost during a deliver operation. |
| –cactivity | Specifies that the currently set activity is to be delivered. | |
| diff | –tiny | Same as –window, but uses a smaller font in a 165-character difference window. |
| –window | Displays output in a separate difference window. | |
| diffbl | –nmerge | Specifies that no merge is to be performed. |
| getcache | –persistent | Displays only those values which have been set to persist across MVFS restarts. |
| lsactivity | -me | Displays activities owned by the current user. |
| –useruser | Displays activities owned by the specified user. | |
| lsbl | -member_of [ –recurse ] | Used by itself, displays the composite baselines of which each baseline is a direct member. Used with the -recurse option, displays all baselines of which each baseline is a direct or indirect member. |
| lsstream | –in { project-selector | stream-selector } | Displays a list of all streams for the specified project, or a list of child streams for the specified stream. |
| mkbl | –viewview-tag | Specifies the view from which to create baselines. |
| mkdir | –master | Assigns mastership of the main branch of the directory element to the VOB replica in which you execute the mkdir command. |
| mkelem | –mkpath | For an element that is being created from a view-private file or directory, this option creates elements from its view-private parent directories. |
| mkproject | –model { SIMPLE | DEFAULT } | Sets the project model. SIMPLE: A single-stream project; DEFAULT: A multiple-stream project. |
| mkstream | –readonly | Creates a read-only stream. |
| protectvob | pname-in-vob | Pathname of the VOB tag or of any file system object within the VOB. |
| rmdo | -beforedate-time, –sincedate-time | Deletes DOs at the specified pathname that were created before or since the specified date and time. |
| setcache | –persistent | Specifies that all options will be applied immediately and also set persistently. |
| –persistent_only | Specifies that all options will be set persistently but will not take effect until the MVFS is restarted. | |
| –vobfreemaxcnt | Sets the maximum number of free (unused) attribute cache entries. | |
| –cvpfreemaxcnt | Sets the number of entries in the cleartext cache. | |
| –vobfreemincnt | Sets the minimum number of mnodes to keep on the VOB free list. | |
| –cvpfreemincnt | Sets the minimum number of mnodes to keep on the cleartext free list. | |
| –mnmaxcnt | Sets the initial number of mnodes cached by the MVFS. | |
| –cto | Enables close-to-open consistency checking. | |
| –ncto | Disables close-to-open consistency checking. | |
| –acache | Enables attribute caching. | |
| –nacache | Disables attribute caching. | |
| –dncache | Enables directory name caching. | |
| –ndncache | Disables directory name caching. | |
| –rlcache | Enables readlink caching. | |
| –nrlcache | Disables readlink caching. | |
| –rvcache | Enables root version caching. | |
| –nrvcache | Disables root version caching. | |
| –readdir_blockscnt | Sets the number of blocks cached for each directory read by the MVFS. | |
| –scalefactorval | Sets the scaling factor used to initialize the MVFS with more memory for better performance. |
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.
This section describes noteworthy changes to the documentation.
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.
A platform-independent edition of Managing Software Projects replaces the separate UNIX and Windows editions that were published at earlier releases.
This chapter summarizes new and changed features in Version 2003.06.00 of Rational ClearCase MultiSite. For more information, see the Administrator's Guide for Rational ClearCase MultiSite and the Help for MultiSite.
You can create new replicas or change existing replicas to preserve permissions. These replicas synchronize changes to element permissions, but do not synchronize changes to element ownership. You must raise the VOB family feature level to 4 in order to change a replica in the family to a permissions-preserving replica or to create a new permissions-preserving replica.
Note: To prevent metadata divergence, the protect command fails if you use the –chmod option, you specify an object in a permissions-preserving replica, and your client host is running a version of ClearCase associated with feature level 3 or lower. Trigger scripts that run the protect –chmod command fail in this situation.
You can replicate a VOB to a host running an earlier major version of ClearCase if the feature level of the VOB or VOB family is the same as the feature level of the ClearCase release on the target host. For example, if a host is running ClearCase Version 2003.06.00 with a VOB at feature level 2, you can replicate that VOB to a host running ClearCase Version 4.2, which is associated with feature level 2.
The Rational Shipping Server can determine whether a target host was unreachable during a previous shipping attempt and avoid sending packets to unreachable hosts during a specified timeout period. For more information, see the shipping.conf (UNIX) or MultiSite Control Panel (Windows) reference page.
The MultiSite Control Panel contains the following new fields:
Table 2.1 lists options and arguments that are new in this release.
Table 2.1. New Options and Arguments in MultiSite Version 2003.06.00
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.
If you request mastership of a branch or branch type associated with a UCM stream, the reqmaster command fails and prints the following error message:
Requests for mastership of UCM objects are not supported.
The phrase “Mastership is in transit to the new master replica” has been added to the following reqmaster output messages:
In previous releases, when you used shipping_server on a firewall and the shipping_server used a port number in the Registered Ports range (1024 through 49151), the shipping.conf parser printed a message recommending that you use a value in the Dynamic/Private Port Range (49152 through 65535). In this release, the message is not printed, but Rational still recommends that you use a value within the Dynamic/Private Port Range.
For attribute types, hyperlink types, and label types, the describe command shows the instance mastership of the type, even if the VOB is not replicated.
For replica objects, the describe –long command contains two lines that describe the replica's preservation mode. In previous releases, the output contained the line identities: preserved or identities: not preserved. In this release, it also contains the line permissions: preserved or permissions: not preserved.
This chapter explains restrictions and guidelines affecting the use of Rational ClearCase Version 2003.06.00 software that are considered noteworthy. These are not necessarily considered defects because the behavior reported is not expected to change in a future release of the product.
This chapter also describes significant problems with the documentation and includes documentation that was inadvertantly omitted from the manuals or Help.
In some cases, you will not be able to view the Rational copyright information online. If you want to see this information, you can find it on the ClearCase product CD under doc/windows/legal_information.html.
This section describes restrictions related to the installation of ClearCase.
File system corruption can sometimes result from installing ClearCase on Windows 2000 to an NTFS partition that has the Windows Change Journal log enabled on it. We are working with Microsoft to fix the problem.
Before installing ClearCase onto a Windows 2000 system, 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.
This section describes limitations on and guidelines for using the ClearCase Web product.
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 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:
This section describes restrictions that affect the ClearCase–ClearQuest integration.
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–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:
It is no longer possible to make a baseline in a rootless component that is not modifiable. Making a baseline of a composite component for the purpose of changing its members is regarded as making a modification in a component. A rootless component should be modifiable except in the following circumstances:
Windows commands that display time stamps adjust for daylight saving time based on the current DST setting rather than whether daylight saving time was in effect at the time of the file modification. This is a deliberate behavior. As a result, the time stamp output from a Windows command for a given file may be different from that shown by cleartool or UNIX commands for the same file.
In the current release, when working with nested and universal groups, a spurious failure may be reported when testing whether the clearcase_albd user account is in the ClearCase Administrators Group. The failure should be ignored. Also, the setup will not create an account in a domain that has a transitive trust with the current domain.
If you attempt to add a large number of files to source control from within Windows Explorer, the operation fails. To add a large number of files to source control, use the cleartool mkelem command instead.
A defect associated with taskpads in the Microsoft Management Console, version 1.1 and 1.2, causes problems in the ClearCase Administration Console. The problem occurs when you follow this sequence of steps:
The taskpad list is blank.
Use either of the following methods to work around the problem:
Note that with MMC 1.1, resizing the console window refreshes the list; resizing has no effect in MMC 1.2
By default, ClearCase software does not create a new version of a file that is identical to its immediate predecessor. When you attempt to check in a .frm file that is identical to the checked-in version, the integration does not check it in. However, if the .frm file has an associated .frx file, the integration checks in the .frx file as a read-only file. To avoid this problem, set the option to allow identical checkins.
To enable logging text to be displayed inside an IDE, the user must set the registry key HKEY_CURRENT_USER\Software\Atria\ClearCase\CurrentVersion\SCC\DebugTrace = 1 (or = 3 for additional logging to a file). This logging mechanism works for any IDE that supports messages from an SCC provider.
The message Not a VOB Object appears if you click Add to Source Control. In this case, the SCC proceeds to add the element to source control.
Customers who use Trend OfficeScan virus-scanning software on MVFS hosts should upgrade that product to scan engine version 6.570 build 1002 or later to avoid problems that could cause the MVFS to hang while a virus scan was active.
This section describes significant problems with the documentation and supplies documentation that is missing from the manuals or the Help.
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.
This chapter contains release notes for Rational ClearCase MultiSite Version 2003.06.00.
If you run protectvob -chown or protectvob -chgrp on a VOB replica that preserves identities, you must follow these steps to prevent owner or group metadata divergence among replicas in the VOB family:
If you do not change the owner or group at all identities-preserving replicas at the same time, metadata divergence can occur for the owner or group of new elements created at nonpreserving replicas. When the oplog entry for the new element is imported at an identities-preserving replica, the element's owner or group is the owner or group of the VOB at the time the entry is imported. If a change to the VOB owner or group has been made at other identities-preserving replicas, the element's owner or group will be different at the different replicas.
If no receipt handler is defined for a storage class, but a default receipt handler is defined, the default receipt handler is invoked for packets in that storage class. The shipping.conf (UNIX) and MultiSite Control Panel (Windows) reference pages do not describe this behavior.
Noteworthy problems found in or resolved in Version 2003.06.00 of Rational ClearCase are listed in the file cc_issues.htm.
You can find this file in two places:
Noteworthy problems found in or resolved in Version 2003.06.00 of Rational ClearCase MultiSite are listed in the file ms_issues.htm.
You can find this file:
Copyright© 2003 Rational Software. All Rights Reserved.