To register a component without checking it in, you need just to create a transfer route which doesn't move the master location to the library. As you probably don't want /need a second copy of the component at this time, you can just create a transfer route which does nothing at all.
Create a transfer route from your development location to itself.
| Function code | It is best to use a new function code, eg REGISTER. If a value other than "XFER" is used, VC/m menus must be customized with new menu options which initiate transfers using this function code, eg ^%vc220("REGISTER") instead of ^%vc220("XFER"). |
|---|---|
| From location | The development location. |
| To location | The same development location. |
| Access codes | A list of access codes, separated by commas, for the groups of users who will be able to register objects using this transfer route. |
| Dependencies | None. |
| New active locations | None. |
| New master location | None. |
| Copy /move (Transfer type) | This should be Copy (or C in the character-based interface). |
| Create new version? | Leave this box unchecked (or enter N in the character-based interface). |
| Audit trail level | Enter a low number (eg 10) to indicate that this is a significant event. A high number (eg 90) indicates a less important event. |
| Audit trail message | Enter the text of the message that you would like to see in the audit trail for this event, eg "Component /object registered". |
| Comments | When a system has a large number of complex transfer routes, it can be helpful to add a comment here to help understand the purpose of the transfer route at a later date. |
| Copy only if changed? | Leave this unchecked (or enter N in the character-based interface). |
| Status date behavior | Enter Hide to hide the status date prompt (or H in the character-based interface). |
| Status date caption | Leave this blank. |
| Function caption | Enter the caption to be used for the menu options in the browser interface. Prefix the hot key with '&', eg "&Register". |
If you are using an editor which has been integrated with VC/m (such as Serenji), configure it so that creation /editing of unregistered components is permitted. For example, for Serenji, do the following:
do setup^%vc670 VC/m - Serenji Interface Setup VC/m - Allow editing of unregistered components? <N> Y VC/m - Allow editing of uncontrolled namespaces/UCIs? <Y> VC/m - Installation complete
Or if you are using the Serenji off-line interface:
do setup^%vc690 VC/m - Serenji Interface Setup - Includes advanced off-line support VC/m - Allow editing of unregistered components? <N> Y VC/m - Allow editing of uncontrolled namespaces/UCIs? <Y> VC/m - Installation complete
To register a newly created component, go to the Component view within the appropriate Development location. Select the component and drag it to the registration location. A normal transfer dialog box will appear where you will need to enter a change request and check the other registration information. Once completed, the component will be registered with VC/m but will have a checked-out state which allows it to be further edited in the development location.
Last reviewed: Nov 23, 2004
Copyright 1997, 2005 George James Software.