VC/m Features

  • Flexible configuration options allow different levels of control to suit the company culture and size of the systems.
  • Web-based interface for object transfers.
  • All development work is linked to a change request recording the reason for the change.
  • The system automatically manages concurrent development and ensures that changes are not lost or inadvertently overwritten as a consequence.
  • An object-based approach allows different components which form a natural unit to be managed together.
  • Components which can be managed include binary files, text files and all types of Caché, Ensemble and M components.
  • The version number of an object is incremented each time a new change is begun.
  • A centralized library stores reference copies of all versions of an object.
  • Old versions of objects are always available for comparison or for re-instatement if this becomes necessary.
  • The VC/m system allows one master copy for each object version and ensures that this version is used as the basis for new development work.
  • The version of each object at each location is recorded to enable the system to track and therefore control the movement of objects.
  • Different variants can be tracked simultaneously (e.g. a customer-specific amendment, English and French language versions).
  • Systems can be defined to allow simple control of objects belonging to different applications.
  • The database defines which version of each object belongs in which system and also where copies of each system are logically located.
  • Transfers provide a simple mechanism to move or copy objects from one location to another.
  • Automatic transfers can be defined which effortlessly keep multiple locations in sync.
  • The release facility provides a way of transferring objects to a remote, live location and providing installation notes for the operator responsible for the release.
  • Access security gives control over who can make which transfers.
  • Multiple objects can be transferred in a single step using the change request number.
  • Transfer route dependencies allow the system manager to restrict the circumstances under which moves are made.
  • Logical locations mean users do not need to be concerned about where on the disk the objects are actually stored.
  • Logical locations allow objects to have a different status (e.g. 'for test' or 'tested'), even though they are in one physical location.
  • Reports inform project managers of the progress of projects, work which is overdue and any concurrent development which is in progress.
  • The VC/m system records a complete audit trail for each object, showing every movement and status change which has been made.
  • Statistical reports provide a breakdown of object movements by system and by type of change request for any given period.



Request further information