Ccms Relnotes
Ccms Relnotes
Ccms Relnotes
RATIONAL® CLEARCASE®
AND CLEARCASE MULTISITE®
RELEASE NOTES
VERSION: 2002.05.000
PART NUMBER: 800-025065-000
UNIX EDITION
SOLARIS 2.6, 7, 8
HP–UX 10, 11
RELEASE NOTES
DOCUMENT NUMBER 800-025065-000 OCTOBER 2001
RATIONAL SOFTWARE CORPORATION 20 MAGUIRE ROAD LEXINGTON, MASSACHUSETTS 02421
IMPORTANT NOTICE
COPYRIGHT NOTICE
Copyright © 1992, 2001 Rational Software Corporation . All rights reserved.
Copyright 1989, 1991 The Regents of the University of California
Copyright 1984–1991 by Raima Corporation
PERMITTED USAGE
THIS DOCUMENT IS PROTECTED BY COPYRIGHT AND CONTAINS INFORMATION
PROPRIETARY TO RATIONAL. ANY COPYING, ADAPTATION, DISTRIBUTION, OR
PUBLIC DISPLAY OF THIS DOCUMENT WITHOUT THE EXPRESS WRITTEN CONSENT
OF RATIONAL IS STRICTLY PROHIBITED. THE RECEIPT OR POSSESSION OF THIS
DOCUMENT DOES NOT CONVEY ANY RIGHTS TO REPRODUCE OR DISTRIBUTE ITS
CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY DESCRIBE,
IN WHOLE OR IN PART, WITHOUT THE SPECIFIC WRITTEN CONSENT OF RATIONAL.
TRADEMARKS
Rational, Rational Software Corporation, the Rational logo, Rational the e-development
company, Rational Suite ContentStudio, ClearCase, ClearCase MultiSite ClearQuest,
Object Testing, Object-Oriented Recording, Objectory, PerformanceStudio, PureCoverage,
PureDDTS, PureLink, Purify, Purify’d, Quantify, Rational Apex, Rational CRC, Rational
PerformanceArchitect, Rational Rose, Rational Suite, Rational Summit, Rational Unified
Process, Rational Visual Test, Requisite, RequisitePro, RUP, SiteCheck, SoDA, TestFactory,
TestMate, TestStudio, The Rational Watch, among others are trademarks or registered
trademarks of Rational Software Corporation in the United States and in other countries.
All other names are used for identification purposes only, and are trademarks or registered
trademarks of their respective companies.
Sun, Solaris, and Java are trademarks or registered trademarks of Sun Microsystems, Inc.
Microsoft, the Microsoft logo, the Microsoft Internet Explorer logo, Windows, the Windows logo,
Windows NT, the Windows Start logo are trademarks or registered trademarks of Microsoft
Corporation in the United States and other countries.
PATENT
U.S. Patent Nos. 5,574,898 and 5,649,200 and 5,675,802. Additional patents pending.
WARRANTY DISCLAIMER
This document and its associated software may be used as stated in the underlying license
agreement. Rational Software Corporation expressly disclaims all other warranties, express
or implied, with respect to the media and software product and its documentation, including
without limitation, the warranties of merchantability or fitness for a particular purpose or arising
from a course of dealing, usage, or trade practice.
TECHNICAL ACKNOWLEDGMENTS
This software and documentation is based in part on BSD Networking Software Release 2,
licensed from the Regents of the University of California. We acknowledge the role of the
Computer Systems Research Group and the Electrical Engineering and Computer Sciences
Department of the University of California at Berkeley and the Other Contributors in its
development.
This product includes software developed by Greg Stein <gstein@lyra.org> for use in the
mod_dav module for Apache (http://www.webdav.org/mod_dav/).
Release Notes Contents
Preface......................................................................... xiii
About This Manual .......................................................................... . . . xiii
ClearCase Documentation Roadmap.................................................... . . . xiv
Typographical Conventions.................................................................... . xv
Online Documentation ...................................................................... . . . xvi
Technical Support............................................................................... xvii
1 READ ME FIRST.......................................................... 1
ClearCase and MultiSite Hardware and Software Requirements .................... . . . . 1
Supported Architectures................................................................ . . . . 1
Supported Platforms for ClearCase Web Servers and Web Interface.......... . . . . 2
Supported File Systems................................................................ . . . . 2
NFS Support......................................................................... . . . . 2
Hardware Requirements................................................................ . . . . 2
Basic Hardware Requirements................................................... . . . . 3
Disk Space Requirements for the Release Area.............................. . . . . 3
Disk Space Requirements for Individual Hosts................................ . . . . 3
Software Requirements................................................................. . . . . 4
Basic Software Requirements ................................................... . . . . 4
Exporting the Release Area....................................................... . . . . 5
Architecture Mnemonics and mount Commands.............................. . . . . 5
Platform-Specific Information Relating to Installation................................... . . . . 6
Operating System Patches May Be Required...................................... . . . . 6
Operating System Vendor Web Sites ................................................ . . . . 9
Layered Software Packages............................................................... 10
ClearCase and MultiSite Patches Incorporated in This Release........................ 10
Upgrading from a Previous Release.......................................................... 11
General Issues with Upgrading........................................................... 11
Upgrading to the New Feature Level for UCM PVOBs............................... 12
Evaluating This Release of ClearCase.................................................. 13
Feature Compatibility Issues Across Releases........................................ 13
Upgrading from ClearCase LT................................................................. 14
MultiSite Compatibility with ClearCase....................................................... 15
MultiSite Version 2002.05.00.............................................................. 15
Compatibility Issues Across MultiSite Releases....................................... 15
Replica Creation........................................................................ 15
Replica Synchronization.............................................................. 15
v
Upgrading to New Schema Format................................................. 16
Enabling VOB Replicas for Interoperation......................................... 16
ClearQuest Compatibility with ClearCase................................................... 16
Installation and Licensing ...................................................................... 16
Pointer to Installation and Licensing Information ..................................... 17
Known Issues Related to Installation.................................................... 17
Deinstalling ClearCase May Remove Web Interface Views.................... 17
Cannot Use New VOB Schema Format with Link-Only or Mount
Installations............................................................. 17
Problems with Link-Only Installations .............................................. 17
Installation of UCM Integration with ClearQuest.................................. 18
Recovering from an Unsuccessful Installation.................................... 19
ClearCase Client Computers Need Consistent Character Encoding. .. . ..... 19
DDTS Integration Uses Wrong Environment Variable........................... 19
............................................................................................. 19
Installing the ClearCase Integration with Forte for Java ........................ 20
vi Contents
clearmake Changes.............................................................................. 28
Recording makefiles within Configuration Records................................... 28
Improved Reporting ........................................................................ 28
Improved Handling of Special Characters in Macro Names......................... 28
Improved Handling of Special Characters in Filenames............................. 28
GUI Support for Date and Time Preservation .............................................. 29
Additional Support for Moving VOBS......................................................... 29
New View Database Format.................................................................... 29
Changes to clearhistory and clearmrgman ................................................. 29
New ClearCase Perl Module................................................................... 30
Other Enhancements............................................................................ 30
Some ClearCase Programs Access Databases as VOB Owner .. .... ... ... ...... 30
chevent-Type Triggers Set to MODIFY_TYPE Now Fire Correctly................. 30
Improved Shared Lock Memory Manager on HP-UX 11............................. 30
New MVFS tuning parameter............................................................. 31
clearfsimport Checks For VOB Locks During Operation............................. 31
rmelem Use Now Restricted to VOB Owner or Privileged User.................... 31
rmelem Triggers fire When Symbolic Link is Removed.............................. 31
recoverview Now Dumps or Loads Very Large Views................................ 31
Improved Error Reporting for diffbl....................................................... 31
xcleardiff Can Now Compare Files With Names containing ’-dir’ .................. 32
Improvements to mktrtype, mkeltype, and cptype..................................... 32
Improvement to describe................................................................... 32
Changes to ClearCase Commands........................................................... 32
New Commands ............................................................................ 32
New Options and Arguments............................................................. 33
Obsolete Options and Arguments ....................................................... 37
Obsolete Commands ...................................................................... 37
Other Changes.............................................................................. 37
Changes to Documentation .................................................................... 37
Unification of UNIX and Windows Command Reference............................ 37
Changes to Release Notes................................................................ 37
Manual Reorganization .................................................................... 38
Changes to Command Reference........................................................ 39
Contents vii
mkreplica................................................................................ 43
reqmaster................................................................................ 43
restorereplica........................................................................... 43
Changes to Command Output............................................................ 43
describe.................................................................................. 43
multitool.................................................................................. 43
restorereplica........................................................................... 43
Changes to MultiSite Documentation......................................................... 43
viii Contents
Internet Explorer 5 May Terminate Display of Web Pages........................... 55
Some Fonts in Netscape on UNIX Are Difficult to Read............................. 55
Web Views Can Only Be Accessed Using the Web Interface....................... 55
Preparing Old Web Views to Run with ClearCase 2002.05.00 .................... 56
Guidelines on Using the XML Diff Merge Tool.............................................. 56
Problems Using Netscape 4 to Compare HTML Files .................................... 57
Guidelines on Using UNIX Snapshot Views................................................. 57
Version Tree Browser Opens a Temporary File ....................................... 57
Version Tree Browser Displays Error on Attempt to Access Eclipsed
Element ............................................................................ 58
Problems When Administrative VOBs Are Unavailable ................................... 58
Restrictions on Use of VOB Schema 54 .................................................... 59
If TZ Variable Is Set, ClearCase Uses It ..................................................... 59
Change to Behavior of Keep checked out Check Box .................................... 59
Verbose Mode Slows xclearcase Performance............................................. 60
Problem Using dtpad Editor on Systems Running CDE.................................. 60
xclearcase Reuses Old Comments During checkin........................................ 60
DDTS Integration Uses Wrong Environment Variable..................................... 61
Documentation Issues........................................................................... 61
Problem with Reference Pages .......................................................... 61
config_ccase............................................................................ 61
mount..................................................................................... 61
rebase.................................................................................... 62
softbench_ccase....................................................................... 62
Problem with Developing Software Manual............................................. 62
Cannot Run ClearCase Commands in a UNIX Snapshot View From a
Windows Client........................................................ 62
Delivering Work From a Snapshot View........................................... 63
Handling Elements That Are Not Visible........................................... 63
Problems with Managing Software Projects............................................ 64
Problems with Administrator’s Guide.................................................... 64
Problems with Online Help................................................................ 65
Using xman to Display Man Pages................................................. 65
Issues with Bristol HyperHelp ....................................................... 65
Help Window is Blank................................................................. 65
Issues with Tutorials........................................................................ 66
Tutorial Setup Script Fails on Windows XP........................................ 66
Tutorials in a Mixed Environment.................................................... 66
Contents ix
Limitation on Editing Mastership Request ACL............................................. 68
Do Not Use MultiSite to Clone a VOB ....................................................... 68
Using UCM and MultiSite ...................................................................... 69
Problems with Documentation................................................................. 69
x Contents
Tables
Figures xi
xii Figures
Preface
xiii
ClearCase Documentation Roadmap
Orientation
Introduction
Release Notes
Online Tutorials
Project
Development Management
More Information
Command Reference
Quick Reference
Online documentation
Build
Management Administration
xiv Preface
Typographical Conventions
This manual uses the following typographical conventions:
ccase-home-dir represents the directory into which the ClearCase Product
Family has been installed. By default, this directory is /usr/atria on UNIX and
C:\Program Files\Rational \ClearCase on Windows.
attache-home-dir represents the directory into which ClearCase Attache has been
installed. By default, this directory is C:\Program Files\Rational \Attache.
Bold is used for names the user can enter; for example, all command names, file
names, and branch names.
Italic is used for variables, document titles, glossary terms, and emphasis.
Preface xv
Online Documentation
The ClearCase graphical interface includes a Microsoft Windows-like help system.
There are three basic ways to access the online help system: the Help menu, the Help
button, or the F1 key. Help>Contents provides access to the complete set of ClearCase
online documentation. For help on a particular context, press F1. Use the Help button
on various dialog boxes to get information specific to that dialog box.
ClearCase also provides access to full “reference pages” (detailed descriptions
of ClearCase commands, utilities, and data structures) with the cleartool man
subcommand. Without any argument, cleartool man displays the cleartool overview
reference page. Specifying a command name as an argument gives information about
using the specified command. For example:
% cleartool man (display the cleartool overview page)
xvi Preface
Technical Support
If you have any problems with the software or documentation, please contact
Rational Technical Support via telephone, fax, or electronic mail as described below.
For information regarding support hours, languages spoken, or other support
information, click the Technical Support link on the Rational Web site at www.rational.com.
Your Location Telephone Facsimile Electronic Mail
North America 800-433-5444 408-863-4194 support@rational.com
toll free or Cupertino, CA
408-863-4000 781-676-2460
Cupertino, CA Lexington, MA
Europe, Middle +31-(0)20- +31-(0)20- support@europe.ratio-
East, and Africa 4546-200 4546-201 nal.com
Netherlands Netherlands
Asia Pacific 61-2-9419-0111 61-2-9419-0123 support@apac.ratio-
Australia Australia nal.com
Preface xvii
xvii Preface
READ ME FIRST
1
This chapter contains important information about Version 2002.05.00 of Rational
ClearCase and Rational ClearCase MultiSite. Read it before you attempt to install
either product. Note that beginning with this release, ClearCase and MultiSite releases
use the same version number and version number format as other Rational Software
products released in the same period.
Note: The term CPF stands for ClearCase Product Family and refers to the products
ClearCase, Attache, and MultiSite. The term 4.x refers to 4.0, 4.1, and 4.2.
Supported Architectures
ClearCase and MultiSite Version 2002.05.00 run on the platforms listed in Table 1.
For more information about differences in features and functionality by platform, see
the ClearCase Platform-Specific Guide in online help. To access the platform guide, go
to ClearCase help and click Help Topics.
1
Supported Platforms for ClearCase Web Servers and Web Interface
The following platforms support a ClearCase Web server:
Solaris SPARC
HP-UX
All supported ClearCase platforms support the ClearCase Web interface. For details
about the Web servers and Web browsers supported on different platforms, see Basic
Software Requirements on page 4.
The following file systems cannot be used to store any ClearCase data on any platform:
Andrew File System (AFS), DCE Distributed File System (DFS)
Any memory-based file system (such as memFS, tmpFS, swapFS)
NFS Support
Third-party automounters are not supported on any platform.
For a given platform, we support the NFS implementations that the platform supports.
If you use non-ClearCase access, see the Administrator’s Guide for Rational ClearCase
for a description of the limitations associated with use of NFS and potential
workarounds.
Hardware Requirements
This section describes hardware requirements for installing and running ClearCase
and MultiSite.
Note: UNIX processes and UNIX file descriptors per host are set as kernel
parameters.
In addition, any host that will have snapshot view directories needs enough disk
space to contain all files loaded into the snapshot views and all view-private files
added to the views. The amount of space required depends on the number and sizes
of the files in the views.
Any host that will have VOB- or view-storage directories must have enough disk
space to contain the files and databases used for storage of VOB- or view-storage
directories. The amount of space required depends on the characteristics and use
of the VOBs and views.
Software Requirements
This section describes software requirements for running ClearCase and MultiSite.
PHNE_19187 10.20
(800)
PHNE_20839 10.20 cumulative mux and Recommended for all
pty patch ClearCase hosts.
PHNE_20091 10.20 cumulative Recommended for all
NFS/NIS ClearCase hosts. Check
megapatch the prerequisites for these
patches.
PHNE_19937 10.20 ARPA transport Recommended for all
(700) patch ClearCase hosts.
PHNE_19936 10.20
(800)
PHNE_20021 10.20 NFS kernel patch Recommended for all
ClearCase hosts.
PHKL_9270 10.20 fix for current Required for all ClearCase hosts.
(700) pathname in
process/thread
PHKL_9271 10.20
(800)
Note: ClearCase users running Solaris 2.6 should avoid installing NFS patches
105720-15, 105720-16, or 105720-17 (current version). ClearCase users running
Solaris 7 should avoid installing kernel patches 106541-13, 106541-14, or 106541-15
(current version). For more information on this, see ClearCase Technical Bulletin #43.
Hewlett-Packard us-support.external.hp.com
In addition to the above patches, a fix for defect #CMBU00052278 is also included in
this release. For more information on that defect, see the cc_issues.htm file available
from the ClearCase CDROM and available from the ccase-home-dir/install directory
once the product is installed.
Before upgrading to a new ClearCase release, you must complete all deliver
operations that are in progress.
See also Known Issues Related to Installation on page 17.
Replica Creation
There are compatibility restrictions on creating replicas. You cannot create a replica
on a Release 4.x host from a replica-creation packet created on a Version 2002.05.00
host. If you want to create a new VOB family with replicas on Release 4.x and Version
2002.05.00 hosts, the VOB from which you export the replica-creation packet must be
located on a host running Release 4.x.
Replica Synchronization
Existing replicas hosted on systems running ClearCase 2002.05.00 can synchronize
with existing replicas on systems running ClearCase 4.x. See the information on
feature levels in the Administrator’s Guide for Rational ClearCase MultiSite.
To upgrade to Release 4.2 from 4.1 and continue to use your integration of UCM with
ClearQuest, you must perform the first two steps. The last two steps are optional.
4 Upgrade your ClearQuest user database to the new version of the schema.
21
Development Stream Hierarchies
In the basic UCM process, the integration stream is the project’s only shared work
area. You may want to create additional shared work areas for developers who work
together on specific parts of the project. Now you can accomplish this by creating a
hierarchy of development streams. For example, you can create a development stream
and designate it as the shared work area for the developers working on a particular
feature. Developers then create their own development streams and views under the
feature-specific development stream. In other words, the developers join the project at
the feature-specific development stream level rather than at the integration stream
level. The developers deliver work to the feature-specific development stream and
rebase their streams to recommended baselines in the that development stream.
Composite Baselines
A baseline selects one version of every element visible in a component. This release
lets you create composite baselines. A composite baseline is a baseline that selects
baselines from other components. By creating a composite baseline that selects
baselines from every component in your project, you can use one baseline to represent
the entire project.
After you create a composite baseline to represent the project, the next time you
invoke the make baseline operation on the composite baseline, UCM performs the
operation recursively. If a component that contributes to the composite baseline has
changed since its latest baseline, UCM creates a new baseline in that component.
Multiple-Component VOBs
You now have greater flexibility in storing components in VOBs. For example, you
can now store multiple components in a VOB. Within a VOB you can make an existing
directory tree into a component. The component’s root directory must be the VOB’s
root directory or one level beneath it. To store multiple components within a VOB,
each component’s root directory must be one level beneath the VOB’s root directory.
UCM Support
This version of the ClearCase Web interface supports the UCM developer role. A
developer can use the Web interface to join a project, create new activities, perform
work in those activities, deliver work to an integration stream, and rebase a
development stream to recommended baselines.
The first nine commands and tools give you all the capabilities you generally need.
However, when you need advanced capabilities, the last command on this list,
xclearcase, gives you access to the complete set of functions of the ClearCase system.
Enhancements to Installation
This version of ClearCase includes the following enhancements to installation.
Enhancements to Installation 27
ClearCase LT Server Install Now Allows Selection of VOB Schema 53
or 54
In this version of ClearCase LT, you have the option during installation of the
ClearCase LT server to install support for either VOB schema 53 or 54.
clearmake Changes
This release provides enhancements to clearmake that do the following:
Record makefile versions within configuration records.
Improve reporting.
Improved Reporting
When clearmake rebuilds a target because a “build script mismatch” is detected, you
can now use the –d and –v options to generate a print of the actual script differences to
standard output.
Other Enhancements
The following sections discuss additional enhancements made to this version of
ClearCase.
Other Enhancements 31
the failure as resulting from the fact that the baselines or streams involved did “not
share a common ancestor (initial or imported) baseline”.
Now the error message describes the cause of the failure more accurately as resulting
from the fact that the baselines/streams “are derived from different import baselines
or the initial baseline”.
Improvement to describe
Previously, the command cleartool describe oid:oid-number returned an extra
version-id-string when the version was not selected by the view. In the current
version of ClearCase, it returns exactly one version-id-string.
New Commands
Table 14 lists new commands in this version of ClearCase. In addition, the clearprompt
command is now available as part of the minimal developer installation.
Obsolete Commands
The clearexport_ffile command is obsolete; use clearfsimport instead.
Other Changes
Redefinition of element types (mkeltype -replace) is no longer allowed in replicated
VOBs.
Changes to Documentation
The following major changes have been made to the documentation:
Integration of UNIX and Windows material in a single Command Reference.
There is significant reorganization of material in the Administrator’s Guide, Building
Software, and the Command Reference.
Changes to Documentation 37
Manual Reorganization
Large sections of material in the Command Reference have been moved to other
manuals, and some material from Building Software has been moved to the Command
Reference.
Certain build-related information that was formerly published in Building Software
is now published in the following reference pages:
clearmake.options
makefile_aix
makefile_ccase
makefile_gnu
makefile_pmake
makefile_smake
makefile_sun
Some reference pages that do not describe any user interface—but rather ClearCase
internals or concepts—have been removed from the Command Reference and the
information has been incorporated into other titles.
In particular, information from the following obsolete reference pages is now
published in the Administrator’s Guide for Rational ClearCase:
abe
admin_server
albd_server
db_server
db_dumper/db_loader
errorlogs_ccase
license.db
lockmgr
registry_ccase
type_object
view
view_server
vob
vob_server
vobrpc_server
Information from the following obsolete reference pages is now published in
Building Software:
bldhost
bldserver.control
Changes to Documentation 39
40 Chapter 2 - What’s New in ClearCase
What’s New in
MultiSite 3
This chapter summarizes new and changed features in this release of Rational
ClearCase MultiSite.
For more information about the commands described in this chapter, see the reference
pages in the Administrator’s Guide for Rational ClearCase MultiSite. For information
about the feature level requirements for using these features, see PVOB Feature Level
Requirements in Chapter 4.
41
New Object Selector for describe Command
The describe command now accepts a replica-uuid-selector argument, which you
can use to display the properties of a replica by specifing its UUID. Specify
replica-uuid-selector in the following form:
oid:replica-uuid@replicauuid:replica-uuid
The replica you specify must be at your current site. If the replica is located at a
remote site, the command does not return any output.
The description of this object selector in the describe reference page incorrectly uses
replica-oid; it should use replica-uuid.
Changes to Commands
Table 16 lists new options and arguments in this release. For more information, see
the reference page for the command.
chmaster
The –force option has been changed to –obsolete_replica.
mkreplica
The –vob option for mkreplica –export is now obsolete. This option was replaced by the
replica-selector argument in Release 3.0.
reqmaster
The –instances option is now optional.
restorereplica
The –completed option has been changed to –override.
describe
The output for describe replica: includes the connectivity property.
multitool
The output for –version and –VerAll displays the version string in a different format.
The new format uses a version string like the following:
2002.05.00
restorereplica
Additional warning text has been added to the output from restorereplica —override.
45
that PVOB must be upgraded to Version 2002.05.00. ClearCase UCM operations will
fail on clients that run previous versions of ClearCase if they try to access a PVOB
whose feature level has been upgraded to FL3.
Recommending a Baseline
You can recommend a baseline for a stream if the baseline is from the stream or the
stream’s foundation.
For a baseline not from the stream or the stream’s foundation, the following rules
apply:
The baseline must be from the same project as the stream.
The baseline must be contained in the stream, which means the baseline has been
delivered to the stream, or the stream has rebased to the baseline or one of its
descendents.
The baseline must contain the current recommended baseline, which means it
must be a descendent of the current recommended baseline.
You are not required to recommend a baseline for every component in the stream’s
configuration.
You can clear the list of recommended baselines. Note that doing this step alone will
cause problems when existing development streams rebase to the recommended
baselines. The rebase operation will attempt to drop all baselines in the development
streams’ configuration. This operation will probably fail or produce errors and
therefore not desirable.
You can choose to reset the recommended baselines to baselines from the stream or
the stream’s foundation with or without clearing the recommended list. This allows
the stream to return to a known correct state after being changed inadvertently to a
bad list.
If a trigger attempts to read directly from standard input, it receives an error, because
standard input does not specify a valid file descriptor.
In addition, any trigger failure in the Web interface context displays this error message:
Interactive triggers are not supported in the Web interface. If the
trigger was interactive, it may have failed for that reason.
Trigger script writers can detect whether a trigger is running in the Web interface
context by checking for the environment variable ATRIA_WEB_GUI. It is set to 1 if you
are running in the Web interface context.
Note that the base ClearCase-ClearQuest integration is dependent on the operation
of interactive triggers; for this reason, the ClearCase Web interface is not a viable
interface for using that integration.
We recommend that you check the Netscape Web site, www.netscape.com, for more
information on general Netscape requirements.
reformatvob uses the space command to calculate the amount of space needed for
a reformatting operation. This fails for large database files, although the failure
does not cause the reformat itself to fail.
The space command cannot successfully run the stat() routine on large database
files. As a result, the cleartool space –vob –generate command can fail. This, in
turn, can cause the Standard ClearCase Daily Tasks task, supported as part of new
administration functionality in Release 4.0, to fail. If you have a VOB with large
database files, the space command fails nightly on scheduled jobs.
To avoid this problem, edit the scheduled job list so that it runs only on VOBs
that do not have large database files.
Documentation Issues
This section presents late changes to documentation and describes errors or
information missing from the documentation delivered with ClearCase software.
config_ccase
The config_ccase reference page on UNIX systems does not mention the file
/var/adm/atria/config/admin.conf, which allows or disallows remote administration of the
host. Also, this reference page says that anyone can edit files in the ../config directory.
That may not be true for all files there, including admin.conf. You must be root to
edit admin.conf.
mount
The mount reference page should contain a section on AUTOMATIC VOB
DEACTIVATION AT SYSTEM SHUTDOWN with the following contents:
At system shutdown, the architecture-specific ClearCase startup script is invoked
with the stop option to execute the ClearCase shutdown procedure. As part of this
procedure, a umount -all command deactivates all VOBs currently active on the local
host.
On UNIX platforms, umount -all invokes the standard umount(1M) utility directly.
In addition, on some UNIX platforms, mounting VOBs with the ro option works
properly; that is, it prevents writes to view-private files within the VOB, but does
not prevent other clients from modifying the VOB nor does it prevent changes
that do not go via the MVFS, such as some cleartool operations. However, on
other UNIX platforms (namely, HP-UX 11.0 mounting VOBs with the ro option
Documentation Issues 61
prevents view-private changes to the file namespace (such as creation or deletion of
view-private files) but does not prevent writes to view-private files.
rebase
With the introduction of stream hierarchies at this release, most of the rules for
rebasing an integration stream and a development stream are now the same. The
rebase reference page contains sections on Rules for Development Streams and Rules
for Integration Streams. These sections are superseded by information in the section
Rebasing a Stream on page 49 in this version of the release notes.
softbench_ccase
The softbench_ccase reference page is incorrect in the following ways:
It states that ClearCase integration with SoftBench supports SoftBench 4.x and 5.x;
ClearCase supports 5.x and 6.x, but does not support SoftBench 4.x
The description of the integration is accurate for the ClearCase integration
with SoftBench 5.x, but not for Softbench 6.x. SoftBench functionality changed
significantly at 6.x, causing the ClearCase integration user interface to also change.
For an accurate description of the integration for this user interface, see the online
help for third-party integrations (available from the top-level online help menu).
On UNIX systems, if you are using the GUI, you see the following messages:
It appears that you have never before accessed the snapshot view (view tag).
As a result, we’re unable to locate the view’s root path name
Please ’cd’ to the snapshot view’s root directory and do a
’cleartool update’. This establishes you as a user of the view.
If you see either of these messages, change directory to the view root directory of the
snapshot view and use the following command in that directory:
cleartool update -print
This preview form of the update command is quicker than update and does not change
the loaded files. After the command completes, retry the deliver.
Do not ignore this situation. The deliver operationfound versions of elements in the
development stream that need to be considered for merging to the target stream,
but did not find the elements in the target stream. Some possible causes for this
situation are:
Documentation Issues 63
A new element was added to source control, but the directory that catalogs the
element is not checked in.
In this case, cancel the deliver or rebase operation, check in the directory, and
start deliver or rebase again.
While a change to the element was being made (in the development stream, for
a deliver; in the stream from which you are rebasing, for a rebase), someone
operated on the element (in the target stream, for a deliver; in the development
stream, for a rebase), as follows:
The name of the element or the name of a VOB symbolic link to the element
was removed.
The element itself or the VOB symbolic link to the element was removed.
In either case, decide whether the removal was appropriate. If the removal was
appropriate, you can allow the deliver or rebase to ignore the element.
The change may be obsolete, because you intended to remove the name of the
element or the element itself.
Because ClearCase cannot tell what caused the situation, you must find the cause, fix
the problem, cancel the current operation, and start over.
The online help and the Managing Software Projects manual continue to use the old
wording for this policy.
The largest value that the Scaling Factor is automatically set to is 24.
Caution: If you create man directories, do not run cleartool man as the root user. If
you do, the man page will be deleted.
Documentation Issues 65
1 In the Help window menu bar, click Options>Font>Normal. The Help window
is refreshed.
2 If the wrong help topic is displayed when the help window is refreshed, click the
Back button to return to the original topic.
When multitool with a newer protocol reads a packet with the older protocol, it prints
this message:
multitool: Warning: Version mismatch, software:new-protocol, packet:old-protocol
This message does not indicate a problem. It means one of the following things:
The feature level of the VOB family is lower than the feature level of the receiving
replica.
The feature level of the VOB family is the same as the feature level of the sending
and receiving replicas. However, when the sending replica created the update
packet, it had not yet received a packet containing the information about the new
VOB family feature level.
67
Synchronization Error When Database Limit Is Exceeded
ClearCase Releases 4.x include support for a new VOB database schema. If you update
one or more replicated VOBs in a family to the new schema (version 54), you do not
have to update the other replicas in the VOB family immediately. However, you must
update all replicas before one of the updated replicas exceeds the database limit of the
previous schema (version 53). If you do not, replicas that have not been updated will
not be able to import synchronization update packets from the updated replica.
When this type of import failure occurs, syncreplica output includes a VOB database
error, and an error is written to the db log.
The syncreplica output includes an error like the following:
multitool: Error: Error from VOB database: ’’\\vob.setup’’.
To fix this problem, you must convert all replicas in the family to schema version 54.
To display the schema version for a VOB replica, use the cleartool describe vob:vob-tag
command. To display the schema version of the ClearCase release installed on your
computer, use the cleartool –ver command.
71
72 Chapter 6 - Status of ClearCase Software Change Requests
Status of MultiSite
Software Change
Requests
7
Noteworthy problems found in or resolved in Version 2002.05.00 of Rational
ClearCase MultiSite are listed in the file ms_issues.html.
You can find this file:
On your ClearCase CD, in the directory Rational/doc/platform, where platform
is an architecture mnemonic like ux (for UNIX computers) or nt (for Windows
computers).
In the directory ccase-home-dir/install/ after you’ve installed the product.
Note that any problems relating to installation or setup of MultiSite are noted in the
section Known Issues Related to Installation on page 17.
73
74 Chapter 7 - Status of MultiSite Software Change Requests
Network Attached
Storage Devices
Certified For Use
A
With ClearCase
Network-attached storage (NAS) devices communicate with other hosts on a local
area network using a network file system protocol like the Network File System (NFS)
or the Common Internet File System (CIFS). While any NAS device can provide
storage for ordinary files that are created and used by ClearCase, only the NAS
devices described in this section have been certified for use with VOB server and view
server hosts. When configured and used as described in this section, these devices can
provide remote storage for VOB and view databases in addition to ordinary files.
Caution: Every certified NAS device must be specially configured to support
remote VOB or view databases. If you do not configure a certified NAS
device as described, you put your VOB or view data at risk. If you host a
VOB or view database on a NAS device that has not been certified for this
purpose, you will put your VOB or view data at risk.
The Administrator’s Guide has more information about putting VOB or view databases
on certified NAS devices.
75
VOB or view
server platforms
Vendor Product Software Version supported
EMC Celerra File Server 2.2 (contact EMC UNIX and
Customer Service Windows
for ClearCase
patch)
Network Series 7xx Filer, DataOnTAP UNIX and
Appliance Series 8xx Filer OS V5.3.6, Windows
DataOnTAP OS
V6.0.1
Note: Rational only supports use of the NFS protocol to connect a UNIX VOB
server host with a VOB database on a NAS device. You must use the CIFS protocol
to connect with NAS devices from Windows hosts. Use of NFS software to connect
Windows hosts to NAS devices is not supported by Rational.
All of the NAS devices described in this document can be configured to support
native interoperation with both UNIX and Windows hosts. You do not need to install
a third-party NFS product on Windows or an SMB server product on UNIX to make
VOBs and views on NAS devices accessible to both UNIX and Windows hosts.
The following sections describe procedures for configuring and using various NAS
devices with ClearCase. In these sections, we assume that:
you are familiar with the basic configuration and operation the NAS device you
are using
you have already installed the device on your network and verified that it can be
used with applications other than ClearCase
We also assume that you have established the appropriate level of cross-platform
interoperability for your site if both UNIX and Windows computers are in use as
ClearCase hosts. All the requirements detailed in the Administrator’s Guide for user
and group accounts on both UNIX and Windows must be met if you are using a NAS
device to host ClearCase data that is accessed from UNIX and Windows computers.
NAS devices often provide their own implementation of cross-platform file-access
solutions such as NFS and CIFS (SMB), but these implementations usually require that
any user who must access files on the NAS device can be authenticated using the same
user name and group name regardless the type of platform (UNIX or Windows) they
are using. If ClearCase users at your site use UNIX and Windows computers, verify
that users can create and delete file and directories on the NAS device from both UNIX
and Windows before proceeding with additional NAS device configuration steps.
Auspex NS2000
This section describes configuration procedures that you must perform before you
can use an Auspex NS2000 NAS device for VOB or view storage as described
in Administering ClearCase. For additional information about the NS2000, see
www.auspex.com.
Data stored on an Auspex NS2000 can be organized into virtual file systems and
shares on virtual partitions and RAID sets. A RAID set may be "sliced" into
independent file systems using virtual partitions. A RAID set must contain at least
three data disks. Auspex recommends a RAID set with at least six data disks for
frequently accessed ClearCase data.
4 Mount the virtual file system. Run the following command to mount the virtual
file system you created in Step #2 at the mountpoint you created in Step #3:
mount -F lfs /dev/axvp/fspNvpX /vobstg
To ensure that a virtual file system is mounted at boot time, create an entry for it
in /usr/AXbase/etc/lfstab.
5 Enable read/write access for the albd_server. All volumes used for VOB or view
storage must be configured with read/write (rw) access by the ClearCase server
process user account (Windows) and root (UNIX).
Auspex NS2000 77
6 Make the file system accessible. Volumes that will only be accessed by UNIX
computers must be shared using the NetOS share command. Volumes that will
only be accessed by Windows computers must be shared using the NetOS net share
command. Volumes that must be accessed by both UNIX and Windows computers
must be made accessible using both commands. The following command makes
the file system mounted at /vobstg accessible to NFS clients:
share -F NFS /vobstg
and type the name of the NS2000 in the Select Computer dialog box.
As with any VOB backup strategy, you must lock the VOB before backing it up.
Because the snapshot backup copy can be made quickly, lock time required for the
backup will be minimal.
A cached snapshot backup should also be backed up to hard media such as tape or
CD, using backup software (for example, the Auspex utility ax_gtar) that will preserve
all file system information, including ACLs if the file system is used to hold VOBs
or views served by a VOB or view server on Windows.
Note: To back up a cached snapshot, you must first mount it.
By default, NS2000 file-based backup does not back up files larger than 2GB. VOBs
using schema version 54 may include some files larger than 2GB. To ensure that these
files are included in hard-media (file-based) backups of a snapshot cache, edit the file
/usr/AXndmp/etc/config on the NS2000 as follows:
Note: When this option is enabled and a large file is encountered during file-based
backup, Auspex’s proprietary extension to standard GNU-tar format is used instead
of the standard GNU-tar format. With this option on, you may not be able to use the
standard GNU-tar command to recover data from file-based backups
Note: You must also configure and start CIFS services if you are exporting a file
system for CIFS access.
Note: Network Appliance Filers provide a specialized snapshot backup facility (not
related to the ClearCase snapshot backup program), which is managed at the
volume level. Keep backup considerations in mind when allocating volumes
to hold VOB data or other ClearCase data. It will simplify implementation of
Network Appliance snapshot VOB backups if you dedicate one or more volumes
exclusively to VOB storage.
2 Disable quotas on volumes to be used for VOB storage. If quotas are enabled,
Network Appliance recommends disabling them on volumes used for VOB
storage. The following Data ONTAP command reports on whether the volume
ccvol has quotas enabled:
The following Data ONTAP command disables quotas on the volume ccvol:
quota off ccvol
3 Make the volume(s) accessible. Volumes that will only be accessed by UNIX
computers must be exported using the Data ONTAP exportfs command. Volumes
that will only be accessed by Windows computers must be shared using the
Data ONTAP cifs_shares command. Volumes that must be accessed by both UNIX
and Windows computers must be exported and shared.
4 Enable read/write access for the albd_server. All volumes used for VOB or view
storage must be configured with read/write (rw) access by the ClearCase server
process user account (windows)and root (UNIX).
5 Create qtrees. A qtree is a special subdirectory of the root directory of a volume.
The following Data ONTAP command creates a qtree named vobstg in a volume
named ccvol.
qtree create /vol/ccvol/vobstg
6 Specify each qtree’s security style. The Data ONTAP qtree command allows you
to specify the type of access checking (security style) that will be used when a
determining whether a user has rights to access a file or directory. You can specify
any of three security styles:
unix evaluates user access rights by considering the UID and GID of the user
and the access mode of the file or directory
ntfs evaluates user access rights by considering the SID of the user and the
ACL of the file or directory
mixed provides support for both security styles
The following Data ONTAP command specifies that the unix security style will be
implemented in the qtree named vobstg
qtree security vobstg unix
Note: For any qtree used to provide VOB storage server by a VOB server running
Windows, you must set the qtree security style to ntfs.