Taking control in PVCS Version Manager
As a way of introducing PVCS Version Manager, we'll go through a typical work-session using it. . The first thing to understand is that PVCS Version Manager stores all files in archives, and any files that are "checked out", in a workfile area.
Before continuing, ensure that the
nokeycheck parameter has been removed from the USYS$UD6_PARAMS setting in the assignment file, otherwise the driver will not work correctly.
Prior to loading your source into PVCS Version Manager, it is wise to compile all objects and forms, eg:
This ensures that all the descriptors have been generated for the forms. Without this information you will not be able to compile forms in the CM tool since they will be read-only and the descriptors cannot be generated (see the nodeny parameter in the USYS$UD6_PARAMS help topic).
For the same reasons you may wish to start up the IDF and select the Assembly Area, then the Assembly Workbench.
Clicking on this ICON will start the initial synchronisation of signatures and diagram.
Create and load a project
Finish taking control
How to use the driver with PVCS Version Manager (cont.)
Releasing a form using PVCS Version Manager
Checking a form in using PVCS Version Manager
Adding a form using PVCS Version Manager
Finding the differences in versions using PVCS Version Manager
Procedures for handling compiled objects with Version Manager
Problems when using PVCS Version Manager
A methodology to Uniface source code control
|$Revision: 1.13 $ $Date: 2011/02/28 02:56:33 $||[go to top]|