Interim fix 601214 for IBM Spectrum Symphony 7.3.2

Readme File for IBM^® Spectrum Symphony 7.3.2 Interim Fix 601214

Readme File for: IBM Spectrum Symphony

Product Release: 7.3.2

Update Name: Interim Fix 601214

Fix ID: sym-7.3-build601214-ms

Publication Date: July 25, 2022

This interim fix is an accumulation of several fixes for IBM Spectrum Symphony 7.3.2:

1. Support for IBM Spectrum Symphony multicluster sessions to failover or migrate away from the home or default cluster. (Original Fix ID: sym-7.2.0.2-build552182-ms)

2. Support to address a security issue when the GSS-Kerberos security plug-in is used in an IBM Spectrum Symphony 7.3.2 cluster and prevents a WSDL client from sending requests to SD with empty credentials. (Original Fix ID: sym-7.2.0.2-build600439-ms)

3. Allow IBM Spectrum Symphony on-premises clients to use a virtual hostname or IP address file to connect to the IBM Spectrum Symphony SD (session director) and SSM (session manager). Apply this enhancement on your IBM Spectrum Symphony client hosts. (Original Fix ID: sym-7.2.0.2-build600622-ms)

4. Resolution for a parsing issue when running the egosh service listinstance command. (Original Fix ID: sym-7.2.0.2-build600784)

5. Enhancement to the logic for querying activity information by reducing the data size returned in an IBM Spectrum Symphony 7.3.2 cluster. (Original Fix ID: sym-7.2.0.2-build600802)

6. Support for the IBM Spectrum Symphony client to select the correct SSM URL based on the SOAM_USE_VIRTUAL_HOSTNAME environment variable. (Original Fix ID: sym-7.2.0.2-build600839-ms)

7. Support for the EGOSC (EGO service controller) to appropriately respond even when many EGO service instances are started in an IBM Spectrum Symphony 7.3.2 cluster. (Original Fix ID: sym-7.2.0.2-build601116)

8. Support to prevent the session director (SD) from crashing when SD recovers a VEMKD connection in an IBM Spectrum Symphony 7.3.2 cluster with the GSS-Kerberos security plug-in. (Original Fix ID: sym-7.2.0.2-build600970)

9. Support to allow an IBM Spectrum Symphony session to be closed if its parent task is complete (that is, the task is in Done, Canceled, or Error state). (Original Fix ID: sym-7.2.0.2-build601136-ms)

10. Enhancement to VEMKD performance when SSL is enabled between VEMKD and its clients in an IBM Spectrum Symphony 7.3.2 cluster. (Original Fix ID: sym-7.2.0.2-build601142)

11. Prevent the IBM Spectrum Symphony 7.3.2 session director (SD) from throwing an unknown exception, when interim fixes 600390 and 600426 are installed in the cluster. (Original Fix ID: sym-7.2.1-build600560-ms)

12. Resolution for a SIM daemon dead lock issue after enabling Docker for service instances in IBM Spectrum Symphony 7.3.2. (Original Fix ID: sym-7.2.1-build600783)

13. Allow the host factory feature to maximize provisioning when there are lingering reserved slots. (Original Fix ID: sym-7.2.1-build600817)

14. Support for the IBM Spectrum Symphony client to select the correct SSM URL based on the SOAM_USE_VIRTUAL_HOSTNAME environment variable. (Original Fix ID: sym-7.2.1-build600827-ms)

15. Resolution for a compatibility issue that provisioned host cannot list on Resources > Cloud > Hosts page. The fix requires to upgrade the hf_provisioned_host schema to add four columns. Then, you can optionally choose from the Settings page the following columns: Price type, Instance type, Instance tags, or Cloud host ID. (Original Fix ID: sym-7.2.1-build600746)

16. Resolution for an issue that fails to get the launch template, it shows the following error message in the provider log file for AWS: Fail to get the launch template <xxx>. Check the AWS console for more details. (Original Fix ID: sym-7.2.1-build600865)

17. Enhancement provides a way to allow the egosh command to retrieve configuration from environment variables, instead of needing to deploy and manage configuration files on client machines. This project allows the egosh command to behave consistently as the other IBM Spectrum Symphony commands. (Original Fix ID: sym-7.2.1-build600920-ms)

18. Ensure that a SIM (service instance manager) thread exists after receiving a SIGTERM signal when enabling Docker for service instances in IBM Spectrum Symphony 7.3.2. (Original Fix ID: sym-7.2.1-build600986)

19. Resolution for the IBM Spectrum Symphony recursive workload feature to avoid backfilling a host blocked by a backfilled service instance. (Original Fix ID: sym-7.2.1-build601005-ms)

20. Resolution for IBM Spectrum Symphony to update the ServiceToSlotRatio format when creating sessions in the SSM log. (Original Fix ID: sym-7.2.1-build601025)

21. Resolve a stop Docker pod timeout issue for IBM Spectrum Symphony 7.3.2. This fix adds a new DISABLE_STOPPING_DOCKER_POD_TWICE setting to disable IBM Spectrum Symphony from running the stop action twice, when the Docker daemon is unresponsive. (Original Fix ID: sym-7.2.1-build601036)

22. Allow the maxmem value to display when an IBM Spectrum Symphony 7.3.2 cluster is running in Kubernetes or Docker containers. (Original Fix ID: sym-7.2.1-build601057)

23. Introduce a new EGO parameter called EGO_IGNORE_CPU_CGROUP_SETTING_IN_CONTAINER, which ignores the CPU cgroup setting when an IBM Spectrum Symphony 7.3.2 cluster is running in Kubernetes or Docker containers. (Original Fix ID: sym-7.2.1-build601184)

24. Leave the “Reclaimed” count as unchanged and appropriately increases the “SIM communication lost” value. (Original Fix ID: sym-7.2.1-build601069-ms)

25. Allow EGO event data to not write hostnames, so that AWS CloudWatch does not truncate the event data file when analyzing ego EGO event data. (Original Fix ID: sym-7.2.1-build601078-ms)

26. Resolve the issue of the IBM Spectrum Symphony host factory feature to scale up hosts beyond the maxNumber configured in the Amazon Web Services (AWS) provider instance host template. (Original Fix ID: sym-7.2.1-build601083)

Contents

1. List of fixes

2. Download location

3. Product and components affected

4. Installation and configuration

5. Uninstallation

6. List of files

7. Product notifications

8. Copyright and trademark information

1. List of fixes

APAR: P104707

2. Download location

Download interim fix 601214 from the following location: https://www.ibm.com/eserver/support/fixes/

3. Product and components affected

Component name, Platform, Fix ID:

EGO/SOAM/SOAM SDK library/PERF, Windows 64, sym-7.3-build601214-ms

EGO/SOAM/SOAM SDK library/PERF, Linux-x86_64 64, sym-7.3-build601214-ms

4. Installation and configuration

Follow the instructions in this section to download and install this interim fix on your cluster.

System requirements

Windows 64-bit or Linux x86_64

Limitation

With this interim fix, IBM Spectrum Symphony Developer Edition does not support to start agent. We will release a new interim fix to resolve this issue.

Installing on IBM Spectrum Symphony management and compute hosts on Linux

a. Log on to the primary host as the cluster administrator, and shut down the cluster:

> egosh user logon –u Admin –x Admin

> soamcontrol app disable all

> egosh service stop all

> egosh ego shutdown

b. On each management and compute host find and remove all the Python pyc files from $EGO_TOP/4.0/linux-x86_64/etc/egodocker/ and its subdirectories:

> find $EGO_TOP/4.0/linux-x86_64/etc/egodocker/ -name *.pyc -exec rm -f {} \;

c. On each management and compute host (or just one host if you are using a shared file system), create a directory (for example, /symfixes) and download the soamcore-7.3.2.0_x86_64_build601214.tar.gz, egocore-4.0.0.0_x86_64_build601214.tar.gz and hfcore-1.2.0.0_x86_64_build601214.tar.gz files to the directory.

d. Run the egoinstallfixes command to install the soamcore-7.3.2.0_x86_64_build601214.tar.gz, egocore-4.0.0.0_x86_64_build601214.tar.gz and hfcore-1.2.0.0_x86_64_build601214.tar.gz files:

> egoinstallfixes /symfixes/egocore-4.0.0.0_x86_64_build601214.tar.gz

> egoinstallfixes /symfixes/soamcore-7.3.2.0_x86_64_build601214.tar.gz

> egoinstallfixes /symfixes/hfcore-1.2.0.0_x86_64_build601214.tar.gz

Note: The hfcore-1.2.0.0_x86_64_build601214.tar.gz is not required on compute hosts.

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.

e. Run the pversions command to verify the installation:

> pversions -b 601214

f. Log on to the primary host as the cluster administrator, start the cluster and enable your applications:

> egosh ego start hostname

> soamcontrol app enable application_name

Installing on IBM Spectrum Symphony Develop Edition on Linux

a. Log on to the IBM Spectrum Symphony Develop Edition host as the cluster administrator and stop the agent:

> soamshutdown

b. For recovery purposes, back up the following files which will replaced by this interim fix:

$SOAM_HOME/7.3.2/linux-x86_64/lib64/libsoambase.so

$SOAM_HOME/7.3.2/linux-x86_64/lib/libsoambase.so

$SOAM_HOME/7.3.2/linux-x86_64/etc/sd

$SOAM_HOME/7.3.2/linux-x86_64/etc/ssm

c. Download the symde-7.3.2.0_x86_64_build601214.tar.gz file and decompress to the $SOAM_HOME directory, for example:

> tar zxfo symde-7.3.2.0_x86_64_build601214.tar.gz -C $SOAM_HOME

d. From the primary host, start the agent:

> soamstartup &

Installing on IBM Spectrum Symphony client hosts on Linux

a. Log on to the IBM Spectrum Symphony client host and stop the running client.

b. Back up the following files which will be replaced by this interim fix:

$SOAM_HOME/lib/libsoambase.so

$SOAM_HOME/lib64/libsoambase.so

$SOAM_HOME/lib/libvem.so.4.0.0

$SOAM_HOME/lib64/libvem.so.4.0.0

c. Download the symclnt-7.3.2.0_x86_64_build601214.tar.gz file and extract its contents to the top-level installation directory:

> tar zxfo symclnt-7.3.2.0_x86_64_build601214.tar.gz -C $SOAM_HOME

Installing on IBM Spectrum Symphony management hosts and compute hosts on Windows

a. Log on to the primary cluster as the cluster administrator and shut down the cluster:

> egosh user logon -u Admin -x Admin

> egosh service stop all

> soamcontrol app disable all

> egosh ego shutdown all

b. On each management host and compute host, back up the following files which will be replaced by this interim fix:

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sim.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sim.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sd.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sd.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\bin\soamview.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\libvem.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\libvem400.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\libvem.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\libvem400.dll

%SOAM_HOME%\..\4.0\etc\vemkd.exe

%SOAM_HOME%\..\4.0\etc\vemkd.pdb

%SOAM_HOME%\..\4.0\etc\egosc.exe

%SOAM_HOME%\..\4.0\etc\egosc.pdb

%SOAM_HOME%\..\4.0\bin\egosh.exe

%SOAM_HOME%\..\4.0\bin\egosh.pdb

%SOAM_HOME%\..\4.0\lib\libvem.dll

%SOAM_HOME%\..\4.0\lib\libvem.pdb

%SOAM_HOME%\..\4.0\lib\libvem400.dll

%SOAM_HOME%\..\4.0\lib\libvem400.pdb

%SOAM_HOME%\..\perf\ego\4.0\win\lib\egoconsumerres.dll

%SOAM_HOME%\..\4.0\lib\jni\VEMApiCommon.dll

%SOAM_HOME%\..\4.0\lib\sec_ego_sspikrb.dll

%SOAM_HOME%\..\4.0\lib\sec_ego_sspikrb.pdb

%SOAM_HOME%\..\hostfactory\1.2\win2003-x64\etc\hostfactory.exe

%SOAM_HOME%\..\hostfactory\1.2\win2003-x64\etc\hostfactory.pdb

%SOAM_HOME%\..\hostfactory\1.2\providerplugins\aws\lib\AwsTool.jar

c. Download the sym-7.3.2.0-soamcore-7.3.2.0_build601214.zip, sym-7.3.2.0-egocore-4.0.0.0_build601214.zip and hfcore-1.2.0.0_build601214.zip files and extract their contents to the top level installation directory.

Note: The hfcore-1.2.0.0_build601214.zip is not required on compute hosts.

Installing on IBM Spectrum Symphony Develop Edition on Windows

a. Log on to the IBM Spectrum Symphony Develop Edition host as the cluster administrator and stop the agent:

> soamshutdown

b. For recovery purposes, back up the following files, and then remove them:

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sd.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sd.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.pdb

c. Download the symde-7.3.2.0_build601214.zip file and extract its contents to %SOAM_HOME% directory.

Installing on IBM Spectrum Symphony client hosts on Windows

a. Log on to the IBM Spectrum Symphony client host and stop the running client.

b. Back up the following files, which will be replaced by this interim fix:

%SOAM_HOME%\lib\soambase.dll

%SOAM_HOME%\lib\soambase.lib

%SOAM_HOME%\lib\soambase.pdb

%SOAM_HOME%\lib64\soambase.dll

%SOAM_HOME%\lib64\soambase.lib

%SOAM_HOME%\lib64\soambase.pdb

%SOAM_HOME%\lib\libvem.dll

%SOAM_HOME%\lib64\libvem.dll

%SOAM_HOME%\lib\libvem400.dll

%SOAM_HOME%\lib\libvem400.pdb

%SOAM_HOME%\lib64\libvem400.dll

%SOAM_HOME%\lib64\libvem400.pdb

c. Download the symclnt-7.2.1.0_build600827.zip file and extract its contents to %SOAM_HOME% directory.

5. Configuration

a. Allow EGO event data to not write hostnames, so that AWS CloudWatch does not truncate the event data file when analyzing ego EGO event data. Configure the EGO_REMOVE_HOSTNAME_FROM_EVENT_DATA parameter with a value of Y in the ego.conf file:

EGO_REMOVE_HOSTNAME_FROM_EVENT_DATA=Y

b. Set following EGO parameter in ego.conf to ignore the CPU cgroup setting. The default value of EGO_IGNORE_CPU_CGROUP_SETTING_IN_CONTAINER is “N”.

EGO_IGNORE_CPU_CGROUP_SETTING_IN_CONTAINER=Y

c. By default, when the Docker daemon is unresponsive, IBM Spectrum Symphony attempts to stop the Docker container pod to a maximum of two attempts. To enable IBM Spectrum Symphony to disable the second try, configure the DISABLE_STOPPING_DOCKER_POD_TWICE setting in the Docker section of the application profile. Valid values are Y or y. By default, this setting is not enabled:

Here is an example of enable this setting:

...

...

<\osType>

<\osTypes>

d. To allow the egosh command to retrieve configuration from environment variables, instead of needing to deploy and manage configuration files on client machines:

On Linux:

a) Set the EGO_DISABLE_EGOCONF_DEPENDENCY environment variable as Y to enable this feature:

> export EGO_DISABLE_EGOCONF_DEPENDENCY=Y

b) Set mandatory parameters as environment variables:

> export EGO_MASTER_LIST=$MASTER_HOSTNAME

> export EGO_KD_PORT=$KD_PORT

c) Set the LD_LIBRARY_PATH environment variable to include the IBM Spectrum Symphony PATH library, for example:

> export LD_LIBRARY_PATH=\opt\sym732\soam\7.3.2\linux-x86_64\lib64:\opt\sym732\soam\7.3.2\linux-x86_64\lib:\opt\sym732\integration\yarn\4.0\linux-x86_64\lib\:\opt\sym732\4.0\linux-x86_64\lib:\opt\sym732\perf\ego\4.0\linux-x86_64\lib:\opt\sym732\perf\soam\7.3.2\linux-x86_64\lib:\opt\sym732\4.0\linux-x86_64\lib\jni

Note: Ensure that all the .so files located at $EGO_TOP\4.0\linux-x86_64\lib can be accessed by the egosh command.

d) If SSL is enabled, also set the EGO_CLIENT_TS_PARAMS environment variable, for example:

> export EGO_CLIENT_TS_PARAMS=SSL[CIPHER=AES256-GCM-SHA384,CAFILE=$EGO_TOP\wlp\usr\shared\resources\security\cacert.pem]

> export EGO_TRANSPORT_SECURITY=SSL

> export EGO_KD_TS_PORT=$SSL_PORT

e) If you want to use the egosh entitlement info command, also set the EGO_LIM_PORT environment variable, for example:

> export EGO_LIM_PORT=$BASE_PORT

Note: Execute this command from the host managed by the cluster (primary, management, or compute host).

f) For safety reasons, running the egosh ego start or egosh ego shutdown commands on client hosts is not recommended; however, if you must run them on client hosts, ensure that the EGO_CONFDIR, EGO_SERVERDIR, and EGO_BINDIR environment variables are correctly set, and execute the commands from the host managed by the cluster (primary, management, or compute host).

g) Run the egosh command. The command should run successfully (that is, without needing to load the ego.conf file from the host, and without errors).

On Windows:

a) Open a new Windows command prompt window and enable this feature:

· To enable for the current user, set the EGO_DISABLE_EGOCONF_DEPENDENCY environment variable as Y.

· To enable for all users, configure EGO_DISABLE_EGOCONF_DEPENDENCY=Y as a Windows system variable for all users using the Windows Control Panel.

b) Set mandatory parameters as environment variables:

> set EGO_MASTER_LIST=%MASTER_HOSTNAME%

> set EGO_KD_PORT=%KD_PORT%

c) Set the Windows Path to include the IBM Spectrum Symphony Path library, for example:

> set Path=%Path%;C:\Program Files\IBM\SpectrumComputing\soam\7.3.2\w2k3_x64-vc7-psdk\bin;C:\Program Files\IBM\SpectrumComputing\soam\7.3.2\w2k3_x64-vc7-psdk\lib;C:\Program Files\IBM\SpectrumComputing\soam\7.3.2\w2k3_x64-vc7-psdk\lib64;C:\Program Files\IBM\SpectrumComputing\4.0\bin;C:\Program Files\IBM\SpectrumComputing\4.0\lib;

Note: Ensure that all the .dll files located at %EGO_TOP%\4.0\lib can be accessed by the egosh command.

d) If SSL is enabled, also set the EGO_CLIENT_TS_PARAMS environment variable, for example:

> set EGO_CLIENT_TS_PARAMS=SSL[CIPHER=AES256-GCM-SHA384,CAFILE=%EGO_TOP%\wlp\usr\shared\resources\security\cacert.pem]

> set EGO_TRANSPORT_SECURITY=SSL

> set EGO_KD_TS_PORT=%SSL_PORT%

e) If you want to use the egosh entitlement info command, also set the EGO_LIM_PORT environment variable, for example:

> set EGO_LIM_PORT=%BASE_PORT%

Note: Execute this command from the host managed by the cluster (primary, management, or compute host).

f) For safety reasons, running the egosh ego start or ego shutdown commands on client hosts is not recommended; however, if you must run them on client hosts, ensure that the EGO_CONFDIR, EGO_SERVERDIR, and EGO_BINDIR environment variables are correctly set, and execute the commands from the host managed by the cluster (primary, management, or compute host).

g) Run the egosh command. The command should run successfully (that is, without needing to load the ego.conf file from the host, and without errors).

e. To enable the feature that closes the session after its parent task is complete (that is, the task is in Done, Canceled, or Error state):

a) Set the SSM_CLOSE_CHILD_SESSIONS_OF_FINISHED_TASK environment variable in the application profile:

<env name="SSM_CLOSE_CHILD_SESSIONS_OF_FINISHED_TASK">Y<\env>

……

<\osType>

<\osTypes>

<\SSM>

b) Register the updated application profile:

> soamreg application_profile.xml

f. To allow IBM Spectrum Symphony on-premises clients to use a virtual hostname or IP address file to connect to the IBM Spectrum Symphony SD (session director) and SSM (session manager):

On the client nodes, execute the clients:

· Linux:

> export SOAM_USE_VIRTUAL_HOSTNAME=Y

> symping

· Windows:

> set SOAM_USE_VIRTUAL_HOSTNAME=Y

> symping

6. Uninstallation

If required, follow the instructions in this section to uninstall this interim fix from your cluster:

Uninstalling from IBM Spectrum Symphony management and compute hosts on Linux

a. Log on to the primary host as the cluster administrator, and shut down the cluster:

> egosh user logon -u Admin -x Admin

> soamcontrol app disable all

> egosh service stop all

> egosh ego shutdown

b. On each management or compute host, roll back this interim fix:

> egoinstallfixes -r 601214

c. On each management and compute host find and remove all the Python pyc files from $EGO_TOP\4.0\linux-x86_64\etc\egodocker\ and its subdirectories:

> find $EGO_TOP\3.7\linux-x86_64\etc\egodocker\ -name *.pyc -exec rm -f {} \;

d. Remove all configurations in above section.

e. Log on to the primary host, start the cluster, and enable your applications:

> egosh ego start all

> egosh user logon -u Admin -x Admin

> soamcontrol app enable application_name

Uninstalling from IBM Spectrum Develop Edition on Linux

a. Log on to the IBM Spectrum Symphony Develop Edition host as the cluster administrator and stop the agent:

> soamshutdown

b. Log on to each IBM Spectrum Symphony Develop Edition host in the cluster and remove the installed fix:

$SOAM_HOME\7.3.2\linux-x86_64\lib64\libsoambase.so

$SOAM_HOME\7.3.2\linux-x86_64\lib\libsoambase.so

$SOAM_HOME\7.3.2\linux-x86_64\etc\ssm

$SOAM_HOME\7.3.2\linux-x86_64\etc\sd

c. Restore your backup files.

d. From the primary host, start the agent:

> soamstartup &

Uninstallating from the IBM Spectrum Symphony client hosts on Linux

a. Log on to the IBM Spectrum Symphony client host and stop the running client.

b. Restore your backup version of the following files:

$SOAM_HOME\lib\libsoambase.so

$SOAM_HOME\lib64\libsoambase.so

$SOAM_HOME\lib\libvem.so.4.0.0

$SOAM_HOME\lib64\libvem.so.4.0.0

Uninstalling from the IBM Spectrum Symphony management hosts and compute hosts on Windows

a. Log on to the primary cluster as the cluster administrator:

> egosh user logon -u Admin -x Admin

b. Shut down the cluster:

> soamcontrol app disable all

> egosh service stop all

> egosh ego shutdown all

c. On each management host and compute host, restore your backup version of the following files:

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sim.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sim.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sd.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\etc\sd.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\bin\soamview.exe

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\libvem.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\libvem400.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\libvem.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\libvem400.dll

%SOAM_HOME%\..\4.0\etc\vemkd.exe

%SOAM_HOME%\..\4.0\etc\vemkd.pdb

%SOAM_HOME%\..\4.0\etc\egosc.exe

%SOAM_HOME%\..\4.0\etc\egosc.pdb

%SOAM_HOME%\..\4.0\bin\egosh.exe

%SOAM_HOME%\..\4.0\bin\egosh.pdb

%SOAM_HOME%\..\4.0\lib\libvem.dll

%SOAM_HOME%\..\4.0\lib\libvem.pdb

%SOAM_HOME%\..\4.0\lib\libvem400.dll

%SOAM_HOME%\..\4.0\lib\libvem400.pdb

%SOAM_HOME%\..\perf\ego\4.0\win\lib\egoconsumerres.dll

%SOAM_HOME%\..\4.0\lib\jni\VEMApiCommon.dll

%SOAM_HOME%\..\4.0\lib\sec_ego_sspikrb.dll

%SOAM_HOME%\..\4.0\lib\sec_ego_sspikrb.pdb

%SOAM_HOME%\..\hostfactory\1.2\win2003-x64\etc\hostfactory.exe

%SOAM_HOME%\..\hostfactory\1.2\win2003-x64\etc\hostfactory.pdb

%SOAM_HOME%\..\hostfactory\1.2\providerplugins\aws\lib\AwsTool.jar

d. Remove all configurations in above section.

e. From the primary host, start the cluster.

Uninstalling from IBM Spectrum Symphony Develop Edition on Windows

f. Log on to the IBM Spectrum Symphony Developer Edition host, and stop all applications:

> soamcontrol app disable all

g. Stop IBM Spectrum Symphony Developer Edition:

> echo .| soamshutdown

h. On each IBM Spectrum Symphony Developer Edition host, restore your backup version of the following files:

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.pdb

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.dll

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.lib

%SOAM_HOME%\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.pdb

i. From the primary host, start the agent:

> echo .|soamstartup

Uninstalling from IBM Spectrum Symphony client hosts on Windows

a. Log on to the IBM Spectrum Symphony client host and stop the running client.

b. Restore your backup version of the following files:

%SOAM_HOME%\lib\soambase.dll

%SOAM_HOME%\lib\soambase.lib

%SOAM_HOME%\lib\soambase.pdb

%SOAM_HOME%\lib64\soambase.dll

%SOAM_HOME%\lib64\soambase.lib

%SOAM_HOME%\lib64\soambase.pdb

%SOAM_HOME%\lib\libvem.dll

%SOAM_HOME%\lib64\libvem.dll

%SOAM_HOME%\lib\libvem400.dll

%SOAM_HOME%\lib\libvem400.pdb

%SOAM_HOME%\lib64\libvem400.dll

%SOAM_HOME%\lib64\libvem400.pdb

7. List of files

soamcore-7.3.2.0_x86_64_build601214.tar.gz

soam\7.3.2\linux-x86_64\lib64\libsoambase.so

soam\7.3.2\linux-x86_64\lib\libsoambase.so

soam\7.3.2\linux-x86_64\etc\ssm

soam\7.3.2\linux-x86_64\etc\sim

soam\7.3.2\linux-x86_64\etc\sd

soam\7.3.2\linux-x86_64\bin\soamview

soam/7.3.2/linux-x86_64/lib64/libvem.so.4.0.0

soam/7.3.2/linux-x86_64/lib/libvem.so.4.0.0

egocore-4.0.0.0_x86_64_build601214.tar.gz

4.0\linux-x86_64\bin\egosh

4.0\linux-x86_64\etc\vemkd

4.0\linux-x86_64\etc\egosc

4.0\linux-x86_64\etc\egodocker\dockercontroller.py

4.0\linux-x86_64\etc\egodocker\libs\pod\dockerclient.py

4.0\linux-x86_64\etc\egodocker\libs\pod\dockerpod.py

4.0\linux-x86_64\etc\egodocker\libs\pod\timeout.py

4.0\linux-x86_64\etc\egodocker\libs\pod\dockercontainers.py

4.0\linux-x86_64\etc\egodocker\libs\external\docker\api\container.py

4.0\linux-x86_64\etc\egodocker\libs\external\docker\api\image.py

4.0\linux-x86_64\etc\egodocker\libs\external\docker\utils\utils.py

4.0\linux-x86_64\etc\egodocker\libs\external\docker\client.py

4.0\linux-x86_64\etc\egodocker\libs\pod\constants.py

4.0\linux-x86_64\lib\jni\libVEMApiCommon.so

4.0\linux-x86_64\lib\sec_ego_gsskrb.so

4.0\linux-x86_64\lib\libvem.so.4.0.0

perf\ego\4.0\linux-x86_64\lib\libegoconsumerres.so

soam\7.3.2\linux-x86_64\lib64\libvem.so.4.0.0

hfcore-1.2.0.0_x86_64_build601214.tar.gz

hostfactory\1.2\linux-x86_64\etc\hostfactory

hostfactory\1.2\providerplugins\aws\lib\AwsTool.jar

symde-7.3.2.0_x86_64_build601214.tar.gz

7.3.2\linux-x86_64\lib64\libsoambase.so

7.3.2\linux-x86_64\lib\libsoambase.so

7.3.2\linux-x86_64\etc\ssm

7.3.2\linux-x86_64\etc\sd

symclnt-7.3.2.0_x86_64_build601214.tar.gz

lib64\libsoambase.so

lib\libsoambase.so

lib64\libvem.so.4.0.0

lib\libvem.so.4.0.0

sym-7.3.2.0-soamcore-7.3.2.0_build601214.zip

soam\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.exe

soam\7.3.2\w2k3_x64-vc7-psdk\etc\ssm.pdb

soam\7.3.2\w2k3_x64-vc7-psdk\etc\sim.exe

soam\7.3.2\w2k3_x64-vc7-psdk\etc\sim.pdb

soam\7.3.2\w2k3_x64-vc7-psdk\etc\sd.exe

soam\7.3.2\w2k3_x64-vc7-psdk\etc\sd.pdb

soam\7.3.2\w2k3_x64-vc7-psdk\bin\soamview.exe

soam\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.dll

soam\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.pdb

soam\7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.lib

soam\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.dll

soam\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.pdb

soam\7.3.2\w2k3_x64-vc7-psdk\lib\soambase.lib

soam\7.3.2\w2k3_x64-vc7-psdk\lib64\libvem.dll

soam\7.3.2\w2k3_x64-vc7-psdk\lib64\libvem400.dll

soam\7.3.2\w2k3_x64-vc7-psdk\lib\libvem.dll

soam\7.3.2\w2k3_x64-vc7-psdk\lib\libvem400.dll

sym-7.3.2.0-egocore-4.0.0.0_build601214.zip

4.0\etc\vemkd.exe

4.0\etc\vemkd.pdb

4.0\etc\egosc.exe

4.0\etc\egosc.pdb

4.0\bin\egosh.exe

4.0\bin\egosh.pdb

4.0\lib\libvem.dll

4.0\lib\libvem.pdb

4.0\lib\libvem400.dll

4.0\lib\libvem400.pdb

perf\ego\4.0\win\lib\egoconsumerres.dll

4.0\lib\jni\VEMApiCommon.dll

4.0\lib\sec_ego_sspikrb.dll

4.0\lib\sec_ego_sspikrb.pdb

hfcore-1.2.0.0_build601214.zip

hostfactory\1.2\win2003-x64\etc\hostfactory.exe

hostfactory\1.2\win2003-x64\etc\hostfactory.pdb

hostfactory\1.2\providerplugins\aws\lib\AwsTool.jar

symde-7.3.2.0_build601214.zip

7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.dll

7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.lib

7.3.2\w2k3_x64-vc7-psdk\lib64\soambase.pdb

7.3.2\w2k3_x64-vc7-psdk\lib\soambase.dll

7.3.2\w2k3_x64-vc7-psdk\lib\soambase.lib

7.3.2\w2k3_x64-vc7-psdk\lib\soambase.pdb

7.3.2\w2k3_x64-vc7-psdk\etc\ssm.exe

7.3.2\w2k3_x64-vc7-psdk\etc\ssm.pdb

7.3.2\w2k3_x64-vc7-psdk\etc\sd.exe

7.3.2\w2k3_x64-vc7-psdk\etc\sd.pdb

symclnt-7.3.2.0_build601214.zip

symclient\lib64\soambase.dll

symclient\lib64\soambase.lib

symclient\lib64\soambase.pdb

symclient\lib\soambase.dll

symclient\lib\soambase.lib

symclient\lib\soambase.pdb

symclient\lib64\libvem.dll

symclient\lib\libvem.dll

symclient\lib64\libvem400.dll

symclient\lib64\libvem400.pdb

symclient\lib\libvem400.dll

symclient\lib\libvem400.pdb

8. Product notifications

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.

9. Copyright and trademark information

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.