Support Content Notification - Support Portal

Welcome to CA Software ChangeManager 5.2.1 Patch 4. (CA Software Change Manager ishereafter called Harvest.) This readme containsinstallation considerations, operating system support,known issues, and instructions for contacting ComputerAssociates Customer Support.

This readme covers all standard and optional componentsfor Harvest 5.2.1:

The Harvest server, client, agent, and command lineutility.
The Harvest SDK components: the Harvest SDK (HSDK),the Java Harvest SDK (JHSDK), and the Component ObjectModel SDK (COM SDK). In previous Harvest releases, SDKcomponents were sold separately.
CA Software Change ManagerWeb Interface (hereafter called Harweb).
CA Software Change ManagerWebSphere Studio Integration (hereafter called WebSphereStudio Integration) also called WSAD Integration.
CA Software Change ManagerTestDirector Integration (hereafter called TestDirectorIntegration).
CA Software Change ManagerVersion Control Interface (hereafter called VCI).
Note: For information aboutCA Software Change Manager CustomReports, see the readme file (readme_samplereports.html orreadme_samplereports.txt) on the CA Software ChangeManager 5.2.1 Custom Reports CD.
2.0 Operating System Support

This section lists the operating systems supported byHarvest 5.2.1 components. Computer Associates supports eachoperating system for the duration of its life cycle (asdetermined by its manufacturer) or until ComputerAssociates announces that we no longer support it. For thelatest information about supported operating systems, seeour web site, http://ca.com/supportconnect.
2.1 Windows

This section lists the Windows operating systemssupported by Harvest 5.2.1 components. The Harvest server, Harvest client, Harweb, WebSphereStudio Integration, Version Control Interface (VCI), andTestDirector Client require one of the following operatingsystems:
Windows 2000 Server
Windows 2000 Advanced Server
Windows Server 2003 Enterprise or Standard
Windows XP Professional
TestDirector server requires one of the following:
Windows 2000 Server
Windows Server 2003 Enterprise or Standard
Harweb requires an operating system that supports one ofthe following web browsers:
Microsoft Internet Explorer 6.0
Mozilla 1.4 to 1.7
2.2 UNIX

This section lists the UNIX operating systems supportedby Harvest 5.2.1 components.
The Harvest server on UNIX requires one of the following:
Sun Solaris 2.7, 2.8, or 2.9
HP-UX 11.00 or 11.11 (11i)
IBM AIX 4.3.3, 5.1, or 5.2
Harweb on UNIX requires one of the following:
Sun Solaris 2.7, 2.8, or 2.9
IBM AIX 4.3.3, 5.1, or 5.2
HP-UX 11.00 or 11.11
The HSDK on Sun Solaris runs on Solaris 2.6, 2.7, or 2.8systems.
Note: If you are using Solaris 2.8 and the SunWorkshop compiler 5 and Forte 6, you must do the following:
Set the flag -compat=4 in the compile stream.
In the cacheckin.h and cacheckout.h files, you mustreplace the following statement:
```
#if defined(__hpux)
```
with this statement:
```
#if defined(__hpux) || ( __SUNPRO_CC >= 0x500 )
```
The HSDK on AIX requires AIX 4.3.3 and IBM CXX compiler3.6.6.
The HSDK on HP-UX requires HP-UX 11.00 and HP aCCcompiler A.03.25 or higher.
2.3 Linux

This section lists the Linux operating systems supportedby Harvest 5.2.1 components.
The Harvest server on Linux requires one of the following:
Red Hat Enterprise Linux AS 3.0. To work properlywith Harvest, Red Hat Enterprise Linux AS 3.0 requires thatyou install the latest applicable ODBC311 patch availablefrom Computer Associates Customer Support at http://ca.com/supportconnect.
On UNIX and Linux, the Harvest command line utilitiesserve as the Harvest clients. The Harvest command lineutilities require one of the operating systems listedpreviously for the Harvest server.
Harweb on Linux requires Red Hat Enterprise Linux AS 3.0.
The HSDK requires Red Hat Enterprise Linux AS 3.0.

The Harvest agent on Linux requires one of the following:
Red Hat Enterprise Linux AS 3.0
Novell SUSE LINUX Enterprise Server 7.0, 8.0 or 9.0 for s/390
2.4 z/OS

The Harvest 5.2.1 components for z/OS (the MVS agent andthe USS agent) are posted on the Computer Associates website, http://ca.com/supportconnect. The posting includes the agent code, installationrequirements, and a readme file(readme_harvest_mvs_uss_only.html orreadme_harvest_mvs_uss_only.txt) to be used with this file,the Harvest 5.2.1 Patch 4 main readme file(readme_harvest.html or readme_harvest.txt).
3.0 System Requirements

This section describes the system requirements for theHarvest components supported on each operating system.
3.1 Windows

This section describes the system requirements for theHarvest components on Windows.
Server
The Harvest server on Windows requires the followinghardware and software:
An Intel Pentium processor (Pentium III recommended).
110 MB of disk space for temporary use during theinstallation process.
At least 70 MB of disk space for the Harvest productfiles.
Approximately 210 MB of disk space for the Oracletablespaces.
The Harvest tablespaces require a minimum 150 MB ofdisk space (50 MB each for HarvestMeta, HarvestIndex, andHarvestBlob). This is the installation default. You mayneed to increase the size of the tablespaces based on yourestimates, as follows: HarvestIndex tablespace requiresapproximately 600 KB and HarvestMeta tablespace requiresapproximately 100 KB per 1000 versions checked in. HarvestBLOB size depends directly on file size.
At least 128 MB of RAM. Each Harvest server processrequires 15 MB of RAM.
Oracle 8.1.7, 9.0.1 EE, 9.2.0 EE, 9.2.0 SE, 10g EE or 10g SE.
If you want to install the Harvest server with aremote database, you must do the following:
Ensure that the Harvest server has Oracle Server orClient Administrator installed.
Define an Oracle service name on the local machine,using an Oracle utility provided by the Oracle Server orClient Administrator.
Client, Installed Locally, Not Shared
When the Harvest client on Windows is installed locallyand is not shared, it requires the following hardware andsoftware:
An Intel Pentium processor (Pentium III recommended).
At least 60 MB of disk space for the Harvest productfiles.
At least 128 MB of RAM.
Network connection to a UNIX or Windows Harvestserver using the TCP/IP protocol.
110 MB of disk space for temporary use during theinstallation process.
HSDK
On Windows, the HSDK is installed automaticallywhenever you install on a supported Windows platform anyHarvest component, except Database and Documentation, fromthe Harvest product CD. Therefore, if you meet theinstallation requirements for any of those components, youalso meet the installation requirements for the HSDK.
Harweb
Harweb requires 65 MB of disk space.
Harweb requires one of the following servlet engines.For instructions to install each of these servlet engines,see the Harvest Web Interface Install Guide in theDoc directory on the Harweb product CD.
Apache Tomcat 4.1.29, 4.1.30, or 5.0.25. Tomcat isavailable for free. For details, see the Apache web site,http://jakarta.apache.org.
Sun Java System Web Server 6.0 or 6.1. Theseeditions are fully J2EE-compliant. These editions provideweb server and servlet support for Harweb. For details, seethe Sun web site, http://www.sun.com.
IBM WebSphere Application Server 5.0 or 5.1. Theseeditions are fully J2EE-compliant. These editions alsoprovide web server support (based on Apache 2.0) andservlet support for Harweb. For details, see the IBM website, http://www.ibm.com.
At publication time, Harweb does not support thefollowing servlet engine. As soon as Harweb supports thisservlet engine, installation requirements and relatedinformation will be posted on http://ca.com/supportconnect
Macromedia JRun 3.1. This servlet and JSP engine canbe plugged into a commercial web server such as Apache orSun One Web Server. For further information, see theMacromedia web site, http://macromedia.com.
The Harweb machine requires the following to beinstalled locally:
The Harvest client
Java 2 SDK Standard Edition (J2SE) 1.4.2 to 1.4.2_05
Harweb requires one of the following web browsers:
Microsoft Internet Explorer 6.0
Mozilla 1.4 to 1.7
3.2 UNIX and Linux

This section describes the system requirements for theHarvest components on UNIX and Linux.
All Clients
On UNIX and Linux, the Harvest command line utilitiesserve as the Harvest clients. The Harvest client (commandline utility) requires 15 MB of disk space.
All Servers
The Harvest server requires the following hardware andsoftware on all supported UNIX and Linux operating systems.In addition to these requirements, you must meet thespecific requirements for your operating system—thoserequirements are listed in the sections that follow.
A minimum 128 MB of main memory.
15 MB of virtual memory for each Harvest serverprocess.
Oracle 8.1.7, 9.0.1 EE, 9.2.0 EE, 9.2.0 SE, 10g EE or 10g SE.
If the Oracle database resides on a machine otherthan the Harvest server, SQL*Net is required.
Approximately 210 MB for the Oracle tablespaces.
Note: The Harvest installation includes thefollowing Computer Associates shared components: CALicensing (Lic98), CAI/PT ODBC, Enterprise Communicator(PEC), and Computer Associates Cryptographic Engine (CACE).A root user account is required to install Lic98. The otherComputer Associates shared components can be installed to auser-specified location, which may not require a rootaccount.
Sun Solaris Servers
The Harvest server on Sun Solaris requires approximately100 MB of disk space for the Harvest product files, Lic98,CACE, PEC, and CAI/PT ODBC.
IBM AIX Servers
The Harvest server on IBM AIX requires approximately 200MB of disk space for the Harvest product files, Lic98,CACE, PEC, and CAI/PT ODBC.
HP-UX Servers
The Harvest server on HP‑UX requires approximately200 MB of disk space for the Harvest product files, Lic98,CACE, PEC, and CAI/PT ODBC.
Linux for x86 Servers
The Harvest server on Linux for x86 requiresapproximately 150 MB of disk space for the Harvest productfiles, Lic98, CACE, PEC, and CAI/PT ODBC.
The UNIX installation program for Linux is designed forthe bash shell, not the ksh shell. If your site hasinstalled the ksh shell and linked it to /bin/sh, you mustmodify the installation scripts (any files which end with.sh or .SH) to specify the new location of the bash shell,such as /bin/bash.
Harweb
Harweb requires 65MB of disk space.
Harweb requires one of the following servlet engines.For instructions to install Harweb and each of theseservlet engines, see the Harvest Web Interface InstallGuide in the Doc directory on the Harweb product CD.
Apache Tomcat 4.1.29, 4.1.30, or 5.0.25. Tomcat isavailable for free. For details, see the Apache web site,http://jakarta.apache.org.
Sun Java System Web Server 6.0 or 6.1. Theseeditions are fully J2EE-compliant. These editions provideweb server and servlet support for Harweb. For details, seethe Sun web site, http://www.sun.com.
IBM WebSphere Application Server 5.0 or 5.1. Theseeditions are fully J2EE-compliant. These editions alsoprovide web server support (based on Apache 2.0) andservlet support for Harweb. For details, see the IBM website, http://www.ibm.com.
At publication time, Harweb does not support thefollowing servlet engine. As soon as Harweb supports thisservlet engine, installation requirements and relatedinformation will be posted on http://ca.com/supportconnect.
Macromedia JRun 3.1. This servlet and JSP engine canbe plugged into a commercial web server such as Apache orSun One Web Server. For further information, see theMacromedia web site, http://macromedia.com.
The Harweb machine requires the following to beinstalled locally:
The Harvest client (command line utility)
CACE
J2SE 1.4.2 or 1.4.2_05
PEC
Mozilla 1.4 to 1.7 web browser
3.3 SuSE Linux s/390

Agent
The Harvest agent on SuSE Linux s/390 requires thefollowing hardware and software:
Novell SUSE LINUX Enterprise Server 7.0, 8.0 or 9.0 for s/390
Approximately 45 MB of disk space for the Harvestproduct files and CACE
Client
The Harvest client (command line utility) requires 30 MBof disk space.
3.4 z/OS

The Harvest 5.2.1 components for z/OS (the MVS agent andthe USS agent) are posted on the Computer Associates website, http://ca.com/supportconnect. The posting includes the agent code, installationrequirements, and a readme file(readme_harvest_mvs_uss_only.html orreadme_harvest_mvs_uss_only.txt) to be used with this file,the Harvest 5.2.1 Patch 4 main readme file(readme_harvest.html or readme_harvest.txt).
3.5 WebSphere Studio Integration

Before you install WSAD Integration, ensure that one ofthe following is installed:
IBM WebSphere Studio Application Developer 5.0 or5.1.x Enterprise Edition
IBM WebSphere Studio Application Developer 5.0 or5.1 Integration Edition
IBM WebSphere Studio Site Developer 5.0 or 5.1.xEnterprise Edition
IBM Eclipse 2.1.2
To operate correctly, WebSphere Studio Integrationrequires that the Harvest client is installed locally andhas access to Harweb.
WebSphere Studio Integration 5.1 is supplied on theHarvest 5.2.1 installation CD. WebSphere Studio Integration5.1 supports IBM WebSphere Studio 5.0 and 5.1. WebSphereStudio Integration 5.1 requires that one of these versionsof IBM WebSphere Studio is already installed on yourmachine. The WebSphere Studio Integration 5.1 installationis customized to match the version of IBM WebSphere Studioalready installed.
Therefore, if you are using IBM WebSphere Studio 5.0 andyou want to upgrade to IBM WebSphere Studio 5.1, you mustperform that upgrade before you install WebSphereStudio Integration 5.1. Otherwise, you must uninstall andreinstall WebSphere Studio Integration 5.1 after youupgrade to IBM WebSphere Studio 5.1.
After installing WebSphere Studio Integration 5.1, youmust recreate your workspace.
3.6 TestDirector Integration

The Harvest TestDirector Integration option must beinstalled on the Mercury TestDirector server machine.Before installing TestDirector Integration, ensure that thefollowing components are installed:
The third-party prep plug-in. This plug-in must beinstalled and enabled; for details, see the MercuryTestDirector Version Control Add-in Guide.
The TestDirector Integration third-party prepplug-in and the Harvest integration require the Java JRE1.4.0 or greater. When using TestDirector or HarvestTestDirector Integration, you must have the Java JRE activein the path prior to installation.
Visual C++ 6.0.
One of the following:
TestDirector 8.0 with third-party version controlplug-in.
TestDirector 7.6 SP3 with third-party versioncontrol plug-in, build number 7.6.2.500.
3.7 Version Control Integration (VCI)

Before installing VCI, ensure that the followingcomponents are installed:
IBM VisualAge 3.5.3 or 4.0
The versions require an external version control patchfrom IBM.
One of the following certified tools for supportingthe Microsoft Common Source Code Control (SCC) Interface:
Visual C++ 6.0 Enterprise Edition
Visual Basic 6.0 Enterprise Edition
Note: In order for Visual Basic to work, you mustinstall Visual Source Safe (VSS) because Visual Basic isnot a native SCC client. Microsoft does not configureVisual Basic for SCC by default. When you install VisualBasic and choose to install Source Safe, Microsoft createsa vb.ini file in your C:winntsystem32 directory. Thisfile sets a flag to support SCC. This configuration isspecific to Visual Basic but not to Harvest. Forinstructions to enable SCC capabilities in Visual Basic,see the SCC help in Visual Basic.
Visual Studio .NET Framework 1.0
Visual Studio .NET 2003 Framework 1.1
Sybase PowerBuilder 8.0.3, 9.0, or 10.0
Visual Cafe 4.5.1 Enterprise Edition
Rational Rose 2001a.04.00
TogetherSoft (formerly WebGain) Visual CaféEnterprise Edition 4.5.1
Before using VCI, complete the setup tasks in theVersion Control Interface User Guide.
3.8 Eclipse 3.0 Integration
CA Software Change Manager Plug-in r6.0 for Eclipse 3.0 is certified with Harvest 5.2.1 P4.Please refer to the Harvest Change Manager Plug-in for Eclipse Readme located onhttp://ca.com/supportconnectfor installation and configuration information.

4.0 Installation Considerations

For instructions to install Harvest 5.2.1, see the Harvest Install Guide in the Doc directory on the Harvest installation CD.
This section contains instructions for installing Harvest 5.2.1 Patch 4, running the database upgrade supplied by this patch, and changing the item access process to GRANT. This section also contains miscellaneous installation considerations for Harvest 5.2.1.
Note: Harvest Release 5.2.1 Patch 4 is cumulative; that is, Patch 4 includes all fixes that were in Patch 2, Patch 3, plus additional fixes. You do not need to install previous patches before you install Patch 4.

4.1 Installing Harvest 5.2.1 Patch 4 on Windows

On Windows, Harvest Release 5.2.1 Patch 4 is supplied in two files:
HAR521PATCH004WIN.MSI for Harvest server and client machines
HARWEB521PATCH004WIN.MSI for Harweb machines
To install Harvest 5.2.1 Patch 4 on Windows, follow these steps:
Close all Windows applications except Windows Explorer. Ensure that you close any IDE programs.
Ensure that the patch files are accessible to all Harvest server, client, and Harweb machines. For example, you can copy the files to a network drive, CD, or local machine and run them from any of those locations.
Run the HAR521PATCH004WIN.MSI file on all your Harvest server, client, and Harweb machines.
On the Harweb machine, you must stop your servlet engine prior to running HARWEB521PATCH004WIN.MSI.
Run the HARWEB521PATCH004WIN.MSI file on your Harweb machine.

Note: The cache of the JSP/Http server needs to be cleaned after applying the patch. Please contact your web Administrator or refer to documentation of the web server on how to do this.

4.2 Rolling Back (Uninstalling) Harvest 5.2.1 Patch 4 on Windows

To roll back (uninstall) Harvest 5.2.1 Patch 4 on Windows, follow these steps:
Log on to the operating system using the Local Administrator account.
Close all Harvest client applications.
If this machine is a Harvest server, shut down the Harvest broker and all Harvest server processes.
Click Start on the Windows task bar and select Settings, Control Panel, Add/Remove Programs.
On the Add/Remove Programs dialog, select CA CA Software Change Manager Patch 4 and click Remove. This step applies to all Harvest server, client, and Harweb machines.
Before uninstalling Harweb, you must stop your servlet engine.
When rolling back this patch on a Harweb machine, select CA CA Software Change Manager Harweb Patch 4 and click Remove.

Note: The cache of the JSP/Http server needs to be cleaned after applying the patch. Please contact your web Administrator or refer to documentation of the web server on how to do this.

4.3 Installing Harvest Release 5.2.1 Patch 4 on UNIX or Linux

On UNIX and Linux, Harvest 5.2.1 Patch 4 is supplied in one file, HAR521PATCH<release><platform>.tar.gz where release is the patch release and platform can be SUN,UNIX,AIX, HPUX, or LINUX.
For example, HAR521PATCH004LINUX.tar.gz. This file includes updates for all Harvest components, including client and server.
To install Harvest Release 5.2.1 Patch 4 on UNIX or Linux, follow these steps:
Ensure that the umask is set to 022.
Log on to the operating system using your UNIX or Linux Harvest account.
Close all Harvest client applications.
If this machine is a Harvest server, shut down the Harvest broker and all Harvest server processes.
If the $HARVESTHOME/PATCHES directory does not exist, create it.
Copy the HAR521PATCH<release><platform>.tar.gz file to the $HARVESTHOME/PATCHES directory.
Change the current directory to $HARVESTHOME/PATCHES.
Enter the following command to decompress the file:
```
 gzip -d HAR521PATCH<release><platform>.tar.gz 
```
Enter the following command to un-tar the file:
```
 tar xvfo HAR521PATCH<release><platform>.tar 
```
This step creates the $HARVESTHOME/PATCHES/HAR521PATCH<release><platform> directory, if it does not already exist.
If you have previously executed this patch, rename or remove any previous backup directory for this patch.
Change the current directory to $HARVESTHOME/PATCHES/HAR521PATCH<release><platform> directory created in Step 9.
Enter the following command:
```
 ApplyPATCH.sh 
```
Review the PATCH.log file in the $HARVESTHOME/PATCHES/HAR521PATCH<release><platform>_BKP directory.

4.4 Rolling Back (Uninstalling) Harvest Release 5.2.1 Patch 4 on UNIX or Linux

To roll back (uninstall) Harvest Release 5.2.1 Patch 4 on UNIX or Linux, follow these steps:
Ensure that the umask is set to 022.
Log on to the operating system using the UNIX Harvest account.
Close all Harvest client applications.
If the machine on which you are installing the patch is a Harvest server, shut down the Harvest broker and all Harvest server processes.
Change the current directory to the $HARVESTHOME/PATCHES/HAR521PATCH<release><platform>_BKP directory.
Enter the following command to run the rollback file:
```
 RollbackUPDATE.sh 
```
Review the PATCH.log file in the $HARVESTHOME/PATCHES/HAR521PATCH<release><platform>_BKP directory.
Note: Rolling back the patch does not remove the backup directory. To remove that directory, delete it manually.

4.5 Installing Harweb 5.2.1 Patch 4 on UNIX or Linux

On UNIX and Linux, Harweb 5.2.1 Patch 4 is supplied in one file HARWEB521PATCH004UNIX.tar.gz. This file includes updates for Harweb.
To install Harweb 5.2.1 Patch 4 on UNIX or Linux, follow these steps:
Ensure that the umask is set to 022.
Log on to the operating system using the UNIX Harweb account.
Close all Harweb Client Applications.
Shut down the Harweb Server components and servlet engine.
Change the current directory to the Harweb home directory (<webappdir>Harweb). This directory should contain the directories <webappdir>HarwebHarweb, <webappdir>HarwebWEB-INF, and <webappdir>HarwebWebDoc.
Back up the following directories: <webappdir>HarwebHarweb, <webappdir>HarwebWEB-INF, and <webappdir>HarwebWebDoc. For example (within Harweb home directory):
```
 tar cvf HARWEB_BKP.tar Harweb WEB-INF 
```
Copy the patch.tar.gz file to the Harweb home directory, <webappdir>Harweb.
Delete the following files (if they exist) from the Harweb home directory:
PATCH.log
ApplyPATCH.sh
readme_harvest.html
readme_harvest.txt
Decompress the PATCH file with the following command:
```
 gzip -d <patch>.tar.gz 
```
Un-tar the PATCH file into the Harweb home directory with the following command:
```
 tar xvfo <patch>.tar 
```
In the <webappdir>HarwebWEB-INFlib folder, rename the following files:
bsf.jar to bsf.old
bsfengines.jar to bsfengines.old
xerces.jar to xerces.old
Execute ApplyPATCH.sh.

Note: The cache of the JSP/Http server needs to be cleaned after applying the patch. Please contact your web Administrator or refer to documentation of the web server on how to do this.
Start the Harweb Server components.

4.6 Rolling Back (Uninstalling) Harweb 5.2.1 Patch 4 on UNIX or Linux

To roll back Harvest 5.2.1 Patch 4 for Harweb on UNIX or Linux, re-install the previous version of Harweb. For example, re-install the previous patch (Patch 3) or the base product installation (5.2.1), whichever was installed before you installed Patch 4.
Then in the <webappdir>HarwebWEB-INFlib folder, rename the following files:
bsf.old to bsf.jar
bsfengines.old to bsfengines.jar
xerces.old to xerces.jar

Note: The cache of the JSP/Http server needs to be cleaned after applying the patch. Please contact your web Administrator or refer to documentation of the web server on how to do this.

4.7 Running the Database Upgrade Patch

Harvest 5.2.1 Patch 4 copies but does not run database upgrade patch files to your Harvest server database machine. To upgrade your databases, run the DBPatch.sql database patch script located in the HAR521PATCH004WIN directory, using your Harvest Oracle account. You can run this database patch more than once, before or after you run Harvest 5.2.1 Patch 4. The DBPatch.sql database patch is:
Permanent
Independent of Harvest 5.2.1 Patch 4
Not intended to be rolled back
The DBPatch.sql script is located in the HAR521PATCH004WIN directory. You can run the script after you have installed the Harvest 5.2.1 base product, after you have installed Patch 1, or after you have installed Patch 4.
If you are upgrading from Patch 1 to Patch 4 and you have already run the DBPatch.sql in Patch 1, you do not have to run the DBPatch.sql again.
Run the PR2329 script after running the DBPatch.sql. See Changing Item Access Process to GRANT for PR2329 script information.
Run DBPatch.sql before running any external fix scripts.
Run DBPatch.sql after completing a Harvest 4.1.x to 5.x conversion.
To run DBPatch.sql, follow these steps:
Change the current directory to the following:
On Unix or Linux: $HARVESTHOME/PATCHES/HAR521PATCH004
On Windows: %HARVESTHOME%PATCHESHAR521PATCH004WIN
Using your Harvest Oracle account, enter the following command:
sqlplus <account>/<password> @DBPatch.sql
Review the DBPatch.log file in the following directory:
On UNIX or Linux: $HARVESTHOME/PATCHES/HAR521PATCH004
On Windows: %HARVESTHOME%PATCHESHAR521PATCH004WIN

4.8 Changing Item Access Process to GRANT

Perform the following steps to change the item access process to use GRANT Access instead of DENY Access. These steps provide a database conversion that cannot be rolled back.
WARNING! After you perform these steps, you will not be able to roll back to a prior release or patch of Harvest.
Make a backup of your current database before you start this process. (After you run the M1 or M2 script, you cannot recover your original database).
Read the PR2329-readme.txt file, Tech Doc TEC324271, Grant Item Access Data Conversion and Installation Instructions, and Tech Doc TEC324326, Repository, Item Path & Item Access Model Uses GRANT Methodology Overview. See one of the following directories for the PR2329-readme.txt file:
On Unix or Linux: $HARVESTHOME/PATCHES/HAR521PATCH004
On Windows: %HARVESTHOME%PATCHESHAR521PATCH004WIN
Both Tech Docs are available from Computer Associates Customer Support at https://support.ca.com.
Using the information and instructions in PR2329-readme.txt and the Tech Docs, run either the PR2329-M1CONVERTData.sql script (Method 1) or the PR2329-M2CONVERTData.sql script (Method 2).

4.9 Miscellaneous

On Windows computers, the Harvest installation may display Internal Error 2343 and abort. The most likely cause of this error is that a release of Harvest earlier than 5.2.1 is already installed. Uninstall the earlier version using the Add/Remove Programs option from the Windows Control Panel. Then try installing Harvest 5.2.1 again.
The custom installation for the Harvest client includes options to install WebSphere Studio Integration, TestDirector Integration, and WSAD Integration; however, the Harvest installation program enables only the option or options that apply to your site.
The operating system requirements for the Harvest components on all platforms include the requirements for the applicable Computer Associates shared components such as PEC, Lic98, CACE, and CAI/PT ODBC.
While installing Harvest on Linux systems, if you are using Red Hat Enterprise Linux 9, you must set the environment variable LD_ASSUME_KERNEL=2.4.1. If you do not set this variable, the Harvest executable files will not start. For instructions, see the Harvest Install Guide.
On UNIX and Linux, if you are re-installing Harvest 5.2.1, to keep the existing Harvest 5.2.1 database created by the first installation, you must use installation option [2] - Upgrade Harvest. If you select option 2, you are prompted to enter the Oracle user name that owns Harvest tables. If you enter the name of the existing database user at this prompt, the installation program proceeds successfully.
On UNIX and Linux, log on as the harvest user (not the root user) to install CACE. For details, see the Installation section of the Known Issues in this readme.
Harweb
Harweb is a standard component of Harvest 5.2.1. Harweb is supplied on its own CD, separate from the Harvest installation CD. There is one Harvest CD for Windows and another for UNIX. For instructions to install Harweb, see the Harvest Web Interface Install Guide in the Doc directory on the Harweb product CD.
Harweb uses the Harvest server's database and requires a remote Harvest agent machine.
Harweb Windows and UNIX Agent-only installations will need to apply the Harvest patch to upgrade to the current patch level.
WebSphere Application Server
Use these procedures to configure and deploy Harweb under IBM WebSphere Application Server on the Microsoft Windows 2000 or Windows XP platform. WebSphere must be properly installed and configured. See the respective product documentation for further information on installing and configuring WebSphere Application Server.
Prerequisites
You need to create the harweb.war file. To do this, follow these steps:
Install Harweb to your local disk (follow all the normal setup instructions).
Change directories to the Harweb root dir.
Verify that you can run the jar command from the command line (it is installed with java).
Run the following command:
```
 jar -cvf harweb.war * 
```
Ensure that harweb.war is lowercase.
Configuration Procedure
Follow these configuration steps:
Ensure that the target WebSphere Application Server is running.
Start the WebSphere Application Server Administrative Console.
Expand the Applications entry in the Actions tree in the left frame.
Click Install New Application.
In the Preparing for the Application Installation dialog, under Path, select Local Path and enter the path name for the fully qualified path to the %temp%webapps folder on the machine where Harweb is installed and configured.
Under Context Root, enter /harweb. Note the presence of the prepended forward slash. Click Next.
Check the Generate Default Bindings check box. Click Next.
In the Application Security Warning dialog, click Continue.
In Step 1 in the Install New Application dialog, enter an appropriate name, for example, Harweb. Click Next.
Select appropriate site-specific options through Step 4: Summary. Click Finish when you are finished.
On the Enterprise Applications frame, select the check box for the name you previously gave this application.
Select and click Start.
Harweb is now deployed into your application server and is addressable as /harweb appended to your web application server's URL.
WSAD Integration
WSAD Integration is an optional component of Harvest client installation. For instructions to install WebSphere Studio Integration, see the Harvest Install Guide in the Doc directory on the Harvest installation CD.
For other important installation considerations, see WebSphere Studio Integration in System Requirements in this readme file.
TestDirector Integration
Mercury TestDirector Integration is an optional component on the Harvest 5.2.1 client custom installation. For instructions to install TestDirector Integration, see the Harvest Install Guide in the Doc directory on the Harvest installation CD.
WARNING! If the Harvest client on the TestDirector server machine is uninstalled and reinstalled in another location after TestDirector data has been checked in to the Harvest repository, the TestDirector interface will be unable to check out the files, because the location of the htdvcElement.dtd file has changed. If the Harvest installation is moved, a copy of htdvcElement.dtd must remain in its original location.
5.0 General Considerations

For a list and brief description of new and changedfeatures supplied by Harvest 5.2.1, see the HarvestRelease Summary in the Doc directory on the Harvestinstallation CD.
The Harvest Release 5.x HSDK replaces the Harvest SIKsupplied with Harvest 4.x and earlier versions. The HarvestSIK was a C language interface to a subset of the Harvestcapabilities. The HSDK is a C++ class set for the samefunctionality. SIK functionality can be reprogrammed usingthe HSDK but is not directly compatible with the HSDK.
6.0 List of Fixes

Harvest 5.2.1 Patch 4 includes all Release 5.2.1 Patch2, Patch 3, and 5.1.1 fixes. These fixes were originallycreated for Harvest 5.1.1 patches 16‑18, WSADIntegration 2.0 patches 5‑7, and Harweb 3.1 patches10‑12. A list of fixes is on our web site, http://ca.com/supportconnect.
6.1 Harvest 5.2.1 Patch 2 Fixes

PR 0766: HCO - CHECK OUT FOR SYNCHRONIZE CHECKS OUTRESERVED VERSION
PR 1130: CREATION AND MODIFICATION TIME IS THE SAME INDATA VIEWS
PR 1382: ERROR MESSAGE IS RETURNED WHEN USER DOES NOTENTER FORM NAME
PR 1448: WRONG TIME IN PACKAGE HISTORY REPORT
PR 1478 – VCI (ROSE) - CANNOT INCLUDE FILES INDIRECTORIES HIGHER THAN HP~
PR 1663: RECURSIVE SEARCH VIA SHELL-EXTENSION SHOWSINCORRECT VIEWPATH
PR 1706: VCI - VB GPF WHEN PERFORMING CREATE PRJ FROMHARWITH PROJ CONTAINING COMMON FIL
PR 1789: HARWEB INSTALL CHANGING DEFAULT TIMEZONE OF JVM
PR 1875: CAN'T RESTORE PROJECT WHEN THERE ARE RESERVEDTAG VERSION
PR 1993: FILE TIMESTAMP NOT IN GUI
PR 2007: CANCEL CLOSES DATAVIEW
PR 2143: CALL PROCESS OUT OF PROJECT BY COMPARE VIEW
PR 2349: HCO FAILS WHEN ITEM WITH FULL PATH
PR 2393: HSQL CONVERTS DATE
PR 2401: HSDK CAVERSIONCHOOSER API RETURNS NO FILESIZE
PR 2405: VERSION WHEN USED AS PRELINK, UDP DOES NOT GETVIEWPATH INFO
PR 2434: HARVEST CLIENT DOES NOT DISPLAY SIZE OF AN ITEM
PR 2466: NOTIFY PROCESS - WRONG NAME
PR 2564: HEXECP FAILS ON WINDOWS AGENT WHEN RUNNING MORETHAN 32 TIMES
PR 2593: HARVEST REPORTS - DATE FORMAT INCORRECT
PR 2621: CHECKIN FAILS ON FILES WITH SAME FILENAME BUTDIFFERENT CASE
PR 2633: STRANGE OUTPUT FOR THE UDP SCRIPT WHEN RUNNINGIN HARVEST
PR 2793: NOT SHOW CHECKOUT MARKS AFTER ADD AND RESERVEIN WSAD
PR 2796: SYNC PROBLEM AFTER COPY/PASTE AN ITEM
PR 2809: FIND VER LIMIT VIEW TO STATE WHEN VIEW OPT ISVER FILTER ALL
PR 2810: FIND VER/DELETE VER SQL ERROR ORA-01795 OVER1000 ITEMS SEL
PR 2857: HARVEST GPF WHEN DRAG PACKAGE WITH NO PROMOTETO STATE
PR 2894: VCI - NEW FILES NOT RECOGNIZED ON USER 2MACHINE
PR 2977: VCI - PERFORMANCE PROBLEMS WHEN ADDING PROJECTSON UNIX
PR 2979: HARWEB VISUAL DIFFERENCE SHOWS INCORRECT FILE
PR 2981: HARVEST ADMIN MAY FAIL WHEN REORDERING STATES
PR 2982: CANCEL BUTTON IN SELECT HARWEB CONTEXT BRINGSHARWEB
PR 2984: HEXECP - ASYN PRODUCES AN ERROR AFTER SECONDCALL.
PR 2985: OSF AGENT WILL ERRANTLY PRODUCE A LOCKEDDIRECTORY MESSAGE
PR 2986: CLICK SYMBOLIC LINE FOLDER FOR CHECKIN INHARWEB FAILS
PR 2997: LATEST_IN_PACKAGE/ALL_IN_PACKAGE MISSING HSDK
PR 3016: VCI - VDIFF DOES NOT WORK WHEN CO HAS PRELINKUDP THAT FAILS
PR 3028: CHECKIN NON-RESERVED ITEM TAKES A LONG TIME
PR 3033: HARVEST ADDS 0X0D [CR] CHARACTER INCOMPRESSED TEXT REPOSITORY
PR 3045: PASSWORD CORRUPTED IN UDP
PR 3051: HUSRMGR RETURNS AN ERROR WHEN NO USER GROUPSPECIFIED
PR 3053: HIMPENV HANGS WITH OPTION -IUG
PR 3054: RUNTIME ERROR WHEN SET CONTEXT TO PROJECT WITHLONG NOTES
PR 3056: REFRESHING THE VERSIONS LIST WILL GET UNKNOWNERROR
PR 3058: CHECK IN FOLDER PROBLEM WHEN FOLDER NAME HASSPACE
PR 3068: CANCEL TAKES LONGER TIME THAN OK IN NOTIFYPROPERTIES WINDOW
PR 3079: VCI - DOC NEEDED FOR COMMON DIRECTORY
PR 3081: ADD EMPTY PROJECTS TO WORKSPACE
PR 3086: TIMESTAMP DISPLAY INCORRECT WHEN TIMEZONE ISGMT +/- #.5HR
PR 3089: STATES ARE BEING PRESENTED ALPHABETICALLYORDERED
PR 3090: HCO CORE DUMP WITH LARGE NUMBER OF FILES ON UNIX
PR 3092: FILE AGENT ERROR WITH HCO
PR 3093: CLIENT UDP CAUSES WORKBENCH LOSING FOCUS
PR 3096: LIST VERSION WITH ACTUAL CHANGES SHOWS NOTHINGIN OUTPUT
PR 3101: FILE EXTENSION FOR COMPRESS NOT RECOGNIZEDCORRECTLY
PR 3106: CHECKIN WITH DELETE OPTION GET ERROR CANNOTOPEN SIG
PR 3124: HARVEST LOGS ERROR WHEN CHECK OUT FROM EMPTYDIRECTORY
PR 3171: CAVERSIONCHOOSER EXECUTE DOC
PR 3176: XERCES/XLAN UPGRADE
PR 3182: PROMOTE TAKING 100% OF CPU
PR 3191: HCI - DCP & -DVP OPTIONS MISSING
PR 3192: CREATE WEB XML FOR TOMCAT 5.0
PR 3206: MODIFY FORM TABLE IN USER CONTACT.HFD ANDMODIFICATION REQUEST.HFD FILES
PR 3209: TOMCAT DIRECTORY SPACE INSTALLATION
PR 3251: RESOLVE THE HOSTNAME TO AN IP ADDRESS TO BEABLE TO CONNECT TO THE AGENT
PR 3254: PACKAGE ASSOCIATED FORMS NOT DELETED
PR 3263: FILE AGENT ALLOWS CHECKIN OF FILE W/OPERMISSIONS
PR 3286: COMPARE VIEW CAUSES PROBLEM
6.2 Harvest 5.2.1 Patch 3 Fixes

PR 3443: NON-ADMIN USER CANNOT CHECK OUT FILES WITHHARVEST 521 P2
PR 3444: DIFFERENT VERSION OF ADVANTAGE.EXE INSTALLEDAFTER P2
PR 3456: COMPARE FILE/VERSION RUNTIME ERROR
PR 3473: WEB.XML NOT INSTALLED WITH PATCH 2
6.3 Harvest 5.2.1 Patch 4 Fixes

PR 781: HARVEST REQUIRES SYSTEM ACCOUNT TO RUN AS A SERVICE
PR 1178: ONLY ONE PAGE OF THE SESSION LOG IS PRINTED
PR 1753: SQL COMMAND NOT PROPERLY ENDED
PR 1857: CANNOT RESTORE PROJECT WHEN THERE ARE RESERVED TAG VERSIONS
PR 2114: UNDO CHECKOUT DOES NOT GET THE LATEST VERSION
PR 2185: PROVIDE MSG WHEN OPERATION CANCELLED DURING ADD TO WORKPSPACE
PR 2203: INCORRECT PASSWORD PASSED TO THE DIRECTORY CHOOSER
PR 2279: CAN CHECKIN/CHECKOUT FROM AN INACTIVE PROJECT
PR 2548: SUMMARY OF TOTALS NEEDED FOR CHECKIN/OUT IN RESULTS WINDOW
PR 2583: CHANGING CONTEXT WHEN CHANGING SOLUTIONS IN .NET
PR 2643: DIR LOAD_REPO EXPANDS FROM PATH DURING REP LOAD CRASHES GUI
PR 2697: VCI-WOULD LIKE CO- TO ONLY LIST FILES NOT CUR CHECKED OUT
PR 2898: LOW DISKSPACE ERROR
PR 2933: '5C' AS LAST CHAR CAUSES PROBLEM
PR 3027: BROKER STOPS UPDATING LOG FILE
PR 3040: WRONG PROCESS SHOWING IN THE PACKAGE GROUP
PR 3066: COPY TO/FROM PROJECT TEMPLATES IS SLOW
PR 3158: UNEXPECTED HAPI ERROR LOG DUMP
PR 3165: HIMPENV USES LARGE MEMORY WHEN USER GROUP NUMBER IS BIG
PR 3167: JHSDK CROSS PLATFORM
PR 3178: AGENT HANG/DIE ON UNIX WITH MULTIPLE CONCURRENT HCOS
PR 3180: STANDALONE UDP SUPPORT IN ECLIPSE
PR 3183: PASSWORD VARIABLE GETS CORRUPTED ON LINUX
PR 3185: EXECUTION OF UDP RETURNS UNEXPECTED ERROR WHEN NO VIEW
PR 3188: Signfile.dll Memory Leaks
PR 3189: HUtilities.dll Memory Leaks
PR 3204: VCI - SCC SERVERPATH INCORRECT AFTER HAR 5.2.1 NETWORK INSTALL
PR 3205: VCI - ERROR WITH MAPPED NETWORK DRIVES WITH VCI
PR 3212: HCD FAILS WHEN USING VERSION_TAGS WITH RTSERVER NAME
PR 3213: hsdk sample failed
PR 3223: TEMPORARY HSERVERS/ASYNCHRONOUS UDPS BECOMING DEFUNCT
PR 3229: VCI-NET CHECK IN WRONG DIRECTORIES WHEN NON-HIER STRUCTURE
PR 3231: UDP OUTPUT REPEATS ITSELF
PR 3245: CHECKIN FILTER OPTION IS IGNORED IN HARVEST PLUGIN
PR 3248: VCI - ERROR MSG CONCERNING HP~ DURING CHECKIN OPERATIONS
PR 3249: BAD ENGLISH IN MESSAGE
PR 3260: MULTIUSER HEXECP SINGLE THREAD
PR 3266: Hserver Memory Leak
PR 3290: REPLACE VERSION WITH HARVEST PROBLEM IN PLUGIN
PR 3298: CONFIG BASELINE LOST FROM MENU
PR 3308: SYNC VIEW WINDOW IS OPENED IN MININAL WINDOW
PR 3309: BACK BUTTON TO HARWEB LOGON
PR 3311: HSIGGET COMMAND GETTING INCORRECT VERSIONOBJID
PR 3312: STATE ORDER CONFLICT
PR 3313: AGENT PROBLEM CHECKIN TEXT CONTAINS NON-PRINTABLE CHAR
PR 3317: MEMORY MISMATCHED ALLOCATION IN SIGNFILE
PR 3323: MEMORY MISMATCHED IN HSERVER
PR 3327: FAILURE CONNECTING TO AGENT/BROKER WITH MIXED CASE HOSTNAME
PR 3346: MEMORY LEAK IN FILEAGENT
PR 3377: GET LATEST: CO FILES RW -> RO
PR 3410: DIRECT-CONNECTION DOES NOT SUPPORT FQDN RESOLUTION
PR 3412: FAILS ON LARGE NUMBERS
PR 3431: HEXECP RUNS AS PT_HAGENT
PR 3445: REPOSITORY INFO IN LOCAL TIME
PR 3448: CONTEXT PROPERTIES CRASH ON UNIX - HP, SOLARIS
PR 3449: ECLIPSE 3.0 CRASHES ON UNIX WHEN EXITING OUT
PR 3467: FIND VERSION HARWEB SQL ERROR
PR 3478: DATE FORMAT ERROR WHEN TAKING SNAPSHOT
PR 3487: STATE ORDER WRONG IN DIALOGS
PR 3494: VCI PERFORMANCE DEGRADATION WITH ADD PROJECT AND CHECKIN
PR 3502: INVALID VIEW PATH ERROR CHECKIN FILE TO REP WITH DIFF CASE
PR 3504: VCI-OPEN FROM SRC CONTROL NON-HIER FILES CONVERTED FROM H4
PR 3525: PROMOTE PKG TAKING TOO LONG
PR 3527: PROMOTE PACKAGE GROUP ERRORS
PR 3536: DELETION OF PROJECT CAUSED LOSS OF PRODUCTION DATA
PR 3539: Harvest/Eclipse Logging on AIX
PR 3540: SEARCH ERROR AFTER CHECKOUT(IN WSAD)
PR 3553: [VERSION] VAR BAD EXPANSION
PR 3560: ERROR ON CHECKING FILE FROM WINDOWS AGENT
PR 3578: BAD ENGLISH IN MESSAGE
PR 3580: HARWEB SHOWS USERNAME-PASSWORD IN LOG FILE
PR 3589: HARVEST WB FREEZES IDE
PR 3624: FIND VERSION SHOW WRONG FULL PATH
PR 3634: VCI .NET UNEXPLAINED CHECKOUT
PR 3637: USER'S EMAIL ADDRESS QUERY (JHSDK)
PR 3652: HCO CHECKS OUT ALL FILES WHEN BOGUS FILENAME IS SPECIFIED
PR 3664: HARWEB PRESENTS GMT TIME ON VERSION PROPERTIES PAGE
PR 3679: VCI - ITEM HISTORY - SORT LOST
PR 3680: HARWEB PRESENTS DIFFERENT TIME FROM GUI
PR 3686: CHECKOUT OF FILE TO MULTI-USER AGENT FAILS WITH "FILE IS WRITABLE"
PR 3716: COMPARE FAILS ON BASE VERSIONS
PR 3767: EXCEPTION IN HAPI
PR 3970: Hfatt can't attach doc files
PR 4015: UNIX PATCH SCRIPT REQUIRES "." IN PATH
PR 4023: TEMPORARY HSERVERS EXITING PREMATURELY ON LINUX

7.0 Known Issues

This section lists the most prominent known issues forHarvest 5.2.1 at publication time. For other known issues,see Computer Associates Customer Support at http://ca.com/supportconnect.
7.1 Access Control

PR2910: A User Group that does not have View access toan item path can modify the item path through command lineutility check in process (hci).
PR2329: Harvest Release 5.2.1 Patch 1 includes files andsteps for changing the item access process to use GRANTAccess instead of the DENY Access. If you perform thesesteps, you will not be able to roll back to a prior releaseor patch of Harvest, because these steps perform a databaseconversion that cannot be rolled back. For moreinformation, see Changing Item Access Process to GRANTunder Installation Considerations in this readme file.
7.2 Agent Connection Problems

PR3117: When you connect to a remote agent by using theConnect to New Agent option of the Remote AgentNeighborhood on the Files tab of the Harvest Administratoror Workbench GUI, the GUI caches the agent connectioninformation.
If the remote agent is shut down and restarted, you mustdisconnect and reconnect the agent in the Remote AgentNeighborhood to reestablish the cached agent connectioninformation. If you do not do so, the GUI cannot performremote agent file handling, even though the remote agentappears valid on the Files tab.
PR3118: When you attempt to connect to a remote agent byusing the Connect to New Agent option of the Remote AgentNeighborhood on the Files tab of the Harvest Workbench GUI,you receive a login timeout error if both of the followingconditions exist:
The machine name of your Harvest broker includes adash (-)
The remote agent is already connected to that broker
As a workaround, try either renaming the current broker(if feasible) or using a different broker.
PR 4030: A command line hco using a multi-user agent outputsan incorrect error message: "File Is Writeable".
If target file has any write permission bit on and the userattempting to checkout the file is not the owner and “Shared Working Directory” is not in effect, then the error message returned will state “Can’t replace readonly file” instead of “File is Writable”.
7.3 Agent Modes

PR2911: A user cannot start multiple single-user agentson the same machine connecting to different Harvest brokers(rtservers) on a z/OS machine with SuSE Linux 7.0installed.
7.4 Agent Shutdown

PR3109: On HP-UX, Solaris, and z/OS, when the RT serveror Harvest broker is shut down, the Harvest agent alsoshuts down. This problem may also affect other platforms.If you experience this problem, first restart the RT serverand the broker and then restart the agent.
7.5 Check In and Check Out

PR2912: Generally, two Harvest users can share the sameproject files; that is, the users can both have the samefiles checked out simultaneously, and their changes can bemerged when both files are checked in again. This abilityto share files does not apply to Sybase PowerBuilderproject files.
PR2913: On Windows, if you check in or check out filesusing HarWind (the Harvest Windows Extension) after youinstall the Harvest client, you may receive error messagessimilar to the following, even if the files are actuallychecked in or checked out properly:
```
E3080003: Requested Message Key Not Found: : HSRV_I_CHECKINE3080003: Requested Message Key Not Found: : HAPI_I_EXECUTE_SUCCESSE3080003: Requested Message Key Not Found: : HSRV_I_CHECKOUTE3080003: Requested Message Key Not Found: : HSRV_I_CHECKOUT
```
To fix this problem on Windows 2000, restart thecomputer.
To fix this problem on Windows XP, close and restart allWindows Explorer sessions.
PR 4054: Low disk space errors when checking out to a floppy disk
The following scenario has been corrected with 5.2.1 P4 PR2898:
Harvest checks out files even through there is not enough disk space. Some of the checked out files will be truncated in size (i.e. zero bytes). Although the checkout has been unsuccessful, it still shows as a completed check out. The items that were check out are also marked as reserved in Harvest.
An outstanding fail scenario is still pending resolution. This behaviour will be address with PR 4054 in a future deliverable:
Attempting to check out 5000 3k size files to a sub folder of a floppy disk will result in some files being truncated in size. These files are also reserved if checked out for update.
7.6 Command Line

PR2914: The project restore command line utility namedhrt requires a remote file agent connection on the machinewhere the project was archived. For example, to restore aproject to Harvest from machine A, a remote file agent mustbe running on machine A. Use the following syntax for hrt:
```
hrt -b <broker> -f <archive file> -m <machine> -musr <user> -mpw <password>    -user <harvest user> -pw <harvest pw>
```
7.7 Graphical User Interface

PR2916: The function for copying multiple Lifecycleprocesses in the Harvest Administrator from one state toanother does not work. You must copy each processindividually.
PR2917: In the Administrator interface, the Add andDelete buttons are disabled on the Access tab of the linkedprocess properties dialogs, because access to a linkedprocess is controlled by its parent process. A user groupgranted access to execute a process has implicit access toexecute the linked processes.
PR2918: The remove item process is slow. For example,removing approximately 25 items requires approximately oneminute. The efficiency of the removal decreases as thenumber of items to be removed increases. Also, after eachitem is deleted, certain pre-link and post-link UDPs areexecuted automatically. Consequently, pre-link andpost-link UDPs are practically unusable for the remove itemprocess.
PR2919: The promote process may be very slow if youpromote a large number of packages (for example, 200) withVerify Package Dependencies and Enable Package Mergeselected.
PR2920: In the Workbench Check Out dialog, the followingproblems may occur:
Making a selection from the file browser changes thesetting for the Context View Path, even if Use Context ViewPath is checked.
Clearing the Use Client View Path check box alsochanges the Context View Path, even if Use Context ViewPath is checked.
The Client View Path may be changed when you browsefiles if Use Context View Path is not checked or if UseClient View Path is checked.
7.8 Harweb

These issues apply to the General Web Client.
PR2921: The compare view process does not allow a userto select an alternate view name (other than the defaultWorking View) unless the Public user group is granted Useaccess to the project. The View Chooser says No View. Towork around this problem, add the Public user group to theUse access method for the Harvest project in the context.
PR2922: The create package process does not format thepackage name correctly if the package name includes one ormore double quotation marks ("). If you specify a packagename that includes a double quotation mark, Harvest assignsthe default package name instead of the name you specified.
PR2923: The create package process does not display theassociated form if the package name contains one or moresingle quotation marks ('). If you specify a package namethat includes a single quotation mark, Harvest issues aConfirmation Message and closes the form. To display theform, open the Package Properties dialog and use the Formstab to locate the form.
PR2924: In Harweb, you cannot use a hyphen (-) as thefirst character of a package name. If you attempt to name anew package or rename an existing package with a hyphen (-)as the first character, the attempt fails.
PR2925: Harweb users cannot check out all files in therepository by specifying only the root path as the pathname for the files to be checked out. Thus, if the defaultview path—the root path ()—is set as the ViewPath Anchor, Harweb users cannot check out the versionsdisplayed when they execute Find Version.
PR2926: If you are using Harweb hosted in IBM WebSphereStudio and you require Tomcat, you must use Tomcat 4.0.6.For details, see System Requirements earlier in this readmefile.
7.9 Installation

PR2927: The Harvest server does not support fullyqualified host names, for example name.domain.com orname1.name2.domain.com. If the host name is fullyqualified, the Harvest server fails to start. To workaround this problem, follow these steps:
Define a host name alias as name or name1 for thefully qualified host name.
Define an environment variable, $RT_FORCE_NODE_NAMEon UNIX or a system variable RT_FORCE_NODE_NAME on Windowsand set it to the alias defined in step 1 above.
Restart the Harvest broker and RTserver if they arealready running.
PR2928: The Computer Associates shared componentsrequired by Harvest are CA Licensing (Lic98), CACryptographic Engine (CACE), CAI/PT ODBC, and EnterpriseCommunicator (PEC). Generally, on Windows, ComputerAssociates products install each of these components in theProgram FilesCA directory.
PR2929: On the s/390 machine running SuSE Linux 7.0, thecommand line utilities-only installation does not promptyou to enter the location of RTHOME; however, theinstallation completes successfully. The command lineutilities-only installation includes the PEC library files.
PR2930: On UNIX and Linux, if you are re-installingHarvest Release 5.2.1, to keep the existing Harvest Release5.2.1 database created by the first installation, you mustuse installation option [2] - Upgrade Harvest. For details,see Installation Considerations.
PR2989: When installing the Harvest server on Windows,use the Oracle SYSTEM account (or another account with therequired DBA privileges). If you use the Oracle SYSaccount, the installation program may "hang" (stop but notclose) without displaying error messages. If you experiencethis problem, use the Windows Task Manager to close theinstallation program. Then run the installation programagain, using the Oracle SYSTEM account.
PR2990: In the chapter "Installing on UNIX and Linux,"the Harvest Install Guide incorrectly states thatyou must log on to UNIX or Linux as the root user toinstall the Computer Associates Cryptographic Engine(CACE). You can install CACE on UNIX or Linux under anon-root account. The Harvest Release 5.2.1 CACEinstallation accepts an installation path directoryargument.
PR2991: On the Harvest Release 5.2.1 InstallationCD, the cmdonly folder contains a subfolder for EnterpriseCommunicator (PEC) 4.5 on s/390. This subfolder is notnecessary, because the Harvest command-line-utilities-onlyinstallation on z/OS includes the PEC files with theHarvest library files. Therefore, you can ignore thissubfolder.
7.10 Illegal Characters

PR2931: On Windows, a load repository command fails withthe following error message if the repository name includesa forward slash (/) or backward slash ():
```
Harvest Output: "E03020151: Error: Invalid View Path:   "
```
Therefore, ensure that the Harvest repository nameincludes no forward or backward slashes.
PR2932: If you rename a checked-in item to includeillegal Harvest characters and then attempt to check outthe new version, the check out attempt fails with thefollowing error message:
```
Harvest Output: "E03020028: File Agent error for item : Permission denied."
```
On Windows, the following characters are illegal andtherefore cannot be used in Harvest file names:
quotation mark (")
forward slash (/), backward slash (), or verticalseparator (|)
colon (:)
asterisk (*)
question mark (?)
carets (< >)
On UNIX and Linux, the forward slash (/) is illegal andmay not be used in Harvest file names.
7.11 Linux

PR2934: If you are installing Harvest on Linux Red Hat9, you must set the environment variableLD_ASSUME_KERNEL=2.4.1 after the installation. For details,see Installation Considerations earlier in this readme file.
7.12 Password Policy

PR2935: When AllowUsernameAsPassword = false, a passwordcan be the user's name if the case of one or more lettersis different. For example, user rabbit can create passwordRABBIT, Rabbit, raBBit, and so on. Validation fails only onpassword rabbit.
PR2936: A user with a # character at the beginning ofthe user name (for example, #uno) cannot receive a useroverride using hppolset because # denotes a comment in thepassword policy configuration file.
7.13 Security Concerns

PR2937: Installing the Harvest components requires onlysystem user access (the system user named harvest).However, installing the required Computer Associates sharedcomponents for the first time requires root user access.The Computer Associates shared components required byHarvest are CA Licensing (Lic98), CA Cryptographic Engine(CACE), CAI/PT ODBC, and Enterprise Communicator (PEC).
7.14 Version Control Interface (VCI)

PR2938: When you are using Harvest with the VersionControl Interface (VCI) on Windows 2003 or Windows .NET,setting the Check out Automatically option of the Tools,Options dialog does not check out files automatically. Usethe following steps as a work around:
Open the Options dialog.
Select the Check out automatically option.
Ensure that this option is not selected: allowchecked in items to be edited.
In your Harvest project, remove all check outprocesses except check out for update.
Open the Checkout Properties dialog and ensure thatUpdate is the only mode enabled.
After you have completed these steps, if you edit achecked in file, the file is checked out automaticallywithout invoking any dialog.
PR2939: When checking out files using Version ControlInterface with Visual Studio 6.x or Visual Studio .NET, youmay use the Synchronize or Browse checkoutoption from the Advanced Checkout dialog. Synchronizesynchronizes the project in Harvest with the versions onthe local file system. Browse replaces the files on thelocal file system with the latest versions from Harvest.Both operations will complete successfully in Harvest.Afterwards, the files remain checked in and read-only.However, both operations appear to fail because VisualStudio displays an error message. This error message isdisplayed because Visual Studio does not support thesefeatures.
7.15 WebSphere Studio Integration (WSAD Integration)

PR2998: If you open a resource in the Navigator byright-clicking and selecting Open in New Window, then bothwindows are closed when close the new window.
PR2999: WebSphere Studio Integration does not supportrefactoring of folders.
PR3000: The user interface sometimes becomes unstablewhen you are using package lists, version lists, or itemlists that contain more than 5000 list items. To avoid thisproblem, close the Harvest list view when you are workingwith extremely large projects or lists.
PR2940: While working in the Workspace, suppose youclose a project and disconnect from the Harvest repository.If you then open the same project and attempt tosynchronize, you may receive a message similar to thefollowing:
```
An unexpected Error has occurred
```
This message means that the connection to the Harvestrepository is not available, because you disconnected fromit earlier.
PR2942: If you are using WebSphere Application Server4.0.x or 5.x as your Harweb web server, you are logged outthe first time you start Harweb from WebSphere Studio,after you press any key. This logout happens only onceafter your initial logon. Afterwards, you can start Harwebfrom WebSphere Studio without being logged out.
PR2943: Before you can delete a folder in the WSADIntegration Navigator view, you must do the following:
Use the Harvest Administrator interface to deletethe folder and all its items.
Synchronize with Harvest in WSAD Integration.
PR2944: While working in project, if you rename an itemand then attempt to rename it back to its old name, youreceive an error message similar to the following:
```
Cannot rename item; new name already exists.
```
The functionality to rename an item and then rename itback to its old name is not supported by the Harvestarchitecture or WSAD Integration.
PR2945: If WebSphere Studio users are forced to changetheir passwords when logging in to WebSphere Studio andthen try to open their projects in Harvest repositories,they are denied access and receive an "incorrect login"message. To open their Harvest projects, these users mustlog out of WebSphere Studio and log back in, using theirnew passwords.
PR2946: Suppose that two users are working on the samepackage, and one user runs an interactive merge processwhile the second user wants to check out files for thatpackage. The first user running the interactive mergeprocess is locking the package so that the second usercannot check out the files. The second user receives amessage displaying that the files are locked because aninteractive merge process is in progress. The messagedisplays the machine name (but not the user name) that hasthe files checked out.
PR2947: If a process is changed in the Harvest Admin GUIwhile WebSphere Studio Integration is open, WebSphereStudio Integration does not display the change until it(WebSphere Studio Integration) is stopped and restarted.
PR2948: If the Client Path entered in the Set HarvestContext dialog is read-only and you attempt to use the Addto Workspace function, the attempt fails and an errormessage is displayed. This error message does not specifythat the path is read-only.
PR2949: If you are using Harweb hosted in IBM WebSphereStudio and you require Tomcat, you must use Tomcat 4.0.6.For details, see System Requirements earlier in this readmefile.
PR2950: When you replace the latest version of a filewith a previous version, and attempt to edit this previousversion, the file is checked out as the latest version.
PR2951: This issue applies if you perform the followingsteps while using WSAD 5.1.1 and Eclipse 2.1.2 with HarvestRelease 5.2.1:
Create a project, add files, share the project withHarvest, and then rename one or more of the files.
In Navigator view, select Replace With, Version InHarvest.
In the Version Compare window, select version 0 (N),right-click, and select Checkout (Check out for concurrentupdate must be available).
From WSAD Integration, attempt to perform any of thefollowing operations on a renamed file, from the Team menu:Undo Checkout, Check In and Keep, or Check In and Release.Each attempt results in the following errors:
```
E0202011b: Error: Item has been previously renamed within the project.           Check in failed for file: D:Workspace_WSSDprojoffline.txtE03060019: ERROR: Process Execute failed. Process Name: Check In Items.
```
PR2953: If you share a project, un-share it, immediatelyshare it again, and then attempt to use the Move and Deletefunctions for the files in that project, the attempt fails,and Harvest displays an error message similar to thefollowing:
```
Problems occurred moving the selected resources:  Resource is out of syncwith the file system...
```
To fix this problem, manually refresh the files bydouble-clicking them.
7.16 Direct Connect Considerations

The implementation of direct connection from Client toServer, Client to Remote Agent, and Remote Agent to Serverintroduces the following requirements:
Client to Server (for example: checkout to localfile system): Client host must be able to resolve theServer's hostname to an IP address.
Client to Remote Agent (for example: login to RemoteAgent): Client host must be able to resolve the RemoteAgent's hostname to an IP address.

Remote Agent to Server (for example: checkout toRemote Agent): Remote Agent host must be able to resolvethe Server's hostname to an IP address.

Note: Hostname refers to a text string up to 24characters drawn from the alphabet (A-Z), digits (0-9),minus sign (-). No distinction is made between upper andlower case. The first character must be an alpha character.The last character must not be a minus sign.

8.0 Language Certifications

After English GA, the English versions of the Harvestserver, client, agent, and Harweb have been certified torun on machines designed to use the following languages:French, German, Spanish, Italian, Portuguese (Brazil),Japanese, Korean, Traditional Chinese, and SimplifiedChinese. This certification means that these Englishversions can run on the non-English operating systems onthose machines. It is not intended to mean that theseversions are localized for those markets and languages.

9.0 Documentation

Each PDF guide in a documentation set has a uniqueDocument ID (DID) that appears on the title page of theguide. The DID uses the first six characters to identifythe guide, a hyphen, then two characters at the end toidentify the edition and language in which it is written.For example, E00110-1E identifies the first edition of theEnglish version of the Release Summary. When thesecond edition of this guide is published, the DID isincremented to E00110-2E. The DID is used withoutthe hyphen for the .PDF file on the product media and onSupportConnect as shown in File Name column of thefollowing table.

The DIDs and file names for the Harvest guides are:

Guide Name	DID	File Name
Administrator Guide	E00094-3E	E000943E.PDF
COM SDK Reference Guide	E00104-2E	E001042E.PDF
Getting Started	E00095-2E	E000952E.PDF
Install Guide	E00096-2E	E000962E.PDF
Integration Tools User Guide	E00102-1E	E001021E.PDF
Reference Guide	E00097-3E	E000973E.PDF
Release Summary	E00110-1E	E001101E.PDF
Sample Reports User Guide	E00105-2E	E001052E.PDF
SDK Reference Guide	E00109-3E	E001093E.PDF
Tutorial Guide	E00098-2E	E000982E.PDF
Harvest User Guide	E00099-2E	E000992E.PDF
Version Control Interface User Guide	E00108-3E	E001083E.PDF
Web Interface Install Guide	E00107-2E	E001072E.PDF
Readme	E00134-3E	E001343E.html

10.0 Contacting Customer Support

For online technical assistance and a complete list oflocations and phone numbers, contact Customer Support at http://ca.com/supportconnect. Customer support is available 24 hours a day, 7days a week.

For telephone assistance, call:

U.S. and Canada — 1-800-645-3042

International — (1) 631-342-4683

11.0 Downloads

CA Software Change Manager 5.2.1 patches are available as two separate downloads:

Apply the HARVEST patch to all Harvest Installations.

Apply the HARVEST and HARWEB patch to the Harweb Installation.

For the MVS and USS Agent downloads, additional details are located on the download page for each agent.

Product	Operating System - File Size
README (Harvest & Harweb)	HTML - 77.8 KB	TEXT - 73.7 KB
HARVEST	Windows - 55.0 MB	Solaris - 6.6 MB	AIX - 14.2 MB	HP-UX - 15.3 MB	RedHat Linux - 3.5 MB	SuSE Linux - 4.0 MB	MVS	USS
HARWEB	Windows - 41.9 MB	Unix - 40.9 MB

HARVEST - Harvest Client (GUI, CLI), Server, Agent, Windows Shell Ext, VCI, SDK, Eclipse Plugin
HARWEB - Harweb