5765-207 IBM Configuration Management Version Control (CMVC) Products

IBM Europe Sales Manual
Revised:  January 10, 2007.

Table of contents  Document options 
TOC Link Product Life Cycle Dates TOC Link Description
TOC Link Program Number TOC Link Technical Description
TOC Link Abstract TOC Link Planning Information
TOC Link Product Positioning TOC Link Security, Auditability, and Control
TOC Link Highlights  
 
Printable version Printable version
 

 
Product Life Cycle Dates
Program NumberVRM Announced Available Marketing Withdrawn Service Discontinued
5622-0632.03.01994/12/201994/12/30 1999/10/202001/02/01
5765-2022.03.01994/12/201994/12/30 1999/10/202001/02/01
5765-2072.03.01994/12/201994/12/30 1999/10/202001/02/01
5765-2072.02.01993/10/121993/12/31 1999/10/201995/06/30
5765-2072.01.01993/05/181993/06/25 1999/10/202001/02/01

Back to topBack to top
 
Program Number

Back to topBack to top
 
Abstract

The IBM Configuration Management Version Control (CMVC) product family is enhanced with the addition of support for IBM's DATABASE 2 AIX/6000 Version 1 (DB2/6000*) (5765-172) and the addition of a CMVC OS/2* client.

The IBM CMVC products provide application developers with configuration management and change control or versioning that is integrated with design and defect tracking for heterogeneous environments. Any CMVC Version 2 Release 2 server can support any of the four different (AIX*, Sun**, HP**, OS/2) CMVC clients.

New functions for Version 2 Release 2 include:

This product is also supported on AIX Version 4.3.
Back to topBack to top
 
Product Positioning

The CMVC products are designed for customers doing application development that need a more comprehensive solution that merges defect and change management with configuration management and version control.

The CMVC Version 2 products span multiple platforms, which allow customers to do their development on IBM RS/6000, Sun, HP, or OS/2 client workstations while utilizing the power of the CMVC Server to provide the versioning and database support. The CMVC/6000 provides support for the DB2/6000, ORACLE, INFORMIX and SYBASE databases on the RS/6000. The CMVC for Sun systems provides support for the ORACLE, and INFORMIX databases on Sun systems. The CMVC for HP systems provides support for the ORACLE, and INFORMIX databases on HP systems.

The new OS/2 client provides the same functionality as the UNIX clients but does not have the graphical browsers that were introduced for the UNIX clients in Version 2.
Back to topBack to top
 
Highlights


Back to topBack to top
 
Description

Integrated Problem Tracking and Control

The CMVC tool integrates problem tracking and design change control into one configurable process to save time and effort. A developer will not have to work with and keep two or three separate systems in synch. All the information, data and access to the source code or objects is available through an easy-to-use, intuitive graphical user interface.

Application Developer Productivity

The CMVC actions that an application developer must take while fixing a defect or implementing a feature are the same steps that an application developer would normally take. No extra effort is needed when using CMVC. Having the problem tracking functions integrated with the version control and change management functions saves time and effort.

Feature and Defect Tracking Process

CMVC strengthens the application development process within an organization as the process is defined and enforced by the CMVC tool.

Improved Application Quality

The CMVC tool ensures that none of the required procedural steps can be bypassed and makes this easy for the application developers by automatically notifying each person that must take some action or provide some input to the system. Mistakes and wasted time are eliminated when everyone that is part of the process knows exactly what to do and when.
Back to topBack to top
 
Technical Description
TOC Link Operating Environment TOC Link Hardware Requirements TOC Link Software Requirements


Functional Highlights

System Overview

AIX includes an implementation of the Berkeley Software Distribution (BSD) interprocess communications facility known as sockets.

Requests from a client are handled by the transaction processor in the server. The single point of control is the CMVC server. The client/server network interface is provided via the Sockets Application Programming Interface (API) for TCP/IP.

Multiple projects can be kept within a single family. The number of users per project is scalable. The size of project and number of users supported is constrained by the system configuration (main storage, disk storage, CPU speed), and the database configuration.

Two client user interfaces are provided:

Command Line Interface

Overview

The command line interface allows the CMVC user to perform tasks by entering commands.

In some circumstances the graphical user interface can not be used. This may be the case when the user uses an ASCII workstation (non-graphics workstation) to access the server. In this case, the command line interface is the users' only interface to the CMVC Server.

The command line interface also allows the use of shell scripts.

Graphical User Interface

Overview

The Graphical User Interface (GUI) provides the user with a graphical interface to CMVC. The following concepts are incorporated into the design of the graphical user interface:

The object-action selection model means that the user first selects an object and then selects an action to perform on that object. Standard controls such as menus and pushbuttons represent the selections. The objects represent CMVC objects. Consistent behavior implies that the set of controls and objects will always operate in the same way.

Direct manipulation with visual feedback means that the user is provided with a response that somehow represents the action taken, and it is done in real time. For example, when a button on a display is selected, the visual feedback might be that the button appears to be pressed in. Real-time feedback implies that the manipulation of objects on the display is synchronized with the motions of the device (mouse and buttons) being used to perform the manipulation. For example, the events on the display should not lag behind the motion of the mouse.

Consistent behavior does not eliminate individuality, nor does it imply rigid conformity. Much flexibility exists within consistent behavior for application developers to present their applications in the best possible light. Novice users typically make a menu selection by displaying the menu, reading the selections, and then clicking the mouse over the item they want. Experienced users make selections using a quicker method, such as entering a one-letter mnemonic or bypassing some menu levels. The specific controls such as pushbuttons and scroll bars do not represent a finite set, but rather a basic core that is expected to evolve as technology changes and users gain more experience.

Project Change Control

Checkin and Checkout

Files can be checked out with or without specifying a lock. If the file is checked out with a lock, other users are not allowed to lock the same file in the same release.

If the user who has checked out a file and made changes to the file decides that the changes would not be made for whatever reason, the lock on the file can be relinquished.

Tracking

A release is created with tracking control either on or off. A release can be modified to enable or disable this control at any time. When tracking control is off, changes to the files are not associated with the feature/defect tracking facilities of the CMVC.

Problem Tracking not enabled:

Integrated Problem tracking control:

Project Communications Facility

Automatic Notification

Users are notified automatically by the CMVC Server/6000 when their action to some event is required. Some examples of automatic notification are:

CMVC allows the users to receive information about the current project activity according to each user's interest and responsibility.

A destination address is specified when an user is created in the system. Users are notified automatically by the system when triggered by an action occurring against an object, according to the notification list, of a component in the system which can be specified by the administrator or the owner of the component.

The notification list specifies:

Project Report Facility

The report facility is a powerful project management tool that the CMVC offers. The underlying SQL relational database allows users to define their reports.

Reports can be created from within the GUI or via the command line interface.

Access and Authority

Access control is enforced according to varying levels of access authority. Access authority is granted implicitly according to object ownership or explicitly according to the component access list attached to the component which owns the object.

Actual authority levels are defined by mapping any configuration of low-level actions to an authority level. To define an authority level, any unique authority level name may be associated with a set of actions. The authority levels can be configured by the CMVC family administrator.

Security

System security can be provided by allowing no user other than the CMVC administrator to log onto the CMVC server. At a component level access to executing low level CMVC commands can be controlled on a per user basis.

Migration/Import from SCCS

Migration from SCCS

A migration tool is provided, and detailed documentation allows customers to migrate their SCCS files into CMVC.

If different projects have common files and wish to maintain that commonality within CMVC., the migration of both projects into the CMVC must occur simultaneously. Staggered migration will prevent these files from remaining common.

Migration of Problem Tracking Records

Users may wish to transfer their current development records such as work orders or problem tracking records into CMVC. Currently there is no automated facility to accomplish this. For users intending to manually enter features and/or designs that correspond to their current development tracking records it is recommended that a reference be made to the records and that the current records be archived in some manner for future reference.

Operating Environment

Not available.

Hardware Requirements

Any CMVC Version 2 Release 2 server can support any CMVC Version 2 Release 1 or Release 2 client. Client platforms for Release 2 are AIX, Sun, HP, and OS/2. An example is a CMVC server on a Sun workstation supporting AIX, Sun, OS/2, and/or HP CMVC clients.

For the CMVC/6000 Version 2 Release 2 (5765-207):

Server

Client

Note: Any Xserver supporting OSF/MOTIF 1.1 and X Windows System X11R4 can be used as a display for any RS/6000 running the CMVC client code. Examples include:

For the CMVC for Sun systems Version 2 Release 2 (5622-063):

Server

Client

For the CMVC for HP systems Version 2 Release 2 (5765-202):

Server

Client

For the OS/2 client feature for the above three products:

Minimum memory requirements:

The following are the minimum hard disk requirements. These do not include the operating system or the database.

The actual requirements will depend on the size and number of objects to be controlled by CMVC. For example, for 5000 files with 1000 defects/features approximately 150MB is required. For 30,000 files with 6000 defects/features, approximately 900MB is required.

Software Requirements

For CMVC for AIX Systems Version 2.3 (5765-207):

Server:

For users of the CMVC for AIX Systems in conjunction with SCCS, SCCS is available with the AIX operating system.

For users of the CMVC for AIX Systems in conjunction with SCCS, SCCS is available with PVCS Version Manager.

INTERSOLV PVCS Version Manager Version 5.1 for AIX must be ordered separately from INTERSOLV Inc.

Client:

Server:

Client:

For CMVC for SunOS Systems Version 2.3 (5622-063):

Server:

For users of the CMVC for SunOS Systems in conjunction with SCCS, SCCS is available with the Sun operating system. CMVC for SunOS systems does not support INTERSOLV PVCS Version Manager.

Client:

For CMVC for Solaris Systems Version 2.3 (5765-397):

Server:

For users of the CMVC for Solaris systems in conjunction with SCCS, SCCS is available with the Solaris operating system.

CMVC for Solaris systems does not support INTERSOLV PVCS Version Manager.

Client:

For CMVC for HP-UX Systems Version 2.3 (5765-202):

Server:

For users of the CMVC for HP-UX Systems in conjunction with SCCS, SCCS is available with the HP-UX operating system.

CMVC for HP-UX Systems does not support INTERSOLV PVCS Version Manager.

Client:

For the OS/2 Client Feature for the above products:

For the DOS/Windows Client Feature for the above products:

The OS/2 or DOS/Windows client feature works as a CMVC client with, and requires, one of four CMVC servers (AIX, Sun, Solaris, or HP) as a corequisite.
Back to topBack to top
 
Planning Information

Customer Responsibilities

Direct Customer Support:

Services for CMVC can be provided by the local Systems Engineer or by the AIX Systems Center (ASC) in Dallas, Texas. Services provided by the ASC on a fee basis include, but are not limited to, such items as the following:

Compatibility

The IBM CMVC Version 1 products CMVC Server/6000 (5765-039), and CMVC Clients (5765-069) are not compatible with the IBM CMVC Version 2 Products CMVC/6000, CMVC for Sun systems, and CMVC for HP systems (5765-207, 5622-063 and 5765-202).

The IBM CMVC Version 2 Release 1 products are compatible with each other such that each CMVC server (AIX, Sun or HP) can support any or all CMVC V2 Release 1 clients; however, the IBM CMVC Version 2 Release 1 products will NOT support the Version 2 Release 2 OS/2 client feature. Version 2 Release 2 level servers are required for this client as a co- requisite.

The IBM CMVC Version 2 Release 2 products are compatible with each other such that any CMVC server (AIX, Sun or HP) can support any or all of the CMVC Version 2 Release 2 clients (AIX, Sun, HP, OS/2).

CMVC Version 2 Release 2 server code will also support the Version 2 Release 1 clients.

Limitations

The IBM CMVC Version 2 Release 2 products CMVC/6000, CMVC for Sun systems, and CMVC for HP systems have a dependency on a relational database: either IBM's DB2/6000 (supported by CMVC/6000 only), Oracle, INFORMIX-OnLine or SYBASE (supported by CMVC/6000 only) and their related products.

Conversion

A database migration script is provided to migrate the database tables for Oracle, Informix or Sybase AIX databases to DB2/6000 for CMVC from CMVC/6000 Version 2 Release 1 (5765-207) to CMVC/6000 Version 2 Release 2.
Back to topBack to top
 
Security, Auditability, and Control

These programs use the security and auditability features of the operating system and the relational database management systems.

Additionally, usage control for UNIX users is maintained by NetLS.

Data integrity is provided by the CMVC server in conjunction with the relational database manager system.

User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.

Trademarks

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.

Windows is a trademark of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
 © IBM Corporation 2007.
Back to topBack to top