Readme file for IBM® Spectrum Conductor 2.5.1 Interim Fix 602102
Readme file for: IBM Spectrum Conductor
Product/Component release: 2.5.1
Fix ID: sc-2.5.1-build602102
Publication date: July 17, 2024
This interim fix resolves an SSL connection failure
from VEMKD’s client to VEMKD in an IBM Spectrum Conductor 2.5.1 cluster.
1.
List of fixes
2.
Download location
3.
Products or components affected
4.
Installation and configuration
5.
Uninstallation
6.
List of files
7.
Product notifications
8.
Copyright and trademark information
APAR: P105180
Download interim fix 602102
from the following location: https://www.ibm.com/eserver/support/fixes/.
Component name,
Platform, Fix ID:
EGO, Linux x86_64, sc-2.5.1-build602102
Follow the
instructions in this section to download and install this interim fix on hosts
in your cluster.
System requirements
Linux x86_64
Prerequisites
Fix
601712 must be installed before applying this fix
package.
Installation
Log on to the primary host as the cluster
administrator, stop all EGO services, and shut down the whole cluster:
> egosh user logon -u Admin -x password
> egosh service stop all
> egosh ego shutdown -f all
a. On each of your
management and compute host, download the following package, for example, to
the /scfixes directory.
egocore-4.0.0.0_x86_64_build602102.tar.gz
b.
Run the egoinstallfixes
command to install the package:
> egoinstallfixes /scfixes/egocore-4.0.0.0_x86_64_build602102.tar.gz
Note: Running the egoinstallfixes command
automatically backs up the current binary files to a fix backup directory for
recovery purposes. Do not delete this backup directory; you will need it if you
want to recover the original files. For more
information on using this command, see the egoinstallfixes command reference.
c. Run the pversions command to verify the installation:
> pversions -b 602102
d.
From the primary
host, start up your cluster:
> egosh ego start -f all
If
required, follow the instructions in this section to uninstall this interim fix
from hosts in your cluster.
a.
Log on to the primary host as the cluster
administrator, stop all EGO services, and shut down the whole cluster:
> egosh user logon -u Admin -x password
> egosh service stop all
> egosh ego shutdown -f all
b. On each host, roll back this interim fix:
> egoinstallfixes
-r 602102
c.
From the primary
host, start up your cluster:
> egosh ego start -f all
4.0/linux-x86_64/etc/vemkd
4.0/linux-x86_64/etc/pem
4.0/linux-x86_64/etc/egosc
4.0/linux-x86_64/lib/libvem.so.4.0.0
4.0/linux-x86_64/lib/jni/libVEMApiCommon.so
To receive information about product solution and
patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM
Support website (http://support.ibm.com). You can edit your subscription
settings to choose the types of information you want to get notification about,
for example, security bulletins, fixes, troubleshooting, and product
enhancements or documentation changes.
© Copyright IBM Corporation 2024
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.