Home

VC/m 2.3 Release Notes
  1. GT.M on Unix
    This version of VC/m includes support for GT.M on Unix. It has been fully tested on RedHat Linux. It is expected that it will work on most other standard Unix platforms. All major components of VC/m have been tested except for the task server which provides connectivity between non-networked and hybrid M implementations. Drivers exist for GT.M on OpenVMS but have not been tested.
  2. Component Add/Remove/Delete
    It is now possible to add or remove Components to or from Objects using the web interface. A component is removed (unregistered) or deleted by selecting the component and then pressing the Delete key (or using the Edit/Delete menu option). If the component is currently registered then this operation will unregister it. This can only be performed at the location to which the object owning the component has been checked out. Deletion of an unregistered component will physically delete it, after obtaining user confirmation.

    Multiple Components can be added to existing Objects by first dragging each Component from within the component view and dropping it over the Work List button in the menu bar (or by selecting the Component and pressing Ctrl+C). Then, by selecting an Object from the location's object view and clicking the Work List button (or by pressing Ctrl+V), the Components stored in the Work List button are added to the selected Object.

  3. Object Add/Remove to/from Change Request
    It is now possible to remove Objects from Change Requests using the web interface. Select the Object within the Change Request and then press the Delete key (or use the Edit/Delete menu option).

    Multiple Objects can be added to Change Requests in the same way as Components are added to Objects. An object may be selected and dragged & dropped over the Work List button or copied there by pressing Ctrl+C. After selecting the Change Request, clicking the Work List button or entering Ctrl+V will add the Objects to the Change Request.

    The Work List button will hold either Components or Objects but not both simultaneously. For example, collected Components are cleared from the list as soon as an Object is copied there.

  4. Installation Script
    The ^%vcins installation script has been improved in a number of areas. The M implementation and Operating System choices are stored and used as defaults for subsequent invocations. Additional set-up questions are asked to allow quick configuration of new and optional features. A VC/m account is created automatically for the user running the installation script for the very first time.
  5. Access Codes
    The format of User, Transfer Route and Location access codes has been extended. Previously they were restricted to a list of single-character codes. They can now be a comma delimited list of alpha-numeric strings of any length. For example, a user might previously have had an access code list of MDT meaning that they had access rights for the roles Manager, Developer and Tester. Now it is possible for a user to be given an access rights list of MANAGER, DEVELOPER, TESTER. Existing access rights are automatically upgraded to the new comma delimited format.
  6. Component View of Library Locations
    The component view of Library locations has been implemented. The list of components that exists within a Library can now be viewed and are shown with their correct status. Components can also be selected from this view and checked-out or transferred as with components in other types of location.
  7. Integrity Check
    When running an integrity check you can now specify the frequency with which the progress message appears. The default is every 100 records, reproducing the behavior of earlier VC/m versions. Setting a value of 0 suppresses the progress message entirely, which is often useful when using the Show option to direct the report to the screen.
  8. Bug Fixes
    • On Unix servers, when components were auto-registered by dragging them to a VC/m location using the web interface the components file extension was not being treated as case sensitive. This, in rare circumstances, could result in a bad object definition being created.
    • Location Maintenance is now able to display information about the expected format of the Physical Address. Some location drivers have been enhanced to provide this information, making it easier to know what format physical address is expected when creating new locations.
    • A bug has been fixed in Location Maintenance that caused an infinite loop if the user pressed CursorDown or PageDown and the Location referenced a physical directory or namespace that was currently not valid.
    • On configurations using the serverLink web gateway reports that are generated in spreadsheet form were not being created with the correct http headers. This has now been corrected.
    • When a user connected to VC/m using the web interface without using built-in web-server authentication then the user id was not being converted to the correct case, resulting in a variety of errors. This has now been fixed.
    • A bug has been corrected in the Load function which could cause unpredictable results if a routine contained a backslash character in its first line. When Load is used for non R-type components it will now always use the component name as the Object description rather than try to use the first line of the component. If the component was a binary file this produced amusing results.
    • On the web interface, if a component was auto-registered by dragging it to a Library from the component view of a developer's sandbox, then the component is updated to reflect its new status. In this situation the component's tool-tip was being double-escaped.
    • On Caché platforms, an undocumented feature of Caché is that it will not allow write access to any file name CACHE.DAT or CACHE.EXT. This prevented VC/m from being able to manage files with these names. A strategy has been adopted within VC/m that allows files with such names to be managed transparently. This is achieved by writing the file with a different name and then renaming it when the file is closed.
    • Dragging items within the web interface now works correctly according to the source and target box sizes.
    • The off-line editor interfaces for Caché Studio and Serenji now work as intended. A maintenance utility, rebuild^%vclM (that is a lowercase "L", not the digit "one") can be run in any VC/m-managed namespace/UCI/directory in which off-line editing might occur. This recreates the ^vcvp("rw") subtree used by the off-line editor interfaces. We recommend that this is done once in each such place after upgrading from an earlier version of VC/m.
    • Configuration entrypoints are now present in the two Caché Studio interfaces (setup^%vc620 and setup^%vc800 for the regular and off-line interfaces respectively), and in the two Serenji interfaces (setup^%vc670 and setup^%vc690 for the regular and off-line interfaces respectively). Off-line settings are now stored in ^vcvp, which is private to each namespace/UCI/directory. Consequently the off-line configuration entrypoint should be run in each off-line location.