![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Control > Check Out (Apex/Summit)This command is only available through the shadowing capabilities of Apex Ada 95/83 for Windows NT.
Files under Summit/CM control must be checked out to be modified. A checked out file has read-write UNIX permissions. Files can be checked out with a reservation or checked out privately.
Checking out a file with a reservation guarantees that the file may be checked in at a later time and will not conflict with the changes of other users. Checking out a file with a reservation locks the version history.
Files can be privately checked out as well. Privately checked out files do not lock the version history. Multiple files in different views may be privately checked out simultaneously. Private check outs may even occur if the version history is checked out with a reservation. Checking in a privately checked out file may require merging to reconcile the file with changes from other views.
Checking out a file creates a new version whose contents may be either the current contents of the file or the contents of the last checked in version. When the file is checked out with a reservation the version number of the new version is one greater than that of the last checked in version. When the file is checked out privately the version is unnumbered.
The Control > Check Out command checks out a controlled file within a specific view for modification. When you choose this command, the Check Out dialog box appears.
Check Out Dialog Box Fields:
Objects To Check Out List Field
The list field displays the names of files to be checked out.
Checking out a controlled file creates a new version of the file within a specific view and within the version history for the file. The new version is frozen when you check in the file.
Use the Add input field to add file names to the list field. Use the Remove or Clear buttons to delete entries from the list.
Check Out Options Radio Buttons
If the contents of the files you are checking out do not currently match the latest version, you must select one of the radio buttons:
- Accept the latest version of each object
Changes the contents of the file to match the latest version before checking it out.
- Keep the current version of each object
Checks out the file without changing the current contents.
Note: This can cause changes made later than the current version to disappear from the latest version.
- Fail if current version is not latest
Check out does not procede if the current version of the file is not the latest version (the default).
Check Out Check Boxes
- Place objects under source control (if needed)
Makes the file controlled before checking it out. Other files that were controlled and checked in are now checked out.
- Private check-out
Causes files to be checked out privately. The radio buttons determine what happens if the file is not the latest version.
- Upgrade private check-out to full
If the file is already checked out privately, upgrades the check out to a check out with a reservation. This succeeds only if the version history of the file is not checked out with a reservation from another view.
If the previous private check out was based on the latest version, the file is checked out with a reservation and the contents are unchanged.
If the latest version was not the basis for the privately checked-out version and the radio button specifies that current contents are to be kept, the file is checked out with reservation and the contents are unchanged.
If the latest version was not the basis for the privately checked-out version and the latest contents are being accepted, the current contents are put into a file called filename.private.saved, the version that was the basis for the private check out is placed in a file called filename.ancestor.saved, and the file contents are changed to those of the latest version. The contents of the filename.private.saved file should then be merged with the current contents of the file.
- Downgrade full check-out to private
If the file is already checked out, the checked-out version is abandoned and the reservation is cancelled. The contents of the abandoned version become the contents of the privately checked-out version.
- Set attribute on checked-out versions
Set an extended version attribute on checked-out versions. Two additional fields will appear: Set Attribute and To Value. Attributes cannot be set in privately checked-out versions.
- Set Attribute
The name of the extended attribute to be set in the checked-out versions. The Alternatives icon displays the extended attributes defined for the enclosing subsystem.
- To Value
The value to be assigned to the specified extended attribute in the checked-out versions. For list attributes, values are appended. The Alternatives icon displays possible values for enumeration attributes.
Associate Tasks Field (Rational Summit/TM)
Specifies the tasks to associate with the checked-out objects. It is initialized with the current task list. The Navigate icon can be used to select a different set of tasks by activating the Select Tasks dialog. The Alternatives icon displays tasks in your "to do" task list.
Task association is not supported for private check outs.
Notes Field
To add a textual notes to the version associated with the file, enter the text of the note in the Notes field.
Shadowing Fields
These fields have been provided to give better control over shadowing when using DHCP. Most users will want the default settings for these fields. The following explanation is useful for advanced users of shadowing.
When using DHCP, the IP address for the NT machine is assigned dynamically and may be different from the one assigned when shadowing was set up. The IP address of the NT machine which contains the view being shadowed is stored on the CM repository. This address is used by the CM server to communicate with the NT machine. The Current IP Address field shows the current IP address of the current NT machine. If the corresponding check box is checked, the IP address stored on the CM repository is replaced by the new value shown in this field. This enables the CM server to correctly communicate with your NT machine even when the IP address of your NT machine has changed. If this box is not checked, the CM server will attempt to talk to the old IP address.
IP addresses on the CM server may be stored directly in the Policy/Shadow_Location file of the view or may be specified in a common file that is included in the Policy/Shadow_Location file. If the update include file radio button is selected, any included files are updated otherwise the change in the IP address is made only in the Policy/Shadow_Location file.
Command Line Interface > check_out
Additional Topics
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |