The VCS Integration feature does not work with all files in the Integration Server directory structure. When you check out a package or element from the VCS repository, you must use the VCS client to manually check out any of its associated unsupported files that you want to work with, such as:

If your package contains C/C++ services, you must check out those services manually with your VCS client and rebuild those services (for example, recompile the program to generate the DLL).

Although packages and folders are never shown as checked out in the Package Navigator view, you can apply the Check Out command to a package or folder to check out all of the elements within the package or folder.

When you check out a package or element from ClearCase, the check out is performed on the branch of the package or element that is currently present in the underlying view.

When you check out an individual Java service, all coded services in the folder containing the Java service are checked out. If, for example, the folder contains three Java services and a C service, all four services are checked out when you check out any of the three Java services. When you check in any of the Java services in a folder, all coded services in the folder are checked in.

If a package or element does not exist in the VCS, applying the Check Out command adds the package or element to the VCS repository. For more information about this behavior, see Adding New Packages and Elements to a VCS.

Although the Check Out command can be applied at the package and folder level, the check mark is not applied to package and folder icons, only to the checked out elements within the package or folder.