Release Notes

CONTROL-M/Agent for UNIX and Microsoft Windows

Version: 6.3.01 with fix pack 1 April 30, 2007 Tracking numbers: UNIX PAKAI.6.3.01.100 and Microsoft Windows PANDN.6.3.01.100

These release notes provide information about the enhancements and resolved problems in version 6.3.01 with fix pack 1 (UNIX PAKAI.6.3.01.100 and Microsoft Windows PANDN.6.3.01.100) of the CONTROL-M/Agent for UNIX and Microsoft Windows product. This information supplements and supersedes information in the CONTROL-M/Agent for UNIX and Microsoft Windows product manuals.

NOTE
Details about recent patches for this product are available from the Customer Support website at http://www.bmc.com/support_home. Before installation, BMC recommends that you check the website to determine whether patches are available for this product.

The following topics are discussed: Whats new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Problems that are corrected by fix pack 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Handling network disconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Compatibility requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Support for CONTROL-M/Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Product documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Customer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

*67710* *67710*
*67710*

Whats new

Whats new
Table 1 describes enhancements that are provided by fix pack 1. Table 1
Tracking number

Enhancements that are provided by fix pack 1

Description

CAR00033224 [UNIX only] Multiple CONTROL-M/Agents can now run on the same host using the same Server-to-Agent port number. However, each CONTROL-M/Agent uses a different hostname/IP address. This support allows a reduction in the number of ports opened in a firewall protecting the specified host. CAR00033497 CONTROL-M/Agent now reports to BMC Batch Discovery the fully qualified domain name (FQDN) of the host that it is running on and of the remote hosts to which it connects. CAR00033651 CONTROL-M can now handle network disconnections between CONTROL-M/Agents and remote hosts. For more information about this feature, see Handling network disconnections on page 4. CAR00033712 CONTROL-M/Agent now supports the following editions of Microsoft Windows Vista on x86 and x86_64 based processors:
s s s

Windows Vista Business Edition Windows Vista Enterprise Edition Windows Vista Ultimate Edition

CAR00033713 CONTROL-M/Agent can now submit jobs to remote hosts that are running on the following platforms:
s s

IBM z/OS USS (Open Edition) with SSH server Microsoft Windows XP with SSH server or using WMI

Note: When working with z/OS USS (OpenEdition) remote hosts, set RJX_CONN_SFTP to N in CONTROL-M/Agent and then restart the agent. For more information about RJX_CONN_SFTP, see Table 3 on page 5.

Release Notes April 30, 2007

Problems that are corrected by fix pack 1

Problems that are corrected by fix pack 1

Table 2 describes problems that were reported in earlier releases of CONTROL-M/ Agent for UNIX and Microsoft Windows and have been corrected in this release. The list of corrected problems is also available under solution KM-000010009881 in the Knowledge Base. Table 2
Tracking number

Problems that are corrected by fix pack 1 (part 1 of 2)

Description

BMPM010010 The status of jobs is set to disappeared when the available disk space is low on the computer where CONTROL-M/Agent is running. BMPM010039 [UNIX only] File Watcher does not issue permission denied messages if there are no permissions for the directory. This occurs when wildcards are used in the input file, and the directory does not have permissions for the current user. BMPM010247 The ctmfw process on Windows crashes when the DELETE option is specified and when the specified file contains wildcards in the file name. BMPM010420 CONTROL-M/Agent cannot copy the sysout of a job based on the owner of the job's secondary group permissions. BMPM010500 [UNIX only] The permissions of the newday file (located in the $CONTROLM/temp/ directory) differ between CONTROL-M/Agents installed on different operating systems. BMPM010534 The CONTROL-M/Agent startup script does not work correctly when the computer is rebooted while CONTROL-M/Agent is running. CAR00033047 When you are running the start-ag script while the server-to-agent port is busy, the script issues a message that the agent listener is already running. The script should report an error and not allow the agent to start. CAR00033059 [Windows only] CONTROL-M/Agent does not issue a message to the jobs log (IOALOG) when a sysout copy or move fails. However, a message similar to the following is displayed in the CONTROL-M/Agent log in the agents proclog directory: JOB LOG COPY TO /home/sysout.log FAILED CAR00033096 [UNIX only] The ctmfw utility does not work when activated as another user. CAR00033112 The View JCL script feature cannot find the shell file when you are using the Overlib parameter. This problem occurs when Simplified Chinese, Japanese, and Korean (CJK) characters are used in the file. CAR00033120 [Windows only] In certain cases jobs end NOT_OK when executed on a remote host by using WMI. This problem occurs when the notification indicating that the job has ended fails to be received by the WMI service and the agent when they are under stress. CAR00033317 The total CPU USED in job sysout does not match the value in the ctmruninf utility.

CONTROL-M/Agent for UNIX and Microsoft Windows Version 6.3.01

Handling network disconnections

Table 2
Tracking number

Problems that are corrected by fix pack 1 (part 2 of 2)

Description

CAR00033569 [Windows only] The File Watcher form displays the characters ? and ??????. This problem occurs when you are using a Japanese localized operating system. CAR00033652 [UNIX only] CONTROL-M cannot determine the operating system of a remote host if an alias to the ver command exists for the job owners UNIX account. CAR00034428 When copy or move of the sysout of a job is performed where the job was executed with the -v option, the operation fails. This occurs when the -v option is set for Bourne or Korn shell in OS.dat.

Handling network disconnections

CONTROL-M/Agent requires an open connection to a remote host from the time of job submission until the end of the job. If there is a network disconnection, CONTROL-M/Agent attempts to restore the connection. During the reconnection attempts, jobs running on the remote host, through the specified CONTROL-M/ Agent, remain in executing status. If the connection is restored, the status of jobs is updated to reflect their current status, either completed or still running. If the connection is not restored after the specified number of attempts, the jobs end with NOT_OK status. The handling of network disconnections to remote hosts is supported when using remote hosts on UNIX, Linux, and z/OS USS (using SSH) and when using remote hosts on Windows (using WMI). The sysout and exit code for jobs are stored in files on the remote host in the user home directory of the jobs owner in the directory specified by RJX_SYSOUT_DIR. For more information about RJX_SYSOUT_DIR, see Table 3 on page 5. If network connections were restored, these files are deleted when the jobs end. If network connections were not restored, these files can be checked to see if the jobs completed successfully or failed. The following section describes configuration parameters related to handling network disconnections of remote hosts.

To modify the network disconnections recovery settings 1 In the computer where CONTROL-M/Agent is installed, modify the registry keys,
for Windows, or modify the parameters in the OS.dat file, for UNIX, as described in the following table, as required. The path to the registry keys is
HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\CONTROL-M/Agent\WIN and the path to the OS.dat file is <agentInstallDir>/ctm/data. 4 Release Notes April 30, 2007

Compatibility requirements

Table 3

Network disconnection parameters or registry keys

Description The number of attempts made to restore the connection. Default: 3 The time interval between tries made to restore the connection. Default: 120 seconds Directory to store temporary files. These files are automatically removed to CONTROL-M/Agent when the jobs end and the network connection is available or restored. Default: blank. This means that the files are stored in the user home directory of the jobs owner in the remote host.

Parameter nameUNIX Registry keyWindows RJX_CONN_TRY RJX_CONN_TOUT RJX_SYSOUT_DIR

RJX_CONN_RECONNECT Indicates whether the network reconnection feature is enabled. Default: Y RJX_CONN_SFTP Determines the protocol used to upload and download files.
s s

When Y is specified, the agent uses SFTP (secured FTP) protocol to retrieve, upload, and download files When N is specified, the agent uses the SSH protocol to retrieve, upload, and download files

Default: Y

2 Restart the CONTROL-M/Agent services on Windows, or the processes on UNIX,

for these changes to take effect.

Compatibility requirements
The requirements for fix pack 1 are the same as the requirements for the base version of CONTROL-M/Agent for UNIX and Microsoft Windows 6.3.01.

NOTE
For the most current compatibility information for this version, see http://www.bmc.com/ support/PAC_utility/index.

CONTROL-M/Agent for UNIX and Microsoft Windows Version 6.3.01

Installation

Installation
Up-to-date, essential installation and service information that becomes available after this product is released will be placed under solution KM-000010009861 in the knowledge base on the Customer Support website. BMC recommends that you access this page before you install this product. The installation program for fix pack 1 is available on the following:
s

FTP server, at the following locations for UNIX: ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROLM_Agent_for_UNIX_and_Microsoft_Windows/6.3.01/PAKAI.6.3.01.100 for Microsoft Windows: ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROLM_Agent_for_UNIX_and_Microsoft_Windows/6.3.01/PANDN.6.3.01.100

NOTE
The CD for fix pack 1 is made available for shipment shortly after the program has been made available on the FTP server. If you already have the installation CD, you do not need to download the program from the FTP server.

installation CD containing PAKAI.6.3.01.100 (for UNIX) and PANDN.6.3.01.100 (for Microsoft Windows)

The files and directory structure that are required for the installation procedures are the same on the installation CD and the FTP server. The installation procedure includes a Silent Install option.

Before you begin

Ensure that CONTROL-M/Agent for UNIX and Microsoft Windows version 6.3.01 exists on your computer.

Release Notes April 30, 2007

Installing fix pack 1 on UNIX

Installing fix pack 1 on UNIX

Before installing fix pack 1, ensure that the following conditions exist on your computer:
s s

Korn Shell (KSH) is installed. CONTROL-M/Agent for UNIX and Microsoft Windows version 6.3.01 (DRKAI.6.3.01) is installed. 100 MB of free disk space is available.

NOTE
Before installing fix pack 1, open a new shell as CONTROL-M/Agent user and run the installation for fix pack 1 from there.

1 Ensure that no CONTROL-M jobs are running. 2 Log on as the root user, and stop the Agent with the shut-ag command.
If you are going to install fix pack 1 on an AIX platform, execute the slibclean command (as the root user).

3 Make a copy of the exe and scripts files and directories in the CONTROL-M/Agent
home directory:
s s

$CONTROLM/exe $CONTROLM/scripts

4 Prepare to install from the BMC Software FTP site or from the CD drive:
s

Installing from the FTP site: A. Log on as the CONTROL-M/Agent user, and create a temporary directory (for example, controlm_agent/PAKAI.6.3.01.100/). B. Copy the PAKAI.6.3.01.100.INSTALL_BIN file in binary mode from the FTP site to the temporary directory that you created in step A. C. Run the following command to ensure that the fix pack installation has the necessary authorizations:
chmod +x PAKAI.6.3.01.100.INSTALL_BIN

CONTROL-M/Agent for UNIX and Microsoft Windows Version 6.3.01

Removing fix pack 1

Installing from the CD: A. As the root user, mount the installation CD. B. Log on as the CONTROL-M/Agent user.

5 Decide whether you want to perform a silent installation or an interactive

installation:
s

To perform a silent installation, run PAKAI.6.3.01.100.INSTALL_BIN -s from the CD or the temporary directory that you created in step A. To run an interactive installation, perform the following steps: A. Run PAKAI.6.3.01.100.INSTALL_BIN from the CD or the temporary directory that you created in step A. B. Specify y.

6 When installation is complete, log on as the root user of CONTROL-M/Agent and

start CONTROL-M Agent and Tracker services with the start-ag command. The installation performs the following tasks:
s

creates the patches/PAKAI.6.3.01.100/BACKUP_ORIG subdirectory under the directory which contains the original files:
$CONTROLM

s s

installs new files (after backing up originals) creates the Install_PAKAI.6.3.01.100_fixpack.log file in the $CONTROLM/log/ directory creates or updates the installed-versions.txt file in the CONTROL-M/Agent home directory

Removing fix pack 1

You can choose between an interactive uninstallation procedure or a silent uninstallation procedure.

To run an interactive uninstallation 1 Log on as the administrator to the computer hosting CONTROL-M/Agent. 2 Shut down CONTROL-M/Agent, and exit all utilities.

Release Notes April 30, 2007

Removing fix pack 1

3 Log on as CONTROL-M/Agent user. 4 Run the uninstallation script by using the following command:
$CONTROLM/patches/remove_fp -f PAKAI.6.3.01.100

5 When prompted, type Y to start the uninstallation. 6 Restart CONTROL-M/Agent by using the start_ag command. To run a silent uninstallation 1 Log on as the administrator to the computer hosting CONTROL-M/Agent. 2 Shut down CONTROL-M/Agent, and exit all utilities. 3 Log on as CONTROL-M/Agent user. 4 Run the uninstallation script by using the following command:
$CONTROLM/patches/remove_fp -f PAKAI.6.3.01.100 -s

5 Restart CONTROL-M/Agent by using the start_ag command.

The uninstallation procedure performs the following tasks:
s

creates the Uninstall_PAKAI.6.3.01.100_fixpack.log uninstallation log file in the log directory copies relevant files from patches/PAKAI.6.3.01.100/BACKUP_ORIG subdirectory under the CONTROL-M/Agent home directory updates the installed-versions.txt file in the CONTROL-M/Agent home directory This file contains information (such as the fix pack number and date) for all fix packs and certain patches for all CONTROL-M products that have been installed.

NOTE
Even if you are uninstalling all fix packs, the installed-versions.txt file remains in the CONTROL-M/Agent home directory for tracking purposes.

CONTROL-M/Agent for UNIX and Microsoft Windows Version 6.3.01

Installing fix pack 1 on Windows

Installing fix pack 1 on Windows

Before installing fix pack 1, ensure that the following conditions exist on your computer:
s

CONTROL-M/Agent for UNIX and Microsoft Windows version 6.3.01 (DRNDN.6.3.01) is installed. 30 MB of free disk space is available.

Installing fix pack 1 on a noncluster computer

To install fix pack 1 on a noncluster computer, perform the following steps:

1 Log on to the CONTROL-M/Agent for Microsoft Windows host computer as a

user with administrator privileges.

2 Close CONTROL-M/Agent utilities. 3 Create a temporary directory. 4 Prepare to install from the BMC Software FTP site or from the CD drive:
s

Installing from the FTP site: For Windows 32 bit: Download the PANDN.6.3.01.100.exe file in binary mode from ftp:// ftp.bmc.com/pub/control-m/opensystem/CONTROLM_Agent_for_UNIX_and_Microsoft_Windows/6.3.01/PANDN.6.3.01.100/ Windows to the directory created in step 3 For Windows 64 bit (Itanium): Download the PANDN.6.3.01.100.exe file in binary mode from ftp:// ftp.bmc.com/pub/control-m/opensystem/CONTROLM_Agent_for_UNIX_and_Microsoft_Windows/6.3.01/PANDN.6.3.01.100/ Windows64IA to the temporary directory created in step 3 For Windows 64 bit (AMD): Download the PANDN.6.3.01.100.exe file in binary mode from ftp:// ftp.bmc.com/pub/control-m/opensystem/CONTROLM_Agent_for_UNIX_and_Microsoft_Windows/6.3.01/PANDN.6.3.01.100/ Windows64AMD to the temporary directory created in step 3

Installing from the CD: Copy the required PANDN.6.3.01.100.exe file from the CD to the temporary directory created in step 3.

5 Run the PANDN.6.3.01.100.exe file.

10 Release Notes April 30, 2007

Installing fix pack 1 on Windows

6 Select the required installation directory from the dialog box that is displayed and
click Unzip.

7 Decide whether you want to run an interactive installation or a silent installation:

s

To run an interactive installation, double-click the setup.exe file and follow the install wizard prompts. As of version 6.1.03, you can install multiple agents on one computer: During the fix pack installation, you are prompted to select the agent for which you are installing fix pack 1. You must perform a separate execution of setup.exe for each agent for which you want to install fix pack 1.

To run a silent installation, perform the following steps: On the Default agent, double-click the silent.bat file. On any other agent, edit the silent.bat file by using a text editor, setting AGENT_NAME to the agent name (for example, AGENT_NAME=agent1) Run the file. A message in the fix pack installation log file
%temp%\Install_PANDN.6.3.01.100_fixpack_silent.log indicates whether the

installation succeeded or failed. A fix pack installation log file is created in the %TEMP% directory on your computer. This file is named Install_ PANDN.6.3.01.100_fixpack.log. (To locate the %TEMP% directory, choose Start => Run, and enter %TEMP% in the Open field.) If errors are encountered during fix pack installation, include a copy of this log file with your questions for Customer Support. The number of the fix pack is entered in the ctmagentHome\installed_versions.txt file. The installation procedure on a noncluster computer performs the following tasks:
s

creates the <agentName> PANDN.6.3.01.100 Fix Pack 01 directory This directory, which is used for copying backup files and should not be modified or deleted, is located in the following path:
%ALLUSERSPROFILE%\Application Data

copies the relevant fix pack files to the CONTROL-M/Agent home directory

CONTROL-M/Agent for UNIX and Microsoft Windows

Version 6.3.01

11

Installing fix pack 1 on Windows

creates or updates the installed-versions.txt file in the CONTROL-M/Agent home directory This file contains information (such as the fix pack number, and date) for all fix packs, binaries, and patches for all CONTROL-M products that have been installed.

CONTROL-M Agent and Tracker services will have the same status they had before the installation

Removing fix pack 1 from a non-cluster computer

You can choose between an interactive uninstallation procedure or a silent uninstallation procedure.

To run an interactive uninstallation 1 Log on to the CONTROL-M/Agent for Microsoft Windows host computer as a
user with administrator privileges.

2 Close the CONTROL-M/Agent utilities, and stop all active services. 3 Verify that CONTROL-M jobs are not running and that utilities invoked by the
Agent are not being processed by CONTROL-M/Server.

4 Choose Start => Settings => Control Panel => Add/Remove Programs =>CONTROL-M/
Agent 6.3.01 fix pack 1 (<Agent name if not default>) and select the Remove option.

-or[For Windows Vista] Choose Start => Settings => Control Panel => Programs and Features =>CONTROL-M/Agent 6.3.01 Fix Pack 1 [<agentNameIfNotDefault>] and select the Uninstall option.

To run a silent uninstallation 1 Navigate to the Uninstall subdirectory in the CONTROL-M/Agent for Microsoft
Windows home directory.

2 Double-click uninst.bat.
The uninstallation procedure from a noncluster computer performs the following tasks:
s

restarts the CONTROL-M/Agent services if they were up when the uninstallation started

12

Release Notes April 30, 2007

Installing fix pack 1 on Windows

creates the Remove_agent_FixPack_log uninstallation log file in the %programfiles%\BMC Software\BMC Logs\ctmag directory copies the relevant files from the <agentName> PANDN.6.3.01.100 Fix Pack 01 backup directory to the CONTROL-M/Agent home directory The backup directory is located in the %ALLUSERSPROFILE%\Application Data directory.

updates the installed-versions.txt file in the CONTROL-M/Agent home directory This file contains information (such as the fix pack number and date) for all fix packs, binaries, and patches for all CONTROL-M products that have been installed.

NOTE
Even if you uninstall all fix packs, the installed-versions.txt file remains in the CONTROL-M/Agent home directory for tracking purposes.

Installing or uninstalling fix pack 1 on a cluster computer

To install or uninstall fix pack 1 on a cluster computer, perform the following steps:

NOTE
Installation and uninstallation of fix pack 1 on a cluster computer must be performed on the same virtual computer on which CONTROL-M/Agent 6.3.01 was installed.
.

1 Log on to the cluster node where CONTROL-M/Agent is active. 2 Determine whether the CONTROL-M File Watcher service is online by running the
following command:
cluster.exe res FWResourceName

If the File Watcher service is online, bring it offline by running the following command:
cluster.exe res FWResourceName /off

FWResourceName is the name of the resource for the File Watcher service that you want to take offline.

CONTROL-M/Agent for UNIX and Microsoft Windows

Version 6.3.01

13

Installing fix pack 1 on Windows

3 Take Listener and Tracker service resources offline by running the following
commands (the services themselves should not be stopped):
cluster.exe res ListenerResourceName /off /wait:60 cluster.exe res TrackerResourceName /off /wait:60

ListenerResourceName is the name of the resource for the Listener service, and TrackerResourceName is the name of the resource for the Tracker service you want to take offline.

4 Perform one of the following actions:

s

Install fix pack 1 according to the instructions in Installing fix pack 1 on a noncluster computer on page 10. Uninstall fix pack 1 according to the instructions in Removing fix pack 1 from a non-cluster computer on page 12.

5 Bring Listener and Tracker service resources online by running the following
commands:
cluster.exe res ListenerResourceName /on /wait:60 cluster.exe res TrackerResourceName /on /wait:60

6 If the File Watcher service was online (see step 2) before fix pack 1 was installed,
run the command:
cluster.exe res FWResourceName /on /wait:60

The installation procedure on a cluster computer performs the following tasks:

s

restarts the CONTROL-M/Agent services if they were up when the installation started creates the <agentName> PANDN.6.3.01.100 Fix Pack 01 directory This directory, which is used for copying backup files and should not be modified or deleted, is located in the following path:
%ALLUSERSPROFILE%\Application Data

s s

copies the relevant fix pack files to the CONTROL-M/Agent home directory creates the Install_PANDN.6.3.01.100_fixpack.log log file (for interactive installation) or the Install_ PANDN.6.3.01.100_fixpack_silent.log log file (for silent installation) in the %programfiles%\BMC Software\BMC Logs\ctmag\Remove_agent_FixPack_log directory

14

Release Notes April 30, 2007

Support for CONTROL-M/Agent

creates or updates the installed-versions.txt file in the CONTROL-M/Agent home directory This file contains information (such as the fix pack number, and date) for all fix packs, binaries, and patches for all CONTROL-M products that have been installed.

The uninstallation procedure from a cluster computer performs the following tasks:
s

restarts the CONTROL-M/Agent services if they were up when the uninstallation started creates the Uninstall_PANDN.6.3.01.100_fixpack.log uninstallation log file in the %TEMP% directory, for silent uninstallations copies the relevant files from the <agentName> PANDN.6.3.01.100 Fix Pack 01 backup directory to the CONTROL-M/Agent home directory. This directory is located in the %ALLUSERSPROFILE%\Application Data directory updates the installed-versions.txt file in the CONTROL-M/Agent home directory This file contains information (such as the fix pack number and date) for all fix packs, binaries, and patches for all CONTROL-M products that have been installed.

NOTE
Even if you uninstall all fix packs, the installed-versions.txt file remains in the CONTROL-M/Agent home directory for tracking purposes.

Support for CONTROL-M/Agent

This section provides information about
s s s s s

BMC Software support for CONTROL-M/Agent how to obtain the latest information about the product how to order the product documents that support the product how to contact BMC Software Customer Support

CONTROL-M/Agent for UNIX and Microsoft Windows

Version 6.3.01

15

Levels of support

Levels of support
BMC Software supports the following versions and releases of CONTROL-M:
Product name and version CONTROL-M/Agent 6.3.01 CONTROL-M/Agent 6.2.01 CONTROL-M/Agent 6.1.03 Level of support Full Full Full

For more information about the latest Support policies and guidelines, see the Customer Support page of the BMC Software website at http://www.bmc.com/ support_home.

Where to view the latest product information

The latest product information is available on the Customer Support web page at http://www.bmc.com/support_home. If you do not already have a user name and password that allow you to fully access the Customer Support web page, register for a user name and password as follows:

1 Access http://www.bmc.com/support_home. 2 Under My Login, click New User Registration. 3 Complete the information and follow the directions provided on the New User
Registration Page.

From the Customer Support web page, you can perform the following tasks:
s

To receive e-mail messages that inform you of new release notes, flashes, and technical bulletins for your products, register for Proactive Notification as follows: 1. Click My Support Administration. 2. Click register. 3. Follow the directions provided.

To search for existing product resolutions and frequently asked questions (FAQs), click Knowledge Base and follow the directions provided.

16

Release Notes April 30, 2007

How to obtain fix pack 1

To view the latest product documentation, click Product Lists & Manuals and navigate through the product list to the version of the product for which you want to view documentation.

How to obtain fix pack 1

Fix pack 1 is available
s s

on CD, which you can order through a BMC Software sales representative electronically, which you can download from the BMC Software FTP server, at the locations described on page 6.

Product documents
To view the latest BMC documents, see the Customer Support website at http://www.bmc.com/support_home. Notices, such as flashes, technical bulletins, and release notes, are available on the website. You can subscribe to proactive alerts to receive e-mail messages when notices are issued or updated. For more information about proactive alerts, see the Customer Support website.

Customer support
If you have problems with or questions about a BMC product, see the Customer Support website at http://www.bmc.com/support_home. You can view or download product documents, find answers to frequently asked questions, and download product updates and maintenance. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent.

Copyright 2007 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices in the product documentation.

BMC SOFTWARE INC 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA 713 918 8800 Customer Support: 800 537 1813 (United States and Canada) or contact your local support center

CONTROL-M/Agent for UNIX and Microsoft Windows

Version 6.3.01

17