Readme
File for IBM ® Spectrum Conductor with Spark 2.2
Interim Fix 452892
Readme
file for: IBM Spectrum Conductor with Spark
Product/Component
Release: 2.2
Update
Name: Interim
Fix 452892
Fix
ID: cws-2.2-build452892
Publication
date: May 17, 2017
Abstract
Description
When you start up IBM
Spectrum Conductor with Spark version 2.2.0, the load information manager (lim)
sets a supplementary group list of cluster admins for vemkd. This interim fix
provides a resolution for this issue.
Contents
1. List of fixes
2. Download location
3. Products or components
affected
4. Installation and
configuration
5. List of files
6. Copyright and trademark
information
1. List of fixes
APAR: P102218
2. Download location
Download
interim fix 452892 from the following location: http://www.ibm.com/eserver/support/fixes/
3. Products or components
affected
Component
Name, Platform, Fix ID:
ego,
Linux 64-bit, cws-2.2-build452892
4. Installation and
configuration
System requirements
Linux
x86_64
Before installation
1.
Log on as the cluster administrator, stop all
services, and shut down the cluster:
> egosh user
logon -u Admin -x Admin
> egosh service
stop all
> egosh ego
shutdown
2.
For recovery purposes, log on to each management
host in the cluster and back up the following file, which is replaced by this
interim fix, to another directory:
>
$EGO_TOP/3.5/linux-x86_64/etc/lim
Installation
1.
Log on to each management host in your cluster as the cluster
administrator and decompress the cws2.2.0.0_x86_64_build452892.tar.gz to
the directory where you installed IBM Spectrum Conductor with Spark:
> tar zxfo
cws2.2.0.0_x86_64_build452892.tar.gz -C $EGO_TOP
After installation
1.
Verify the installation by running the lim -V
command. The following is a sample output of successfully running this command:
> lim -V
EGO 3.5.0 build 452892, May 08
2017
binary type: linux-x86_64
notes:
fixes:
2.
Start the cluster:
> egosh user
logon -u Admin -x Admin
> egosh ego
start
Uninstallation (if required)
1.
Log on as the cluster administrator, stop all
services, and shut down the cluster:
> egosh user
logon -u Admin -x Admin
> egosh service
stop all
> egosh ego
shutdown
2.
Log on to each management host in the cluster and
restore the backup for the following file:
>
$EGO_TOP/3.5/linux-x86_64/etc/lim
3.
Start the cluster:
> egosh user
logon -u Admin -x Admin
> egosh ego
start
5. List of files
lim
6. Copyright and trademark
information
© Copyright
IBM Corporation 2017
U.S. Government
Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
IBM®, the IBM
logo, and ibm.com® are trademarks of International Business Machines Corp.,
registered in many jurisdictions worldwide. Other product and service names
might be trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.