This window presents additional information about
the checkout and prompts you to make a choice based on that information.
The following situations may occur:
The latest version is not the version currently
in your view
- Explanation
- The branch on which you are working can have a version later than the
one that your view is currently selecting.
In a snapshot view, the version
loaded in your view is not the latest version on the branch for either of
these reasons:
- Someone in a different view checked in a newer version since
you last updated your view.
- The version-selection rules in your config spec do not select
the latest version on the branch. This can occur if the config spec selects
versions based on a time rule, a specific label, a specific version, or some
other criterion.
In a dynamic view, the version-selection rules in your config
spec do not select the latest version on the branch. This can occur if the
config spec selects versions based on a time rule, a specific label, a specific
version, or some other criterion.
- User action
- You have the following choices:
- To check out the version currently in your view
- In the Confirm Version to Check Out window, select Current
Version and click OK. Because you can create
new versions only on the end of a branch, you must merge the latest version
on the branch with your work when you check in this version.
- To check out the latest version on the branch
- In the Confirm Version to Check Out window, select Latest
Version and click OK.
- If you check out the latest version on the branch, this
latest version can depend on changes made in newer versions of files that
are not currently loaded in your view. For example, the version of a source
file that you check out may depend on definitions added to a version of a
header file that is newer than the version loaded in your view. Consider updating
your view to get a consistent set of versions.
Remember: The update operation loads the version that is
selected by the config spec. If your config spec does not select the latest
version on the branch, when you update your snapshot view, the version loaded
in your view may not be the version you checked in. In a dynamic view, if
your config spec does not select the latest version on the branch, as soon
as you check in the new version, your view may not select the version you
just checked in.
The branch is already checked out reserved
- Explanation
- You may have a checkout status conflict.
There is already a reserved
checkout on the branch, and there can be only one reserved checkout at a time.
- User action
- You have the following choices:
- To check out the version unreserved. In the Confirm Version
to Check Out window, click Yes.
- To check out the version reserved. In the Confirm Version
to Check Out window, click No. Ask the user who did
the reserved checkout to check in the version, and then try your checkout
again.
The branch is not mastered by the current
replica
- Explanation
- If Rational® ClearCase MultiSite® is
being used, there may be mastership considerations.
You are working in a
replicated VOB. This replica (your current replica) does not master the branch
involved in the checkout.
To work on the version immediately, you must
check it out unreserved and nonmastered. Before you can check in your work,
you must request mastership of the branch. You may need to merge your work.
If
you do not need to work on the version immediately, you can request mastership
of the branch and then check out the version reserved after the mastership
change is imported at your current replica. With this method, you do not need
to merge your work.
- User action
- You can check out the version unreserved and nonmastered, or you can check
out the version reserved.
To check out the version unreserved and nonmastered,
do one of the following in the Confirm Version to Check Out window:
- To request mastership of the branch later, click Yes.
The version is checked out. Before you can check in your work, you must request
mastership of the branch and (if required) perform a merge.
- To request mastership of the branch immediately, click Request
mastership of the branch and click Yes.
The version is checked out and the Request Mastership window opens. Click Request
Mastership. After the mastership change is imported at your current
replica, you can check in your work. A merge may be required.
To check out the version reserved, do the following in the Confirm
Version to Check Out window:
- Click Request mastership of the branch and
click No. The Request Mastership window opens. Click Request
Mastership. After the mastership change is imported at your current
replica, you can check out the version reserved.