Home

KB0023

What Functions will Help me to Set Up New Development Areas?

Applies to: VC/m

Setting up the Location and Transfer Route Definitions

From version 2.4 onwards, the best way to set up locations and transfer routes which are repeated according to a pattern is to use the XML configuration files. These allow you to set up templates. The files for the XML schema are in the configuration sub-directory of the VC/m installation directory. See the manual or the notes in the files for more details of how to do this.

Preparing the First Development Location for Use with VC/m

Whether the development location is an existing one, or an area which has been newly set up, it needs to be made ready for use under VC/m control. It needs to be given an up-to-date copy of the software, and the object versions at the location need to be recorded in VC/m's database.

Steps 1 and 4 are only necessary if the location already contains some or all of the components. Setting the physical locations to be uncontrolled means that VC/m will not issue an error when it tries to transfer and finds that the location contains a copy of the component which it was not aware of.

  1. In VC/m, change each of the physical locations to which the location maps to be uncontrolled.
  2. Set up a transfer route, with function code XFER, from the library location to the development location. This route should have the development location in the list of new active locations, and it should not increment the version number.
  3. Use the bulk transfer option to transfer the objects from the library to the development location. (You can use */*.h to select only the highest version of each object.)
  4. Change each of the physical locations from step 1 back to being controlled.
  5. Disable the transfer route set up in step 2 if it is not required for any other purpose, eg refreshing the development location.

If there are more locations to set up, the procedure given below may then be used.

Preparing Additional Development Locations

If there is a location which is already set up in VC/m with the object versions which are required at the new location:

  1. Ensure that no modifications are made to the source location while you are copying it.
  2. Use the normal operating system or M procedures to copy all the components to the new location.
  3. In VC/m, use the 'Copy' option under 'Location maintenance' to copy the version information from the first location to the new one.

Undoing the Copy of Another Location

If the 'Copy' option used in the previous section does not give the correct results, you can undo it as follows:

  1. In VC/m, use the 'Version' option under 'Location maintenance' to delete the version information at the location which you copied to.
  2. Use the 'Add/Modify' option of 'Location maintenance' to remove any unwanted systems which were added to the location by the copy operation.

Last reviewed: Nov 22, 2004

Back to VC/m Knowledge Base Articles