CA Software Change Manager r7 Readme E001703E - CA Technologies
{{search ? 'Close':'Search'}}

CA Software Change Manager r7 Readme
E00170-3E


1.0 Welcome
1.1 Plug-in for Eclipse

2.0 Operating System Support
2.1 Windows
2.2 UNIX
2.3 Linux
2.4 z/OS
2.5 Novell SUSE LINUX Enterprise Server for s/390

3.0 System Requirements
3.1 Windows
3.2 UNIX and Linux
3.3 Web Servers
3.4 ISPF Client
3.5 LDAP Provider
3.6 Security
3.7 TestDirector Integration
3.8 Version Control Interface (VCI)
3.9 Harvest Sample Reports

4.0 Installation Considerations
4.1 Security Concerns
4.2 For Ingres Users - Windows
4.3 For Ingres Users - Novell SUSE LINUX Enterprise Server
4.4 For Oracle Users
4.5 For Novell SUSE LINUX Enterprise Server for s/390 Users
4.6 For Novell SUSE LINUX Enterprise Server for x86 Users
4.7 For Red Hat Linux Users
4.8 For Harweb Users Running Sun Java System Web Server
4.9 For Harweb Users Running WebSphere Application Server on AIX
4.10 Sample Reports
4.11 Sample Reports and Ingres
4.12 CA Cryptographic Engine (CACE) on Sun Solaris 8
4.13 TestDirector Integration
4.14 Computer Associates Licensing (Lic98)
4.15 For RACF Users
4.16 Plug-in External Merge/Compare Tools

5.0 General Considerations
5.1 Performance Management
5.2 Accessing Harvest Objects using Visual Basic Scripts

6.0 Documentation Changes
6.1 Sample Reports User Guide
6.2 SDK Reference Guide
6.3 Version Control Interface User Guide

7.0 List of Fixes
7.1 How to Find Known Issues and Fixes

8.0 Known Issues
8.1 Access Control
8.2 Agent Connection Problems
8.3 Broker Shutdown
8.4 Character Sets
8.5 Check In and Check Out
8.6 Command Line
8.7 Direct Connection Considerations
8.8 Graphical User Interface
8.9 Harweb
8.10 Ingres
8.11 Installation
8.12 Illegal Characters
8.13 Linux
8.14 Oracle
8.15 Password Policy
8.16 Version Control Interface (VCI)
8.17 z/OS Agent and ISPF Client

9.0 International Support

10.0 Documentation

11.0 Contacting Customer Support


1.0 Welcome

Welcome to AllFusion Harvest Change Manager r7. (Harvest.) This readme file 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 r7:

  • 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 Sample Reports.

  • CA Software Change Manager TestDirector Integration (TestDirector Integration).

  • CA Software Change Manager Version Control Interface (VCI).

  • CA Software Change Manager Web Interface (Harweb).


    1.1 Plug-in for Eclipse

    To use Harvest r7 with AllFusion Harvest Change Manager Plug-in for Eclipse (AllFusion Harvest Plug-in for Eclipse), you must use the version of AllFusion Harvest Plug-in for Eclipse that is compatible with Harvest r7. For further information, see your Computer Associates account representative.

    For information about generally available (GA) versions of AllFusion Harvest Plug-in for Eclipse that work with GA versions of Harvest, see the AllFusion Harvest Plug-in for Eclipse documentation, including the AllFusion Harvest 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 r7 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 are no longer supporting it. For the latest information about supported operating systems, see our website, https://support.ca.com.


    2.1 Windows

    This section lists the Windows operating systems supported by Harvest r7 components.

    Multiple Components

    The Harvest server, Harvest client, agent, Harweb, VCI, and TestDirector Client require one of the following operating systems:

  • Windows 2000 Server

  • Windows 2000 Advanced Server

  • Windows 2000 Professional

  • Windows Server 2003 Standard

  • Windows Server 2003 Enterprise

  • Windows XP Professional

    TestDirector Server

    TestDirector Server requires one of the following:

  • Windows 2000 Server

  • Windows Server 2003 Enterprise

    Harweb

    Harweb requires an operating system that supports one of the following web browsers:

  • Microsoft Internet Explorer 6.0

  • Mozilla 1.4 to 1.7

    Sample Reports

    The database server running the Harvest Sample Reports component requires a Windows operating system that supports CA Software Change Manager Server r7. The database server is the machine that stores the Harvest database.

    A machine running Sample Reports locally requires one of the following operating systems:

  • Windows 2000

  • Windows XP

    A server hosting Sample Reports on a network requires one of the following operating systems:

  • Windows 2000 Server

  • Windows 2000 Advanced Server

  • Windows 2000 Professional

  • Windows 2003 Server

  • Windows 2003 Advanced Server

    A client accessing the host server for Sample Reports requires a Windows operating system that supports the following:

  • CleverPath Forest & Trees Runtime Option 7.0

  • Microsoft Internet Explorer 6.0

    LDAP Authentication

    LDAP authentication for Harvest multi-user agents is supported on the following Windows platforms:

  • Windows 2000 Server

  • Windows 2000 Advanced Server

  • Windows 2000 Professional

  • Windows Server 2003 Standard

  • Windows Server 2003 Enterprise

  • Windows XP Professional

    Note: For information about LDAP authentication for Harvest multi-user agents, see Configuring LDAP Authentication in the chapter "Client/Server Communication" in the CA Software Change Manager Administrator Guide.


    2.2 UNIX

    Important! If you are using Sun Solaris 8, your operating system must have the required patches installed to support the CA Cryptographic Engine (CACE). For details, see Installation Considerations in this readme.

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

    Multiple Components

    On UNIX, the Harvest server, Harweb, client (command line utilities), and agent require one of the following operating systems:

  • Sun Solaris 8, 9, or 10

  • HP-UX PA-RISC 11.00, 11i

  • HP-UX Itanium 11.23

  • IBM AIX 5.1, 5.2, or 5.3

    Additional requirements and information follow, as needed.

    Command Line Utilities (including HSDK and JHSDK)

    The Harvest command line utilities on UNIX serve as the Harvest clients.

    The HSDK and JHSDK are installed automatically when you install the command line utilities.

    Note: If you are using Solaris 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, replace the following statement:
     #if defined(_hpux) 

    with this statement:
     #if defined(_hpux) || ( _SUNPRO_CC >= 0x500 ) 

    The HSDK on AIX requires AIX 5.1, 5.2, or 5.3 and the IBM XL C/C++ compiler for 7.0.

    The HSDK on AIX or HP-UX requires stlport 4.6.2.

    The HSDK on Solaris requires stlport 4.5, which is supplied with the Sun compiler SunOne Studio 8.

    LDAP Authentication

    Multi-user agent LDAP authentication is supported on the following UNIX platforms. Your UNIX operating system must support random number generators for TLS certificates, as noted in the following list:

  • IBM AIX 5.1, 5.2, 5.3

    OpenSSH on these versions of AIX is compiled using the entropy gathering mechanism (random numbers) provided with the OpenSSH source code (ssh-rand-helper).

    The AIX 5.1, 5.2, or 5.3 base security provides new pseudo random number generator devices, /dev/random and /dev/urandomM.

  • Hewlett-Packard HP-UX

  • HP-UX PA-RISC 11.00, 11i

  • HP-UX Itanium 11.23

    The /dev/random and /dev/urandom devices are not available on certain release of HP-UX 11.x. They are available as part of the "rng" software kit and can be downloaded from http://hp.com.

  • Sun Solaris 8, 9, 10

    On Sun Solaris 8, Patch 112438-03 or higher is required for random number generation.

    Note: For information about LDAP authentication for Harvest multi-user agents, see Configuring LDAP Authentication in the chapter "Client/Server Communication" in the CA Software Change Manager Administrator Guide.


    2.3 Linux

    This section lists the Linux operating systems supported by Harvest r7 components.

    Multiple Components

    On Linux, the Harvest server, Harweb, client (command line utilities), and agent require one of the following operating systems:

  • Red Hat Enterprise Linux Advanced Server 3.0 and 4.0 and Red Hat Enterprise Linux Enterprise Server 3.0 and 4.0

  • Novell SUSE LINUX Enterprise Server 8 or 9 for x86 with an ext3 file system.

    Additional requirements and information follow, as needed.

    Command Line Utilities (including HSDK and JHSDK)

    On Linux, the Harvest command line utilities serve as the Harvest clients.

    The HSDK and JHSDK are installed automatically when you install the command line utilities.

    Important! If you are using Linux, your operating system must have the required files and rpm packages installed. For details, see Installation Considerations in this readme.

    LDAP Authentication

    Multi-user agent LDAP authentication is supported on the following Linux platforms. Your Linux operating system must support random number generators for TLS certificates, as noted in the following list:

  • Red Hat Enterprise Linux Advanced Server 3.0 and 4.0 and Red Hat Enterprise Linux Enterprise Server 3.0 and 4.0

    On Red Hat Enterprise Linux, the /dev/random and the /dev/urandom devices are installed by the base operating system as part of the dev rpm (for example, dev-3.3.8-1 on Red Hat Enterprise Linux Advanced Server 3.0).

  • Novell SUSE LINUX Enterprise Server 8 or 9

    On Novell SUSE LINUX Enterprise Server, the /dev/random and the /dev/urandom devices are installed by the base operating system as part of the dev rpm (for example, devs-2002.10.4-9 on SUSE LINUX Enterprise Server 8).


    2.4 z/OS

    The z/OS agent allows a Harvest client to access a remote USS file system or MVS data sets. This agent requires z/OS 1.4, 1.5, or 1.6.

    The z/OS agent requires:

  • TCP/IP protocol

  • C ++ Runtime Libraries

    On z/OS, Harvest supports partitioned data sets and HFS files.


    2.5 Novell SUSE LINUX Enterprise Server for s/390

    The Harvest client (command line utility) and agent on Novell SUSE LINUX Enterprise Server 8 or 9 for s/390 requires the following hardware and software:

  • Novell SUSE LINUX Enterprise Server 8 or 9 for s/390

  • Approximately 45 MB of disk space for the agent, CA Cryptographic Engine (CACE), and Enterprise Communicator (PEC)

  • Approximately 30 MB of disk space for the client


    3.0 System Requirements

    This section describes the system requirements for the Harvest components supported on each operating system.


    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 4 recommended).

  • Memory: 512 MB; 1 GB if running both Harvest and Ingres.

  • 110 MB of disk space for temporary use during the installation process.

  • At least 70 MB of disk space for the Harvest product files.

  • A local or remote Oracle database or a local Ingres database running a supported version of Oracle or Ingres. Details about each database's requirements are provided in this section.

    Harvest Server with an Ingres Database

    Harvest with Ingres requires the following:

  • An Intel Pentium processor (Pentium 4 minimum).

  • Disk Space: 3 GB recommended.

  • Memory: 1 GB RAM, minimum. Each Harvest server process requires 15 MB of RAM.

    Ingres

    Ingres requires the following:

  • A minimum 512 MB of RAM; 1 GB if running both Harvest and Ingres.

  • 130 MB of disk space for the initial installation.

  • Approximately 1 to 10 GB of disk space to account for database growth.

  • 512 MB to 2 GB for the Ingres transaction log.

    Important! The Harvest express installation sets the Ingres transaction log file size to 512 MB. The total file size the Harvest server can process at any one time is approximately one-sixth of the transaction log size. Therefore, if you use the express installation, the total file size the Harvest server can process at any one time is approximately 128 MB. If this file size does not meet your requirements, you should either use the custom installation (see the CA Software Change Manager Installation Guide) or set the transaction log size to a sufficiently higher value after installation (see the Ingres System Administrator Guide).

    For further information about Ingres, see your Ingres documentation.

    Oracle

    Oracle requires the following:

  • Oracle 9.2.0 EE, 9.2.0 SE, or 10g

  • Approximately 210 MB of disk space for the Oracle tablespaces

    For further information about Oracle, see your Oracle documentation.

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

  • If you want to install the Harvest server with a remote Oracle database, see the AllFusion Harvest Change Manager Installation Guide.

    Agent and 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. These requirements also apply to the Harvest agent on Windows.

  • An Intel Pentium processor (Pentium 4 recommended).

  • At least 60 MB of disk space for the Harvest product files.

  • At least 512 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 any Harvest component, except Database and Documentation, on a supported Windows platform. 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 CA Software Change Manager Installation Guide in the Docs directory on the Harweb installation media.

  • Apache Tomcat 4.1.29, 4.1.30, 5.0.25, 5.5.4, 5.5.7, or 5.5.9. Tomcat is available for free. For details, see the Apache website, 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 website, http://sun.com.

  • IBM WebSphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support and servlet support for Harweb. For details, see the IBM website, http://ibm.com.

    The Harweb machine requires the following to be installed locally:

  • The Harvest client (command line utility)

  • One of the following versions of Java SDK Standard Edition:
    - 1.4.2_04, 1.4.2_05, 1.4.2_06, 1.4.2_07
    - 1.5 (also called 5.0)
    - 1.5.0_01 (also called 5.0 Update 1)
    - 1.5.0_02 (also called 5.0 Update 2)

    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 requirements 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 later in this section.

    Requirements for Linux machines include the following:

  • An Intel Pentium processor (Pentium 4 recommended).

  • A minimum 128 MB of main memory.

  • 15 MB of virtual memory for each Harvest server process.

  • A local or remote Oracle database or a local Ingres database running a supported version of Oracle or Ingres. Details about each database's requirements are provided in this section.

    Requirements for UNIX machines include the following:

  • IBM AIX: 1.65 GHz, 512 MB RAM.

  • HP-UX: 650 MHz, 512 MB RAM.

  • Sun Solaris: 1.28 GHz, 512 MB RAM.

  • 15 MB of virtual memory for each Harvest server process.

  • A local or remote Oracle database or a local Ingres database running a supported version of Oracle or Ingres. Details about Oracle's requirements are provided in this section.

    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 CA Licensing (Lic98). The other Computer Associates shared components can be installed to a user-specified location, which may not require a root account.

    Ingres

    Ingres requires the following:

  • A minimum 512 MB of RAM; 1 GB if running both Harvest and Ingres.

  • 130 MB for the initial installation.

  • Approximately 1 to 10 GB to account for database growth.

  • 512 MB to 2 GB for the Ingres transaction log.

  • Ingres runs on Novell SUSE LINUX Enterprise Server. For important related requirements, see Operating System Support in this readme.

    Important! The Harvest express installation sets the Ingres transaction log file size to 512 MB. The total file size the Harvest server can process at any one time is approximately one-sixth of the transaction log size. Therefore, if you use the express installation, the total file size the Harvest server can process at any one time is approximately 128 MB. If this file size does not meet your requirements, you should either use the custom installation (see the CA Software Change Manager Installation Guide) or set the transaction log size to a sufficiently higher value after installation (see the Ingres System Administrator Guide).

    For more information about Ingres, see your Ingres documentation.

    Ingres database files cannot be stored in a reiser file system ("reiserfs").

    Important! If you plan to install Harvest and Ingres on Novell SUSE LINUX, the GCC (GNU C Compiler) must be installed before you install Harvest!

    Oracle

    Oracle requires the following:

  • Oracle 9.2.0 EE, 9.2.0 SE, or 10g.

  • If the Oracle database resides on a different machine than the Harvest server, SQL*Net is required.

  • Approximately 210 MB for the Oracle tablespaces.

    For more information about Oracle, see your Oracle documentation.

    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.

    For Solaris 8, only, Harvest on Solaris requires the latest Sun patches for SUNWlibC and SUNWlibCx. The patches installed must be at least the following versions:

  • SUNWlibC 32-bit requires 108434-17

  • SUNWlibCx 64-bit requires 108435-17

    If the following command does not return libCrun.so.1 and libCstd.so.1, your system needs to be patched.
     ls /usr/lib/libC* 

    To obtain a patch, go to the Sun website, http://sun.com.

    To determine what version of a patch is already installed on your machine, enter the following command:
     showrev -p | grep patch# 

    where patch# is the number of the patch, for example, 108434 or 108436. This command returns the version of the patch.

    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.

    Harvest on AIX requires IBM C Set ++ Runtime for AIX at level 7.0.0.0 or higher. To check what version of C Set ++ Runtime for AIX is installed on your server, enter the following command at the command line:
     $ lslpp -L xlC.rte 

    Something similar to the following should be returned:
     Fileset                Level  State  Type  Description (Uninstaller) -------------------------------------------------------------------- xlC.rte              7.0.0.0    C     F    C Set ++ Runtime 

    The Level must be 7.0.0.0 or higher with a State of C for Committed. If you do not have at least level 7.0.0.0 of C Set ++ Runtime for AIX installed, you must upgrade your AIX runtime libraries before running Harvest.

    For more information on IBM C Set ++ Runtime for AIX, go to the IBM website, http://ibm.com.

    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.

    Novell SUSE LINUX Enterprise Server for x86 Servers

    The Harvest server on Novell SUSE LINUX Enterprise Server 8 or 9 for x86 requires approximately 150 MB of disk space for the Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.

    The Linux installation program 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 65 MB of disk space.

    Harweb requires one of the following servlet engines. For instructions to install Harweb and each of these servlet engines, see the AllFusion Harvest Change Manager Installation Guide in the Docs directory on the Harweb installation media.

  • Apache Tomcat 4.1.29, 4.1.30, 5.0.25, 5.5.4, 5.5.7, or 5.5.9. Tomcat is available for free. For details, see the Apache website, 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 website, http://sun.com.

  • IBM WebSphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support and servlet support for Harweb. For details, see the IBM website, http://ibm.com.

    The Harweb machine requires the following to be installed locally:

  • The Harvest client (command line utility)

  • CA Cryptographic Engine (CACE)

  • One of the following versions of Java SDK Standard Edition:
    - 1.4.2_04, 1.4.2_05, 1.4.2_06, 1.4.2_07
    - 1.5 (also called 5.0)
    - 1.5.0_01 (also called 5.0 Update 1)
    - 1.5.0_02 (also called 5.0 Update 2)

  • Enterprise Communicator (PEC)

  • Mozilla 1.4 to 1.7 web browser


    3.3 Web Servers

    Note: Ensure that the version of Java SDK Standard Edition you install is supported by the web server you plan to install.

    Microsoft IIS

    Sample Reports requires Microsoft Internet Information Server (IIS) version 5.0 or 6.0.

    Sun Java System Web Server

    Harweb supports Sun Java System Web Server Enterprise Edition 6.0 and 6.1.

    Note: This edition is supported as both web server and J2EE platform for Harweb.

    IBM WebSphere

    Harweb requires IBM WebSphere Application Server 5.0 or 5.1.

    Note: WebSphere Application Server includes an HTTP web server based on Apache Webserver and is fully J2EE compliant. This edition also provides web server and servlet support for Harweb. For details, see the IBM website, http://ibm.com.


    3.4 ISPF Client

    The ISPF Client requires 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


    3.5 LDAP Provider

    At publication time, to use LDAP authentication, you must install Novell eDirectory 8.7.3 on your LDAP server.


    3.6 Security

    By default, Harvest agents that have LDAP authentication installed and configured use Transport Layer Security (TLS) to communicate with the LDAP server. However, you can optionally configure the file agent to use no encryption mechanism. For details, see the AllFusion Harvest Change Manager Administrator Guide.


    3.7 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.2_04. When using TestDirector or Harvest TestDirector Integration, you must have the Java JRE active in the path prior to installation.

  • Visual C++ 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.8 Version Control Interface (VCI)

    Before installing Version Control Interface (VCI), ensure that one of the following certified tools for supporting the Microsoft Common Source Code Control (SCC) Interface is installed:

  • Visual C++ 6.0 Enterprise Edition

  • Visual Basic 6.0 Enterprise Edition

    Note: In order for Visual Basic to work, you must install Visual Source Safe (VSS) because Visual Basic is not a native SCC client. Microsoft does not configure Visual Basic for SCC by default. When you install Visual Basic and choose to install Source Safe, Microsoft creates a vb.ini file in your C:winntsystem32 directory. This file sets a flag to support SCC. This configuration is specific to Visual Basic but not to Harvest. For instructions 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

  • Visual Studio .NET 2005

  • Sybase PowerBuilder 8.0.3, 9.0, and 10.0

  • Rational Rose:
    - Rational Rose 2003
    - Rational Rose XDE Developer for Java
    - Rational Rose XDE Developer for .NET
    - Rational Rose XDE Developer for Visual Studio

    Before using the VCI, complete the setup tasks in the CA Software Change Manager Version Control Interface User Guide.


    3.9 Harvest Sample Reports

    This section describes the system requirements for the Harvest Sample Reports component.

    Database Server

    The database server requires AllFusion Harvest Change Manager Server r7.

    A machine running Sample Reports locally requires the following software:

  • CleverPath Forest & Trees 7.0 (required to customize reports, optional to view reports)

  • CleverPath Forest & Trees Runtime Option 7.0 (required to view reports)

  • Oracle Client 9.2.0 EE, 9.2.0 SE, or 10g; or Ingres r3 client

  • System DSN (with Ingres or Oracle data source)

  • Ingres vnode (with Ingres)

    Server

    A server hosting Sample Reports on a network requires the following software:

  • CleverPath Forest & Trees 7.0 (required to customize reports, optional to view reports)

  • CleverPath Forest & Trees Runtime Option 7.0

  • Remote Data Server Components

  • Microsoft Internet Information Services (IIS) 5.0 or 6.0

  • Microsoft Data Services

  • CleverPath Portal 4.01 (optional)

  • Windows Authentication Component (optional)

  • Oracle Client 9.2.0 EE, 9.2.0 SE, or 10g; or Ingres r3 client

  • System DSN (with Ingres or Oracle data source)

  • Ingres vnode (with Ingres)

    Client

    A client accessing the host server for Sample Reports requires a Windows operating system that supports the following:

  • CleverPath Forest & Trees Runtime Option 7.0

  • Microsoft Internet Explorer 6.0


    4.0 Installation Considerations

    For instructions to install Harvest r7, see the CA Software Change Manager Installation Guide in the Docs directory on the Harvest installation media.

    This section contains miscellaneous installation considerations for Harvest r7.

    Notes:

  • Harvest r7 is cumulative.

  • For additional installation-related information in this readme, see Installation in Known Issues and Installation Guide in Documentation Changes.


    4.1 Security Concerns

    PR2937: On UNIX and Linux, 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).

    After these Computer Associates shared components have been installed once, only system user access (the system user named harvest) is required to update, delete, or re-install them. The only exception is Lic98, which always requires root access to install, update, delete, or re-install.

    Also, you must have root access to install Harvest with the Harvest server with Ingres. This requirement applies to custom and express installations.


    4.2 For Ingres Users - Windows

    PR4045: On Windows, if you install Ingres while installing the Harvest server, do not use an operating system user named "harvest" to install the Harvest server.

    This warning applies to both the express and custom installations of the Harvest server documented in the chapter "Upgrading or Installing the Harvest Server on Windows" in the CA Software Change Manager Installation Guide.


    4.3 For Ingres Users - Novell SUSE LINUX Enterprise Server

    Using Harvest with Ingres is supported on Novell SUSE LINUX Enterprise Server only, not on any other Linux platforms. Using Harvest with Ingres is not supported on UNIX.

    As noted earlier in PR2937 under Security Concerns, you must have root access to install Harvest with the Harvest server with Ingres (custom or express).

    Ensuring Required File Permissions for Ingres

    While installing Harvest with Ingres on Novell SUSE LINUX Enterprise Server, after accepting the license agreement, you may receive an error message similar to the following:
     System user : ingres has been created but no password has been set. Please set the password to enable login for this user. Response file is not readable by user : ingres     II_RESPONSE_FILE=/root/harvest/harvest/install/ingrestmp.rsp ...  execution of ca-ingres-EI-3.0.1-109 script failed, exit status 5  ca-ingres is not installed under /opt/CA/IngresEI  Aborting... ... 

    The message may indicate that several Ingres scripts have failed and aborted.

    The error is issued because the : ingres user does not have the required access rights. For the installation to complete successfully, the : ingres user must exist and must have read and execute permission to the parent folders of the Harvest installation script. If the : ingres user does not exist, the installation creates it automatically. However, if you receive the error message above, do the following to fix the problem:

  • Before running the express installation again, check to see if the : ingres user already exists.

  • If the : ingres user does already exist, ensure that it (or the user group to which it belongs) has read and execute permission to the parent folders of the Harvest installation script.

    If the : ingres user does not already exist, ensure that all users have read and execute permission to the parent folders of the Harvest installation script.

  • Run the installation again.

    GCC Compiler Required

    Important! If you plan to install Harvest and Ingres on Novell SUSE LINUX, the GCC (GNU C Compiler) must be installed before you install Harvest!

    ext3 File System Required

    If you are using Ingres on Novell SUSE LINUX Enterprise Server, you must use an ext3 file system. Ingres database files cannot be stored in a reiser file system ("reiserfs").

    Changing Ownership of the hsvr.dfo File

    PR4052: After you have completed a custom or express installation of the Harvest server, the root user owns the .hsvr.dfo file. Consequently, the Harvest server cannot read the .hsvr.dfo file. Therefore, the Harvest server cannot start and you cannot run the database configuration utility.

    To fix this problem, after the installation has completed, while logged on as the root user, run the following commands to change the ownership of the .hsvr.dfo file:
     chown harvest .hsvr.dfo  chgrp harvest .hsvr.dfo 


    4.4 For Oracle Users

    WARNING! You must install Oracle before installing Harvest!

    WARNING! If you are using Oracle, do not use configdsn to set up your Harvest database. You must use the database configuration utility instead. For instructions to use it, see the chapter "Installing, Configuring, and Maintaining Your Database" in the AllFusion Harvest Change Manager Installation Guide.

    Note: If you are upgrading your version of Oracle from 8.x to a newer version, you must upgrade Oracle first, before upgrading Harvest.


    4.5 For Novell SUSE LINUX Enterprise Server for s/390 Users

    If you are using Novell SUSE LINUX Enterprise Server for s/390 and you encounter an error regarding a missing libstdc++-libc6.1-2.so.3 file, you must install the gcc-c++-2.95.2-4.s390.rpm package. This rpm package may be provided on the Novell SUSE LINUX Enterprise Server installation CDs. If necessary, download this rpm package from (http://linux.s390.org/ or http://rpmfind.net/) and install it. For instructions to install or update an rpm package, see the rpm man pages.


    4.6 For Novell SUSE LINUX Enterprise Server for x86 Users

    If you are using Novell SUSE LINUX Enterprise Server for x86 and you encounter an error regarding a missing libgcc_so.1 or libstdc++.so.5 file, install one of the following packages:

  • Novell SUSE LINUX Enterprise Server 8.2 - libgcc 3.3-23.i586 rpm and libstdc++ 3.3-23.i586.rpm

  • Novell SUSE LINUX Enterprise Server 9.0 - libgcc 3.3.1-29.i586 rpm and libstdc++ 3.3.1-29.i586.rpm

  • Novell SUSE LINUX Enterprise Server 9.1 - libgcc 3.3.3-41.i586 rpm and libstdc++ 3.3.3-41.i586.rpm

    These rpm packages may be provided on the Novell SUSE LINUX Enterprise Server installation CDs. If necessary, download these rpm packages from the SUSE website (http://novell.com/linux/suse or http://rpmfind.net/) and install them. Doing so is required if you are using an emulator to connect from a Windows machine to a /linux_base port. For instructions to install or update an rpm package, see the rpm man pages.


    4.7 For Red Hat Linux Users

    If you are using Red Hat Enterprise Linux Advanced Server 3.0 or 4.0 or Red Hat Enterprise Linux Enterprise Server 3.0 or 4.0 and you encounter an error regarding a missing *.so file, install the corresponding rpm package for your Red Hat operating system. For example:

  • If the libgcc_s.so.* file is missing, install the libgcc-*.i386.rpm package

  • If the libstdc++.so.* file is missing, install the libstdc++-*.i386.rpm package

  • If the libstdc++-libc6.2-2.so.* file is missing, install the compat-libstdc++*.i386.rpm package

    Normally, the rpm packages for your Red Hat operating system are provided on the installation CDs for your Red Hat operating system. However, if necessary, you can download these rpm packages from the Red Hat website (http://redhat.com/ or the RPM website http://rpmfind.net/). After acquiring the rpm packages you need, install them. Doing so is required if you are using an emulator to connect from a Windows machine to a /linux_base port. For instructions to install or update an rpm package, see the rpm man pages.

    Note: Harvest is built with the libraries in the libgcc-3.2.3-20.i386.rpm and libstdc++-3.2.3-20.i386.rpm packages.


    4.8 For Harweb Users Running Sun Java System Web Server

    PR4637: Harweb may not work correctly if you use Sun Java System Web Server 6.1 SP4 and Sun Solaris 10 together. As a workaround, try the following:

  • Adding the following lines in the harweb.cfg file:
     user=username  password=password 

    where username and password are your user name and password for accessing your Harvest database.

  • Using Sun Java System Web Server 6.1 SP4 on Solaris 9

  • Using Tomcat 5.0.25, 5.5.4, 5.5.7, or 5.5.9 on Solaris 10

    PR4700: When deploying Harweb on Sun Java System Web Server, update the internal library path names of the web server with the Harvest libraries. To do so, follow these steps:

  • Log in to the Admin console of Sun Java System Web Server.

  • Select Manage WebServer.

  • Select Java.

  • Select JVM Path Settings.

  • Add the following path names to Native Lib Path Prefix. These names are the default path names. If you are using different path names, enter your path names instead:
     /opt/CA/CAcrypto:  /opt/CA/harvest/lib:  /opt/CA/pec/lib/i86_linux24 


    4.9 For Harweb Users Running WebSphere Application Server on AIX

    When you attempt to deploy Harweb on WebSphere Application Server 5.x on AIX, WebSphere Application Server may issue an OutOfMemoryError exception error and abort the attempt. If this problem occurs, perform the following steps:

  • On the AIX machine running WebSphere Application Server, change to the WebSphere Application Server installation directory.

  • Change to the /bin subdirectory.

  • In the /bin directory, edit the wsadmin.sh file.

  • Locate the following statement:
     "$JAVA_HOME/bin/java"  

  • On the next line, add the following:
     -Xmx192m  

    The new statement should be:
     "$JAVA_HOME/bin/java" 
    -Xmx192m

  • Save the file.

    After performing these steps, attempt to deploy Harweb again.

    For instructions to install and deploy Harweb, see the CA Software Change Manager Installation Guide. For more information about the WebSphere Application Server memory error, see the IBM website, http://ibm.com.


    4.10 Sample Reports

    You must install the Harvest r7 server and client before you install Sample Reports. For instructions to install Harvest r7, see the CA Software Change Manager Installation Guide.

    For instructions to install and use Sample Reports, see the CA Software Change Manager Sample Reports User Guide in the Docs directory on the Harvest installation media.


    4.11 Sample Reports and Ingres

    If you are using Sample Reports and Ingres, you must set up an ODBC data source using the System DSN tab of the Windows ODBC Data Source Administrator, as explained in the chapter "AllFusion Harvest CM Sample Reports" in the CA Software Change Manager Sample Reports User Guide. In that chapter, when performing Step 5 in Setup for Ingres (Local), to set up the ODBC data source for a local Ingres user, add the group name harvest_rep in the Group field of the System DSN tab.


    4.12 CA Cryptographic Engine (CACE) on Sun Solaris 8

    To use the CA Cryptographic Engine (CACE) on Sun Solaris 8, you must install Patch 108434-14 and its dependent patch, 109147-08. To obtain these patches, go to the Sun website, http://sun.com.


    4.13 TestDirector Integration

    Mercury TestDirector Integration is an optional component on the Harvest r7 client custom installation. For instructions to install TestDirector Integration, see the CA Software Change Manager Installation Guide in the Docs directory on the Harvest installation media.

    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 of the change of location of the file htdvcElement.dtd. If the Harvest installation is moved, a copy of htdvcElement.dtd must remain in its original location.


    4.14 Computer Associates Licensing (Lic98)

    All UNIX and Linux versions of Harvest r7 have been updated to the latest version of Computer Associates Licensing (Lic98), which includes a new default directory structure. By default, the latest Lic98 installation now creates /opt/CA/SharedComponents/ca_lic and /opt/CA/SharedComponents/lib directories for the licensing files.

    The installation creates $CASHCOM/ca_lic and $CASHCOMP/lib directories that contain the Lic98 files. The default location for the $CASHCOMP directory is /opt/CA/SharedComponents.

    If you are installing on a machine that has never had Lic98 installed and you want to change this location, change the $CASHCOMP environment variable from the default setting (/opt/CA/SharedComponents) to a new path name before running the installation. If the $CASHCOMP environment variable is not set, you can set it according to the instructions provided by your UNIX or Linux operating system.

    Important! Once Lic98 is installed on a machine, the Lic98 installation directory cannot be changed, even by updating the $CASHCOMP variable described above.


    4.15 For RACF Users

    For instructions to establish RACF security, see the IBM z/OS Unix System Services Planning Guide. This guide is available from the IBM website at http://ibm.com.

    The z/OS agent uses USS and requires a valid OMVS segment for users using and starting the agent. If users have no OMVS segment defined, a default OMVS segment must be defined. The z/OS agent issues authorization functions for users logged in to it.


    4.16 Plug-in External Merge/Compare Tools

    Harvest supports the following external difference/merge tools, some of which allow three-way merge:

  • Araxis Ltd. Merge v6.5 Professional Edition

  • Guiffy Software, Inc. Guiffy 6.4

  • WinMerge 2.1.6.0

  • Scooter Software Inc. Beyond Compare 2 2.2.7

  • SoftInterface, Inc. Diff Doc 3.08

    For more information on these tools, see the CA Software Change Manager User Guide.


    5.0 General Considerations

    For a list and brief description of new and changed features supplied by Harvest r7, see the AllFusion Harvest Change Manager Release Summary in the Docs directory on the Harvest installation media.


    5.1 Performance Management

    Harvest includes several configuration options that you can customize to yield optimal performance for your Harvest environment. For options to configure your server, broker, and other Harvest components for best performance, see the CA Software Change Manager Administrator Guide. Key parameters that can directly affect performance are listsize and commsize. Listsize specifies the number of records to retrieve from the database and send across the network at the same time. Commsize specifies the size of the data buffer sent between the agent and the server during check in and check out.


    5.2 Accessing Harvest Objects using Visual Basic Scripts

    In Harvest r7, you use Visual Basic scripts to access COM SDK objects from the task bar and forms in the Harvest Workbench or Administrator application. To write these Visual Basic scripts, use the Component Object Model SDK (COM SDK). For instructions, see the AllFusion Harvest Change Manager COM SDK Reference.

    In a Visual Basic script for accessing the COM SDK objects from the task bar or forms, use the following sample code as a starting point:
     Set Project = Application.Project Set objHarvest = Project.GetHarvestObject() If (objHarvest Is Nothing) Then      MsgBox "Could not get Harvest object"    Exit Function End If 

    After you code the lines above, you can access any COM SDK object documented in the COM SDK Reference.
     Set objContext = objHarvest.GetContext() If (objContext Is Nothing) Then      MsgBox "Could not get context object"    Exit Function End If 

    After completing your script, you can test it and run it in the Workbench or Administrator application, from the task bar or a form.

    Notes:

  • When the script is run, the contents of the context object reflect the current context values in the Workbench.

  • The information in this section does not apply to Visual Basic scripts that are not run in the Workbench or Administrator application.


    6.0 Documentation Changes

    This section provides updates to the Harvest documentation that became known after the documentation was published.


    6.1 Sample Reports User Guide

    For instructions to use Harvest Sample Reports, see the CA Software Change Manager Sample Reports User Guide. An important update to the chapter "AllFusion Harvest Change Manager Sample Reports" in that guide follows: If you are using Oracle 10g, when configuring the ODBC Data Source harrep1, you must use the driver supplied by Oracle 10g.


    6.2 SDK Reference Guide

    Before completing the steps in Building and Running the JHSDK Sample Programs in the chapter "Using the Harvest Software Development Kit" in the AllFusion Harvest Change Manager SDK Reference Guide, ensure that you have installed, tested, and set up the JHSDK, as described in the CA Software Change Manager Installation Guide.


    6.3 Version Control Interface User Guide

    Add the following section to chapter "Getting Started with Harvest Version Control Interface" immediately after the heading Harvest VCI Integration Installation in the Version Control Interface User Guide:

    Apply the New Security Policy

    Important! If you have a network installation of Harvest, you must apply the new security before can use the VCI Integration.

    The default local Microsoft .NET framework security policy does not allow code execution from a network share; that share is in the local intranet security zone rather than the local computer zone. For the plug-in to function correctly, use the Code Access Security Policy Tool (Caspol.exe) tool to modify the security policy on each local client computer that wants to use the plug-in (Microsoft provides this tool as part of the Microsoft .NET framework).

    To apply the new security policy to a network installation of Harvest

  • Open a command prompt and change the current directory to the Microsoft .NET framework location.

  • Execute the following command:
     caspol -machine -addgroup 1.2 -url "file://%HARVESTHOME%/*" FullTrust -n HarvestVCI.NET 

    Note: The Harvest installation sets the HARVESTHOME environment variable. Executing caspol requires a network installation of Harvest.

    -machine Applies the security policy to the computer-level policy. Logged-in users will benefit from this change. You must have administrative rights to use this option.

    -addgroup Adds a new security policy code group with the following information:

    1.2
    Identifies the parent group of the new policy. 1.2 is the local intranet security zone.

    -url "file://%HARVESTHOME%/*"
    Specifies the code membership field.

    FullTrust
    Sets permissions. Grants full permissions to code coming from the -url "file://%HARVESTHOME%/*" file share.

    Note: This new policy applies to code from the HARVESTHOME directory and all of its subdirectories.

    For more information on the caspol.exe tool, see the article, "Code Access Security Policy Tool (Caspol.exe)", at http://msdn.microsoft.com.


    7.0 List of Fixes

    Harvest r7 includes all Harvest 5.2.1 and 5.1.1 fixes. A list of fixes is on our website, https://support.ca.com.


    7.1 How to Find Known Issues and Fixes

    You can find Known Issues and Fixes by going through SupportConnect and the Knowledge Base. Follow these steps:

  • Log in to SupportConnect.

  • Click Knowledge Base.

  • Select AllFusion Harvest product.

  • Enter keywords.

  • Select criteria for your search by checking for the following: Reported Problems, Published Solutions, FAQs, and Technical Documents.

  • Click Search.


    8.0 Known Issues

    This section lists the most prominent known issues for Harvest r7 at publication time. For other known issues, see Computer Associates Customer Support at https://support.ca.com.


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


    8.2 Agent Connection Problems

    PR3118: When you attempt to 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 Workbench GUI, you receive a login timeout error if both of the following conditions exist:

  • The machine name of your Harvest broker includes a dash (-)

  • The remote agent is already connected to that broker

    As a workaround, try renaming the current broker (if feasible) or using a different broker.

    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.


    8.3 Broker Shutdown

    The Harvest broker options file (HBroker.arg) in the $HARVESTHOME directory includes several options for specifying how Harvest server processes are started, run, and shut down.

    The -killperiod=seconds option (default=300) in the HBroker.arg file defines the amount of time that temporary server processes can be idle before the Harvest broker shuts them down. Temporary server processes are server processes started in addition to the server processes started by the -minserver setting. The -minserver setting specifies the minimum number of server processes to be started.

    On Red Hat Enterprise Linux Advanced Server 3.0, regardless of the -killperiod value specified, temporary server processes above the -minserver setting are shut down if they are idle for 30 seconds.

    As a workaround to prevent constant shutdown and startup cycles, set the -minserver value equal to the -maxserver value. The -maxserver option specifies maximum number of server processes that can be running at the same time. For more information about HBroker.arg and its options, see the AllFusion Harvest Change Manager Administrator Guide.


    8.4 Character Sets

    PR3907: Extended ASCII characters are dropped or not displayed correctly in queries or Harvest GUIs.

    The operating system character set and the nls_lang or lang variables used on the Harvest server and client machines must match the character set and nls_lang variables used in the Harvest database. If the character sets differ between client shells and the database, some extended ASCII characters inserted and selected with queries do not display correctly or may be dropped.

    In Ingres, extended ASCII characters are not supported in literal query strings. For other databases, consult the DBMS documentation on how to verify and change the character set and other language variables on the specific operating system.


    8.5 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:
     E0380003: Requested Message Key Not Found: : HSRV_I_CHECKIN  E0380003: Requested Message Key Not Found: : HAPI_I_EXECUTE_SUCCESS  E0380003: Requested Message Key Not Found: : HSRV_I_CHECKOUT E0380003: 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.

    PR3763: This is a problem within Rational Rose when SourceSafe is used as a Source Control provider. After performing undo checkout on a file that is checked out, the decorator next to the file still shows it as being checked out (checkmark).

    As a workaround, users can click on View Browser twice, so that the decorators are refreshed.

    PR3990: When using Harvest and Ingres, you can check in files greater than 132 MB into the Harvest database but cannot check them out. Therefore, if you are using Harvest and Ingres, do not check in files greater than 132 MB into the Harvest database if you will need to check them out later.

    PR4426: Windows has a limit of 240 or 244 characters for path names. On Windows systems, if you check out files from a view path that is longer than 240 characters, you will receive a file agent error. The file agent is unable to write the file because of the path name length limitation.

    PR4468: This problem occurs in Rational Rose when you try to check out a reserved file (a file that is already checked out). No error message is displayed, and the Harvest Workbench is launched.


    8.6 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>

    For more information about the hrt command, including its options for restoring projects on remote machines, see the CA Software Change Manager Reference Guide.


    8.7 Direct Connection 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: check out 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: log in 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: check out 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), or 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.


    8.8 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 application, 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.

    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.

    PR4035: In the Administrator application, if you open the process list for any state and drag and drop any column before the Name column, the columns and rows may not be refreshed correctly. Instead, the characters in the first column and other columns may become unreadable.

    PR4039: In the Administrator application, if you are using Ingres, when you load a repository, you may receive error messages similar to the following if you do not check the Compress option on the Load Repository dialog:
     E03020003: Database Error: [CA][Ingres ODBC Driver]String data, length
    mismatch SQLSTATE=22026. E0306001b: ERROR: Load repository items failed.

    As a workaround, check the Compress Option on the Load Repository dialog.


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

    PR3413: Harweb will not work inside of Eclipse 3.0 when Eclipse 3.0 is installed on a UNIX platform. The SWT browser is only ported on Windows (Internet Explorer 6 or above), Mac (Panther OS X.3 or above, Safari based), and Linux GTK and Linux Motif (both using Mozilla 1.4 GTK2 - or above 1).

    PR4624: When using Harweb, you may encounter problems or failures when attempting to check in or check out large numbers of files--for example, on some systems, several thousand files. The number of files that you can check in and check out successfully depends on many factors, including hardware configuration, application server configuration, memory, database configuration, file sizes, and system load.


    8.10 Ingres

    PR4633: If you are using Ingres on Linux, when you start the Harvest broker, you may receive an error message in the HServer.log file similar to the following:

    ERROR: [CA][Ingres ODBC Driver]Ingres API failure probably to due to transaction already abnormally terminated SQLSTATE=S1000

    To correct this problem, rename the $ODBC_HOME/lib/libiiodbcdriver.1.so file to $ODBC_HOME/lib/xxxlibiiodbcdriver.1.so.

    Depending on how security is implemented in your environment, you may require root access to rename the file.

    PR4655: If you are using Ingres, when you delete a form using the Forms tab of the Harvest Administrator application, an error message similar to the following is displayed:

    Formtype delete failed.

    The message is displayed even though the form is actually deleted. You can verify that the form was deleted by refreshing and checking the existing forms available in the Harvest Workbench.

    After you receive the error message, you cannot recreate a form with the same name as the one you deleted. If you do not need to recreate a form with the same name, you can simply use a different name. If you do need to recreate a form the same name, then before recreating the form, you must manually delete an Ingres database table that has the same name as the form. To do so, follow these steps:

  • Log in to the machine on which Ingres is installed (the Harvest server machine).

  • Use one of the following methods:

  • On the command line, enter the following command:
     sql -umdbadmin mdb 

    The SQL Terminal Monitor utility starts. At the SQL Terminal Monitor prompt, enter the following command to drop the table:
     drop table tablenameg 

    Enter q to exit the SQL Terminal Monitor utility.

  • Create a SQL script named droptable.sql with the following content:
     drop table <tablename> pg 

    On the command line, enter the following command:
     sql -umdbadmin mdb < droptable.sql 


    8.11 Installation

    Note: For additional installation-related information in this readme, see Installation Considerations and see Installation Guide in Documentation Changes.

    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.

  • Restart the Harvest broker and RTserver if they are already running.

    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.

    PR4401: Due to a defect in Sun Java, the directory selection dialog is not working as expected. After selecting a directory file, it is repeated twice in the File location. For more information, see the Sun website, http://sun.com.

    PR4700: When deploying Harweb on Sun Java System Web Server, update the internal library path names of the web server with the Harvest libraries. To do so, follow these steps:

  • Log in to the Admin console of Sun Java System Web Server.

  • Select Manage WebServer.

  • Select Java.

  • Select JVM Path Settings.

  • Add the following path names to Native Lib Path Prefix. These names are the default path names. If you are using different path names, enter your path names instead:
     /opt/CA/CAcrypto:  /opt/CA/harvest/lib:  /opt/CA/pec/lib/i86_linux24 

    PR4742: When you install the Harvest client on a Windows machine that does not currently have Harvest installed, the Start menu options for the Messages Guide, Procedures Guide, and Reference Guide help (*.hlp) files are not created, unless you chose Windows Shell Extensions, also named HarWind. This feature enables you to perform Harvest check in and check out functions by right-clicking files in Windows Explorer.

    If you did not install HarWind and you want to create the Start menu options for the Messages Guide, Procedures Guide, and Reference Guide help (*.hlp) files, do one of the following:

  • Install HarWind.

  • Create the Start menu options manually.

    To install HarWind, follow these steps:

  • Re-run the Harvest client installation program.

  • On the Welcome window, click Next.

  • On the Program Maintenance window, click Modify.

  • On the Custom Setup window, select Windows Shell Extensions (HarWind).

  • On the next window, click Install. The progress of the installation is displayed.

  • When prompted, click Finish to exit the installation program.

    To create the Start menu options manually, follow these steps:

  • Note the path name for each guide on your machine. The default location is C:Program FilesCAAllFusion Harvest Change Manager. The file names are:

  • Messages Guide - tngmesg.hlp

  • Procedures Guide - harprc.hlp

  • Reference Guide - rgccharv.hlp

  • Use the complete path name for each file to create the Start menu option. Follow the instructions provided with your Windows operating system.

    To test that the options were created properly, select Start on the Windows taskbar, and then select Programs, Computer Associates, AllFusion, Harvest CM, Docs. In the Docs options, check that the Messages Guide, Procedures Guide, and Reference Guide options are included. Check that each guide opens correctly.


    8.12 Illegal Characters

    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.

    PR3950: When creating a Harvest repository, ensure that the repository name includes no forward or backward slashes; otherwise, the attempt fails with an error message like the following:
     E03020190 ERROR: The repository name shouldn't contain:  or /. 

    PR4516: On Windows, if you are using international character codes for folder and file names, be aware that depending on the client locale and character sets enabled on the machine, file folders or their contents may not be visible from the Workbench GUI. Harvest uses Multi-Byte Character Set (MBCS) strings to hold folder and file names, and not all Unicode character values are translatable into MBCS character sequences.

    For example, when using the Harvest Workbench on a Japanese-enabled client machine, characters not displayed in the Japanese Industrial Standard (JIS) selection on the Input Method Editor (IME) Pad Character list on the Language Bar should not be used for folder and filenames, if they are to be viewable from the Harvest Workbench GUI.


    8.13 Linux

    PR2934: 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 


    8.14 Oracle

    PR3903: If you are using Oracle, you may not be able to check in and check out files larger than 1 GB, depending on how busy Oracle is and whether the system on which Oracle is installed provides enough RAM or virtual memory. If you experience problems attempting to check in and check out files larger than 1 GB, try increasing the system's RAM or virtual memory.


    8.15 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, the user rabbit can create password RABBIT, Rabbit, raBBit, and so on. Validation fails only if the password is 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.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 workaround:

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

    PR5033: If Harvest installs to a shared network drive using the administrative installation to a network, the VCI.NET plug-in may fail to load.

    The default local Microsoft .NET framework security policy does not allow code execution from a network share; that share is in the local intranet security zone rather than the local computer zone. For the plug-in to function correctly, use the Code Access Security Policy Tool (Caspol.exe) tool to modify the security policy on each local client computer that wants to use the plug-in (Microsoft provides this tool as part of the Microsoft .NET framework).

    You can find the caspol.exe tool in the directory containing the Microsoft .NET framework installation on your computer. For Visual Studio .NET 2003 users, this location typically is %WINDIR%Microsoft.NETFrameworkv1.1.4322

    Note: The subdirectory name may vary depending on the version of the framework you have installed.


    8.17 z/OS Agent and ISPF Client

    PR3140: The z/OS agent and ISPF client allow z/OS files to be checked in to 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 manage, we recommend setting the repository options to manage MVS and USS files in binary mode only.

    PR3113: For RACF users only. If your attempt to log in to the z/OS 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 z/OS agent job log for RACF messages indicating why your login attempt failed.

    PR3129: If the z/OS 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).

    PR3130: The z/OS 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 a z/OS security product or if the attempt to read catalog information about the data set fails.

    PR3132: The file name filter is not supported on check in from the z/OS 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: Harvest, 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 z/OS agent job or task and will have names like nnnnnnnn.POnnnnnn.SInnnnnn.Xnnnnnnn.Ynnnnnnn (where nnnnnn is numeric).

    PR4036: The load repository function does not support MVS partitioned data sets (PDSs). If you attempt to use the load repository function for these data sets, error messages similar to the following are displayed:
     E0302003a: Unable to find files in <pds name>  matching * .  E0306001b: ERROR: Load repository items failed. 

    To add items from an MVS PDS to the Harvest repository, use the check in process.

    PR4495: For users of BrightStor CA-PDSMAN PDS Library Management. Using the z/OS agent to check in approximately 7000 or more PDS members could possibly degrade the system and abort the agent. To fix the problem, apply the following solutions:

    For BrightStor CA-PDSMAN PDS Library Management 7.4, apply the following:

  • Solution: PM74609
    Apar: 391 QO59126
    Description: LSQA usage may creep in some situations

  • Solution: PM75044
    Apar: 391 38 QO63314
    Description: Possible SD78-04 after applying PM75009

    For BrightStor CA-PDSMAN PDS Library Management 7.5, apply the following:

  • Solution: PM75009
    Apar: 10 QO59100
    Description: LSQA usage may creep in some situations

  • Solution: PM75044
    Apar: 38 QO63314
    Description: Possible SD78-04 after applying PM75009


    9.0 International Support

    For Harvest r7 GA the Harvest server, client, agent, and Harweb are 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.

    This English version of CA Software Change Manager Sample Reports has been certified to run on machines designed to use the English language.


    10.0 Documentation

    The readme and the PDFs in a documentation set each have a unique Document ID (DID) on the title page. The DID uses the first six characters to identify the document, a hyphen, then two characters at the end to identify the edition and language in which it is written. For example, E00165-1E identifies the first edition of the English version of the CA Software Change Manager Administrator Guide. When the second edition of this document is published, the DID is incremented to E00165-2E. The DID is used without the hyphen for the document on SupportConnect at https://support.ca.com, as shown in File Name column of the following table. The documents for each release are posted on SupportConnect when the release becomes generally available (GA).

    To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.

    The DIDs and file names for the Harvest documents are:

    Guide Name DID File Name
    Administrator Guide E00165-2E E001652E.PDF
    COM SDK Reference Guide E00166-2E E001662E.PDF
    Getting Started E00167-1E E001671E.PDF
    Installation Guide E00168-2E E001682E.PDF
    Integration Tools User Guide E00169-1E E001691E.PDF
    Readme E00170-2E E001702E.HTML
    Reference Guide E00171-2E E001712E.PDF
    Release Summary E00172-1E E001721E.PDF
    Sample Reports User Guide E00173-1E E001731E.PDF
    SDK Reference Guide E00174-2E E001742E.PDF
    Tutorial Guide E00175-1E E001751E.PDF
    User Guide E00176-2E E001762E.PDF
    Version Control Interface User Guide E00177-1E E001772E.PDF


    11.0 Contacting Customer Support

    For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Customer Support at https://support.ca.com.


Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing