Platform LSFVersion 9 Release 1.2Using IBM Platform License Scheduler SC27-5308-02

Platform LSFVersion 9 Release 1.2Using IBM Platform License Scheduler SC27-5308-02

NoteBefore using this information and the product it supports, read the information in “Notices” on page 175.First editionThis edition applies to version 9, release 1, modification 2 of IBM Platform License Scheduler (product number5725G82) and to all subsequent releases and modifications until otherwise indicated in new editions.Significant changes or additions to the text and illustrations are indicated by a vertical line ( ) to the left of thechange.If you find an error in any Platform Computing documentation, or you have a suggestion for improving it, pleaselet us know. Send your suggestions, comments and questions to the following email address:[email protected] sure include the publication title and order number, and, if applicable, the specific location of the informationabout which you have comments (for example, a page number or a browser URL). When you send information toIBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriatewithout incurring any obligation to you. Copyright IBM Corporation 1992, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

ContentsChapter 1. Introduction . . . . . . . . 1Overview . . .Differences betweenGlossary . . . .Architecture . . . .License. . . . . . . . . . .Scheduler editions . . . . . . . . . . . . .1123Chapter 2. Installing and startingLicense Scheduler . . . . . . . . . . 7Install License Scheduler . . . .Start License Scheduler . . . .LSF parameters in License SchedulerAbout submitting jobs . . . . .After configuration changes . . .Add a cluster to License SchedulerConfigure multiple administrators .Upgrade License Scheduler . . .Firewalls . . . . . . . . . 7. 12. 13. 14. 14. 15. 15. 16. 17Chapter 3. License Scheduler concepts 19License Scheduler modes . . . . .Project groups . . . . . . . .Service domains in License SchedulerDistribution policies . . . . . .Project mode preemption . . . . .License usage with FlexNet . . . .192122242730Chapter 4. Configuring LicenseScheduler . . . . . . . . . . . . . 33Configure cluster mode . . . . . .Configure cluster mode with guarantees.Project mode with projects . . . . .Project mode optional settings . . . .Project mode with project groups . . . Copyright IBM Corp. 1992, 2013.3341445261Configure fast dispatch project mode .Automatic time-based configuration .Failover . . . . . . . . . .User authentication . . . . . . .65707380Chapter 5. Viewing information andtroubleshooting . . . . . . . . . . . 83About viewing available licenses .About error logs . . . . . . .Troubleshooting . . . . . . .Chapter 6. Referencelsf.licensescheduler .bladmin . . . .blcollect . . . .blcstat . . . . .blhosts . . . .blinfo . . . . .blkill . . . . .blparams . . . .blstat . . . . .bltasks. . . . .blusers . . . .fod.conf . . . .fodadmin. . . .fodapps . . . .fodhosts . . . .fodid . . . . .taskman . . . . 83. 85. 86. . . . . . . . 89. Notices . . . . . . . . . . . . . . 175Trademarks . . . . . . .Privacy policy considerations . 177. 177iii

ivUsing IBM Platform License Scheduler

Chapter 1. IntroductionOverviewApplying policies to how licenses are shared can have significant benefits both interms of productivity and cost savings.Share licenses more easilyIBM Platform License Scheduler (License Scheduler) makes it easy to share licensesbetween project teams and departments within the same design center or aroundthe globe. With tools to allocate and monitor licenses, license owners can sharelicenses not in use, while still ensuring immediate access to licenses when needed.With more effective sharing, all users perceive a larger pool of licenses.Ensure appropriate license allocationLicense Scheduler enables flexible, hierarchical sharing policies that reflect theneeds of the business. During quiet periods, when licenses are not in contention,licenses can be allocated to anyone who needs them keeping utilization andthroughput high. During busy periods, the supply of licenses can be allocatedbased on policy toward the most time or revenue critical projects.Improve service levels and productivityBy ensuring access to a minimum share of licenses and enabling allocation to flexbetween clusters that are based on need, licenses are more readily available andjobs are less likely to pend in queues that are awaiting license resources. Thistranslates into reduced wait times and better productivity, and contributes to afaster, more efficient design environment.Reduce or avoid costBy being able to allocate scarce licenses to the most critical projects, and by beingable to analyze license usage in the context of cluster resources, users and projects,planners are better able to find and remove bottlenecks, making their existinglicenses more productive. With better visibility to how licenses are being used, theycan plan license requirements more effectively ultimately helping to contain costsand boost productivity.License Scheduler controls the software license sharing in your organization.License Scheduler works with FlexNet products to control and monitor licenseusage.Differences between License Scheduler editionsLicense Scheduler is available in two editions: Basic Edition and Standard Edition.License Scheduler Basic Edition is included with LSF and is not intended to applypolicies on how licenses are shared between clusters or projects. Rather, LicenseScheduler Basic Edition is intended to replace an external load informationmanager (elim) to collect external load indicies for licenses managed by FlexNet.To replace this elim, License Scheduler Basic Edition limits the license use of jobs Copyright IBM Corp. 1992, 20131

Introductionof a single cluster to prevent overuse of the licenses and tracks license use ofindividual jobs by matching license checkouts to these jobs. License SchedulerBasic Edition provides cluster mode features distributed to a single cluster withone service domain per license feature.License Scheduler Standard Edition not only provides cluster mode features for asingle cluster, but also provides full License Scheduler functionality, includingsupport for all modes (cluster mode, project mode, and fast dispatch project mode),multiple clusters, features and feature groups, multiple service domains per licensefeature, and taskman jobs.Important: A License Scheduler entitlement file (ls.entitlement) is now requiredto run License Scheduler Standard Edition. Copy the entitlement file(ls.entitlement) to the LSF ENVDIR directory before starting License Scheduler torun as Standard Edition.To install and run License Scheduler Basic Edition, download and install theLicense Scheduler packages as described in “Install License Scheduler” on page 7,but follow any specific steps for installing and configuring License Scheduler BasicEdition instead of Standard Edition.License Scheduler Standard Edition is assumed in all License Schedulerdocumentation unless it is explicitly stated as describing License Scheduler BasicEdition.GlossaryblcollectThe License Scheduler daemon that queries FlexNet licensing software for licenseusage. blcollect collects information from lmstat.You can spread the load of license collection by running the license informationcollection daemon on multiple UNIX hosts.Also called the collector.bldThe License Scheduler batch daemon.cluster modeLicense tokens are allocated to clusters by License Scheduler, and job schedulingwithin each cluster is managed by the local mbatchd. Cluster mode is only availablefor License Scheduler version 8.0 and later.Each license feature can use either cluster mode or project mode, but not both.lmgrdThe main FlexNet licensing daemon. Usually grouped into service domains insideLicense Scheduler.2Using IBM Platform License Scheduler

Introductionproject modeLicense tokens are allocated to projects by License Scheduler, and job schedulingfor license projects takes place across clusters that follow the license distributionpolicy that is configured for each project. Corresponds to License Scheduler version7.0.5 and earlier.Each license feature can use either cluster mode or project mode, but not both.service domainA group of one or more FlexNet license servers.You configure the service domain with the license server names and port numbersthat serve licenses to a network.taskman jobA job that is run by theIBM Platform LSF (LSF) Task Manager (taskman) tooloutside of LSF, but is scheduled by License Scheduler.tokenOne license token represents one actual license, and is used by License Schedulerto track license use and determine which job to dispatch next.License Scheduler manages license tokens instead of controlling the licensesdirectly. After they reserve license tokens, jobs are dispatched, then the applicationthat needs the license is started. The number of tokens available from LSFcorresponds to the number of licenses available from FlexNet, so if a token is notavailable, the job is not dispatched.ArchitectureLicense Scheduler manages license tokens instead of controlling the licensesdirectly. Using License Scheduler, jobs receive a license token before starting theapplication. The number of tokens available from IBM Platform LSF (LSF)corresponds to the number of licenses available from FlexNet, so if a token is notavailable, the job does not start. In this way, the number of licenses that arerequested by running jobs does not exceed the number of available licenses.When a job starts, the application is not aware of License Scheduler. Theapplication checks out licenses from FlexNet in the usual manner.Chapter 1. Introduction3

IntroductionFigure 1. Daemon interactionHow scheduling policies workWith License Scheduler, LSF gathers information about the licensing requirementsof pending jobs to efficiently distribute available licenses. Other LSF schedulingpolicies are independent from License Scheduler policies.The basic LSF scheduling comes first when starting a job. License Scheduler has noinfluence on job scheduling priority. Jobs are considered for dispatch according tothe prioritization policies configured in each cluster.For example, a job must have a candidate LSF host on which to start before theLicense Scheduler fairshare policy (for the license project this job belongs to)applies.Other LSF fairshare policies are based on CPU time, run time, and usage. If LSFfairshare scheduling is configured, LSF determines which user or queue has thehighest priority, then considers other resources. In this way, the other LSF fairsharepolicies have priority over License Scheduler.When the mbatchd is offlineWhen a cluster is running, the mbatchd maintains a TCP connection to bld. Whenthe cluster is disconnected (such as when the cluster goes down or is restarted), thebld removes all information about jobs in the cluster. License Scheduler considerslicenses that are checked out by jobs in a disconnected cluster to be non-LSF use oflicenses.When mbatchd comes back online, the bld immediately receives updatedinformation about the number of tokens that are currently distributed to thecluster.4Using IBM Platform License Scheduler

IntroductionWhen the bld is offlineIf the mbatchd loses the connection with the bld, the mbatchd cannot get bld’s tokendistribution decisions to update its own.However, because the mbatchd logs token status every minute in LSF TOP/work/data/featureName.ServiceDomainName.dat file, if the connection islost, the mbatchd uses the last logged information to schedule jobs.f3.LanServer1.dat# f3 LanServer1 3 2# p1 50 p2 222200000000f3 on LanServer1 has three tokens and two projects. Projects p1 and p2 sharelicenses 50:50.At 14:27:55, the bld dispatched one token to p1, which has 0 in use, 1 free, 0reserve. At the same time, the bld dispatched two tokens to p2, which has 0 in use,2 free, and 0 reserve.The mbatchd continues to schedule jobs that are based on the token distributionthat is logged at 14:27:55 until the connection with the bld is re-established.Chapter 1. Introduction5

6Using IBM Platform License Scheduler

Chapter 2. Installing and starting License SchedulerInstall License Scheduler1. Perform the pre-installation steps.2. Choose an installation plan:v UNIX: License Scheduler manages licenses for jobs that run through LSF andthrough applications other than LSF.v Windows, in a mixed cluster:A Licenser Scheduler installation requires UNIX hosts to run the bld.Windows hosts in a mixed cluster can run License Scheduler commands.When you have License Scheduler UNIX hosts working with LSF, runLicense Scheduler on Windows hosts as well.Before you installIBM Platform LSF ("LSF") must be installed and running before you install LicenseScheduler.Log on to any LSF host as root and use lsid to make sure that the cluster isrunning. If you see the message "Cannot open lsf.conf file", verify that the LSF ENVDIR environment variable is set correctly.To set your LSF environment:v For csh or tcsh:% source LSF TOP/conf/cshrc.lsfv For sh, ksh, or bash: . LSF TOP/conf/profile.lsfWhat the License Scheduler setup script doesv Finds the appropriate lsf.conf for the running cluster.v Copies the License Scheduler files to your LSF directories:– LSF ENVDIR:- lsf.licensescheduler- ls.users– LSF SERVERDIR:- bld- blcollect- globauth- auth– LSF BINDIR:- blstat- blcstat Copyright IBM Corp. 1992, 2013blusersblinfobladminblstartupblhosts7

Installing and starting License Scheduler- blkill- bltasks- blparams- taskman– LSF LIBDIR:- libglb.a-– LSF MANDIR: various man pagesv Finds the appropriate lsf.cluster.cluster name file for the running cluster.v Creates the following additional directories:– LSB SHAREDIR/cluster name/db– LSB SHAREDIR/cluster name/datav Sets your License Scheduler administrators list in the lsf.licensescheduler file.v Configures LSF to use License Scheduler.Install License Scheduler with LSF (UNIX)You must have write access to the LSF TOP directories.1. Log on as root to the installation file server host.2. Download, uncompress, and extract the License Scheduler packages for theplatforms you need.For example, for x86 64-bit systems that run Linux kernel 2.6.x and compiledwith glibc 2.3.x:ftp get lsf9.1.2 licsched lnx26-libc23-x64.tar.ZMake sure that you download the License Scheduler distribution files to thesame directory where you downloaded the LSF product distribution tar files.3. Extract the distribution file.For example:# zcat lsf9.1.2 licsched lnx26-libc23-x64.tar.Z tar xvf 4. Change to the extracted distribution directory.For example:# cd lsf9.1.2 licsched linux2.6-glibc2.3-x86 645. Edit ./setup.config to specify the installation variables you want.Uncomment the options that you want in the template file, and replace theexample values with your own settings.Tip: The sample values in the setup.config template file are examples only.They are not default installation values.6. Run the setup script as root:# ./setup7. Enter y (yes) to confirm that the path to lsf.conf is correct.To enter a path to a different lsf.conf, type n (no) and specify the full path tothe lsf.conf file you want to use.8. Enter y to confirm that the path to lsf.cluster.cluster name is correct.To enter a path to a different lsf.cluster.cluster name file, type n (no) andspecify the full path to the lsf.cluster.cluster name file you want to use.8Using IBM Platform License Scheduler

Installing and starting License Scheduler9. Enter y to confirm that you want to use the LSF Administrators list forLicense Scheduler with LSF.To enter a different list of administrators for License Scheduler, enter aspace-separated list of administrator user names. You can change your LicenseScheduler administrators list later, if necessary.10. If you are installing License Scheduler Standard Edition, copy the LicenseScheduler entitlement file (ls.entitlement) to the LSF ENVDIR directory.If you do not copy the entitlement file to LSF ENVDIR before starting LicenseScheduler, License Scheduler runs as Basic Edition.If you are installing License Scheduler Basic Edition, configure License SchedulerBasic Edition and LSF as described in “Configure License Scheduler Basic Edition”on page 10.Install License Scheduler on WindowsYou can install License Scheduler on Windows hosts when your cluster includesboth Windows and UNIX hosts.The License Scheduler Windows Client package includes:v READMEv Commands:– blstat.exe– n.exeblhosts.exe– blkill.exe– bltasks.exe– blparams.exe– taskman.exev lsf.licensescheduler: License Scheduler configuration filev lsf.conf: LSF configuration fileInstall License Scheduler with LSF (Windows)You must already have LSF installed on all Windows hosts you intend to installLicense Scheduler on.This installation option means that License Scheduler manages licenses for jobsthat are submitted through LSF and through any other applications.Install License Scheduler on Windows hosts only when your LSF cluster includesboth UNIX and Windows hosts.1. Download the License Scheduler Client for Windows package.2. Copy all commands to LSF BINDIR (the bin subdirectory in your LSFinstallation directory) on your Windows hosts.3. Copy lsf.licensescheduler to LSF ENVDIR.4. Edit lsf.licensescheduler to suit your License Scheduler Master hostconfiguration.Chapter 2. Installing and starting License Scheduler9

Installing and starting License SchedulerTroubleshoot1. If you receive the following message, configure your Windows host name andIP address in the /etc/hosts file on the master host:Failed in an LSF library call: Failed in sending/receiving a message:error 0: The operation completed successfully.2. To enable the blhosts command, make sure that your Windows host canresolve the master host IP address correctly.Configure License Scheduler Basic EditionConfigure LSF and License Scheduler Basic Edition.Configuring License Scheduler Basic Edition and LSFConfigure LSF to use License Scheduler Basic Edition as a replacement for an elimto collect external load indices where the external resources are licenses managedby FlexNet.The following example assumes that LSF cluster named cluster1 uses an elim fora license resource named f1.1. In the LSF environment, disable the existing elim for the license resource byremoving the license feature configuration from the lsf.shared andlsf.cluster.cluster name files.For example, remove the configuration for f1 from the lsf.shared andlsf.cluster.cluster name files.2. Configure the lsf.licenscheduler file with the appropriate hosts and thelicense feature.For example, configure the following sections in lsf.licenscheduler:Begin ParametersPORT 1700HOSTS hostAADMIN lsadminLM STAT INTERVAL 15LMSTAT PATH /usr/binEnd ParametersBegin ClustersCLUSTERScluster1End ClustersBegin ServiceDomainNAME LanServerLIC SERVERS (([email protected]))End ServiceDomainBegin FeatureNAME f1CLUSTER MODE YCLUSTER DISTRIBUTION LanServer(cluster1)End Feature3. Start License Scheduler and LSF.For more details, refer to “Start License Scheduler” on page 12.From LSF, use bsub to submit a job without a duration requesting the f1 resource.For example,bsub -R "rusage[f1 1]" myjob -f "f1 1" -c [email protected] -t 2000010Using IBM Platform License Scheduler

Installing and starting License SchedulerUpgrading from License Scheduler Basic Edition to StandardEditionIf you use License Scheduler Basic Edition and wish to upgrade to LicenseScheduler Standard Edition, obtain the License Scheduler entitlement file, thenupgrade License Scheduler as follows:1. Copy the License Scheduler entitlement file (ls.entitlement) to the LSF ENVDIRdirectory.2. Restart License Scheduler.bladmin reconfig3. Restart the mbatchd on the LSF master host.badmin mbdrestartSupported parameters for License Scheduler Basic EditionThe following is a list of specific lsf.licensescheduler parameters that LicenseScheduler Basic Edition supports:v Parameters section:– ADMIN– CLUSTER MODE (License Scheduler Basic Edition only supportsCLUSTER MODE Y)– HEARTBEAT INTERVAL– HEARTBEAT TIMEOUT– HOSTS– LIB CONNTIMEOUT– LIB RECVTIMEOUT– LM STAT INTERVAL– LM STAT TIMEOUT–––––LMSTAT PATHLOG EVENTLOG INTERVALLS DEBUG BLCLS DEBUG BLD– LS DEBUG CMD– LS LOG MASK–––––LS MAX STREAM FILE NUMBERLS MAX STREAM SIZELS STREAM SIZELS STREAM FILEMBD HEARTBEAT INTERVAL– MBD REFRESH INTERVAL– STANDBY CONNTIMEOUT– BLC HEARTBEAT FACTORv Clusters section:– CLUSTERS (one cluster only, License Scheduler Basic Edition ignoresadditional clusters)v ServiceDomain section (one ServiceDomain section per license feature only,License Scheduler Basic Edition ignores additional ServiceDomain sections in thesame license feature):Chapter 2. Installing and starting License Scheduler11

Installing and starting License Scheduler–––––NAMELIC SERVERSLM STAT INTERVALLM STAT TIMEOUTLIC COLLECTORv Feature section:– NAME– CLUSTER MODE (Optional. This parameter may be specified in theParameters section instead, but License Scheduler Basic Edition only supportsCLUSTER MODE Y)– FLEX NAME (Optional. License Scheduler Basic Edition does not support thespecification of multiple FlexNet feature names to combine into a single alias)– CLUSTER DISTRIBUTION (License Scheduler Basic Edition supports a singlecluster with a single service domain only, and ignores any additional clustersor service domains).– LIC COLLECTORTip: A specific lsf.licensescheduler configuration template for License SchedulerBasic Edition is available and contains specifications for all supported parameters.This file is named lsf.licensescheduler.basic and is included in the LicenseScheduler installation package. License Scheduler uses the Standard Editionconfiguration file by default, but License Scheduler Basic Edition ignoresunsupported Standard Edition parameters with a warning message. To ensure thatLicense Scheduler Basic Edition uses only supported parameters and to prevent thelogging of the warning messages, back up the lsf.licensescheduler configurationfile, then move the lsf.licensescheduler.basic file to the LSF ENVDIR directoryand rename it to lsf.licensescheduler.Start License SchedulerYou can configure LSF to start the License Scheduler daemon (bld) on the LicenseScheduler host as well as on candidate License Scheduler hosts that can take overlicense distribution in the case of a network failure. The LSF LIM daemon startsbld automatically.1. Log on as the primary LSF administrator.2. Set your LSF environment:v For csh or tcsh:% source LSF TOP/conf/cshrc.lsfv For sh, ksh, or bash: . LSF TOP/conf/profile.lsf3. In LSF CONFDIR/lsf.conf, specify a space-separated list of hosts for theLSF LIC SCHED HOSTS parameters:LSF LIC SCHED HOSTS "hostname 1 hostname 2 . hostname n"Where:hostname 1, hostname 2, hostname n are hosts on which the LSF LIM daemonstarts the License Scheduler daemon. The order of the host names is ignored.Note: Set the LSF LIC SCHED HOSTS parameter to the same list of candidatehosts you used in the lsf.licensescheduler HOSTS parameter. TheLSF LIC SCHED HOSTS parameter is not used in any other function.4. Run lsadmin reconfig to reconfigure the LIM.12Using IBM Platform License Scheduler

Installing and starting License Scheduler5. Use ps -ef to make sure that bld is running on the candidate hosts.6. Run badmin mbdrestart to restart mbatchd.7. If you specified a LIC COLLECTOR name in your service domains, start eachlicense collector manually:blcollect -m "host list" -p lic scheduler port -c lic collector nameWhere:v host listSpecifies a space-separated list of License Scheduler candidate hosts to whichlicense information is sent. Use fully qualified host names.v lic scheduler portCorresponds to the License Scheduler listening port, which is set inlsf.licensescheduler.v lic collector nameSpecifies the name of the license collector you set for LIC COLLECTOR in theservice domain section of lsf.licensescheduler.For example:blcollect -m "hostD.designcenter hostA.designcenter"-p 9581 -c CenterBA file named collectors/CenterB is created in your LSF WORKDIR.Note:If you do not specify a license collector name in a License Scheduler servicedomain, the master bld host starts a default blcollect.LSF parameters in License SchedulerParameters in lsf.conf that start with LSF LIC SCHED are relevant to both LSFand License Scheduler:v LSF LIC SCHED HOSTS: LIM starts the License Scheduler daemon (bld) oncandidate License Scheduler hosts. CAUTION:You cannot use LSF LIC SCHED HOSTS if your cluster was installed withUNIFORM DIRECTORY PATH or UNIFORM DIRECTORY PATH EGO. Donot set UNIFORM DIRECTORY PATH orUNIFORM DIRECTORY PATH EGO for new or upgrade installations. Theyare for compatibility with earlier versions only.v LSF LIC SCHED PREEMPT REQUEUE: Requeues a job whose license is preempted byLicense Scheduler. The job is killed and requeued instead of suspended.v LSF LIC SCHED PREEMPT SLOT RELEASE: Releases memory and slot resources of aLicense Scheduler job that is suspended. These resources are only available topending License Scheduler jobs that request at least one license that is the sameas the suspended job.Job slots are released by default, but memory resources are also released ifmemory preemption is enabled (that is, PREEMPTABLE RESOURCES mem is set inlsb.params).v LSF LIC SCHED PREEMPT STOP: Uses job controls to stop a job that is preempted.When this parameter is set, a UNIX SIGSTOP signal is sent to suspend a jobinstead of a UNIX SIGTSTP.Chapter 2. Installing and starting License Scheduler13

Installing and starting License Schedulerv LSF LIC SCHED STRICT PROJECT NAME: Enforces strict checking of the LicenseScheduler project name upon job submission. If the project named is misspelled(case sensitivity applies), the job is rejected.LSF parameters used by License Schedulerv LSB SHAREDIR: Directory where the job history and accounting logs are kept foreach clusterv LSF LOG MASK: Logging level of error messages for LSF daemonsv LSF LOGDIR: LSF system log file directoryAbout submitting jobsWhen you submit an LSF job, you must reserve the license with the resourcerequirement usage section (bsub -R "rusage." option).Tip:You cannot successfully reserve a license by running bsub -R "select".v Specify the license token name (same as specifying a shared resource).v If you use project mode, specify a license project name with the bsub -Lp option.If you also have LSF LIC SCHED STRICT PROJECT NAME y in lsf.conf andwithout configuring a default project for the required feature, the job is rejected.Tip:Use the blstat command to view information about the default license project.v Update resource requirements.If your queue or job starter scripts request a license that is managed by an LSFELIM, you must update the job submission scripts to request that license thatuses the license token name.Examples:bsub -R "rusage[AppB 1]" -Lp Lp1 myjobThis command submits a job named myjob to license project Lp1 and requests oneAppB licensebsub -R "rusage[AppC 1]" myjobThis command submits a job named myjob and requests one AppC license.After configuration changesIf you make configuration changes to License Scheduler, you must reconfigureLicense Scheduler to apply the changes. If you make configuration changes to LSF,you must also reconfigure LSF.1. Run bld -C to test for configuration errors.2. Run bladmin reconfig all.3. If you changed lsf.conf or other LSF configuration files, run badminmbdrestart and lsadmin reconfig.Note:14Using IBM Platform License Scheduler

Installing and starting License SchedulerAfter certain License Scheduler configuration changes, you must runbadmin mbdrestart for the changes to take effect. The following configurationchanges require you to run badmin mbdrestart:v Project changes, additions, or deletionsv Feature changes, additions, or deletions, including mode changesv Cluster locations changesYou must also run lsadmin reconfig for any changes to the LIM to take effect(for example, if you changed LSF LIC SCHED HOSTS).Add a cluster to License SchedulerYou must be a License Scheduler administrator.You can add a new cluster to an existing License Scheduler implementation.1. Download the License Scheduler package.Note: Acquire the same version of master bld binary files and otherarchitectures that are used in existing member clusters.2. Install the License Scheduler package on the new cluster.3. Use an existing lsf.licensescheduler from LSF ENVDIR of another clusterwith the same bld master.4. Add new cluster name to the Clusters section of lsf.licensescheduler.5. Add or modify license distribution policies that are defined inlsf.licensescheduler.6. Maintain one central lsf.licensescheduler file and have all the clusters accessit.Remember:The lsf.licensescheduler file in each cluster must be identical.You can accomplish this using either of the following methods:v Create a symbolic link from each cluster’s LSF ENVDIR to the centrallsf.licensescheduler file.v Use a CRON-based synchronization script to synchronize the changes thatare made from the central lsf.licensescheduler file to the correspondinglsf.licensescheduler files in all the clusters.7. Check that there is no firewall or network is

The number of tokens available from IBM Platform LSF (LSF) corresponds to the number of licenses available from FlexNet, so if a token is not available, the job does not start. In this way, the number of licenses that are requested by runni