George James Software logo

KB0054

What Considerations should I be Aware of when More than One Logical Location Maps to the Same Physical Location?

Applies to: VC/m

VC/m can be configured so that more than one logical location maps to the same physical location or locations. For example, there may be the main multi-version library location called LIBRARY and also single-version library locations called RELEASE1 and RELEASE2.

Moving from a Single-version Location

When VC/m moves an object from a single-version location, it performs the following actions:

  1. Get the components from the 'from location'.
  2. Put the components in the 'to location'.
  3. Delete the components from the 'from location'.

If the 'to location' and 'from location' map to the same physical location, the transfer will delete the components from the location as the last stage of the transfer!

Assuming that the desired effect is to remove the object from the 'to location' without deleting the components, use the following:

Instead of setting up a Move, set up a Copy route, which de-activates the version in the 'from location'. To do this, enter the location name, prefixed with a minus sign, in the new active locations field.

Copying a Location

In the 'Copy' option under 'Location maintenance', VC/m will not copy from a 'to location' which maps to the same physical location as the 'from location'. If you wish effectively to rename a location, see article KB0055 for information on how to do this.

Last reviewed: Jan 20, 2005

Back to top