1 Status of ClearCase Software Change Requests
This
file contains descriptions of noteworthy problems found in and not yet resolved
in ClearCase Version 2002.05.00. Note: The ClearCase Product Family development
group switched to a new change request system after ClearCase 4.0 was released.
ID numbers differ between the old and new systems. This document lists both
numbers. The new number appears first and includes a CMBU prefix. The former
four- or five-digit number, if one exists, appears in parentheses. Known Problems in This Release
The
following are the known problems in ClearCase Version 2002.05.00. #CMBU00002462 (#7328) permissions problem building over winked-in derived
object
When
your build script builds over a target without first removing it, the script
must retain the permissions of the built-over DO. Your view maintains these
permissions correctly, but the data container created by the MVFS gets new,
potentially different permissions. As a result, subsequent attempts to build
over the target may fail. #CMBU00010087 (#11485) grp files do not handle multibyte characters
xclearcase may fail with grp files using the Shift-JIS (SJIS)
Japanese character encoding. xclearcase does not correctly discriminate between
the second byte of some shift JIS characters (which are in hexadecimal code
0x5c) and the ASCII code for backslash (\). #CMBU00013753
(#15505) remote abe should inherit group-id of the clearmake process that
invoked it
If
you use multiple groups to control access, and you use parallel builds, a
remote abe does
not inherit the group ID from clearmake. clearmake uses rsh to start an abe process on the remote machine. The
user name is not passed by clearmake; it is set by the rsh command. There is no way to pass the
effective group. Instead, the abe picks up the user’s primary group. For these
reasons, starting clearmake in a newgrp shell does not pass the group across
the remote abe interface. Workaround: Create two Bourne-shell scripts What this script does: The environment variable CLEARCASE_ABE_PN is
set to point to this script. The distributed build runs this script instead
of /bin/abe. The
script first finds the group setting on the directory in which the build is
made, and then copies another script abe.run to the local /tmp, changes the group setting on it and
sets the s bit. When this is done, the abe.startup script
fires the abe.run script. What this script does: This script, after being copied and
modified by abe.startup,
runs the real /bin/abe but
with the correct group set. Script for abe.startup
#!/bin/sh
# Get Vobpathname to the directory where the build will be made
VOB_PATH=$3
# Get View tag
VIEW=$9
# Find out which ls to use
for LS_TEST in /usr/5bin/ls /usr/bin/ls /bin/ls; do
if [ -x $LS_TEST ] ; then
LS=$LS_TEST
fi
done
# Get the group name of the build directory
VIEW_EXT_PATH=/view/${VIEW}$VOB_PATH
CLEARCASE_GROUP=‘$LS -lagd $VIEW_EXT_PATH | awk ‘{print $3}’‘
export CLEARCASE_GROUP
# Set the path for clearmake
PATH=${PATH}:${ATRIAHOME:-/usr/atria}/bin
export PATH
# Copy the ‘abe.run’ script to local /tmp directory, and change group
# to the same as the build directory. Then set the ‘s’ bit on the ‘abe.run’
\cp ‘echo $0 | sed ‘s@abe\.startup$@abe\.run@’‘ /tmp/abe.run.$$
chgrp $CLEARCASE_GROUP /tmp/abe.run.$$
chmod g+s /tmp/abe.run.$$
# Run the setuid script
/tmp/abe.run.$$ $*
STAT=$?
# Remove the script
\rm -f /tmp/abe.run.$$
# Exit with same status as the real abe
exit $STAT
Script
for abe.run
#!/bin/sh -p
# Optional debug line
#echo “‘uname -n‘ : ‘date‘ : ‘echo $* | awk ‘{print $3, $18}’‘ : $$” >>
/tmp/abe_run.log
exec /bin/abe $*
exit $?
#CMBU00021475 (#24196) some applications may require increase in size
of data limits
On computers configured with a per-process
data size limit of 16 MB, certain applications, including some of ClearCase
GUI programs and some HyperHelp online help files, may run out of memory and
display errors. In addition, some GUI programs may
not work with some older versions of X Windows/CDE. #CMBU00026201
(#29379), (#26909), (#30185) global types: differences in command line behavior
and GUI behavior
The ClearCase Type Explorer and Properties
Browser always display information about local copies of global types, instead
of displaying information about the global type. If
the client VOB you are browsing does not contain a local copy of a global
type, the ClearCase Type Explorer does not display the global type. #CMBU00028068 (#31461) diffbl does not work with imported baselines
The cleartool diffbl command,
which compares two baselines and shows the differences between them, does
not work correctly when one or both of the baselines are imported baselines. #CMBU00028214 (#31626) changing activity name breaks link with ClearQuest
record
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 illustrated above. 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. #CMBU00028501
(#31944) snapshot view limitation on VOB symbolic links
VOB
symbolic links are limited to one level of indirection in snapshot views.
That is, the result of cleartool ln –s is loaded as a native file-system symbolic
link only if the source is not another VOB symbolic link. #CMBU00029594 (#33174) integration stream property sheets may not show
delivered activities
In the Project Explorer, the Activities tab
of the baseline and integration stream property sheets does not list the activities
that have been delivered to the integration stream and incorporated into the
baseline. The Activities tab displays only activities that were created
in the integration stream, including integration activities, which ClearCase
generates during deliver operations. #CMBU00030700,#CMBU00032384
(#36267) Print to File option does not work
The Print
to file option of applications
such as Microsoft Word does not work for an MVFS file. Attempting to print
to file within the MVFS may result in the error access denied or
the application may appear to hang as it continues to try to write the file.
The problem is that the mechanism used for this function uses an identity
that does not have the proper credentials for the MVFS to be able to validate
it. The workaround is to print the file to a file outside the MVFS (such as
a local or network drive) and then copy it into the MVFS from there. #CMBU00031042 (#34757) GUI does not display Version Tree after checkin
of hijacked file
If you use the Update window (opened
by clearviewupdate)
to check in a hijacked file element, and then try to use the GUI to display
a version tree of that element, the version tree is not displayed. Instead,
the tool displays the following error message: xclearcase: Error: Invalid pathnames
The
error message is displayed on the command line in the terminal window where
you started clearviewupdate. Workaround: Use the command line interface tool xlsvtree to
display the version tree. #CMBU00031043
(#34758) on Linux and Solaris Intel systems, selecting hijacked folder produces
empty Name field
On Linux and Solaris Intel platforms,
if you use the Clear View Update GUI to check in a hijacked file element,
and then use the GUI to select the hijacked folder, the tool displays an empty Name field,
instead of listing the name of the hijacked file that was checked in. #CMBU00031647 (#35432) config spec may not be synchronized before update
preview
In
a UNIX snapshot view, your config spec may not be correctly synchronized before
all update previews. However, synchronization is always correct for full updates. #CMBU00032492
(#36392) relocate –update command stops at nonmastered element
The relocate –update command
fails to relocate an element if the element is mastered by a replica at a
remote site. Workaround: To relocate an element that is mastered at another
site, you must change the mastership of the element using the chmaster command. #CMBU00033367
(#37371) delivery of selected activity does not detect directory dependency
across activities
If you create a new element in one
activity (for example, A) while the directory containing the element is checked
out to a different activity (for example, B), you have created an implicit
dependency of A on B. When selectively delivering activity A, you must also
include activity B. Otherwise deliver reports the error: DBID not found. #CMBU00033579
(#37602) Project Explorer Transcript window does not always respond
The
Transcript window may open when exception conditions have occurred during
an operation. When the Transcript window and another modal dialog box are
open, such as a properties dialog in which operations can be initiated, the
Transcript window does not respond to user actions. You must close the dialog
box before you can adjust the scroll bar of the Transcript window to view
the full message or event log. #CMBU00033849 (#37912) MVFS cache
sizes should not use too much kernel memory
When adjusting MVFS caches as described
in Administrator’s Guide, take
care not to use too much of your kernel memory. If the cache size settings
are too large, you may exhaust kernel memory, which can cause your system
to hang or crash. The upper limits for cache sizes depend on the amount of
memory in the system, the particular system configuration, and the nature
of the work being performed on the system. A ClearCase administrator should
monitor system memory use while increasing MVFS cache sizes. #CMBU00034173
(#38270) relocate does not preserve lock applied to branches
If
a branch of an element is locked, rather than the element itself, you can
relocate the element along with the branch. However, the relocated branch
is no longer locked. #CMBU00034704
(#38851) symbolic links to hijacked files show up as duplicates in list
Symbolic
links to a hijacked file appear in the clearviewupdate hijacked file list along with the
file itself. As a result, multiple entries in the hijacked list refer to the
same file. #CMBU00034794
(#38950) update –add command in snapshot view may fail if working directory
is global network path
When you are working in a snapshot
view whose working directory is a global network path (for example, of the
form /net/hostname/directory), the update –add command may fail with the message: cleartool: Error: Unable to determine version for VOB root directory element.
Workaround: Specify your working directory using
the local absolute path, for example, /usr1/smith/views/4.0_view. #CMBU00035331 canceling a uncheckout
confirm window hangs ClearCase-FrameMaker integration
There
is a known error that occurs when you close an Uncheckout confirmation dialog
box. It causes Adobe FrameMaker to hang. #CMBU00040782 (#39625) on Red
Hat Linux, Describe command displays error message when multiple files are
selected
On
Red Hat Linux, if you select multiple files before you click Report Describe in
the File Browser, the Describe window displays an error message: Workaround: The Describe window displays the correct
information when you select one file. #CMBU00040833 (#39678) on Compaq
Alpha platform, ClearCase GUIs can display font warning
When
you invoke a ClearCase graphical interface on a Compaq Alpha platform, you
may see this type of warning: Cannot convert string
-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1 to type FontStruct
You
can ignore this message because it does not interfere with the functions in
ClearCase’s graphical interfaces. #CMBU00040916 (#39764) problem
with SGI R5000 chips at revision level 1.0
If you try to execute a file built
in n32 binary format from within the MVFS, the executable or the system may
crash. The crash results from a defect in revision level 1.0 of the SGI R5000
chip. This defect has been fixed in revision level 2.1. Workaround: Upgrade your R5000 chip to revision
level 2.1. To check the revision level of your current chip, run the IRIX hinv command. #CMBU00040953
(#39803) HTML generation code uses local paths even when inappropriate
When
a file in an xcleardiff pane is rendered to a HTML browser, the HTML browser
may not be able to display the file if the browser is running on a different
host than xcleardiff.
This situation occurs when xcleardiff does not generate a pathname to the
file that is accessible from the host on which the Web browser is running. Workaround: Run xcleardiff on the machine where the HTML browser
is running. #CMBU00041571
describe -graphical cannot handle white space in path name
Attempting
to describe files whose names have shell special characters (for example, *) or spaces
from the graphical interface may fail with a file
not found error. For
example, the following describe command fails because it treats the file name
as two separate names: cleartool
describe –graphical “my file“ #CMBU00042778
cleartool commands use one date format
The output of most cleartool commands that display date information
uses an invariant format that ignores regional standards. #CMBU00043178
using Web interface with Netscape causes error messages
Clients
using Netscape Navigator may cause error message similar to the following
to appear in the web server logs:
File does not exist: /usr/atria/web/applets/com/ms/security/PermissionID.class
File does not exist: /usr/atria/web/applets/com/ms/security/PolicyEngine.class
These
error messages are harmless and can be ignored.
#CMBU00043725
change in behavior of rgy_backup causes no backup to be done and no errors
rgy_backup does not copy a new rgy_hosts.conf file to any client running the command.
To configure a new registry backup server, the rgy_hosts.conf file on the new backup host must be
edited to add the backup host name. Any subsequent runs of rgy_backup on that host cause a registry backup
to occur. #CMBU00044762
ClearCase/DDTS Integration on Linux Needs Environment Variable Defined
If
you want to use ClearCase on a Linux client, you must set the environment
variable BUGTRACK_RSH_COMMAND for the integration to work successfully with
a remote DDTS server. #CMBU00048303 lsclients command no longer shows if release is patched
Patch
information for ClearCase releases may not be correctly displayed by cleartool lsclients. Workaround: Use cleartool –ver . #CMBU00051601
Anomalous behavior when more than one user uses same snapshot view from same
user account
Anomalous
behavior can result when more than one user uses the same snapshot view from
the same user account. This usage pattern is neither recommended nor supported
for snapshot views, and the results are not guaranteed. #CMBU00051283
Link-time failures for some example programs on UnixWare
When
using the C++ compilation system 3.1, some example programs will fail at link
time with an error message similar to the following: attempt to load old C++ object /usr/atria/shlib/libatriasum.so.
# CMBU00052228 Problem with mounting a non-ClearCase related filesystem
from within a view on Linux
Problem: If you mount a non-ClearCase
file system, such as cdrom, ext2, etc., from within a view, that now-mounted
file system is not visible from outside that view. For example, if you mount
the cdrom while inside a view the cdrom contents are visible from only that
view. This
occurs on Red Hat 6.2 Linux and Red Hat 7.0 Linux systems. Explanation:
The observed behavior is a result of a difference between Linux and Unix.
Linux does all of its lookups through a cache of directory names. Inodes
are accessed from these directory entries. This means that file accesses
are tied to your directory name space. When you are set to a view, you have
effectively changed the root of your process to /view/<viewtag>.
This then is linked to the real system root. However, even though it isn’t
visible to you, your namespace still has the /view/<viewtag> prepended
to it. Therefore, when you are set to a view and you mount /dev/cdrom onto /cdrom, for example, you have actually mounted
the device on /view/<viewtag>/cdrom. The MVFS maintains a shadow file system
under the view namespace that redirects file references, when possible, to
the actual underlying file. However, the mount code directly calls into the
MVFS only if it is mounting an MVFS filesystem. There is no way of trapping
and redirecting the mount request since the mount itself is handled by the
cdrom’s filesystem. If the cdrom is mounted outside of a view, it is
also visible inside the view. However, if the cdrom is mounted from within
the view, it is visible only by using the full view-extended pathname to the
mount point. # CMBU00052242 Deliver Operation may fail on UnixWare when file descriptor
limit is less than 128
Under some circumstances, a UCM deliver
operation run from the GUI may fail on UnixWare 7.1.1 systems. To ensure that
this will not occur, please check that the file descriptor limit is set to
128. You can use the limit command from a C shell or an equivalent command
to check or set process resource limits. #CMBU00052325
ClearCase Integration with Forte for Java not available on Linux
The
Rational ClearCase integration with Forte for Java is not available for Red
Hat 6.2 Linux and Red Hat 7.0 Linux. This is because of a defect in Sun’s
Java Virtual Machine implementation that interferes with command line processing. #CMBU00055513
Netscape doesn’t list integration stream when creating a UCM project
view
When creating a UCM integration view, the stream
it will be attached to, and any existing web views for that stream, are displayed
in Internet Explorer, but not in Netscape Navigator, due to limitations of
the support for dynamic HTML in Navigator 4.x.
#CMBU00056755 limitations on
deliver/rebase status display when using Netscape Navigator
On
Internet Explorer and above, deliver and rebase status is indicated by incremental
updates to the status text area, the transcript, and the file listing area,
as data is received from the server. Because of bugs in Netscape Navigator
4 which causes the browser to crash when partially occluded, the file listing
area cannot be updated incrementally (that is, changes to checkout and merge
state cannot be updated incrementally). When using the ClearCase Web interface
through Netscape Navigator 4, the file listing area is updated after each
major phase of the deliver/rebase request has completed.
#CMBU00056810 UCM pre-defined
queries are broken when upgrading to package UCM3.0 or UCM4.0
The
UnifiedChangeManagement package has six pre-defined public queries,
-- UCMUserQueries\UCMProjects -- UCMUserQueries\MyToDoList -- UCMUserQueries\ActiveForUser -- UCMUserQueries\ActiveForProject -- UCMUserQueries\ActiveForStream -- UCMSystemQueries\UCMCustomQuery1 Two
of the above queries are used by UCM/ClearQuest integration, UCMCustomQuery1
and MyToDoList.
In UCM1.0 and UCM2.0 Package, query
MyToDoList is defined as:
AND
ucm_statetype in (’Active’, ’Ready’)
Owner = ’(CURRENT_USER)’
Upgrading to the UCM3.0 package requires
the AMStateType 1.0 package; after applying the AMStateType 1.0 package,
the field ucm_statetype no
longer exists (using am_statetype instead). But since the pre-defined
queries in UCM 3.0 do not reflect this change, they do not perform the expected
functions. This problem is corrected in the UCM 4.0 package
shipped with ClearQuest Version 2002.05.00. To correct the problem in UCM
3.0, replace occurences of ucm_statetype with am_statetype where they appear, using the same
values that were associated with the previous field name. For example, the
MyToDoList query should be defined as AND
am_statetype in (’Active’, ’Ready’)
Owner = ’(CURRENT_USER)’
#CMBU00056997 Netscape browser
crashes if window is resized
When running the Web interface from
a Netscape browser, avoid resizing the browser window during operation; this
can cause Netscape to crash.
#CMBU00057114 interoperability
issues running UNIX Web server and Windows ClearCase Web client
When
entering a version identifier as an Advanced version-selector in the Welcome to Merge Manager page,
you must use forward slashes (/) if the Web server is running on UNIX. If
the Web server is running on Windows, you may use either forward (/) or backward
(\) slashes.)
#CMBU00057168
occasional problems using ’Back’ button on Netscape 4
When
using the ClearCase Web interface on a Netscape 4 browser, use of the browser’s Back button
can cause unintended results in the Web user interface.
#CMBU000 57847 Install scripts
may abort when an obsolete German locale is specified
added
at 5.0 NR
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.
#CMBU000
57983 Javascript error when navigating to certain directories with symlinks
In
the ClearCase Web interface, when you browse to a directory that contains
a symbolic link with a backslash (’\’) in its link text, a Javascript
error is displayed.
Workaround: Change symbolic links to use forward
slashes instead. (Forward slashes work with both Windows and UNIX clients.)
#CMBU000
59621 Netscape not supported for use with ClearCase Web on SGI6
Netscape
on SGI IRIX 6.x systems is not supported for use with
CCWeb.
Problems
Fixed in ClearCase Version 2002.05.00
Table 1 lists significant problems in previous ClearCase
releases that are fixed in this release. Table
1 ClearCase
Problems Fixed in This Release
|
|
|
(#26478)
some Merge Manager menu selections not enabled during use |
|
(#28184)
xclearmrgman limitations |
|
(#29143)
Merge Manager does not detect changes to VOBs |
|
(#29438)merge
from window displays incorrect branch list |
|
(#29503)
uncheckout and refresh causes Merge Manager to display bad data |
|
(#29616)
possible to install /usr/atria when this is a mount point |
|
(#30193)install
fails if /etc/nsswitch.conf has services set to files |
|
(#36719)
Merge Manager does not allow selection of an activity |
|
(#38056)
UCM: cannot convert unmodified read/write |
|
(#38327)
Merge Manager cannot be displayed before displaying status |
|
clearmrgman
does not find elements that needed merges. |
|
xclearcase
fails on dual-headed Solaris machines |
|
‘fill
error’ is displayed from clearmrgman. |
|
(#39688)
Find Wizard in Merge Manager does not display branch and label information
in snapshot views. |
|
(#39784)
ClearCase-ClearQuest integration requires printenv command in user’s path. |
|
z_type
managers broken for filenames with embedded blanks |
|
using
ClearCase Web Interface, problem overriding primary group |
|
Attache
client removes read-only attribute, even if it cannot overwrite a file |
|
Attache
4.1 helper causes edcs, find, findmerge, update commands
to fail |
|
clearmrgman
does not merge elements |
|
xclearcase closes abruptly on report of checkouts |
|
add
to source control not recursive |
|
UCM:
status bar clipping top off some informational messages |
|
view_sr
fails if view already references new and old replica |
|
Restrictions
on using ClearQuest security model with UCM |
|
problem
with clearmake parallel builds |
|
view_server
errors due to fopen being limited to 256 file descriptors |
|
mvfs_periodic_maintenance
garbage collection was inadvertantly turned off causing a performance slowdown
over time. |
Disposition
of Previously Reported Problems
Table 2 lists the status of problems reported in previous
releases. Table
2 Disposition
of Problems in Previous ClearCase Releases
|
|
|
|
|
(#15536)
do not share Purecaches within ClearCase |
|
Fixed
in earlier release. |
(#15854)
default –notify argument incorrect in vob_snapshot_setup |
|
|
(#23062)
problem using dtpad editor on systems running CDE |
|
|
(#25628)
view profile wizard fails if there is no existing local copy of a global label
type |
|
Moved
to Administrator’s Guide |
(#26665)
avoid ‘:’ usage in an environment that requires UNIX/Windows interoperation |
|
|
(#27994)
two licenses per user required under some conditions |
|
Moved
to online Platform-Specific Guide |
(#29217)
changes to ClearCase SoftBench Integration at SoftBench 6 |
|
Moved
to online Platform-Specific Guide |
(#29563)
resize of Merge Manager xterms can cause bad data |
|
Moved
to Command Reference |
(#32140)
lslock may not show locked global types |
|
|
(#32429)
cannot use clearimport –nsetevent on datafile created by clearexport_ccase |
|
|
(#33502)
problems with update –graphical command |
|
|
|
|
|
(#34584)
rmview may write benign messages to error log |
|
Moved
to Command Reference |
(#34909)
rebase silently resets activity in a view |
|
|
(#34929)
using the Version Tree Browser, cannot open a file from within a snapshot
view |
|
|
(#35653)
cannot update promotion level from Policy page |
|
|
(#36091)
limitation on xclearcase operations on VOB root directories |
|
|
(#38023)
rebase –cancel doesn’t reset config spec |
|
|
(#38189)
trying to access disabled Excluded Users list may lock system |
|
|
(#38217)
describe/lstype/lshistory of an eclipsing ordinary type incorrectly forwards
to global type |
|
|
(#38501)
View Creation Wizard displays ‘switching project context” error |
|
|
(#39081)
rebase error falsely implies corrupted VOB or view |
|
Moved
to Command Reference |
(#39205)
clients not updated cannot use degraded mode to locate the new registry server |
|
|
(#37817)
findmerge and Find Wizard cannot traverse symlinks in snapshot views |
|
|
(#37678)
canceled rebase causes incorrect view behavior |
|
|
(#39806)
on Solaris Intel, Red Hat Linux, and IRIX platforms, History Browser appears
different in snapshot views tutorial |
|
|
Linux
Token Ring support (sysutl_my_ieee_hostid on Linux if no ‘eth0’ network
card) |
|
|
using
the Version Tree Browser in a snapshot view, problem doing a graphical merge |
|
|
Attache
Helper memory corrupted when reading large directory |
|
moved
to Administrator’s Guide |
view
server does not treat non-local root users as root |