IBM DevOps Code ClearCase 11.0.1

If both the ClearCase AI Assistant (read-only documentation) and the ClearCase Toolbox (which can execute ClearCase commands) are connected in the same IDE session, a question intended only as a documentation lookup can occasionally be routed to the Toolbox and run as a live command instead of being answered from the docs, or vice versa.

Workaround: For documentation lookups, keep only the ClearCase AI Assistant enabled in the session, or name the intended server explicitly in your request (for example, "using the CC AI Assistant"). Avoid running both servers together when you only need documentation answers.

-

For some questions, mostly about command options for whose names are shared across many ClearCase commands, the assistant may return an answer that sounds confident but is inaccurate, for example, stating that a valid command option doesn't exist or citing documentation text that doesn't quite match the source.

Guidance: Treat the assistant's answers as a helpful starting point rather than a final authority, especially for exact command syntax and options. For critical commands, confirm against the official ClearCase reference documentation. Rephrasing the question (for example, including the full command name) can improve results.

-

When the assistant checks out a file, edits it, and checks it back in, the check-in can sometimes happen before the edit has been fully applied and saved. When this occurs, the version checked in does not contain the intended change - the file looks complete but is missing the new logic, and extra unnecessary versions may be created. Importantly, in Visual Studio, an AI edit is not saved to disk by clicking "Apply" in chat alone. The change is only written after you also click "Accept all changes" in the Visual Studio editor. It's easy to assume "Apply" is sufficient.

Guidance: Before allowing a check-in, make sure the edit is fully persisted - in Visual Studio, click Apply in the chat and Accept all changes in the editor. After check-in, confirm your change is present in the new version.                                                                           

-

During AI-assisted flows, a file can be checked in automatically—after code generation or when a check-in is requested—without first asking you to confirm. Because whether you're prompted depends on the AI flow, it is not consistent. This can result in code being checked in before you've reviewed it.

Guidance: Review generated or modified code before allowing a check-in. Be aware that a check-in may proceed without an explicit prompt; if you want to review or edit first, do so before requesting any operation that could lead to check-in.

-

When ClearTeam Explorer is started on Linux and the ClearCase bin directory is not included in the PATH environment variable, you will be blocked from creating an automatic view because the Automatic button will be greyed out on the Create View dialog and on the Join Project wizard. To work around this issue: Add /opt/rational/clearcase/bin to the PATH environment variable and then restart ClearTeam Explorer.

Occasionally deleting a GitView from the UI will fail, and an error will be reported to the user. Future operations for other GitViews hosted on the same server may report additional errors. Should such an error occur, an administrator can log in to the backend server and run "sudo systemctl restart gitview" to resolve future problems.

7262910

Executing a "git mv" of a directory might leave one directory checked out in the backing ClearCase snapshot view, preventing deliver and rebase operations in the view. Users can fix the issue by logging into the backend server and checking in the directory within the context of the backing snapshot view.

7262926

On Linux s390x, IBM Installation Manager hangs displaying the splash screen. To work around this issue, use the -noSplash option to IBMIM or set the environment variable SWT_GTK3 to 0 before starting Installation Manager.

While setting up a profile with the IBM HTTP Server (IHS) plugin enabled on WebSphere Application Server 9.0.5.19, it is not possible to establish an SSL connection between IHS and WebSphere profile because the configuration management system (CMS) keystore plugin-key.kdb file is missing. To work around this issue, run this command to install iFix 9.0.5.0-WS-WAS-IFPH60850 on WAS_9.0.5.19. For example:

C:\Program Files\IBM\Installation Manager\eclipse\tools>imcl.exe install 9.0.5.0-WS-WAS-IFPH60850 -repositories C:\iFix\9.0.5.0-WS-WAS-IFPH60850.zip -installationDirectory "C:\Program Files\IBM\WebSphere\AppServer" -log logfix.log

Once the command is completed, install ClearCase with the CCRC WAN Server option selected. The plugin-key.kdb, and plugin-key.sth files are successfully created in the location common\ccrcprofile\config\cells\dfltCell\nodes\host-node\servers\webserver1\plugin-key.kdb  .

Updating ClearCase to a newer version removes ClearQuest web from the IHS configuration.

Currently, after you have implemented the ClearCase®-Microsoft Visual Studio 2019 integration, when you try to create a new Visual Studio 2019 project from its UI, it might fail. To work around this problem, integrate with Visual Studio 2022 instead.

-

Before you upgrade to this release from IBM® Rational ClearCase MultiSite 8.0.0.3 or earlier (including 8.0) on servers that have feature level 6 VOB families, refer to this technote for important information.

Open defects

Review the list of open defects for ClearCase on the IBM® Support Portal. To view the list of open defects, go to the DevOps Code ClearCase support page and locate the Recent known issues section.

-