Documente Academic
Documente Profesional
Documente Cultură
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
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
Release Notes
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
CAR00047638
CAR00047700
Installation Guide.
Release Notes
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
CAR00046792
CAR00046845
CAR00047146
CAR00047229
The ctmextract utility cannot extract SAP jobs when the job
definition size is over 32k.
CAR00047367
CAR00047479
CAR00047628
Release Notes
Tracking #
Description
CAR00047755
CAR00048075
CAR00048192
CAR00048708
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:
Bits
Compatible Processors
Windows XP Professional
32
x86
64
x86_64
Release Notes
Operating System
Bits
Compatible Processors
x86
x86_64
x86
x86_64
Itanium (ia64)
x86
x86_64
x86
x86_64
Itanium (ia64)
64
x86_64
Release Notes
Version
Bits
Compatible processors
AIX
7.1
64
Power
HP-UX
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
Version
Control-M/Enterprise Manager
7.0.00
7.0.00
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
Level of support
Traditional Chinese
Simplified Chinese
Japanese
Korean
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 the BMC sales representative (on page 11)
<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:
Download and save the .iso file to a temporary directory, and then burn it onto a DVD.
10
Release Notes
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
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>
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 :
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.
100 MB of free hard disk space available (same amount on the %temp% directory)
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.
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.
100 MB of free hard disk space available (same amount on the /tmp directory)
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.
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
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
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.
2.
To perform an interactive uninstall, type the following command, and then press Y:
$CONTROLM/patches/remove_fp -f PAKAI.7.0.00.500
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
Enhancements
The following table describes Control-M/Agent enhancements in earlier fix packs:
Tracking #
Description
QM001771383
QM001771381
CAR00045489
CAR00046180 CAR00046181
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
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
CAR00042199
CAR00044021
17
Release Notes
Tracking #
Description
CAR00044123
CAR00044141
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:
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
CAR00042623
CAR00043798
CAR00044230
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
CAR00045400
CAR00045506
19
Release Notes
Tracking #
Description
CAR00045587
CAR00045590
CAR00045591
CAR00045600
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
CAR00045680
CAR00045921
(CJK only) If a sysout has many lines when using the ctmpsm utility,
it might lose characters.
CAR00046008
20
Release Notes
Tracking #
Description
CAR00046052
CAR00046185
CAR00046350
CAR00046352
CAR00046492
CAR00046728
21
Release Notes
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
23