![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
CM > Checkin (Apex/ClearCase)Elements under Apex/ClearCase control must be checked out to be modified and then checked in when modifications are complete. You can place an object under control by using the CM > Make Element (Apex/ClearCase) command.
The Control > Checkin command creates a successor to a version that was perviously check out in the current view by copying the contents of the checked-out view-private file to the VOB database and then deleting that file. A checkin event record is created. Only elements can be checked in.
After the element is checked in, your view typically selects the version you just created. However, it is possible that your view will select another version (perhaps on another branch). In this case, check in displays a warning message.
Check In of Reserved and Unreserved Check Outs
At the time you enter a Check In command, there may be several check outs of the same version. At most one of the check outs (perhaps yours) is reserved -- all the others are unreserved. Your Check In command succeeds in either of these cases:
- yours was a reserved checkout
- all checkouts were unreserved, and no one has checked in a successor version
If the command fails because someone else has a reserved check out, you must wait until that check out is resolved, with a CM > Check In or CM > Uncheckout (Apex/ClearCase) command. If the command fails because someone has checked in a successor version ahead of you, you can check in your work now, by:
- executing the CM > Merge (Apex/ClearCase) command to merge from the current LATEST version on the branch to your checked-out version
- entering the command again
Checkin of Derived Objects
You can checkin a derived object to make it a version of an element (a DO version). By default, both the data and configuration record of a derived object are checked in.
Permissions and Locks
The Checkin command performs the following permission checks:
- If the element's set-UID bit is set, only the element's owner, the VOB owner, or the root user can perform a check in.
- If the element's set-GID bit is set, only a member of the element's group, the VOB owner, or the root user can perform a check in.
- For all elements, an error occurs if you are not the user who checked out the element, the element's owner, the VOB owner, or the root user.
Even if you have permission to execute this command, it fails if any of the following objects have been locked:
- VOB
- element type
- branch type
- element
- branch
- pool (file elements only).
When you choose the CM > Check In command, the ClearCase Check In dialog box appears.
ClearCase Check In Dialog Box Fields:
Objects to Check In field:
Specifies the name of the objects (can be files or directories) you want to check in to Apex/ClearCase. Use the Add input field to add additional file names to the Check In list field. Use the Remove or Clear button to delete entries from the list.
Comment options radio buttons:
- No Comment
Use the check out comment (creatied by the CM > Checkout (Apex/ClearCase) command or automatically generated to record changes to a checked-out directory) if it exists. This will override the default comment specified in $HOME/.clearcase_profile.
- Comment.
When selected, displays a comments text box. The entered text will override the default comment specified in $HOME/.clearcase_profile.
- Comment file
When selected, displays a Comment Filename file selection field. The contents of this file will will override the default comment specified in $HOME/.clearcase_profile.
View Private File Disposition radio buttons:
- Keep current contents in view-private file(s)
Saves the contents of each checked-out version in a view-private file, in addtition to creating a new version. The view-private file is named file.keep.
- Remove view-private file(s)
Removes each view-private name file after creating a new version.
Suppress warning messages check box:
The default is to display all warning messages.
Preserve modification time of objects check box:
Do not reset the modification time to the check-in time. This option allows the objects not to be rebuilt just because they have been checked in.
Force check in even if identical check box:
Checks in the object even if the predecessor version is identical to the checked-out version. By default, the check in operator is canceled in such cases.
Additional Topics
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |