Control-M/Agent for UNIX and

Microsoft Windows
7.0.00.500
Release Notes

November 2013

www.bmc.com

Contents
Introduction to the Control-M/Agent for UNIX and Microsoft Windows Release Notes ........... 3
Control-M/Agent enhancements ....................................................................................... 3
Control-M/Agent corrected problems ................................................................................ 4
Control-M/Agent compatibility ......................................................................................... 5
Control-M/Agent compatibility with Windows ....................................................................................5
Control-M/Agent compatibility with UNIX .........................................................................................7
Control-M/Agent compatibility with Control-M components................................................................8
Control-M/Agent language compatibility ...........................................................................................9

Product Distribution ...................................................................................................... 10

Obtaining installation files through EPD ......................................................................................... 10
Obtaining installation files using FTP .............................................................................................. 11
Obtaining installation files through the BMC sales representative ..................................................... 11

Installation .................................................................................................................. 12
Installing Control-M/Agent version 7.0.00 fix pack 5 on Microsoft Windows ...................................... 12
Installing Control-M/Agent version 7.0.00 fix pack 5 on UNIX .......................................................... 13
Uninstalling Control-M/Agent version 7.0.00 fix pack 5 from UNIX ................................................... 15
Uninstalling Control-M/Agent version 7.0.00 fix pack 5 from Microsoft Windows ............................... 14

In earlier fix packs ........................................................................................................ 16

Enhancements ............................................................................................................................. 16
Corrected problems ...................................................................................................................... 18

Support for Control-M 7.0.00.500 .................................................................................. 22

Levels of support .......................................................................................................................... 22
Related documentation ................................................................................................................. 22

Release Notes

Introduction to the Control-M/Agent for UNIX

and Microsoft Windows Release Notes
BMC Software is releasing version 7.0.00 fix pack 5 of Control-M/Agent for UNIX and Microsoft Windows
(Control-M/Agent). These release notes provide information about the enhancements and resolved problems
in this release. The information in this document supplements and supersedes information in the Control-M
Workload Automation manuals.
Up-to-date, essential installation and service information that becomes available after this product is
released will be placed under solution https://kb.bmc.com/infocenter/index?page=content&id=KA405507
Before installation, BMC recommends that you check the website for any up-to-date information and also to
determine whether recent patches are available for this product.

Control-M/Agent enhancements
The following table describes Control-M/Agent enhancements for version 7.0.00 fix pack 5.
Tracking #

Description

CAR00034852

(Linux Agents) The ctmkilljob utility can now kill both job process
and child processes, which are created in a different session.

CAR00047232

(Remote host on OpenVMS OS)

You can now use the new variable "COPYSYSOUT" to copy JOB
output to a path specified on the remote agent.
The result of the copy action is reflected in the job output file.

CAR00047638

cttmcreate and ctmorder support variables with a maximum length

of 4000 characters.

CAR00047700

Control-M/Agent supports shutdown using rc.agent_user stop, as

part of machine shutdown procedures.
See: Control-M/Agent automatic startup procedures in Control-M

Installation Guide.

Release Notes

Control-M/Agent corrected problems

The following table describes Control-M/Agent corrected problems for version 7.0.00 fix pack 5 .The list of
corrected problems is also available under solution in the Knowledge base:
https://kb.bmc.com/infocenter/index?page=content&id=KA405508.
Tracking #

Description

CAR00045385

(UNIX only) Files are left in the temp directory after each run of the
get_cpu_specs script.

CAR00045825

(Windows only) Statistics for Job elapsed time are incorrect when
the job failed on the first attempt.

CAR00046179

(UNIX Remote Hosts) Agentless jobs using the jobtype command

cannot include "cd" as part of the command.

CAR00046792

(Linux Only) When processing on statements, Agents cannot

handle multiple level commands. Example: ls | grep xxx | wc
Linux systems show ++ at job output for each command; other Unix
systems show +

CAR00046845

(Windows only) In a heavily loaded environment, some jobs fail with

message Job failed to initialize" in the job log.

CAR00047146

Control-M/Agent fails to send an email when there is no sysout file,

if setting ATTACHMENT_TYPE = A and using the "ctmshout" utility.

CAR00047229

The ctmextract utility cannot extract SAP jobs when the job
definition size is over 32k.

CAR00047367

When Control-M/Agent starts as root, watchdog files in the PID

folder are created under root.

CAR00047479

Control-M/Agent AS processes crash when hundreds of remote

hosts or CMs are connected to a single agent.
The crash generally occurs once a day when a
Get_machine_spec_request' request (DSECT Type 17) is sent to
that Agent.

CAR00047628

(UNIX only) Control-M/Agent jobs that exit almost immediately and

end with NOTOK may be reported as OK. This happens in a stressed
environment. An error message may be issued in the Agent debug
logs. For example:
1026 13:50:09:500 AM:OS_SCRIPT_system : waiting for
a child 5073 ...

Release Notes
Tracking #

Description

CAR00047755

(Agentless) Agent SSH connection performance with remote hosts

does not function properly.

CAR00048075

(Unix Agents, CJK environment, HP Itanium)

In some instances, when upgrading to CTM Agent version 7.0.00 fix
pack 4, jobs may disappear.

CAR00048192

Control-M/Agent scripts using ${# end NOTOK.

CAR00048708

(Microsoft Windows only) Control-M/Agent failed to install on

Windows 2012 cluster.

Control-M/Agent compatibility
Control-M/Agent can be installed on Windows and/or UNIX computers and works together with other
products in the Control-M scheduling solution (for example, Control-M/EM and Control-M/Server).
The following lists the operating systems and other pre-installation requirements for Control-M/Agent:

Control-M/Agent compatibility with Windows (on page 5)

Control-M/Agent compatibility with UNIX (on page 7)

Control-M/Agent compatibility with Control-M components (on page 8)

Control-M/Agent language compatibility (on page 9)

Control-M/Agent compatibility with Windows

The following table lists the supported Windows operating systems for Control-M/Agent.
Operating System

Bits

Compatible Processors

Windows XP Professional

32

x86

Windows Vista Enterprise Edition

64

x86_64

Windows Vista Business Edition

Windows Vista Ultimate Edition
Windows 7 Enterprise Edition

Release Notes
Operating System

Bits

Compatible Processors

Windows 7 Business Edition

Windows 7 Professional Edition
Windows 7 Ultimate Edition
Windows 8
Windows 8 Enterprise
Windows 8 Pro
Windows Server 2008 Standard
Edition

x86

x86_64

Windows Server 2008 Enterprise

Edition

x86

x86_64

Itanium (ia64)

Windows Server 2003 Standard

Edition

x86

x86_64

Windows Server 2003 Enterprise

Edition

x86

x86_64

Itanium (ia64)

Windows Server 2008 R2 Standard

Edition

64

x86_64

Windows Server 2008 R2 Enterprise

Edition
Windows Server 2012 Standard
Edition
Windows Server 2012 R2

Release Notes

Control-M/Agent compatibility with UNIX

The following table lists the supported UNIX operating systems for Control-M/Agent.
Operating system

Version

Bits

Compatible processors

AIX

7.1

64

Power

HP-UX

Red Hat Enterprise

Linux Server

6.1

32

5.3

64

5.2

11.31

32

11.23

64

11.11

11.31

11.23

64

PA RISC processors

Itanium 64

32

x86_64

64

x86

Itanium (ia64)

x86_64

x86

IBM zSeries

Itanium (ia64)

x86_64

x86

IBM zSeries

Release Notes
Operating system

Version

Bits

Compatible processors

Oracle Solaris

11

64

SPARC

x86_64

10

SUSE Linux
Enterprise Server

Oracle Enterprise
Linux Server

32

SPARC

64

x86_64

x86

9 (update level
9 and higher)

SPARC

11

Itanium (ia64)

10

IBM zSeries

x86_64

x86

x86_64

x86

Control-M/Agent compatibility with Control-M components

The following table lists the versions of Control-M/EM and Control-M/Server that are compatible with
Control-M/Agent.
Component

Version

Control-M/Enterprise Manager

7.0.00

Control-M/Server for UNIX and

Microsoft Windows

7.0.00

Control-M Application Plug-ins

All Control-M Application Plug-ins released versions

NOTE: Some of the Control-M Application Plug-ins are installed automatically when you install Control-M/EM
version 7.0.00 full installation. For more information, see Control-M installation.

Release Notes

Control-M/Agent language compatibility

The following table lists the languages that are compatible with Control-M/Agent.
Language

Level of support

East Asian (CJK)

The following languages are now supported:

Traditional Chinese

Simplified Chinese

Japanese

Korean

Western European (Latin-1

character set)

Special Western European characters used in English, Spanish,

German, and French can be specified in most free-text fields and
parameters.

Basic ASCII

US English

Chapter
Chapt

Release Notes

Product Distribution
The following procedures describe how to obtain the installation files for Control-M/Agent for UNIX and
Microsoft Windows version 7.0.00 fix pack 5 , using EPD, FTP, or the BMC Sales Representative:

Obtaining installation files through EPD (on page 10)

Obtaining installation files using FTP (on page 11)

Obtaining installation files through the BMC sales representative (on page 11)

Obtaining installation files through EPD

This procedure describes how to obtain the Control-M/Agent for UNIX and Microsoft Windows installation
files through EPD.

To obtain installation files via EPD:

1. Click https://webapps.bmc.com/epd/and follow the instructions on the EPD site until you reach the
Download Files page.
2. Do one of the following:

UNIX: Do the following:

a. Download and save the file into a temporary directory :

<INST_TEMP_DIR>
If you downloaded it to your computer, transfer it to a UNIX computer using binary ftp mode to
an intermediate location:

<UNIX_TAR_Z_LOCATION>
b. CD into:

<INST_TEMP_DIR>
c. Extract the compressed tar file with the following command:

uncompress c <UNIX_TAR_Z_LOCATION>/<InstallationFileName.tar.Z> |
tar xf
For example : uncompress c /tmp/DROST.7.0.00_Linux-x86_64.tar | tar xf

If you have do not have an uncompress command, use zcat instead of uncompress c:

zcat <UNIX_TAR_Z_LOCATION>/<InstalltionFileName.tar.Z> | tar xf

Windows: Do one of the following:

o

Download and save the .iso file to a temporary directory, and then burn it onto a DVD.

Download and save the relevant .zip file to a temporary directory.

10

Release Notes

Obtaining installation files using FTP

This procedure describes how to obtain the Control-M/Agent for UNIX and Microsoft Windows installation
files using FTP.

To obtain installation files using FTP:

1. Download the installation files from one of the following locations:

UNIX:
ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Agent_for_UNIX_and_Microsoft_Wind
ows/7.0.00/PAKAI.7.0.00.500/Unix

Windows:
ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Agent_for_UNIX_and_Microsoft_Wind
ows/7.0.00/PAKAI.7.0.00.500/Windows

2. Log on as a Control-M/Server user, and create a temporary directory (for example,TEMP_INST_DIR).

3. Copy the required files, as follows:

UNIX: Copy the setup.sh and PAKAI.7.0.00.500_<platform>.INSTALL.BIN files that are

relevant to your UNIX system in binary mode from the FTP site to the temporary directory that you
created.

Windows: Copy the PAKAI.7.0.00.500_<Windows_platform>.exe file that is relevant to

your Windows system from the FTP site to the temporary directory that you created.

4. Type the following command for each copied installation file to ensure that the fixpack installation has
the necessary authorizations (UNIX only):
chmod +x <installation_file>

Obtaining installation files through the BMC sales

representative
This procedure describes how to obtain the Control-M/Agent for UNIX and Microsoft Windows installation
files through the BMC sales representative.

To obtain installation files through the BMC Sales representative:

To obtain a product DVD, contact your BMC Sales Representative.

Contact information is available on the BMC website see
http://www.bmc.com/corporate/contacts-locations/

11

Release Notes

Installation
The installation files for Control-M/Agent version 7.0.00 fix pack 5 are available from the BMC FTP site, on
the installation CD, or through Electronic Product Distribution (EPD), as described in Product Distribution (on
page 10).
The following procedures enable you to install and uninstall fix pack 5 :

Installing fix pack 5 on Windows (on page 12)

Installing fix pack 5 on UNIX (on page 13)

Uninstalling fix pack 5 from Windows (on page 14)

Uninstalling fix pack 5 from UNIX (on page 15)

These release notes provide installation procedures of fix pack 5 for Control-M/Agent. For detailed
instructions regarding installation of Control-M/Agent, see the Control-M Installation Guide.

Installing Control-M/Agent version 7.0.00 fix pack 5 on

Microsoft Windows
This procedure describes how to install Control-M/Agent version 7.0.00 fix pack 5 on Windows computers.

Before You Begin

Ensure that you have met the following requirements:

Control-M/Agent version 7.0.00 installed

100 MB of free hard disk space available (same amount on the %temp% directory)

Ensure that all jobs running on the Control-M/Agent have stopped.

To install Control-M/Agent version 7.0.00 fix pack 5 on Microsoft Windows:

1. Log in as a Control-M/Agent administrator.
2. Do one of the following:

If you obtained the installation files through FTP (see obtaining installation files using FTP) navigate
to the temporary directory that you created.

If you obtained a CD (through EPD or BMC Sales Representative), insert the CD, and navigate to the
Windows directory.

12

Release Notes
Install the fix pack using one of the following methods:

3.

To perform an interactive installation, double-click the

PAKAI.7.0.00.500_<Windows_platform>.exe file and continue with the installation wizard,
following the on-screen instructions until the completion of the installation.

To perform a silent installation, open a command line and do the following:

a. Extract the fix pack files by typing the following command:
PAKAI.7.0.00.500_<Windows_platform>.exe -e
By default the files are extracted to %temp%. You can use -d<extractPath> to extract the files
to another directory. Ensure that there is no space between -d and<extractPath>. Otherwise,
the fix pack files are extracted to the default location: %temp%.

NOTE: If you are using Windows Vista, Windows 7, or Windows Server 2008, run the silent installation
from a command prompt that was opened with administrator privileges.
b. Navigate to %temp%\<PAKAI.7.0.00.500> and type the following command:
silent.bat -i <instance_name>
4. To view the installation log, click the link.
5. Click Finish.

Installing Control-M/Agent version 7.0.00 fix pack 5 on UNIX

This procedure describes how to install Control-M/Agent version 7.0.00 fix pack 5 on UNIX computers.

Before You Begin

Ensure that you have met the following requirements:

Korn Shell (KSH) installed

Control-M/Agent version 7.0.00 installed

100 MB of free hard disk space available (same amount on the /tmp directory)

To install fix pack 5 on UNIX:

1. Do one of the following:

Keep the Control-M/Agent running, and continue to step 2.

Log in as the user (root or agent owner) and stop Control-M/Agent by typing the following
command:
<Control-M Agent_directory>/ctm/scripts/shut-ag -u <agentUser> -p all
If you are using an AIX operating system, you must remove unused libraries from memory, by typing
the following command as a root user:
/usr/sbin/slibclean

13

Release Notes
Do one of the following:

2.

If you obtained the installation files through FTP (see Obtaining installation files using FTP), navigate
to the temporary directory that you created.

If you obtained a CD (through EPD or BMC Sales Representative), mount the installation CD.

3. Log in as the Control-M/Agent user.

4. Install the fix pack using one of the following methods:

To perform an interactive installation, type one of the following commands, and then press Y:
o

CD: <CD>/Unix/setup.sh

FTP: <temp_dir>/setup.sh

To perform a silent installation, type one of the following commands:

o

CD: <CD>/Unix/setup.sh -s

FTP: <temp_dir>/setup.sh -s

NOTE: You can change the directory location where the temporary installation files are extracted. For
example, when there is insufficient disk space in the /tmp directory.
You can use the following sample path to extract the files to another directory:
<cdmount>/UNIX/setup.sh -d<location>
The <location> variable is the required location. Ensure that there is no space between -d and
<location>.
5. If you stopped the Control-M/Agent, log in as user (root or agent owner), and start the
Control-M/Agent by running the following command:
<CONTROL-M Agent_directory>/ctm/scripts/start-ag -u <agentUser> -p all

Uninstalling Control-M/Agent version 7.0.00 fix pack 5 from

Microsoft Windows
This procedure describes how to uninstall Control-M/Agent version 7.0.00 fix pack 5 from Windows
computers.

Before You Begin

Ensure that all jobs running on the Control-M/Agent have stopped.

To uninstall Control-M/Agent version 7.0.00 fix pack 5 from Microsoft Windows:

1. Log in as a Control-M/Agent administrator.
2. Uninstall the fix pack by using one of the following methods:

To perform an interactive uninstall, do the following:

14

Release Notes
a. From the Start menu, select Control Panel > Add/Remove Programs >
CONTROL-M/Agent 7.0.00 fix pack 5 .
b. Select Remove.

To perform a silent uninstall, do the following:

c. Navigate to the following directory:

<CONTROL-M/ Agent_ directory>\<instance_name>\install\PAKAI.7.0.00.500\

NOTE: If you are using Windows Vista, Windows 7, or Windows Server 2008, run the silent installation
from a command prompt that was opened with administrator privileges.
d. From a command line, type the following command:
uninstallSilent.bat

Uninstalling Control-M/Agent version 7.0.00 fix pack 5 from

UNIX
This procedure describes how to uninstall Control-M/Agent version 7.0.00 fix pack 5 from UNIX computers.

Before You Begin

Ensure that all jobs running on the Control-M/Agent have stopped.

To uninstall fix pack 5 from UNIX:

1. Log in as the user (root or agent owner) currently running the agent, and stop Control-M/Agent by
typing the following command:
<CONTROL-M Agent_directory>/ctm/scripts/shut-ag -u <agentUser> -p all
If you are using an AIX operating system, you must remove unused libraries from memory, by typing the
following command as a root user:
/usr/sbin/slibclean
Log in as a Control-M/Agent user. Uninstall the fix pack by using one of the following methods:

2.

To perform an interactive uninstall, type the following command, and then press Y:
$CONTROLM/patches/remove_fp -f PAKAI.7.0.00.500

To perform a silent uninstall, type the following command:

$CONTROLM/patches/remove_fp -f PAKAI.7.0.00.500 -s

3. Log in as user (root or agent owner), and start the Control-M/Agent by typing the following command:
<CONTROL-M Agent_directory>/ctm/scripts/start-ag -u <agentUser> -p all

15

Release Notes

In earlier fix packs

This section discusses enhancements and corrected problems in earlier fix packs.

Enhancements
The following table describes Control-M/Agent enhancements in earlier fix packs:
Tracking #

Description

QM001771383

Control-M/Agent is now supported on Windows Server 2012

QM001771381

Control-M/Agent is now supported on Windows 8

CAR00045489

File Watcher application fields are now supported in "Find and

Update" and "Job Filter" in Control-M/EM desktop and "Find Jobs"
and "Hierarchy" in the Control-M/EM GUI as well as the Application
tab in Self Service. Do the following:
1. Ensure that Control-M/EM has fix pack 7.0.00.400 installed.
2. Place the file FileWatch_appl.xml into the <Control-M/EM home
directory>/etc/applfields directory for both Control-M/EM server
and Control-M/EM client.
3. Restart Control-M/EM GUI server, and reopen Control-M/EM
Desktop and Control-M/EM.

CAR00046180 CAR00046181

(Control-M for Oracle Business Intelligence only) Changing the

account password by using the ag_change_password utility when
entering ORACLE_BI as application_type parameter is now
supported for defining user and password for FTP transfers. It is
now possible to update the user and passwords for the FTP transfers
in the Oracle Business Intelligence Configuration Manager.

CAR00045951

(UNIX only) Allow starting the SAP extractor process upon Agent
start-up. The parameter, XT_AUTOSTART is manually added to the
SAP parameter file data/SAP.dat and set to Y, so the SAP extractor
process (p_ctmxt) starts upon Agent startup.

CAR00045115

Control-M/Agent is now supported on Solaris 11 SPARC and x86_64

architectures.

16

Release Notes
Tracking #

Description

CAR00044872

During job submission to remote hosts over SSH, you can now
disable the automatic mechanism that determines the remote host
platform type, and specify the platform type manually. This feature
is enabled by setting parameter RJX_FORCE_OS_CHECKING to M in
the Control-M/Agent system parameters of the Control-M
Configuration Manager. The following rules apply:

CAR00045455

If the correct remote host file already exists, no further action is

required.
Once a remote host detail file has been created, Control-M/Agent
will continue to rely on the information in the file without attempting
to detect the remote host for future runs.
If the remote host details file for the remote host is missing from
the DATA\rhdetails directory, all jobs targeted to the remote host
fail and the following error message is recorded in the job log: Error:
Remote OS platform must be explicitly defined. Check logs in
proclog directory for more details. Additional information regarding
the problem and its solution are also recorded in the log files of the
proclog directory. You can define a remote host details file using one
of the following methods:
Define and run a job on the desired remote host with autoedit
variable %%RJX_REMOTE_PLATF set to Windows, UNIX, or OVMS
(depending on the remote host OS type) Do not type the %%
characters before the autoedit name in the Control-M/EM GUI as
they are added automatically. A successful job run creates the
remote host details file. Once the details file is created, the autoedit
name can be removed or kept in the job definition as desired.
Duplicate an existing remote host details file and modify the
information as required.
CAR00042722

Control-M/Agent now supports Red Hat Enterprise Linux 6 on IBM

zSeries .

CAR00042199

You can now automate password changes of Control Modules

accounts using the Control-M/Agent ag_change_password
command line utility. For more information see fix pack 2.

CAR00044021

Control-M/Agent now sends an Exception Alert to the Control-M

Configuration Manager when the free disk space is low. Set the
MIN_FREE_SPACE_WARN system parameter (Default: 100 MB) in
the Control M Configuration Manager to receive warnings when the
minimum free space level is approached.
Note: Use the MIN_FREE_SPACE parameter (Default: 50 MB) to set
the minimum free space level that is required to run a job on a
specific agent.

17

Release Notes
Tracking #

Description

CAR00044123

Control-M/Agent can now block incoming requests based on the IP

address of the sender. Use the Authorized Control-M/Server IP
addresses option in the Control-M Configuration Manager with the
configuration format AUTHORIZED_CTM_IP IP1|IP2|IP3 to block IP
addresses that are not authorized. When Control-M/Agent is set to
work in persistent mode, to configure the feature of creating an
authorized list of IP addresses that Control-M/Agent will accept
connections from, you must configure the AUTHORIZED_CTM_IP
parameter and then restart Control-M/Agent.

CAR00044141

You can now limit the amount of information sent by

Control-M/Agent for a view SYSOUT request. To limit the amount of
information, add the SYSOUT_LIMIT_SIZE_START and
SYSOUT_LIMIT_SIZE_END configuration parameters to the
config.dat file and specify the size in KB of the header and footer for
display, respectively. The agent truncates the SYSOUT, passing only
the required data to the server.

Corrected problems
The following table describes Control-M/Agent corrected problems in earlier releases. The list of corrected
problems is also available in the knowledge base as follows:

Fix Pack 4: KA381165

Fix pack 3: KA360106

Fix pack 2: KA352530

Fix pack 1: KA344786

Tracking #

Description

CAR00040461

(Agentless UNIX only) The agent now supports the system autoedit
%%ECHO_SYSOUT also for agentless. This autoedit overrides
agent configuration parameters, CTM_PRM_SH_FLAGS/
CTM_PRM_KSH_FLAGS that determines if and how the job script
commands are written to the job sysout.

CAR00041379

(UNIX only) The start-ag and shut-ag scripts update the parameter
in the CONFIG.dat file by creating a temporary file. This overrides
the current file with temporary file content including the updated
parameter. On rare occasions, CONFIG.dat becomes corrupted,
causing the agent to fail.

18

Release Notes
Tracking #

Description

CAR00042210

The File Watcher and emreportcli application fields do not appear in

"Find Jobs" and "Hierarchy" in the Control-M/EM GUI and in "Find
and Update", and "Job Filter" in Control-M/EM desktop as well as in
the SLS Application tab.

CAR00042623

(UNIX only) Control-M/Agents jobs that exit almost immediately

and ends NOTOK, may be reported as OK. This may happen in a
stressed environment. An error message may be issued in the Agent
debug logs. For example: 1026 13:50:09:500
AM:OS_SCRIPT_system : waiting for a child 5073 ...

CAR00043798

(UNIX only) When a job script is in CSH, On Statements may be

wrongly matched where they are defined with Stmt=* and
Code=*something* ("something" appears inside an if statement in
the job script).

CAR00044230

(Microsoft Windows only) Cannot get the job sysout when

SYSOUT_NAME is changed from MEMNAME to JOBNAME or
JOBNAME to MEMNAME.

CAR00044441

(Linux only) The su.bmc utility does not add /usr/local/bin to the
PATH.

CAR00044658

(UNIX only) Where many control modules are installed, and the
shut-ag utility is used, not all of the containers stop.

CAR00045051

(UNIX only) The Agent fails to start if the server to agent port has a
parallel internal port with the same number as a UNIX Domain
Socket inode. This can be viewed in 'netstat output'. An error is
displayed by the start-ag script. For example: "Control-M/Agent
Listener port 10501 is busy" "Control-M/Agent
Listener start failed."

CAR00045330

(Microsoft Windows only) The Agent fails to run a domain-user log

on script. This occurs when the Agent is configured to log on as user
and to run a user log on script.

CAR00045400

(Linux Agents 700 fix pack 1 and above) Control-M Configuration

Manager agent properties request times out as the Agent is
persistently connected.

CAR00045506

After installing Control-M/Agent fix pack 2, jobs may fail if they

contain a CSH script with nested IF statements and other nested
blocks.

19

Release Notes
Tracking #

Description

CAR00045587

(Control-M for IBM Cognos only) The ag_change_password utility

does not work if Control-M for IBM Cognos is installed after
Control-M/Agent fix pack 3. The following error messages are
issued: -String index out of range: -1 -Application COGNOS doesn't
support changing account's password

CAR00045590

(Control-M for IBM Cognos only) When changing the password

using the ag_change_password utility, the utility fails to issue a
message advising the user to restart the container.

CAR00045591

(Control-M for PeopleSoft only) When changing the password using

the ag_change_password utility, an incorrect message is issued
advising the user to shut down the utility instead of advising the user
to restart the utility.

CAR00045600

(Control-M for SAP fix pack 1 UNIX only) The

ag_change_password utility does not work when changing the
password.

CAR00045604

(Control-M for AFT only) When changing the password using the
ag_change_password utility, the output does not correctly
specify to which user name the password changes or fails. The
following error messages are issued: ag_change_password
-application_type FILE_TRANS -account unix_local -host cessna
-user sapr3 -old_password sapr3 -new_password kuku Password
change for account 'unix_local' in path: 'remote' Completed
Successfully

CAR00045672

Autoedit values longer than 214 characters are truncated by the

Agent before passing to Control-M, causing the job to submit with
incorrect data.

CAR00045680

(UNIX only) A job may show status as DISAPPEARED although it

successfully completes when submitting a job with large sysout and
heavy on-statement post processing. This can probably occur when
debug level is set to 4.

CAR00045921

(CJK only) If a sysout has many lines when using the ctmpsm utility,
it might lose characters.

CAR00046008

(Microsoft Windows only) When a remote host is defined with more

than one IP address, and some of these addresses are invalid,
occasionally the Agent crashes. Jobs that are running, end NOTOK,
with the status, "disappeared". The error is visible on AMD64 but
may affect other Windows versions as well as OpenVMS remote
hosts and possibly other SSH remote hosts.

20

Release Notes
Tracking #

Description

CAR00046052

(Microsoft Windows only) After upgrading from Control-M/Agent

640 to 700 the Control-M/Agent parameter RJX_CONN_TOUT has
an empty value after installation.

CAR00046185

(Linux 64 bit only) ag_change_password does not work. Usage

message does not appear.

CAR00046350

(Microsoft Windows only) Agent may crash when using WMI to

submit a job and a very late asynch. WMI callback is returned when
the agent cannot handle it.

CAR00046352

(Microsoft Windows only) Unable to recycle and restart

Control-M/Agent in Control-M Configuration Manager. The Agent
does not shut down, and becomes unavailable. The following error
message is issued: Failed to recycle agent Error AGT7901
CTM_AGENT

CAR00046492

(Control-M for Oracle Business Intelligence only) Changing the

account password by using the ag_change_password utility is
now supported.

CAR00046728

(Control-M for IBM InfoSphere DataStage only) Changing the

account password by using the ag_change_password utility
when entering DATASTAGE as application_type parameter is
now supported.

21

Release Notes

Support for Control-M 7.0.00.500

These topics provide information about the following:

Levels of support (on page 22)

Related documentation (on page 22)

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

Related documentation
To view the latest BMC documents, including documents in other languages, see the Customer Support
website at http://www.bmc.com/support.
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.

22

 Copyright 2013 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.
IBM Tivoli Workload Scheduler trademark or registered trademark is the trademark or registered
trademark of International Business Machines Corporation in the United States, other countries, or both.
Linux is the registered trademark of Linus Torvalds.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
UNIX is the registered trademark of The Open Group in the US and other countries.
The information included in this documentation is the proprietary and confidential information of BMC
Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions
of the applicable End User License agreement for the product and to the proprietary and restricted rights
notices included in the product documentation.
For the provisions described in the BMC License Agreement and Order related to third party products or
technologies included in the BMC Product, see the "ThirdParty" subdirectory in the installation directory of
this product.
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.

23