README.USR: PVCS Tracker for Windows
====================================

*****************************************************************
Tracker Administrators: This readme file is installed into the
PVCS Tracker program group when a client setup is performed on
a workstation.  If you wish to customize this file for your
Tracker users, edit the README.USR file located
in ...\pvcstrkw\sys.
*****************************************************************


Table of Contents
-----------------------------------------
1. Contacting Intersolv
2. Setup & Installation Notes
3. Network Specific Information
4. Lock Manager Notes
5. PVCS Version Manager Sample Database
6. Lotus Notes Mail
7. LAF Issues
8. Corrections to Manual
-----------------------------------------


------------------------------------
  PRODUCT NAME & FILE NAME CHANGES
------------------------------------

This product was formerly known as Defect Control System, or DCS for
short.  The product and version is now PVCS Tracker 2.2.  Versions
prior to 2.2 refer to DCS.  PVCS Tracker is frequently referred to
in the accompanying documentation as simply "Tracker".

If you own a prior version of DCS, you should be aware that some of the
more common file names have been changed to reflect the new product
name.  Some lesser used files still refer to "DCS".  The following file
names have changed:

  Old File Name      New File Name
  -------------      -------------
  DCS.INI            PVCSTRKW.INI
  DCSSYS.INI         PTKSYS.INI
  DCSSTYLE.INI       PTKSTYLE.INI
  DCSMAIN.INI        PVCSNFYW.INI
  DCSPROJ.INI        PTKPROJ.INI
  DCS.EXE            PVCSTRKW.EXE
  DCSMAIL.EXE        PVCSNFYW.EXE

The Tracker setup script will automatically perform all file name
changes for you.



-------------------------
1. Contacting Intersolv
-------------------------

You may contact Intersolv via telephone, facsimile, BBS, or mail.
For fastest response to technical questions, please dial our technical
support number, or send a fax to the fax number listed below.

Technical Support: 800/443-1601
Main Line:         800/547-PVCS
Fax:               503/645-6260
BBS:               CompuServe - "GO INTERSOLV"
Internet:          pvcs_answerline@intersolv.com

Intersolv
1700 NW 167th Place
Beaverton, OR 97006



-------------------------------
2. Setup & Installation Notes
-------------------------------

Information specific to the Tracker setup utility is available in
the SETUP.TXT file on Disk 1 of the Tracker installation disks.

Please refer to this file if you encounter errors while
installing PVCS Tracker.

The LOCKMGR.DBL file format is incompatible with DCS 2.0.  These
files exist in each Tracker project subdirectory.  For this reason,
the 2.1 installation procedure will automatically attempt to
delete these files from the project subdirectories.  If you
encounter a sharing violation while installing, it is most likely
because someone is logged into a project, preventing setup from
deleting this file.  Please ensure everyone is logged out of
Tracker before attempting to upgrade to 2.1.

If you manually copy or move database files from a 2.0 installation
into a 2.1 installation, you will need to delete both the
LOCKMGR.DBL and VISTA.TAF files from the appropriate Tracker project
subdirectory.  The easiest way to do this is to perform all of
your copy operations, then use the Tracker "Recover Sessions" utility
on the project(s) you copied.  This has the affect of deleting the
necessary files.



---------------------------------
3. Network Specific Information
---------------------------------

Information specific to installing PVCS Tracker on various
network operating systems is available in the NETWORKS.TXT file on
Disk 1 of the Tracker installation disks.



-----------------------
4. Lock Manager Notes
-----------------------

Terminology Change: The term "Recovery Manager", used in previous
versions of of Tracker has been changed.  We will now refer to this
as the "Lock Manager".  In places where existing printed documentation,
help files, or text files still refer to the Recovery Manager,
simply subsitute the term Lock Manager.

Version 2.1 does not contain the Windows or TSR versions of the
lock managers (LMW.EXE, LM_TSRS.EXE, and LM_TSRB.EXE) as listed in
the Tracker Administrator's Guide.  Our testing indicates these executables
are not reliable enough to use in a production environment.  If our
database vendor provides updated versions of these lock managers, we
will place them on our bulletin board for you to download.

To run the DOS Lock Manager in a DOS box inside of Windows, add the
following to your system.ini file under the [386Enh] section:

     IdleVMWakeUpTime=1
     TimerCriticalSection=500
     ReflectDosInt2A=true
     NetHeapSize=28



-------------------------
5. PVCS Sample Database
-------------------------

To let you experiment with the Tracker/PVCS Version Manager integration
features without having to use your production environment, we have
provided a sample database, complete with sample work files and
PVCS Version Manager archives, to let you set up a sample database
as quickly and easily as possible.


  Installing the Sample Database

  1. Under your Tracker database directory (e.g., C:\PVCSTRKW\DB), create a
     subdirectory named "pn" where "n" represents an unused project
     number.  We'll assume project number 2 for the rest of this example.

       C:\>cd \pvcstrkw\db
       C:\PVCSTRKW\DB>md p2


  2. Change into the newly created directory.

       C:\PVCSTRKW\DB>cd p2


  3. Copy the file SAMPLE.EXZ from the Tracker bin directory, and rename
     it to sample.exe.

       C:\PVCSTRKW\DB\P2>copy ..\..\bin\sample.exz sample.exe


  4. Run sample with the -d option.  This is a self extracting archive
     that will expand the files and create several subdirectories.
     Be sure to use the -d option.  Otherwise, the subdirectories will
     not be created.

       C:\PVCSTRKW\DB\P2>sample -d


  5. Using a text editor, edit the VCS.CFG file contained in the newly
     created ARCHIVE subdirectory.  There are several parameters in this
     file that you will need to change to match your directory structure.
     The file is well commented and it should only take a few minutes to
     configure the file for your environment.

       C:\PVCSTRKW\DB\P2>edit archive\vcs.cfg


  Setting up Tracker to use the Sample Database

  1. You must have Version 5.1 of the PVCS Version Manager Windows DLL
     (PVCSVMW.DLL) to use Tracker and PVCS Version Manager together.
     Tracker searches for this DLL in your Windows directory and in your
     PATH directories.  Therefore, you will need to have the proper
     PVCS Version Manager directory in your DOS PATH environment setting.
     For example, if PVCSVMW.DLL is contained in L:\PVCS\GUI, then that
     directory needs to be in your path.

  2. As noted in the comments of VCS.CFG, the VCSID environment variable
     needs to contain the PVCS Version Manager user id you wish to use
     (unless you have modified VCS.CFG accordingly).

  3. Log into the sample database using the Admin user id.  The project
     name is PVCS Sample Database.  Leave the password field blank.

  4. Select PVCS Version Manager Setup ... from the Admin menu.

  5. Clear the Read Standard PVCS Configuration Files check box.

  6. Press Add ... to add a configuration file.  Use the Add Configuration
     File dialog box to select the VCS.CFG file from the ARCHIVE
     subdirectory of the sample database.  Press OK to accept the
     configuration file.

  7. Press OK to close the Version Control Setup dialog box and accept
     the configuration.


  Using the Sample Database

  At this point, you are free to use the Tracker Check In and Check Out facilities
  to check work files in and out of their respective archives.  Below is a
  sample scenario to help you get started.

  1. Select a defect in the In Tray or Query window.

  2. Select Update|PVCS Check Out.  If this command is grayed, either the
     PVCS Version Manager DLL could not be found, or you do not have the
     proper permissions to perform a check out.  In the latter case,
     use Admin|Modify User Group while logged on as an administrator
     (e.g., Admin), and check the permissions for the desired user group.

  3. Press Add ... to add a work file to check out.  Change into the
     WORKFILE subdirectory of the sample database and select a work file.
     Also, select the Check Out for Edit option button.  Press OK to accept
     the work file.

  4. Press OK to perform the check out operation.

  5. Using a text editor of your choice, make some changes to the work file
     just checked out.

  6. Back in Tracker, select the same defect and choose Update|PVCS Check In.

  7. Press Add ... and select the work file to check in.  Press OK to accept
     the work file.

  8. Type in your change text, then press OK to perform the check in operation.

  9. From the first drop-down list box in the tool bar, select the PVCS Verbose
     style sheet.  Now scroll through the detail pane to view the source
     code changes.



---------------------
6. Lotus Notes Mail
---------------------

Tracker and PVCS Notify currently do not support using Lotus Notes as
an underlying mail system.

If you have both cc:Mail and Lotus Notes installed on your system, be sure
the directory to cc:Mail is in your path before your Lotus Notes directory.

Example: PATH C:\DOS;C:\WINDOWS;L:\CCMAIL;L:\NOTES

This way Tracker will find and use the cc:Mail mail system instead of the Lotus
Notes mail system.



---------------
7. LAF Issues
---------------

When you run the Tracker main setup program, it will prompt you insert the
LAF licensing disk and ask you for a location to install the LAF database.
You should install the LAF database on a network drive, since all Tracker
users will need access to it.

To ease the client setup process, the main setup program remembers the
LAF database location by placing an entry in the PTKSYS.INI file located
in the Tracker SYS directory.  By doing this, the client setup program
does not need to prompt the user enter the location of the LAF database.

If the main setup program does not complete successfully, however, the
necessary entry in PTKSYS.INI may be missing.  If so, the client setup
program will display an error to the user and will not complete.

If you see such an error, place an entry in PTKSYS.INI as follows:

[LAFINST_DBPATHS]
PVCS Tracker_2.2_WIN=put_laf_database_location_here

After making the correction, re-run the client setup program on the
machine that received the error.

If your network supports UNC names, you can and should enter the UNC
name for the LAF location.  This way, users will be able to access the
LAF database regardless of the drive mappings.  For example, if the
LAF database is in directory LAFDB on volume SYS1 of server MYSERVER,
your entry should look like:

[LAFINST_DBPATHS]
PVCS Tracker_2.2_WIN=\\MYSERVER\SYS1\LAFDB

     ***********************************************************
                              IMPORTANT

       If you move the LAF database, you will need to update
       the entry discussed above to reflect the correct
       location, and re-run client setup program.
     ***********************************************************



--------------------------
8. Corrections to Manual
--------------------------

There are no known corrections to the manual at this time.
