Configuration information for PVCS Version Manager

The PVCS Version Manager is a client only type SCM tool, which can run on multiple platforms. NT shares or SAMBA shares can be used to distribute the controlled files across a network. PVCS also has a VM server, which can be used in a server based environment. The setup is almost identical for the two products, except that with the server based product some of the NT share or samba share techniques discussed in the section on how to use UD6/CMtool Driver with eChange Man would have to be used.

These examples are all using the Win32 based PVCS Version Manager.

• Install PVCS Version Manager according to the installation guide provided with it.
  
  
• Create a shared network directory (eg: on an NT server) for the work files. This will be the place that you create the initial load of source code, and in future where source code that is ‘checked out’ will reside.
  
  
• Share the created directory as ‘workfiles’, allowing full read-write access.
  
  
• Connect a drive on an NT Workstation to the NT share ‘workfiles’ (we have used drive M:)
  For the purposes of the demonstration at this point, the default directory of the shortcut used to start the IDF should be m:\ (the drive where the sources have been loaded).
  
  
• Install PVCS Version Manager on this workstation if it has not been done so far. (It is possible to install PVCS Version Manager on a shared file system, but it must be individually installed to each workstation).
  
  
• Install Uniface and UD6/CMtool Driver on to the NT Workstation.
  
  
• Alter the usys.ini and usys.asn files as per the Guide to Installing UD6/CMtool driver.
  
  
• Alter the Joins File (in the Uniface bin directory) to locate the source code on drive M:
  
  
• Alter the usys.asn file to have a ’catchall’ to direct all non-joined source code to drive M:, set the $MAXFILES and set temporary files to be stored in another database.
  
  
• Start and then close the IDF to initialise an empty repository. (For the purposes of the demonstration at this point, the default directory of the shortcut used to start the IDF should be m:\ (the drive where the sources have been loaded). The file m:\sources\other.dir\udicver.xml now exists.
  
  
• Add the nokeycheck parameter to the USYS$UD6_PARAMS setting in the usys.asn file (this setting improves the performance of the UD6 driver for bulk load operations, but must be disabled for normal use).
  
  
• Load the repository from a backup with a command like:
  
  idf /com=100 /cpy trx:7204bkp07Feb2000.trx idf:
  
  (some unix environments may require the /com=10 switch to reduce the number of file handles used).
  
  
• Alter the usys.asn file to remove the nokeycheck parameter.