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.

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 (\).

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 abeinterface.

Workaround: Create two Bourne-shell scripts

#!/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

#!/bin/sh -p
# Optional debug line
#echo "`uname -n` : `date` : `echo $* | awk ‘{print $3, $18}'` : $$" >>
/tmp/abe_run.log
exec /bin/abe $*
exit $?

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.

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.

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.

When a ClearCase activity in a ClearQuest-enabled project 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.

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.

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.

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.

If you use the Update window (invoked 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.

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.

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.

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.

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.

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.

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.

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.

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.

There is a known error that occurs when you cancel an Uncheckout confirmation dialog box. It causes Adobe FrameMaker to hang.

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.

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"

The output of most cleartool commands that display date information uses an invariant format that ignores regional standards.

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.

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.

Patch information for ClearCase releases may not be correctly displayed by cleartool lsclients .

Workaround: Use cleartool -ver.

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.

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.

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.

The UnifiedChangeManagement package has six pre-defined public queries,

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)'

When running the Web interface from a Netscape browser, avoid resizing the browser window during operation; this can cause Netscape to crash.

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.)

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.

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.)