Readme File for IBM?/sup> Spectrum Symphony RFE 141850

Readme file for: IBM Spectrum Symphony

Product release: 7.2.0.2

Fix ID: sym-7.2.0.2_build546013-ms

Publication date: May 1, 2020

 

RFE 141850 replaces RFE 139578. This enhancement updates the priority scheduling policy to limit the number of service instances assigned to a session based on the maxServices sessionType parameter defined in the application profile or the session creation attribute using the API. Without this maxServices parameter, the highest priority session would be assigned all service instances available to the application while the highest priority session has enough tasks. The policy will avoid over-allocating slots if they cannot be used by an active session. The minServices sessionType parameter will be ignored if specified. This will allow higher priority sessions to get slots from lower priority sessions submitted previously. This feature is enabled using the SSM_ENABLE_PRIORITY_SCHEDULING_MAX_SERVICES control parameter.

 

Contents

1.       Scope

2.       Installation

3.       Configuration and usage

4.       Uninstallation

5.       Product notifications

6.       Copyright and trademark information

 

1.   Scope

Before you install this enhancement to your cluster, note the following requirements:

Operating system

RHEL 6 64-bit

Product version

IBM Spectrum Symphony 7.2.0.2

2.   Installation

Follow these instructions to download and install this enhancement on Linux management hosts in your cluster.

Package

Name

Description

sym-7.2.0.2_x86_64_build546013.tar.gz

Package for Linux management hosts.

Installation

a.        Log on to the master host as the cluster administrator and disable all applications:

> egosh user logon -u Admin -x Admin

> soamcontrol app disable all -f

b.        Log on to each management host and back up the following binary file:

$EGO_TOP/soam/7.2/linux-x86_64/etc/ssm

c.        On each management host, copy the sym-7.2.0.2_x86_64_build546013.tar.gz package and decompress it to the $EGO_TOP directory:

> tar zxof sym-7.2.0.2_x86_64_build546013.tar.gz -C $EGO_TOP

d.        Verify the installation:

> ssm -V

IBM Spectrum Symphony 7.2 build 546013, Apr 28 2020

e.        From a management host, enable your applications:

> soamcontrol app enable appName

3.   Configuration and usage

After you have applied this enhancement, enable the priority scheduling policy and define the maxServices configuration in the application profile.

The application profile can be modified using a text editor or using the cluster management console.

1.      To enable the priority scheduling policy, set the following parameter in the Consumer section of the application profile:
policy="R_PriorityScheduling"

2.      Add the SSM_ENABLE_PRIORITY_SCHEDULING_MAX_SERVICES environment variable to the SSM section:

     ?/span><SSM resReq="" shutDownTimeout="300" startUpTimeout="60" workDir="${EGO_SHARED_TOP}/soam/work">

    ?    <osTypes>

           <osType name="all">

            ?    <env name="SSM_ENABLE_PRIORITY_SCHEDULING_MAX_SERVICES">Y</env>?    ?

            ?</osType>        ?

?  ??/span></osTypes>

3.      To define the maxServices value, add the maxServices attribute to the sessionType section:

<Type name="mySessionType" priority="1" recoverable="false" maxServices="3" preemptive="false"/>

4.      To define the maxServices parameter using the API, use the SessionCreationAttributes object. This value will override the value set in the application profile.

void setMaxServices (const SoamInt32 numOfServices) throw (SoamException)

Sets the maximum number of service instances that this session will demand and receive. The maxServices attribute is applicable only when the R_MinimumServices or R_PriorityScheduling scheduling policy is used. This allows you to cap the number of resources that a session can use. The value must be greater than or equal to the value of minimum services. The R_PriorityScheduling policy ignores the minimum services configuration.

Parameters:

numOfServices [IN] - The number of maximum services.

Exceptions:

   SoamException

 

4.   Uninstallation?

Follow these instructions to uninstall this enhancement from management hosts in your cluster, if required:

a.      Log on to the master host as the cluster administrator and disable all applications:

> egosh user logon -u Admin -x Admin

> soamcontrol app disable all -f

b.        On each management host, restore the following file from your backup:

$EGO_TOP/soam/7.2/linux-x86_64/etc/ssm

c.        From a management host, enable your applications:

> soamcontrol app enable appName

5.   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. ?/span>

6.   Copyright and trademark information

?Copyright IBM Corporation 2020

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. ?/span>