VC/m 2.3 Release Notes |
![]() |
Right software, right time, right place
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
Copyright 2002 George James Software
For assistance contact support@georgejames.com