PVCS_SS

PVCS_SS.exe converts a PVCS project or file into a VSS project or file.

VSS and PVCS use different internal file storage methods, so PVCS users cannot simply switch to using VSS; they must first extract all PVCS log files and enter them into VSS projects.

You can convert a project manually by getting a PVCS file and then adding it to VSS. However, there are disadvantages: It takes a lot of time and is error pron since it does not retain file histories and comments; only the latest version of each file is converted.

PVCS_SS.exe provides an automatic solution. It converts PVCS log files into VSS files, with histories and comments intact.

Note Only the VSS administrator can run PVCS_SS.exe.

Preparing to run PVCS_SS.exe:

Back up your PVCS project files and VSS database.
Make sure both PVCS and VSS are fully installed on your system. PVCS_SS.exe does not replace the installation process for VSS; it is run after VSS installation.
Log on to VSS as the Admin user. The best way to do this is by setting environment (operating system) variables at the command prompt. SSUSER and SSPWD are environment variables that indicate your username and password, respectively. For example:
```
Set ssuser = admin
Set sspwd = hoof
```
By default, the VSS administrator is not assigned a password; specify a password only if you have assigned Admin a password.
Make sure that the PVCS folder (where executable files such as Get.exe and VLog.exe are located), and the VSS folder, are both on your MS-DOS path. While adding these folders to the path is not required, it makes running PVCS_SS.exe easier.

You are now ready to run the PVCS_SS.exe and convert all your files.

To run PVCS_SS.exe:

Change to the folder where the PVCS log files are located.
PVCS log files store all your data, comments, histories, and so on. In general, they are named with the extensions that your filenames use, terminated with a V, so that Test.C becomes Test.C_V, and Test.pas becomes Test.pav. However, the PVCS configuration setting LOGSUFFIX can change the log file extension name.
Type PVCS_SS <PVCS logfiles> <VSS project>
The destination VSS project name must start with a dollar sign ($). Otherwise, this variable is assumed to be a PVCS log file. A few examples are given below.
```
PVCS_SS *.??V $/Project
PVCS_SS TEST.C_V TEST.H_V $/Test
PVCS_SS *.PAV TEST.TXV $/
```
Repeat steps 1 and 2 for all PVCS log files you want to convert.

Remarks

The filename in VSS is not the name of the PVCS log file; it is the name of the PVCS work file, that is, the real name of the file. For example, Test.C_V becomes Test.C in VSS.
If the VSS project you specify exists, the converted files are added to it. If the project does not exist, it is created. If you do not specify a project, the current project for the VSS Admin user is used.
If a file has gone through ten revisions in PVCS, there are ten versions of the file in VSS. However, the numbering systems used by the two programs are different. PVCS starts off with 1.0, followed by 1.1, 1.2, 1.3, and so forth. VSS uses whole numbers: 1, 2, 3, and so on. Therefore, what was 1.3 in PVCS becomes version 4.0 in VSS.
While PVCS_SS.exe is running, it displays all files that it is converting and all branches that it is ignoring. This is logged in a file called PVCS_SS.log in the folder in which VSS is installed.
A null revision in PVCS is a revision of a file that encodes no changes to the file contents. PVCS_SS.exe determines how to treat these revisions based on the Update_No_Change initialization variable in the Admin user's SS.INI file. If the Update_No_Change variable is not set, PVCS_SS.exe assumes the default value, updates, and converts all null revisions.
Both PVCS and VSS support Branches, but PVCS_SS.exe does not convert PVCS branches to VSS branches. You must manually convert the branches you want to keep. PVCS_SS.exe assists with this process by reporting and logging in PVCS_SS.log all the branches that it passes over.