Support Content Notification - Support Portal

Welcome to CA Software Change Manager 5.2.1 Patch 5. (CA Software Change Manager is hereafter called Harvest.) This readme contains installation considerations, operating system support, known issues, and instructions for contacting Computer Associates Customer Support.

This readme covers all standard and optional components for Harvest 5.2.1:

The Harvest server, client, agent, and command line utility.
The Harvest SDK components: the Harvest SDK (HSDK), the Java Harvest SDK (JHSDK), and the Component Object Model SDK (COM SDK). In previous Harvest releases, SDK components were sold separately.
CA Software Change Manager Web Interface (hereafter called Harweb).
CA Software Change Manager TestDirector Integration (hereafter called TestDirector Integration).
CA Software Change Manager Version Control Interface (hereafter called VCI).

Note: For information about CA Software Change Manager Custom Reports, see the readme file (readme_samplereports.html or readme_samplereports.txt) on the CA Software Change Manager 5.2.1 Custom Reports CD.

1.1 Plug-in for Eclipse

To use Harvest 5.2.1 Patch 5 with CA Software Change Manager Plug‑in for Eclipse (hereafter called AllFusion Harvest Plug‑in for Eclipse), you must use the version of CA Software Plug‑in for Eclipse that is compatible with Harvest 5.2.1 Patch 5. For further information, see your Computer Associates account representative.

For information about generally available (GA) versions of CA Software Plug-in for Eclipse that work with GA versions of Harvest, see the CA Software Plug-in for Eclipse documentation, including the CA Software Plug-in for Eclipse readme, on http://supportconnectw.ca.com/public/harvesteclipse.

2.0 Operating System Support

This section lists the operating systems supported by Harvest 5.2.1 components. Computer Associates supports each operating system for the duration of its life cycle (as determined by its manufacturer) or until Computer Associates announces that we no longer support it. For the latest information about supported operating systems, see our web site, https://support.ca.com.

2.1 Windows

This section lists the Windows operating systems supported by Harvest 5.2.1 components. The Harvest server, Harvest client, Harweb, Version Control Interface (VCI), and TestDirector Client require one of the following operating systems:

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 of the following web browsers:

Microsoft Internet Explorer 6.0
Mozilla 1.4 to 1.7

2.2 UNIX

This section lists the UNIX operating systems supported by Harvest 5.2.1 components.

The Harvest server and Harweb on UNIX require one of the following:

Sun Solaris 2.8, 2.9, or 10
HP-UX PA-RISC 11.00 or 11.11 (11i)
HP-UX Itanium 11.20 or 11.23
IBM AIX 5.1, 5.2, or 5.3
The HSDK on Sun Solaris runs on Solaris 2.8, 2.9, or 10 systems.
Note: If you are using Solaris 2.8 and the Sun Workshop 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 must replace the following statement:
```
 #if defined(__hpux) 
```
with this statement:
```
 #if defined(__hpux) || ( __SUNPRO_CC >= 0x500 ) 
```
The HSDK on HP-UX requires HP-UX 11.00 and HP aCC compiler A.03.25 or higher.

2.3 Linux

This section lists the Linux operating systems supported by Harvest 5.2.1 components.
The Harvest server on Linux requires Red Hat Enterprise Linux Advanced Server 3.0 or 4.0, or Red Hat Enterprise Linux Enterprise Server 3.0 or 4.0. To work properly with Harvest, Red Hat Enterprise Linux Advanced Server 3.0 or 4.0 requires that you install the latest applicable ODBC311 patch available from Computer Associates Customer Support at http://ca.com/supportconnect.
On UNIX and Linux, the Harvest command line utilities serve as the Harvest clients. The Harvest command line utilities require one of the operating systems listed previously for the Harvest server. Harweb on Linux requires Red Hat Enterprise Linux Advanced Server 3.0 or 4.0, or Red Hat Enterprise Linux Enterprise Server 3.0 or 4.0.
The HSDK requires Red Hat Enterprise Linux Advanced Server 3.0 or 4.0, or Red Hat Enterprise Linux Enterprise Server 3.0 or 4.0.
The Harvest agent on Linux requires one of the following:
2.4 z/OS

The Harvest 5.2.1 components for z/OS are the ISPF client, MVS agent, and the z/OS Unix System Services (USS) agent. These agents allow a Harvest client to access a remote USS file system or MVS data sets.
The MVS and USS agents require the following:
Red Hat Enterprise Linux Advanced Server 3.0 or 4.0, or Red Hat Enterprise Linux Enterprise Server 3.0 or 4.0
Novell SUSE LINUX Enterprise Server zSeries 8.0 or 9.0 for s/390
z/OS 1.4 or 1.5
TCP/IP protocol
C ++ Runtime Libraries
On z/OS, Harvest supports partitioned data sets and HFS files.

3.0 System Requirements
This section describes the system requirements for the Harvest components supported on each operating system.
Important! For all Harvest components on all platforms, Harvest 5.2.1 Patch 5 is not a stand-alone installation. To install this patch successfully for any Harvest component, you must have an existing Harvest 5.2.1 version of the component already installed! For instructions to install the original release of Harvest 5.2.1, see the Harvest Install Guide in the Doc directory on the Harvest installation CD.

3.1 Windows

This section describes the system requirements for the Harvest components on Windows.
Server
The Harvest server on Windows requires the following hardware and software:
An Intel Pentium processor (Pentium III recommended).
110 MB of disk space for temporary use during the installation process.
At least 70 MB of disk space for the Harvest product files.
Approximately 210 MB of disk space for the Oracle tablespaces.
The Harvest tablespaces require a minimum 150 MB of disk space (50 MB each for HarvestMeta, HarvestIndex, and HarvestBlob). This is the installation default. You may need to increase the size of the tablespaces based on your estimates, as follows: HarvestIndex tablespace requires approximately 600 KB and HarvestMeta tablespace requires approximately 100 KB per 1000 versions checked in. Harvest BLOB size depends directly on file size.
At least 128 MB of RAM. Each Harvest server process requires 15 MB of RAM.
One of the following releases of Oracle Standard Edition, Standard Edition One, or Enterprise Edition: 9i R1 (9.0.1), or 9i R2 (9.0.2).

Important! You can use Oracle 10g with Harvest 5.2.1 by downloading the required ODBC drivers, related files, and instructions from Customer Support at https://support.ca.com.
If you want to install the Harvest server with a remote database, you must do the following:
Ensure that the Harvest server has Oracle Server or Client Administrator installed.
Define an Oracle service name on the local machine, using an Oracle utility provided by the Oracle Server or Client Administrator.
Client, Installed Locally, Not Shared
When the Harvest client on Windows is installed locally and is not shared, it requires the following hardware and software:
An Intel Pentium processor (Pentium III recommended).
At least 60 MB of disk space for the Harvest product files.
At least 128 MB of RAM.
Network connection to a UNIX or Windows Harvest server using the TCP/IP protocol.
110 MB of disk space for temporary use during the installation process.
HSDK
On Windows, the HSDK is installed automatically whenever you install on a supported Windows platform any Harvest component, except Database and Documentation, from the Harvest product CD. Therefore, if you meet the installation requirements for any of those components, you also 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 the Doc directory on the Harweb product CD.
Apache Tomcat 4.0.6, 4.1.31, 5.0, or 5.5. Tomcat is available for free. For details, see the Apache web site, http://jakarta.apache.org.
Sun Java System Web Server 6.0 or 6.1. These editions are fully J2EE-compliant. These editions provide web server and servlet support for Harweb. For details, see the Sun web site, http://www.sun.com.
IBM Websphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support (based on Apache 2.0) and servlet support for Harweb. For details, see the IBM web site, http://www.ibm.com.
The Harweb machine requires the following to be installed locally:
The Harvest client
Java 2 SDK Standard Edition (J2SE) 1.4.2 to 5.0
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 the Harvest components on UNIX and Linux.
All Clients
On UNIX and Linux, the Harvest command line utilities serve as the Harvest clients. The Harvest client (command line utility) requires 15 MB of disk space.
All Servers
The Harvest server requires the following hardware and software on all supported UNIX and Linux operating systems. In addition to these requirements, you must meet the specific requirements for your operating system—those requirements are listed in the sections that follow.
A minimum 128 MB of main memory.
15 MB of virtual memory for each Harvest server process.
One of the following releases of Oracle Standard Edition, Standard Edition One, or Enterprise Edition: 9i R1 (9.0.1), or 9i R2 (9.0.2).
Important! You can use Oracle 10g with Harvest 5.2.1 by downloading the required ODBC drivers, related files, and instructions from Customer Support at https://support.ca.com.
If the Oracle database resides on a machine other than the Harvest server, SQL*Net is required.
Approximately 210 MB for the Oracle tablespaces.
Note: The Harvest installation includes the following Computer Associates shared components: CA Licensing (Lic98), CAI/PT ODBC, Enterprise Communicator (PEC), and Computer Associates Cryptographic Engine (CACE). A root user account is required to install Lic98. The other Computer Associates shared components can be installed to a user-specified location, which may not require a root account.
Sun Solaris Servers
The Harvest server on Sun Solaris requires approximately 100 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 200 MB 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 approximately 200 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 requires approximately 150 MB of disk space for the Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.
The UNIX installation program for Linux is designed for the bash shell, not the ksh shell. If your site has installed the ksh shell and linked it to /bin/sh, you must modify 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 these servlet engines, see the Harvest Web Interface Install Guide in the Doc directory on the Harweb product CD.
Apache Tomcat 4.0.6, 4.1.31, 5.0, or 5.5. Tomcat is available for free. For details, see the Apache web site, http://jakarta.apache.org.
Sun Java System Web Server 6.0 or 6.1. These editions are fully J2EE-compliant. These editions provide web server and servlet support for Harweb. For details, see the Sun web site, http://www.sun.com.
IBM WebSphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support (based on Apache 2.0) and servlet support for Harweb. For details, see the IBM web site, http://www.ibm.com.
The Harweb machine requires the following to be installed locally:
The Harvest client (command line utility)
CACE
J2SE 1.4.2 to 5.0
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 the following hardware and software:
Novell SUSE LINUX Enterprise Server zSeries 8.0 or 9.0 for s/390
Approximately 45 MB of disk space for the Harvest product files and CACE
Client

The Harvest client (command line utility) requires 30 MB of disk space.

3.4 z/OS

The Harvest 5.2.1 components for z/OS (the MVS agent and the USS agent)

On z/OS, Harvest 5.2.1 supports partitioned data sets with the ISPF client and MVS agent. Harvest supports HFS files with the USS agent.

Unix System Services (USS) Agent

The z/OS UNIX Systems Services (USS) agent allows a Harvest client to access a remote USS file system. This agent requires z/OS 1.3 or 1.4.

MVS Agent and ISPF Client

The MVS agent and ISPF Client require the following hardware and software:
TSO region size of 4096
550 tracks of temporary space
620 tracks for permanent data sets
TCP/IP protocol
C ++ Runtime Libraries
AGNTD must be installed in an apf-authorized load library for MVS installations.

3.5 TestDirector Integration

The Harvest TestDirector Integration option must be installed on the Mercury TestDirector server machine. Before installing TestDirector Integration, ensure that the following components are installed:
The third-party prep plug-in. This plug-in must be installed and enabled; for details, see the Mercury TestDirector Version Control Add-in Guide.
The TestDirector Integration third-party prep plug-in and the Harvest integration require the Java JRE 1.4.0 or greater. When using TestDirector or Harvest TestDirector Integration, you must have the Java JRE active in the path prior to installation.
Visual C++ Enterprise Edition 6.0.
One of the following:
TestDirector 8.0 with third-party version control plug-in.
TestDirector 7.6 SP3 with third-party version control plug-in, build number 7.6.2.500.

3.6 Version Control Integration (VCI)

Before installing VCI, ensure that the following components are installed:
One of the following certified tools for supporting the Microsoft Common Source Code Control (SCC) Interface:
Visual C++ 6.0 Enterprise Edition
Visual Basic 6.0 Enterprise Edition
Note: If you do not have Visual Source Safe installed, add the following line to the C:Winntvbaddin.ini file:
```
 vbscc=3 
```
Otherwise, Visual Basic source control options will not
be available.
Visual Studio .NET 2002 with Development Environment version 7.0.9372 using .NET Framework 1.0 version 1.0.3328
Visual Studio .NET 2003 with Development Environment version 7.1.3088 using .NET Framework 1.1 version 1.1.4322
Sybase PowerBuilder 9.0 or 10.0
Rational Rose Enterprise Edition 2002.05.00 or 2002.05.20
Unicenter SQL Station 6.1 or 7.0
Before using VCI, complete the setup tasks in the Version Control Interface User Guide.

4.0 Installation Considerations

Important! For all Harvest components on all platforms, Harvest 5.2.1 Patch 5 is not a stand-alone installation. To install this patch successfully for any Harvest component, you must have an existing Harvest 5.2.1 version of the component already installed!

For instructions to install the original release of 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 5, 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 5 is cumulative; that is, Patch 5 includes all fixes that were in Patch 4, Patch 2, plus additional fixes. You do not need to install previous patches before you install Patch 5.

4.1 Installing Harvest and Harweb 5.2.1 Patch 5 on Windows

On Windows, Harvest Release 5.2.1 Patch 5 is supplied in two files:
HAR521PATCH005WIN.MSI for Harvest server and client machines
HARWEB521PATCH005WIN.MSI for Harweb machines
To install Harvest 5.2.1 Patch 5 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 HAR521PATCH005WIN.MSI file on all your Harvest server, client, and Harweb machines.
On the Harweb machine, you must stop your servlet engine prior to running HARWEB521PATCH005WIN.MSI.
Run the HARWEB521PATCH005WIN.MSI file on your Harweb machine.
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
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 and Harweb 5.2.1 Patch 5 on Windows

To roll back (uninstall) Harvest 5.2.1 Patch 5 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 5 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 5 and click Remove.
To roll back Harvest 5.2.1 Patch 5 for Harweb on Windows, re-install the previous version of Harweb. For example, re-install the previous patch (Patch 4) or the base product installation (5.2.1), whichever was installed before you installed Patch 5.

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.3 Installing Harvest Release 5.2.1 Patch 5 on UNIX or Linux

On UNIX and Linux, Harvest 5.2.1 Patch 5 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, HAR521PATCH005LINUX.tar.gz. This file includes updates for all Harvest components, including client and server.

To install Harvest Release 5.2.1 Patch 5 on UNIX or Linux, follow these steps:
On Linux, ensure that the umask is set to 0022. On UNIX, 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> 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> directory created in Step 9.
Enter the following command:
```
 ApplyPATCH.sh 
```
Review the PATCH.log file in the $HARVESTHOME/PATCHES/HAR521PATCH<release>_BKP directory.

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

To roll back (uninstall) Harvest Release 5.2.1 Patch 5 on UNIX or Linux, follow these steps:
On Linux, ensure that the umask is set to 0022. On UNIX, 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>_BKP directory.
Enter the following command to run the rollback file:
```
 RollbackUPDATE.sh 
```
Review the PATCH.log file in the $HARVESTHOME/PATCHES/HAR521PATCH<release>_BKP directory.

Note: Rolling back the patch does not remove the backup directory. To remove that directory, delete it manually.

4.5 Installing Harvest Release 5.2.1 Patch 5 for USS

To install Harvest 5.2.1 patch 5 for USS, follow the instructions in the CA Software Change Manager Install Guide.

4.6 Installing Harvest Release 5.2.1 Patch 5 for MVS and the ISPF Client

Patch 5 contains a new load library with agent and ISPF interface executables and a new henglish.msg file. Therefore, before installing Patch 5, rename the load libraries for the MVS agent, the ISPF interface, and the henglish.msg file.

To install Harvest Release 5.2.1 Patch 5 for MVS and the ISPF Client, follow these steps:
Download the henglish.msg file and the unload data set from Customer Support at https://support.ca.com.

Use ASCII FTP to download henglish.msg. The FTP process allocates the sequential file for henglish.msg automatically. FTP to <hlq>.henglish.msg, where <hlq> is the product installation high-level qualifier. Use the same value used for the initial installation of Harvest 5.2.1.

Use binary FTP to download the unload data set. Before downloading it, allocate a sequential file for it, using the following sample JCL as a model. Customize this JCL for your environment.
```
 <job card> //***************************************************************** //* JCL TO PREALLOCATE HARVEST MVS INSTALLATION FILES * //* 1. ADD VALID JOB CARD * //* 2. CHANGE HLQ TO A VALID HIGH LEVEL QUALIFIER * //* 3. REMOVE COMMENTS AND SUPPLY UNIT AND STORCLAS IF REQUIRED * //***************************************************************** //ALLOCATE EXEC PGM=IEFBR14 //UNLOAD DD DISP=(NEW,CATLG),RECFM=FB,LRECL=80,BLKSIZE=6160, // SPACE=(6160,(5000,500)),DSORG=PS, //* UNIT=unitname, //* STORCLAS=storclass, // DSN=hlq. 
```
Use the TSO RECEIVE command to create the product load library. Enter the following command:
```
 RECEIVE INDSN('hlq.UNLOAD') <ENTER> 
```
where "hlq" is the product installation high-level qualifier.
When prompted for information, enter:
```
 DSNAME('hlq.LOADLIB') <ENTER>
```
where hlq is the product installation high-level qualifier.

Note: The RECEIVE command allocates and restores the LOADLIB on a volume according to the site default values. To override those values, when prompted, you can optionally specify custom values for the STORCLAS(storclas), VOLUME(vol), or UNIT(unit) parameters.
Make sure that the agent load library is APF-authorized.
If you are also using the ISPF client, use a copy of the load library for ISPF because the ISPF library cannot be APF-authorized.

4.7 Installing Harweb 5.2.1 Patch 5 on UNIX or Linux

On UNIX and Linux, Harweb 5.2.1 Patch 5 is supplied in one file HARWEB521PATCH005UNIX.tar.gz. This file includes updates for Harweb.

To install Harweb 5.2.1 Patch 5 on UNIX or Linux, follow these steps:
On Linux, ensure that the umask is set to 0022. On UNIX, 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>/Harweb/Harweb, <webappdir>/Harweb/WEB-INF, and <webappdir>/Harweb/WebDoc.
Back up the following directories: <webappdir>/Harweb/Harweb, <webappdir>/Harweb/WEB-INF, and <webappdir>/Harweb/WebDoc. For example (within Harweb home directory):
```
 tar cvf HARWEB_BKP.tar Harweb WEB-INF 
```
Copy the HARWEB521PATCH005UNIX.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 HARWEB521PATCH005UNIX.tar.gz 
```
Un-tar the PATCH file into the Harweb home directory with the following command:
```
 tar xvfo HARWEB521PATCH005UNIX.tar 
```
In the <webappdir>/Harweb/WEB-INF/lib 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.8 Rolling Back (Uninstalling) Harweb 5.2.1 Patch 5 on UNIX or Linux

To roll back Harvest 5.2.1 Patch 5 for Harweb on UNIX or Linux, re-install the previous version of Harweb. For example, re-install the previous patch (Patch 4) or the base product installation (5.2.1), whichever was installed before you installed Patch 5.

Then in the <webappdir>/Harweb/WEB-INF/lib 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.9 Running the Database Upgrade Patch

Harvest 5.2.1 Patch 5 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 HAR521PATCH005WIN 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 5. The DBPatch.sql database patch is:
Permanent
Independent of Harvest 5.2.1 Patch 5
Not intended to be rolled back
The DBPatch.sql script is located in the HAR521PATCH005WIN 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 5.

If you are upgrading from Patch 1 to Patch 5 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/HAR521PATCH005

On Windows: %HARVESTHOME%PATCHESHAR521PATCH005WIN
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/HAR521PATCH005

On Windows: %HARVESTHOME%PATCHESHAR521PATCH005WIN

4.10 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/HAR521PATCH005

On Windows: %HARVESTHOME%PATCHESHAR521PATCH005WIN

Both Tech Docs are available from Computer Associates Customer Support at http://ca.com/supportconnect.
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.11 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 TestDirector Integration and VCI 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 Advanced Server 3.0 or Enterprise Server 3.0, 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 General Considerations in this readme.

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.

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
This section contains general information about using Harvest.

5.1 Linux

If you run a Harvest component on Red Hat Enterprise Linux Advanced Server 3.0 or Enterprise Server 3.0 and you receive a runtime error stating that GLIBC is not defined, set the environment variable LD_ASSUME_KERNEL=2.4.1 before launching any Harvest executable, including the broker, server, agent, and command line utilities.
For convenience, you can set this variable in the login profile for every user who will use Harvest executables. If you use a script to start up your Harvest server, or if you configure your system to start Harvest automatically, you should also set this variable in the appropriate scripts, as follows:
```
 LD_ASSUME_KERNEL=2.4.1  export LD_ASSUME_KERNEL 
```
If you are using the C shell, use the following command:
```
 setenv LD_ASSUME_KERNEL 2.4.1 
```
5.2 Harweb

To enable Harweb to display characters properly, edit the <webappdir>HarwebWEB-INFharweb.cfg file and modify the following line to match the character set you are using:
```
 CharacterSet = <yourCharacterSet> 
```
This character set is used to determine how to translate the bytes in the web pages into characters on the screen. It is not related to the database character set; it depends on the language and web browser used. For example, using Microsoft Internet Explorer as the web browser:
To set the language to English, use the following:
```
 CharacterSet=iso-8859-1 
```
To set the language to Chinese Simplified, use the following:
```
 CharacterSet=gb2312 
```
For additional information on web-browser/language/character-sets, see the following web links:
http://www.w3.org/International/O-charset-lang.html
http://www.w3.org/International/O-charset-list.html

5.3 New and Changed Features

For a list and brief description of new and changed features supplied by Harvest 5.2.1, see the Harvest Release Summary in the Doc directory on the Harvest installation CD.

5.4 HSDK Replaces SIK

The Harvest Release 5.x HSDK replaces the Harvest SIK supplied with Harvest 4.x and earlier versions. The Harvest SIK was a C language interface to a subset of the Harvest capabilities. The HSDK is a C++ class set for the same functionality. SIK functionality can be reprogrammed using the HSDK but is not directly compatible with the HSDK.

6.0 Documentation Changes

6.1 Administrator Guid

This update applies to Defining the Port Range, located in Specifying the Harvest Communication Port Number in the chapter "Enterprise Communicator (PEC)" in the Administrator Guide. In Defining the Port Range, add the following steps after the existing Steps 1-3:
If a Harvest remote agent exists behind a network firewall, do the following:
Verify that the file <PEC HOME>standardHAgent.cm exists on the Harvest agent machine. If the file does not exist, create it.
Add the following entry to the file:
```
 setopt use_server_managed_ports true 
```
Configure the specified port range in the firewall to allow TCP/IP traffic into the Harvest server and remote agent machines. If necessary, see your network administrator for assistance.

7.0 List of Fixes

Harvest 5.2.1 Patch 5 includes all Release 5.2.1 Patch 2, Patch 3, 4, and 5.1.1 fixes. These fixes were originally created for Harvest 5.1.1 patches 16-18, WSAD Integration 2.0 patches 5-7, and Harweb 3.1 patches 10-12. A list of fixes is on our web site, http://ca.com/supportconnect.

7.1 Harvest 5.2.1 Patch 2 Fixes

PR 0766: HCO - CHECK OUT FOR SYNCHRONIZE CHECKS OUT RESERVED VERSION

PR 1130: CREATION AND MODIFICATION TIME IS THE SAME IN DATA VIEWS

PR 1382: ERROR MESSAGE IS RETURNED WHEN USER DOES NOT ENTER FORM NAME

PR 1448: WRONG TIME IN PACKAGE HISTORY REPORT

PR 1478 –VCI (ROSE) - CANNOT INCLUDE FILES IN DIRECTORIES HIGHER THAN HP~

PR 1663: RECURSIVE SEARCH VIA SHELL-EXTENSION SHOWS INCORRECT VIEWPATH

PR 1706: VCI - VB GPF WHEN PERFORMING CREATE PRJ FROM HARWITH PROJ CONTAINING COMMON FIL

PR 1789: HARWEB INSTALL CHANGING DEFAULT TIMEZONE OF JVM

PR 1875: CAN'T RESTORE PROJECT WHEN THERE ARE RESERVED TAG 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 GET VIEWPATH 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 MORE THAN 32 TIMES

PR 2593: HARVEST REPORTS - DATE FORMAT INCORRECT

PR 2621: CHECKIN FAILS ON FILES WITH SAME FILENAME BUT DIFFERENT CASE

PR 2633: STRANGE OUTPUT FOR THE UDP SCRIPT WHEN RUNNING IN HARVEST

PR 2793: NOT SHOW CHECKOUT MARKS AFTER ADD AND RESERVE IN WSAD

PR 2796: SYNC PROBLEM AFTER COPY/PASTE AN ITEM

PR 2809: FIND VER LIMIT VIEW TO STATE WHEN VIEW OPT IS VER FILTER ALL

PR 2810: FIND VER/DELETE VER SQL ERROR ORA-01795 OVER 1000 ITEMS SEL

PR 2857: HARVEST GPF WHEN DRAG PACKAGE WITH NO PROMOTE TO STATE

PR 2894: VCI - NEW FILES NOT RECOGNIZED ON USER 2 MACHINE

PR 2977: VCI - PERFORMANCE PROBLEMS WHEN ADDING PROJECTS ON 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 BRINGS HARWEB

PR 2984: HEXECP - ASYN PRODUCES AN ERROR AFTER SECOND CALL.

PR 2985: OSF AGENT WILL ERRANTLY PRODUCE A LOCKED DIRECTORY MESSAGE

PR 2986: CLICK SYMBOLIC LINE FOLDER FOR CHECKIN IN HARWEB FAILS

PR 2997: LATEST_IN_PACKAGE/ALL_IN_PACKAGE MISSING HSDK

PR 3016: VCI - VDIFF DOES NOT WORK WHEN CO HAS PRELINK UDP THAT FAILS

PR 3028: CHECKIN NON-RESERVED ITEM TAKES A LONG TIME

PR 3033: [CR] HARVEST ADDS 0X0D [CR] CHARACTER IN COMPRESSED TEXT REPOSITORY

PR 3045: PASSWORD CORRUPTED IN UDP

PR 3051: HUSRMGR RETURNS AN ERROR WHEN NO USER GROUP SPECIFIED

PR 3053: HIMPENV HANGS WITH OPTION -IUG

PR 3054: RUNTIME ERROR WHEN SET CONTEXT TO PROJECT WITH LONG NOTES

PR 3056: REFRESHING THE VERSIONS LIST WILL GET UNKNOWN ERROR

PR 3058: CHECK IN FOLDER PROBLEM WHEN FOLDER NAME HAS SPACE

PR 3068: CANCEL TAKES LONGER TIME THAN OK IN NOTIFY PROPERTIES WINDOW

PR 3079: VCI - DOC NEEDED FOR COMMON DIRECTORY

PR 3081: ADD EMPTY PROJECTS TO WORKSPACE

PR 3086: TIMESTAMP DISPLAY INCORRECT WHEN TIMEZONE IS GMT +/- #.5HR

PR 3089: STATES ARE BEING PRESENTED ALPHABETICALLY ORDERED

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 NOTHING IN OUTPUT

PR 3101: FILE EXTENSION FOR COMPRESS NOT RECOGNIZED CORRECTLY

PR 3106: CHECKIN WITH DELETE OPTION GET ERROR CANNOT OPEN SIG

PR 3124: HARVEST LOGS ERROR WHEN CHECK OUT FROM EMPTY DIRECTORY

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 AND MODIFICATION REQUEST.HFD FILES

PR 3209: TOMCAT DIRECTORY SPACE INSTALLATION

PR 3251: RESOLVE THE HOSTNAME TO AN IP ADDRESS TO BE ABLE TO CONNECT TO THE AGENT

PR 3254: PACKAGE ASSOCIATED FORMS NOT DELETED

PR 3263: FILE AGENT ALLOWS CHECKIN OF FILE W/O PERMISSIONS

PR 3286: COMPARE VIEW CAUSES PROBLEM

7.2 Harvest 5.2.1 Patch 3 Fixes

PR 3443: NON-ADMIN USER CANNOT CHECK OUT FILES WITH HARVEST 521 P2

PR 3444: DIFFERENT VERSION OF ADVANTAGE.EXE INSTALLED AFTER P2

PR 3456: COMPARE FILE/VERSION RUNTIME ERROR

PR 3473: WEB.XML NOT INSTALLED WITH PATCH 2

7.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.4 Harvest 5.2.1 Patch 5 Fixes

PR 1318 Unexpected server termination error when server still alive

PR 1500 - AGENT DOES NOT WORK WITH NIS

PR 1550 - HSQL ERROR IF INPUT FILE HAS # COMMENT LINES

PR 1589 - MENUS OF ADVANTAGE.EXE BUILT ON OS HIGHER THAN NT4 PROBLEM

PR 2118 - COMMAND-LINE UTILITIES CONTAIN PASSWORDS IN CLEAR TEXT

PR 2455 - CMDLINE USING PACKAGE NAMES BEGINNING WITH '-'

PR 3021 - Servlet error when performing concurrent merge on Package group.

PR 3022 - Move Package Process should not be available for Package groups

PR 3023 - Harweb closed after Package group related processes has executed

PR 3190 - HSDK FAILED TO CHECK OUT FILE TO REMOTE AGENT

PR 3262 - HARWEB FILE NAVIGATE HTTP 500

PR 3305 - CANT RENAME PATH IF SNAPSHOT

PR 3316 - PATCH MSI DOES NOT CHECK APPROPRIATE DIRECTORY

PR 3379 - HARWIND CHECKIN RECURSIVELY

PR 3380 - Agent NFS bug

PR 3390 - AGENT STARTUP IGNORES SERVER_NAMES DEFINED IN LICENSE.CM

PR 3396 - VERSION CHOOSER USABILITY BUG

PR 3409 - COMPARE VIEW WINDOWSIZE

PR 3431 - Multiple concurrent hexecps hang

PR 3484 - User Properties Looses Password

PR 3508 - ITEM PROPERTIES NOT ACTIVE

PR 3522 - CREATE USRGRP FROM PROJECT

PR 3532 - Create empty Dir. fail if item has D tag

PR 3533 - BROKER ABNORMAL SHUTDOWN

PR 3542 - Mass concurrent HCOs got remote agent login timeout error

PR 3562 - CI OF FILES BEGINING WITH '.'

PR 3568 - GARBLE CHARACTER

PR 3592 - agent thread issues

PR 3608 - concurrent HCO on solaris got permission denied error

PR 3609 - Add more detailed trace output for remote agent

PR 3636 - Refresh files recursive

PR 3636 - Refresh Status Problem In Plugin

PR 3671 - OPTION -DIR OF SVRENC

PR 3675 - HARWEB - FIND VERSIONS PAGE - DATE/TIME

PR 3708 - VCI - RECREATED HP~ EMPTY WHEN PERFORM ADD TO SRC CONTROL

PR 3714 - VCI - NET INCORRECT DIR PATH WHEN DIR CONTAINS DUP NAMES

PR 3734 - HARWEB Checkout Dialoge

PR 3805 - RETRY-CANCEL SCREEN-HARWEB

PR 3823 - FORM ATTACHMENT-UNKNOWN ERROR

PR 3839 - WINDOWS EXTENSION ERROR

PR 3840 - SORTING BY DATASIZE

PR 3860 - VCI - DOTNET C/O FILES WRITEABLE WHEN UNBIND/BIND

PR 3875 - HARWIND - Recursive Check in fails depending on folder level

PR 3931 - VCI - NET ADD SRC CONTROL FILE ALREADY IN HAR BECOME WRTABLE

PR 3955 - DBPRIM logging enhanced

PR 3957 - Fix Eclipse ClassCastException During Sync

PR 3957 – Migrate to 2.1.x plugin

PR 3978 - Add queue trace option for broker

PR 4017 - HARWEB - CHECK IN PROCESS PROPERTIES UPDATE

PR 4037 - Beta 2 - Forms - improper save confirmation

PR 4083 - SetDefaultBroker Return Code

PR 4088 - CI DIALOG CACHES VERSION LIST

PR 4100 - Remove Inbranch Index

PR 4105 - LOGIN FAILS AGAINST BROKER WITH VERSION_TAGS

PR 4134 - WEB LOGIC - ACCESS VIOLATION

PR 4156 - hco -nt doesn't work

PR 4192 - APPROVAL PROCESS BEHAVIOR WITH LINKED UDP''s

PR 4206 - AGNTD -HELP HAS TYPO IN TRLVL OPTION

PR 4212 - Performance with hco -br

PR 4217 - VCI - PERFORMANCE PROBLEM DURING ADD TO SRC CONTROL

PR 4255 - HARWIND: CHECK OUT FAILS WITH MSG NO "NO VERSION FOUND"

PR 4260 - Korean Language Broken

PR 4267 - Eclipse Multi-select Synchronization

PR 4275 - Eclipse 2.0 - Decorator, Share Project, et al

PR 4285 - CHECK IN AND VIEW REG FILES

PR 4319 - Can't Get New Items By Get Latest Versions

PR 4329 - HCBL-NO ACCESS:WRONG MESSAGE

PR 4356 - HARWIND: C/O VIEWPATH/FOLDERS

PR 4365 - UPPER LEVEL FOLDER CLIENT FOLDER MUST MATCH REPOSITORY FOLDER WITH NONHIER PROJECTS

PR 4455 - Cannot attach URL to a form
PR 4461 - HARWIND: SETTING COMMON ROOT FOLDER
PR 4465 - Disconnect project should mark files r/w
PR 4518 - HAR MSG FILE: DUP MESSAGE NUMS
PR 4533 - SQL HAS SECURITY HOLE
PR 4552 - MESSAGE CONTAINER HEM_F_BAGERROR ENHANCEMENT
PR 4581 - VIEW BASED VERIFY PKG DEPEND
PR 4610 - SHADOW PASSWORD SUPPORT FOR HP11
PR 4642 - HARWEB: FORMS WITH RADIO BUTTONS AND CHECK BOXES
PR 4659 - Slow Thruput in CCCHV, Client
PR 4667 - UDP: OUTPUT DISPLAY MIGHT FAIL
PR 4689 - E03020003: DATABASE ERROR when promote pkg with dependency/bind checked
PR 4741 - HARWEB - REMOVE DATE FROM A FORM - FAILURE
PR 4779 - SQL INJECTION ATTACK
PR 4789 - CATOLOG ORDER CONFUSED
PR 4808 - Dataview Navigation Slow
PR 4809 - HGUI: ADMIN: INITIAL STATE DROP-DOWN LIST
PR 4820 - ERRONEOUS ERROR DIALOG (V.V.)
PR 4848 - Verify Package Dependency wrong for branch version

8.0 Known Issues
This section lists the most prominent known issues for Harvest 5.2.1 at publication time. For other known issues, see Computer Associates Customer Support at http://ca.com/supportconnect.

8.1 Access Control

PR2910: A User Group that does not have View access to an item path can modify the item path through command line utility check in process (hci).
PR2329: Harvest Release 5.2.1 Patch 1 includes files and steps for changing the item access process to use GRANT Access instead of the DENY Access. If you perform these steps, you will not be able to roll back to a prior release or patch of Harvest, because these steps perform a database conversion that cannot be rolled back. For more information, see Changing Item Access Process to GRANT under Installation Considerations in this readme file.

8.2 Agent Connection Problems

PR3117: When you connect to a remote agent by using the Connect to New Agent option of the Remote Agent Neighborhood on the Files tab of the Harvest Administrator or Workbench GUI, the GUI caches the agent connection information.
If the remote agent is shut down and restarted, you must disconnect and reconnect the agent in the Remote Agent Neighborhood to reestablish the cached agent connection information. If you do not do so, the GUI cannot perform remote agent file handling, even though the remote agent appears valid on the Files tab.
PR 4030: A command line hco using a multi-user agent outputs an incorrect error message: "File Is Writable."
If target file has any write permission bit on and the user attempting 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."

8.3 Agent Modes

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

8.4 Check In and Check Out

PR2912: Generally, two Harvest users can share the same project files; that is, the users can both have the same files checked out simultaneously, and their changes can be merged when both files are checked in again. This ability to share files does not apply to Sybase PowerBuilder project files.
PR2913: On Windows, if you check in or check out files using HarWind (the Harvest Windows Extension) after you install the Harvest client, you may receive error messages similar to the following, even if the files are actually checked in or checked out properly:
```
 E3080003: Requested Message Key Not Found: : HSRV_I_CHECKIN E3080003: Requested Message Key Not Found: : HAPI_I_EXECUTE_SUCCESS E3080003: Requested Message Key Not Found: : HSRV_I_CHECKOUT E3080003: Requested Message Key Not Found: : HSRV_I_CHECKOUT 
```
To fix this problem on Windows 2000, restart the computer.
To fix this problem on Windows XP, close and restart all Windows Explorer sessions.
PR2948: If the client path name on a check out is set to read-only, the checkout attempt fails and you receive a message similar to the following:
```
 E03020028: File Agent error for item <drive><path>File A.txt:             Permission denied or the file is being used by another process.. 
```
The error message does not specify that the path is read-only. To fix this problem, ensure that the user attempting the check out has write access to the client path name. If necessary, see your system administrator for assistance.
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 behavior 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.

8.5 Command Line

PR2914: The project restore command line utility named hrt requires a remote file agent connection on the machine where the project was archived. For example, to restore a project to Harvest from machine A, a remote file agent must be 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> 
```
8.6 Graphical User Interface

PR2916: The function for copying multiple Lifecycle processes in the Harvest Administrator from one state to another does not work. You must copy each process individually.
PR2917: In the Administrator interface, the Add and Delete buttons are disabled on the Access tab of the linked process properties dialogs, because access to a linked process is controlled by its parent process. A user group granted access to execute a process has implicit access to execute the linked processes.
PR2918: The remove item process is slow. For example, removing approximately 25 items requires approximately one minute. The efficiency of the removal decreases as the number of items to be removed increases. Also, after each item is deleted, certain pre-link and post-link UDPs are executed automatically. Consequently, pre-link and post-link UDPs are practically unusable for the remove item process.
PR2919: The promote process may be very slow if you promote a large number of packages (for example, 200) with Verify Package Dependencies and Enable Package Merge selected.
PR2920: In the Workbench Check Out dialog, the following problems may occur:
Making a selection from the file browser changes the setting for the Context View Path, even if Use Context View Path is checked.
Clearing the Use Client View Path check box also changes the Context View Path, even if Use Context View Path is checked.
The Client View Path may be changed when you browse files if Use Context View Path is not checked or if Use Client View Path is checked.

8.7 Harweb

These issues apply to the General Web Client.
PR2921: The compare view process does not allow a user to select an alternate view name (other than the default Working View) unless the Public user group is granted Use access to the project. The View Chooser says No View. To work around this problem, add the Public user group to the Use access method for the Harvest project in the context.
PR2922: The create package process does not format the package name correctly if the package name includes one or more double quotation marks ("). If you specify a package name that includes a double quotation mark, Harvest assigns the default package name instead of the name you specified.
PR2923: The create package process does not display the associated form if the package name contains one or more single quotation marks ('). If you specify a package name that includes a single quotation mark, Harvest issues a Confirmation Message and closes the form. To display the form, open the Package Properties dialog and use the Forms tab to locate the form.
PR2924: In Harweb, you cannot use a hyphen (-) as the first character of a package name. If you attempt to name a new 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 the repository by specifying only the root path as the path name for the files to be checked out. Thus, if the default view path-the root path ()-is set as the View Path Anchor, Harweb users cannot check out the versions displayed when they execute Find Version.

PR2926: If you are using Harweb hosted in IBM WebSphere Studio and you require Tomcat, you must use Tomcat 4.0.6. For details, see System Requirements earlier in this readme file.

8.8 Installation

PR2927: The Harvest server does not support fully qualified host names, for example name.domain.com or name1.name2.domain.com. If the host name is fully qualified, the Harvest server fails to start. To work around this problem, follow these steps:
Define a host name alias as name or name1 for the fully qualified host name.
Define an environment variable, $RT_FORCE_NODE_NAME on UNIX or a system variable RT_FORCE_NODE_NAME on Windows and set it to the alias defined in step 1 above.
Restart the Harvest broker and RTserver if they are already running.
PR2928: The Computer Associates shared components required by Harvest are CA Licensing (Lic98), CA Cryptographic Engine (CACE), CAI/PT ODBC, and Enterprise Communicator (PEC). Generally, on Windows, Computer Associates products install each of these components in the Program FilesCA directory.
PR2929: On the s/390 machine running SuSE Linux, the command line utilities-only installation does not prompt you to enter the location of RTHOME; however, the installation completes successfully. The command line utilities-only installation includes the PEC library files.
PR2930: On UNIX and Linux, if you are re-installing Harvest Release 5.2.1, to keep the existing Harvest Release 5.2.1 database created by the first installation, you must use 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 the required DBA privileges). If you use the Oracle SYS account, the installation program may "hang" (stop but not close) without displaying error messages. If you experience this problem, use the Windows Task Manager to close the installation program. Then run the installation program again, using the Oracle SYSTEM account.
PR2990: In the chapter "Installing on UNIX and Linux," the Harvest Install Guide incorrectly states that you must log on to UNIX or Linux as the root user to install the Computer Associates Cryptographic Engine (CACE). You can install CACE on UNIX or Linux under a non-root account. The Harvest Release 5.2.1 CACE installation accepts an installation path directory argument.
PR2991: On the Harvest Release 5.2.1 Installation CD, the cmdonly folder contains a subfolder for Enterprise Communicator (PEC) 4.5 on s/390. This subfolder is not necessary, because the Harvest command-line-utilities-only installation on z/OS includes the PEC files with the Harvest library files. Therefore, you can ignore this subfolder.

8.9 Illegal Characters

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

8.10 Linux

PR2934: If you are installing Harvest on Red Hat Enterprise Linux Advanced Server 3.0 or Enterprise Server 3.0, you must set the environment variable LD_ASSUME_KERNEL=2.4.1 after the installation. For details, see General Considerations in this readme.

8.11 MVS Agent

Note: For related known issues, see also the following sub-sections in this section (Known Issues) in this readme:
USS Agent
USS Agent, MVS Agent, and ISPF Client
PR884: If you enter a fully qualified PDS name when selecting an initial directory from the Workbench GUI, you cannot expand the Agent node and clicking the plus sign (+) simply removes it (the plus sign). To correct this problem, right-click the agent and enter the PDS name without the final qualifier. The Agent node can now be expanded and it should be possible to select the required data set.
PR2190: When you exit the ISPF client, you may receive the following messages:
```
 "BPXP018I THREAD 1252A28000000001, IN PROCESS 83886182, ENDED WITHOUT BEING  UNDUBBED WITH COMPLETION CODE 0013E000, AND REASON CODE 00000000." 
```
These messages relate to mixed mode (MVS and Open Systems Unix) process termination and can be ignored.
PR3020: When the Harvest broker is shut down with the all option (bkrd -shutdown=all), the MVS agent issues a message indicating that the message was received. However, the agent stays active and consumes CPU time until the CPU time limit is reached. At that time, error message CEE5230S is issued. If you must shut down the MVS agent, first check that there are no active users and then simply CANCEL the job or started task.
PR3113: For RACF users only. If your attempt to log in to the MVS agent fails because you have an invalid OMVS segment, you may receive the following misleading error messages: an "Inaccessible Initial directory" message followed by a "Wrong user name for agent" message. If you receive these messages and you believe that your OMVS segment, username, and password are valid, check the MVS agent job log for RACF messages indicating why your login attempt failed.
PR3128: If you select an invalid Initial directory when connecting to an MVS agent from the Workbench GUI, clicking the plus sign (+) beside the remote agent name does not expand the node or display any data sets. The plus sign is removed, to indicate that this node cannot be expanded. In addition, the message "ERROR RETURNED FROM CATALOG SEARCH" is written to the Agent log. To correct this problem, right-click the agent and enter a valid initial directory.
PR3129: If the MVS agent is restarted while Workbench users are connected, those users are no longer able to authenticate with the agent. Attempts to check in, check out, or list PDS contents fail, and no members are displayed in the selected data sets). The MVS Agent job log shows messages like the following:
```
 "FINDFILE 5758| Spec<//'PREFIX.FILE.NAME'> Recurs<0> Fm</pt_HClient://HARSERVER/  1508> |-160 | Hnd<8> #Item<0>" 
```
The file I/O return code "-160" indicates that the security key is invalid. To correct this problem, either stop and restart the Workbench GUI, or remove and re-add the MVS agent in the Remote Agent Neighborhood on the Files tab of the Harvest Workbench GUI.
PR3130: The MVS agent abends with a B37 or E37 error if you attempt to check out items to a full partitioned data set (PDS) or if you attempt to check out new items to a full directory. To prevent or address this problem, try one or more of the following:
Use partitioned data set/extended (PDS/E) format instead of PDS format. At publication time, IBM recommends PDS/E format.
Compress your data sets frequently.
Carefully monitor directory usage, extents, and free space in your data sets. Whenever necessary, create new data sets, or reorganize existing ones, to suit your needs.
Use a utility such as BrightStor CA-PDSMAN PDS Library Management. This Computer Associates solution addresses many common library issues and which can dynamically reallocate the unused or "dead" space in a PDS. For more details about this solution, see https://support.ca.com.
If an ISPF client attempts to access an MVS data set, the list of members may not be displayed, without any corresponding error message. This problem occurs if the data set is protected by an MVS security product or if the attempt to read catalog information about the data set fails.
PR3131: If you attempt to start the MVS agent before you start the Harvest server, the agent fails to connect and issues message like the following:
```
 Could not connect to <tcp:machine-name> RTserver. Skipping starting <start_never:tcp:machine-name> RTserver. HAgent | 1040303 09:58:07 | ERROR: Initialization fails HAgent | 1040303 09:58:07 | ---- stopped ---- connect: EDC8128I Connection refused. 
```
Even if the Harvest server is subsequently started, the attempt to connect fails. To correct this problem, cancel and restart the MVS agent after you start the Harvest server.
Note: Once the MVS agent has connected successfully, you can stop and restart the Harvest server, if necessary.
PR3132: The file name filter is not supported on check in from the MVS agent. To check in a subset of members from an MVS PDS or library, use the Find button to return all members, and then select (using Shift+Click, Ctrl+Click, or both) to highlight the member(s) you require.
PR3133: Unless you specify an override HARVESTMVSHLQ= parameter, the Harvest MVS agent, by default, creates and uses temporary data sets in the HFS subsystem in the /tmp directory. These files may not always be cleaned up when the agent is shut down. Your standard housekeeping policies should include removing any leftover files in this directory. The Harvest files may be identified as having the OWNER/GROUP set to match the userid associated with the MVS agent job or task and will have names like nnnnnnnn.POnnnnnn.SInnnnnn.Xnnnnnnn.Ynnnnnnn (where nnnnnn is numeric).
PR3134: The Administrator, load repository facility does not support MVS agent files in this release. As a workaround, check in the files and members and promote them throughout your life cycle.
PR3136: When you attempt to check out a sequential file using the ISPF client, the "new" file is always allocated as FB80. As a workaround, if other DCB parameters are required, copy the file to a PDS or PDS/E and check in or check out to that data set instead.
PR3137: The ISPF client does not support multiple invocations on split screens. A U4093 abend may occur if you attempt to issue an HCI or HCO command on a split screen while a second HCI or HCO command is active or while a Harvest client is active. If a U4093 abend occurs, switch to the alternate screen(s) and shut down any instances of the Harvest application that are not required.
PR3138: If an item in an uncompressed repository is checked out to an MVS agent PDS and then simply checked back in (without being updated), Harvest creates a new version instead of reporting that no changes were detected in the file.

8.12 Password Policy

PR2935: When AllowUsernameAsPassword = false, a password can be the user's name if the case of one or more letters is different. For example, user rabbit can create password RABBIT, Rabbit, raBBit, and so on. Validation fails only on password rabbit.
PR2936: A user with a # character at the beginning of the user name (for example, #uno) cannot receive a user override using hppolset because # denotes a comment in the password policy configuration file.

8.13 Security Concerns

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

8.14 USS Agent

Note: For related known issues, see also the MVS Agent sub-section in this section (Known Issues) in this readme.
PR1205: When you start the USS agent using a UNIX X terminal remote connection to USS, your login password is echoed on the screen in plain text. This problem typically occurs when you start this connection by logging in to a non‑USS UNIX system from a Windows client and you telnet to USS from the remote UNIX shell. To prevent your login password from being echoed on the screen in plain text when you start the USS agent, use a direct telnet session, not an X terminal connection.
PR3127: This problem occurs if the broker machine suddenly restarts after you start a remote USS agent and then connect to the same agent by using the Connect to New Agent option of the Remote Agent Neighborhood on the Files tab of the Harvest Workbench GUI. If the broker machine suddenly restarts for example, because of a power failure or other unintentional shutdown, you need to re-establish your connections. To do so, start the broker, start the Workbench, and double-click the remote agent connection to the USS agent. When you double-click the remote agent connection and enter your password, you may receive an incorrect error message that your username is incorrect.
If this problem occurs, to reconnect to the agent, issue a kill -9 command to stop the agent and then restart the agent. After doing so, you can use the Workbench to connect to the newly started instance of the USS agent.
PR3139: The Harweb 5.2.1 installation overwrites files installed by Harvest 5.2.1 Patch 1. To enable Harweb to connect to USS agents, follow the steps in For Harweb and USS Agents Only in the Installation Considerations section of this readme file.

8.15 USS Agent, MVS Agent, and ISPF Client

PR3140: The USS agent, MVS agent, and ISPF client allow z/OS files to be checked into a Harvest repository as text files, performing ASCII-to-EBCDIC and record-to-stream conversion as needed. However, due to the limitations of code page conversion, not all permissible characters may be supported by this conversion. For information about code page conversion, see the IBM document z/OS V1R4.0 C/C++ Programming Guide (Document Number SC09-4765-03).
Therefore, we strongly recommend that you test to ensure that the code pages and character sets you use are compatible. If you have any doubt that the conversion does not support the source files you need to manage, we recommend setting the repository options to manage MVS and USS files in binary mode only.

8.16 Version Control Interface (VCI)

PR2938: When you are using Harvest with the Version Control 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. Use the following steps as a work around:
Open the Options dialog.
Select the Check out automatically option.
Ensure that this option is not selected: allow checked in items to be edited.
In your Harvest project, remove all check out processes except check out for update.
Open the Checkout Properties dialog and ensure that Update is the only mode enabled.
After you have completed these steps, if you edit a checked in file, the file is checked out automatically without invoking any dialog.
PR2939: When checking out files using Version Control Interface with Visual Studio 6.x or Visual Studio .NET, you may use the Synchronize or Browse checkout option from the Advanced Checkout dialog. Synchronize synchronizes the project in Harvest with the versions on the local file system. Browse replaces the files on the local 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 Visual Studio displays an error message. This error message is displayed because Visual Studio does not support these features.

8.17 Direct Connect Considerations

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

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

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

9.0 Language Certifications

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

10.0 Documentation

Each PDF guide in a documentation set has a unique Document ID (DID) that appears on the title page of the guide. The DID uses the first six characters to identify the guide, a hyphen, then two characters at the end to identify the edition and language in which it is written. For example, E00110-1E identifies the first edition of the English version of the Release Summary. When the second edition of this guide is published, the DID is incremented to E00110-2E. The DID is used without the hyphen for the .PDF file on the product media and on https://support.ca.com as shown in File Name column of the following table.

The DIDs and file names for the Harvest guides are:

Guide Name	DID	File Name
Administrator Guide	E00094-4E	E000944E.PDF
COM SDK Reference Guide	E00104-3E	E001043E.PDF
Getting Started	E00095-2E	E000952E.PDF
Install Guide	E00096-3E	E000963E.PDF
Integration Tools User Guide	E00102-1E	E001021E.PDF
Reference Guide	E00097-4E	E000974E.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
User Guide	E00099-3E	E000993E.PDF
Version Control Interface User Guide	E00108-3E	E001083E.PDF
Web Interface Install Guide	E00107-2E	E001072E.PDF
Readme	E00134-4E	E001344E.html

11.0 Contacting Customer Support

For assistance, contact Customer Support at http://ca.com/supportconnect.

12.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.

Product	Operating System - File Size
README (Harvest & Harweb)	HTML - 77.8 KB	TEXT - 73.7 KB
HARVEST	Windows - 53 MB	Solaris - 7 MB	AIX - 14 MB	HP-UX - 15 MB	HP-Itanium - 12 MB	Redhat Linux - 3 MB	SuSE Linux - 3 MB
HARWEB	Windows - 42 MB	Unix - 41 MB

CA Software Change Manager 5.2.1 MVS and USS agent downloads are available below:

MVS Agent	USS Agent
HENGLISH.MSG - 39 KB unload - 51 MB	agentonly_uss.tar - 20 MB

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