README.USR: Defect Control System for Windows
=============================================

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


Table of Contents
-------------------------------
1. Contacting The Software Edge
2. Setup & Installation Notes
3. Network Specific Information
4. Lock Manager Notes
5. PVCS Sample Database
6. Corrections to Manual
-------------------------------



---------------------------------
1. Contacting The Software Edge
---------------------------------

You may contact The Software Edge 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: 719/598-3787
Main Line:         719/598-3713
Fax:               719/598-3970
BBS:               719/531-7924 (8 data bits, No parity, 1 stop bit)

The Software Edge Inc.
5526 North Academy Blvd.
Suite 204
Colorado Springs, CO 80918



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

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

Please refer to this file if you encounter errors while
installing Defect Control System.

The LOCKMGR.DBL file format is incompatible with DCS 2.0.  These
files exist in each DCS 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
DCS 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 DCS project
subdirectory.  The easiest way to do this is to perform all of
your copy operations, then use the DCS "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 Defect Control System on various
network operating systems is available in the NETWORKS.TXT file on
Disk 1 of the DCS installation disks.



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

Terminology Change: The term "Recovery Manager", used in previous
versions of of DCS 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 DCS 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 DCS/PVCS integration features without 
having to use your production environment, we have provided a sample 
database, complete with sample work files and PVCS archives, to let 
you set up a sample database as quickly and easily as possible.  


  Installing the Sample Database

  1. Under your DCS database directory (e.g., C:\DCS\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 \dcs\db
       C:\DCS\DB>md p2

  
  2. Change into the newly created directory.

       C:\DCS\DB>cd p2

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

       C:\DCS\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:\DCS\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:\DCS\DB\P2>edit archive\vcs.cfg
       
       
  Setting up DCS to use the Sample Database

  1. You must have Version 5.1 of the PVCS Windows DLL (PVCSVMW.DLL) to 
     use DCS and PVCS together.  DCS searches for this DLL in your Windows 
     directory and in your PATH directories.  Therefore, you will need to 
     have the proper PVCS 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 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 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 DCS 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 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 DCS, 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. Corrections to Manual
--------------------------

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