<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:readme="urn:com:ibm:fmt:readmetemplate">
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">

<script type="text/javascript" language="JavaScript1.2">
<!-- 
function _dSectionExpand(imageElementID,textElemenetID) {
	if( document.getElementById(imageElementID) != null && document.getElementById(textElemenetID) != null ) {
   		document.getElementById(imageElementID).style.display = "none";
   		document.getElementById(textElemenetID).style.display = "";
    }
}
function _dSectionCollapse(imageElementID,textElemenetID) {
	if( document.getElementById(imageElementID) != null && document.getElementById(textElemenetID) != null ) {
   		document.getElementById(textElemenetID).style.display = "none";
   		document.getElementById(imageElementID).style.display = "";
   	}
}
// -->
</script>
 </head>
<body onload="_dSectionCollapse();">
<a name="Top_Of_Page" id="Top_Of_Page"></a>
<h1>Readme and Release notes for release 4.1.1.5 (LL) IBM Tivoli Workload Scheduler LoadLeveler 4.1.1.5 LL_scheduler-4.1.1.5-x86-Linux-RHEL5 Readme</h1>
<p>
<b>Readme file for:</b>LL_scheduler-4.1.1.5-x86-Linux-RHEL5<br>
<b>Product/Component Release:</b>4.1.1.5<br>
<b>Update Name:</b>LL_scheduler-4.1.1.5-x86-Linux-RHEL5<br>
<b>Fix ID:</b>LL_scheduler-4.1.1.5-x86-Linux-RHEL5<br>
<b>Publication Date:</b>28 July 2011<br>
<b>Last modified date:</b>28 July 2011<br>
<br>
<b>Online version of the readme file:</b><a href="http://www-01.ibm.com/support/docview.wss?rs=0&uid=isg400000671">http://www-01.ibm.com/support/docview.wss?rs=0&amp;uid=isg400000671</a>
<br>
<b>Important</b>: The most current version of the readme file can always be found online.<br>
</p>
<font size="4"><b>Contents</b></font>
<br>
<br>
<a href="#Download location" class="fbox">Download location</a>
<br>
<a href="#Prerequisites and co-requisites" class="fbox">Prerequisites and co-requisites</a>
<br>
<a href="#Known issues" class="fbox">Known issues</a>
<br>
<a href="#Known limitations" class="fbox">Known limitations</a>
<br>
<br>
<b>Installation information</b>
<br>
<br>
<a href="#Additional information" class="fbox">Additional information</a>
<br>
<a href="#Copyright and trademark information" class="fbox">Copyright and trademark information</a>
<br>
<br>
<! ##################################################################################### --> <br>
<br>
<a name="Download location"><font size="4"><b>Download location</b></font></a>
<br>
<br>
<p>Below is a list of components, platforms, and file names that apply to this Readme file.<br>
<br>
</p>
<span id="imageElementLinux" style="position:relative; display:none;"><a onclick="return _dSectionExpand(&quot;imageElementLinux&quot;,&quot;textElementLinux&quot;);">
                
				<img src="http://www-01.ibm.com/support/docview.wss?uid=swg24018266&aid=2" border="0" alt="" ></img>
			     <b>Fix Download for Linux</b></a></span><span id="textElementLinux" style="position:relative"><a onclick="return _dSectionCollapse(&quot;imageElementLinux&quot;,&quot;textElementLinux&quot;);">
                
				<img src="http://www-01.ibm.com/support/docview.wss?uid=swg24018266&aid=3" border="0" alt="" ></img>
			     <b>Fix Download for Linux</b></a>
<table cellspacing="0" cellpadding="0" width="600" style="background-color:FFFFFF" bordercolor="000000" border="1">
<br>
<tr>
<td><b>Product/Component Name:</b></td><td><b>Platform:</b></td><td><b>Fix:</b></td>
</tr>
<tr>
<td>(LL) IBM Tivoli Workload Scheduler LoadLeveler</td><td>Linux 32-bit,x86 RHEL 5<BR/></td><td><a href="http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/power/IBM+Tivoli+Workload+Scheduler+LoadLeveler&function=fixid&fixids=LL_scheduler-4.1.1.5-x86-Linux-RHEL5">LL_scheduler-4.1.1.5-x86-Linux-RHEL5</a></td>
</tr>
</table>
</span>
<br>
<br>
<br>
<br>
<br>
<a name="Prerequisites and co-requisites"><font size="4"><b>Prerequisites and co-requisites</b></font></a>
<br>
<br>
None
	  <br>
<br>
<a name="Known issues"><font size="4"><b>Known issues</b></font></a>
<br>
<br><!-- BASIC TWISTY SHOW/HIDE -->
<div class="ibm-container ibm-alternate">
<div class="ibm-container-body">
<ul class="ibm-twisty">
<li>
<a class="ibm-twisty-trigger" href="#toggle"><img alt="-" src="//www.ibm.com/i/c.gif" /></a>
<span class="ibm-twisty-head"><b>Known Issues</b>
</span>
<div class="ibm-twisty-body">

<div>
<p>For known issues, please see the HPC Central wiki:</p>
</div>
<div class="ibm-indent">
<p><a href="http://www.ibm.com/developerworks/wikis/display/hpccentral/Tivoli+Workload+Scheduler+LoadLeveler" target=new.window>
http://www.ibm.com/developerworks/wikis/display/hpccentral/Tivoli+Workload+Scheduler+LoadLeveler</a>
</p>
</div>


</div>
</li>
</ul>
</div>
</div>
<br>
<br>
<a name="Known limitations"><font size="4"><b>Known limitations</b></font></a>
<br>
<br><!-- BASIC TWISTY SHOW/HIDE -->
<div class="ibm-container ibm-alternate">
<div class="ibm-container-body">
<ul class="ibm-twisty">
<li>
<a class="ibm-twisty-trigger" href="#toggle"><img alt="-" src="//www.ibm.com/i/c.gif" /></a>
<span class="ibm-twisty-head"><b>Known Limitations</b>
</span>
<div class="ibm-twisty-body">

<p><b>For LL 4.1.1:</b></p>
<ul class="ibm-bullet-list">
<li>On any machine where you plan to install the scheduler rpm, you must install the resource manager rpm and the resource manager rpm must be installed before the scheduler rpm.</li>
<li>If the scheduler and resource manager filesets are installed on the same machine, then the LoadLeveler version of those filesets have to be at the same level in order for transactions to be processed correctly.</li>
</ul>
 
<br/>
 
</div>
</li>
</ul>
</div>
</div>
<br>
<br>
<a name="Installation information"><font size="4"><b>Installation information</b></font></a>
<br>
<br><div class="ibm-container-body">     
<p>Use these instructions to install the LoadLeveler update RPMs on IBM Systems running supported versions of Red Hat Enterprise Linux and SUSE Linux Enterprise Server.</p>
<div class="ibm-rule"><hr/></div>


<!-- BASIC TWISTY SHOW/HIDE -->
<div class="ibm-container ibm-alternate">
<div class="ibm-container-body">
<ul class="ibm-twisty">
<li>
<a class="ibm-twisty-trigger" href="#toggle"><img alt="-" src="//www.ibm.com/i/c.gif" /></a>
<span class="ibm-twisty-head"><b>Read-me-first installation notes</b>
</span>
<div class="ibm-twisty-body">

<div class="ibm-container">
<div class="ibm-container-body">
<p>
This installation procedure assumes that you are updating a machine running the full version of LoadLeveler.</p>
 
<p><b>License RPM</b></p>
<p>Do not proceed if the  LoadL-full-license- &lt OS-ARCH &gt - &lt installed_license_version &gt license package is not installed. For example, if you are currently running LoadLeveler 3.5.x for Linux, you cannot install an update for LoadLeveler 4.1.x. You must first upgrade to LoadLeveler 4.1.0.5-0 before you can install an update package for a 4.1.0.X-0 release.  Please contact your IBM marketing representative for information on how to obtain the appropriate LoadLeveler CD-ROM that has the license package.</p>
 
<p>If you are installing a mod level (point release), you can use either the current license or the mod level license. For example, if you are installing LoadLeveler 3.5.1.0, you can use either the LoadLeveler 3.5.0.0 or the LoadLeveler 3.5.1.0 license package.
</p>
 
<p>When uninstalling the "LoadL- &lt fileset &gt -full" RPM currently installed on your machine, <u>do not</u> uninstall the "LoadL-full-license" RPM for your currently installed LoadLeveler release. The "LoadL- &lt fileset &gt -full" update RPM has a dependency on the currently installed license RPM. Also, the LoadLeveler daemons will not start unless the license package is installed and you have accepted the terms and conditions of the license agreement.</p>

<p><b>Submit-only machines</b></p>
<p>The update steps for a LoadLeveler submit-only machine are similar to those associated with a machine running the full product. Simply replace the relevant "full" file names by their "so" counterparts.  Also, on a submit-only machine there is no need to execute the <b>llctl drain</b>, <b>llctl stop</b>, or <b>llctl start</b> commands because LoadLeveler daemons do not run on a submit-only machine.</p>
 
<p><b>File name conventions</b></p>
<p>Download packages and RPMs for LoadLeveler updates use consistent file naming conventions. By looking at the components of the file name, you can determine which update package you will need to download based on the machine's architecture, Linux operating system, and the installed version of LoadLeveler.</p>
 
<p class="ibm-list-next"><i>Example</i></p>
<div class="ibm-indent"><p>If your System p (POWER server) is running scheduler and resource manager SLES11 with LoadLeveler 4.1.0.5-0 installed, and you want to download and install the LoadLeveler 4.1.0.6-0 update, then the file name components would be as follows:</p>
</div>
<p class="ibm-list-next">Download package:</p>
<div class="ibm-indent"><p><b>LoadL-</b> &lt update_version &gt <b>.</b> &lt OS-ARCH &gt <b>.</b> &lt base_version &gt <b>.tar.gz</b><br/>
 
Specifies the LoadL-scheduler-4.1.0.6-0.SLES11-PPC64.4.1.X.tar.gz file<br/>
Specifies the LoadL-resmgr-4.1.0.6-0.SLES11-PPC64-4.1.X.tar.gz file</p>
</div>

<p class="ibm-list-next">Package RPMs:</p>
<div class="ibm-indent"><p><b>LoadL- &lt fileset &gt -full-</b> &lt OS-ARCH &gt <b>-</b> &lt update_version &gt <b>.</b> &lt arch &gt <b>.rpm</b><br/>
Specifies the LoadL-scheduler-full-SLES11-PPC64-4.1.0.6-0.ppc64.rpm file<br/>
Specifies the LoadL-resmgr-full-SLES11-PPC64-4.1.0.6-0.ppc64.rpm file</p>
 
<p><b>LoadL-scheduler-so-</b> &lt OS-ARCH &gt <b>-</b> &lt update_version &gt <b>.</b> &lt arch &gt <b>.rpm</b><br/>
Specifies the LoadL-scheduler-so-SLES11-PPC64-4.1.0.6-0.ppc64.rpm file</p>
 
<p><b>LoadL-utils-</b> &lt OS-ARCH &gt <b>-</b> &lt update_version &gt <b>.</b> &lt arch &gt <b>.rpm</b><br/>
Specifies the LoadL-utils-SLES11-PPC64-4.1.0.6-0.ppc64.rpm file</p>
</div>
 
 
 
<p class="ibm-list-next">Currently installed LoadLeveler and License RPMs:</p>
 
<div class="ibm-indent"><p><b>LoadL- &lt fileset &gt -</b> &lt OS-ARCH &gt <b>-</b> &lt currently_installed_version &gt <br/>
Specifies that LoadL-scheduler-full-SLES11-PC64-4.1.0.5-0 is installed<br/>
Specifies that  LoadL-resmgr-full-SLES11-PPC64-4.1.0.5-0 is installed</p>
 
<p><b>LoadL-full-license-</b> &lt OS-ARCH &gt <b>-</b> &lt installed_license_version &gt <br/>
Specifies the LoadL-full-license-SLES11-PPC64-4.1.0.5-0 license</p>
</div>
 
<p class="ibm-list-next">where</p>
 
<p class="ibm-list-next"> &lt fileset &gt </p>
<div class="ibm-indent"><p>The LoadLeveler scheduler or resource manager fileset.</p>
</div>
 
<p class="ibm-list-next"> &lt OS-ARCH &gt </p>
<div class="ibm-indent"><p>The Linux Operating System and platform architecture of the machine where you are installing a LoadLeveler update package. For example, if you are upgrading an installation of LoadLeveler on a PowerPC 64 machine running SLES11, then &lt OS-ARCH &gt would be SLES11-PPC64.</p>
</div>
 
<p class="ibm-list-next"> &lt update_version&gt </p>
<div class="ibm-indent"><p>Specifies the version number of the LoadLeveler update package that you want to install on your system. For example, if you are updating to LoadLeveler 4.1.0.6-0, then the &lt update_version &gt is the number 4.1.0.6-0. The &lt update_version &gt appears in the file name of the package download (*.tar.gz file) and in the update RPMs in the package.</p>
</div>
 
<p class="ibm-list-next"> &lt arch &gt </p>
<div class="ibm-indent"><p>Used in RPM file names. Specifies the platform architecture, where &lt arch &gt =<br />
<b>i386</b> (32-bit IBM System x),<br />
<b>x86_64</b> (64-bit IBM System x) or <br />
<b>ppc64</b> (64-bit IBM System p)</p>
</div>
 
<p class="ibm-list-next"> &lt base_version &gt </p>
<div class="ibm-indent"><p>Used only in the file name of the downloadable update package (gzipped tar file). Specifies the LoadLeveler Version/Release to which the update can be applied, for example, 4.1.X.</p>
</div>
 
<p class="ibm-list-next"> &lt currently_installed_version &gt </p>
<div class="ibm-indent"><p>Specifies the version number of the current LoadLeveler release installed on your system.</p>
</div>
 
<p class="ibm-list-next"> &lt installed_license_version &gt </p>
<div class="ibm-indent"><p>Specifices the license RPM for the base release (or a lower release) of the LoadLeveler version you are updating. For example, to install the a LoadLeveler 3.5.1.6 update, you must have an installed license RPM for LoadLeveler 3.5.0.0 (base version) or 3.5.1.x.</p>
</div>
 
</div>
</li>
</ul>
</div>
</div>


<!-- BASIC TWISTY SHOW/HIDE -->
<div class="ibm-container ibm-alternate">
<div class="ibm-container-body">
<ul class="ibm-twisty">
<li>
<a class="ibm-twisty-trigger" href="#toggle"><img alt="-" src="//www.ibm.com/i/c.gif" /></a>
<span class="ibm-twisty-head"><b>Installation procedure</b>
</span>
<div class="ibm-twisty-body">

<div class="ibm-container">
<div class="ibm-container-body">

<ol>
<li>Change to the &lt UpdateDirectory &gt directory, that is, the directory where the *.tar.gz file for the LoadLeveler update resides and where you have write access:<br/><br/>
<b>cd &lt UpdateDirectory &gt </b></li>
 
<li>Extract the RPM files from the tar file:<br/><br/>
<b>tar -xzvf LoadL- &lt fileset &gt - &lt update_version &gt . &lt OS-ARCH &gt . &lt base_version &gt .tar.gz</b>
<br/><br/>
At the end of this step the files extracted from the archive should match the files listed in the Readme ("View" link) for the LoadLeveler update you downloaded.</li>
<li>Verify that the LoadLeveler "license" RPM for the LoadLeveler version that you are updating is currently installed on this system:<br/><br/>
<b>rpm -qa | grep LoadL</b>
<br/><br/>
The output of this command should be similar to the following:<br/><br/>
<b>
LoadL- &lt fileset &gt -full- &lt OS-ARCH &gt - &lt currently_installed_version &gt <br/>
LoadL-full-license- &lt OS-ARCH &gt - &lt installed_license_version &gt
</b>
</li>
 
<li>If LoadLeveler resource manager fileset is running on this machine, enter the following command to "drain" the <b>LoadL_schedd</b> and <b>LoadL_startd</b> daemons on this machine and all other machines in the LoadLeveler cluster:
<br/><br/>
<b>llctl -g drain</b>
<br/><br/>
<b>Note:</b> To avoid potential incompatibility problems, all machines
in the cluster should be upgraded to the same LoadLeveler update release before
restarting the LoadLeveler daemons.
</li>
 
<li>Use the <b>llstatus</b> command to verify that the <b>LoadL_schedd</b> and
<b>LoadL_startd</b> daemons are in "Drned" (drained) state, and then enter the following command to stop the LoadLeveler daemons:<br/><br/>
<b>llctl -g stop</b></li>
 
<li>To apply the update, use one of the following options:
<br/><br/>
<b>OPTION 1</b><br/><br/>
Uninstall the currently installed "LoadL- &lt fileset &gt -full" RPM and then install the "LoadL- &lt fileset &gt -full" update package by running the following commands:<br/><br/>
<b>rpm -e LoadL- &lt fileset &gt -full- &lt OS-ARCH &gt - &lt currently_installed_version &gt </b><br/>
<b>rpm -ivh LoadL- &lt fileset &gt -full- &lt OS-ARCH &gt - &lt update_version &gt . &lt arch &gt .rpm</b>
<br/><br/><br/>
<!--  
<b>For&nbsp;Blue&nbsp;Gene/L&nbsp;or&nbsp;Parallel&nbsp;POE&nbsp;only</b><br/><br/>
Run these additional commands:<br/>
<b>rpm -e LoadL-full-lib- &lt OS-ARCH &gt - &lt currently_installed_version &gt </b><br/>
<b>rpm -ivh LoadL-full-lib- &lt OS-ARCH &gt - &lt update_version &gt . &lt arch &gt .rpm</b>
<br/><br/><br/>
-->
<b>OPTION 2</b>
<br/><br/>
Use the -U option of the rpm command to apply the update directly:<br/><br/>
<b>rpm -Uvh LoadL- &lt fileset &gt -full- &lt OS-ARCH &gt - &lt update_version &gt . &lt arch &gt .rpm</b><br/><br/><br/>
<!--  
<b>For&nbsp;Blue&nbsp;Gene/L&nbsp;or&nbsp;Parallel&nbsp;POE&nbsp;only</b><br/><br/>
Run this additional command:<br/>
<b>rpm -Uvh LoadL-full-lib- &lt OS-ARCH &gt - &lt update_version &gt . &lt arch &gt .rpm</b>
-->
</li>
 
<li>Repeat step 6 for all the machines in the LoadLeveler cluster. On completion
of this task, restart the LoadLeveler daemons with the following command:<br/><br/>
<b>llctl -g start</b>
</li>
</ol>
 
<p>For further information, consult the <a href=http://publib.boulder.ibm.com/infocenter/clresctr/vxrx/index.jsp?topic=/com.ibm.cluster.loadl.doc/llbooks.html>LoadLeveler Library</a> for the appropriate version of the LoadLeveler AIX 6L, AIX 5L and Linux Installation Guide.</p>

</div>
</div>

</div>
</li>
</ul>
</div>
</div>


<br>
<br>
<a name="Additional information"><font size="4"><b>Additional information</b></font></a>
<br>
<br><!-- BASIC TWISTY SHOW/HIDE -->
<div class="ibm-container ibm-alternate">
<div class="ibm-container-body">
<ul class="ibm-twisty">
<li>
<a class="ibm-twisty-trigger" href="#toggle"><img alt="-" src="//www.ibm.com/i/c.gif" /></a>
<span class="ibm-twisty-head"><b>Package contents</b>
</span>
<div class="ibm-twisty-body">

<div class="ibm-container">
<div class=ibm-container-body>
<p>
<b>Update for Red Hat Enterprise Linux 5 (RHEL 5) on IBM servers with POWER processors</b>
</p>
<p>
LL_scheduler-4.1.1.5-x86-Linux-RHEL5 is a corrective fix for LoadLeveler for RHEL 5 on Intel X86 servers, version 4.1.1.X-0. 
</p>
<p>
The updates contained in the LL_scheduler-4.1.1.5-x86-Linux-RHEL5.tar.gz available for download from this site provide corrective fixes for LoadLeveler for RHEL 5 on X86 systems, version 4.1.1. Updates for both the full LoadLeveler product and the submit-only component of the LoadLeveler product are provided.

<p><b>Update to Version:</b></p>
<div class=ibm-indent>
<p>4.1.1.5</p>
</div>
<p><b>Update from Version:</b></p>
<div class=ibm-indent>
<p>4.1.1.0 through 4.1.1.4</p>
</div>

<p><b>Update scheduler (tar file) contents:</b>
<p>RPM files:
<div class=ibm-indent>
<p>LoadL-scheduler-full-RH5-X86-4.1.1.5-0.i386.rpm<br />
LoadL-scheduler-so-RH5-X86-4.1.1.5-0.i386.rpm</p>
</div>
 
<p>README file:</p>
<div class=ibm-indent>
<p>README<br /></p>
</div>
 
<p>For further information, consult the <a href="http://publib.boulder.ibm.com/infocenter/clresctr/vxrx/index.jsp?topic=/com.ibm.cluster.loadl.doc/llbooks.html" target=new.window>LoadLeveler for Linux Version 4.1.0 Installation Guide</a>.</p>

</div>
</div>


</div>
</li>
</ul>
</div>
</div>
<!-- BASIC TWISTY SHOW/HIDE -->
<div class="ibm-container ibm-alternate">
<div class="ibm-container-body">
<ul class="ibm-twisty">
<li>
<a class="ibm-twisty-trigger" href="#toggle"><img alt="-" src="//www.ibm.com/i/c.gif" /></a>
<span class="ibm-twisty-head"><b>Changelog</b>
</span>
<div class="ibm-twisty-body">

<div class="ibm-container">
<div class="ibm-container-body">

<!-- Content body begin -->
<div id="ibm-content-body">

<!-- main content begin -->
<div id="ibm-content-main">

<div class="ibm-rule"><hr/></div>

<div class="ibm-container ibm-alternate">
<div class="ibm-container-body">
<div class="ibm-two-column ibm-directory">
 
<div class="ibm-column ibm-first">
<ul class="ibm-link-list">
<li><a class="ibm-anchor-down-em-link" href="#genfix">General fixes</a></li>
<!-- COMMENTED OUT
<li><a class="ibm-anchor-down-em-link" href="#multifix">Multicluster fixes</a></li>
-->
</ul>
</div>
 
<div class="ibm-column ibm-second">
<ul class="ibm-link-list">
<!--<li><a class="ibm-anchor-down-em-link" href="#BGfix">Blue Gene fixes</a></li>-->
<li><a class="ibm-anchor-down-em-link" href="#APARlist">APAR listing</a></li>
</ul>
</div>

</div>
<div class="ibm-rule"><hr/></div>
</div>
</div>

<div class="ibm-container">
<b>Notes</b>
<div class="ibm-container-body"
<p>Unless specifically noted otherwise, this history of problems fixed for LoadLeveler 4.1.1.x applies to:</p>
<ul class="ibm-bullet-list">
<li>LoadLeveler 4.1.1.x for AIX 6</li>
<li>LoadLeveler 4.1.1.x for AIX 5</li>
<li>LoadLeveler 4.1.1.x for SUSE LINUX Enterprise Server 11 (SLES11) on POWER servers</li>
<li>LoadLeveler 4.1.1.x for SUSE LINUX Enterprise Server 11 (SLES11) on servers with 64-bit Opteron or EM64T processors</li>
<li>LoadLeveler 4.1.1.x for Red Hat Enterprise Linux 6 (RHEL6) on POWER servers</li>
<li>LoadLeveler 4.1.1.x for Red Hat Enterprise Linux 6 (RHEL6) on servers with 64-bit Opteron or EM64T processors</li>
<li>LoadLeveler 4.1.1.x for Red Hat Enterprise Linux 5 (RHEL5) on servers with 64-bit Opteron or EM64T processors</li>
<li>LoadLeveler 4.1.1.x for Red Hat Enterprise Linux 5 (RHEL5) on Intel based servers</li>
</ul>

</div>
</div>

<div class="ibm-container">
<b>Restriction section</b>
<div class="ibm-container-body">
 
<p><b>For LL 4.1.1:</b></p>
<ul class="ibm-bullet-list">
<li>On any machine where you plan to install the scheduler rpm, you must install the resource manager rpm and the resource manager rpm must be installed before the scheduler rpm.</li>
<li>If the scheduler and resource manager filesets are installed on the same machine, then the LoadLeveler version of those filesets have to be at the same level in order for transactions to be processed correctly.</li>
</ul>
 
<br/>
 
</div>
</div>


<div class="ibm-container">
<a name=genfix></a><b>General LoadLeveler problems</b>
<div class="ibm-container-body">

<p><b>Problems fixed in LoadLeveler 4.1.1.5 [July 28, 2011]</b></p>
<ul class="ibm-bullet-list">
 <li>Multiple configuration editor and form-based GUI issues are resolved.
 <li>LoadLeveler will not submit the job if there are no class in the default class list that can satisfy the job requirements.
 <li>LoadLeveler now creates cpuset files with permissions that are searchable by non-root users under the /dev/cpuset directory.
 <li>The unthread_open() error in the Schedd Log will no longer be printed when querying the remote cluster job since LoadLeveler will no longer try to route a nonexistent remote submit job command file in a multi cluster environment.
 <li>LoadLeveler has been enhanced so it now displays the job eligibility time.
 <li>Intel MPI and Open MPI are now supported under LoadLeveler.
<li><b>Resource Manager only:</b>
    <ul class="ibm-bullet-list">
    <li>The llctl command is now able to support "start drained" option on the remote node.
    </ul>
<li><b>Scheduler only:</b>
    <ul class="ibm-bullet-list">
    <li>LoadLeveler LoadL_negotiator daemon will not core dump when processing a multi-step job which contains a dependency statement longer than 2048 characters. 
	<li>LoadLeveler "llq -s" command will provide information about why a step is in Deferred state.
	<li>The llsummary command and API will no longer core dump if the number of history files are greater than or equal to the PTHREAD_DATAKEYS_MAX constant value.
	<li>In a Blue Gene environment, when running jobs are preempted by new incoming jobs, the top-dog job will not lose its status as top-dog.
    </ul>
</ul>
<br/>

<p><b>Problems fixed in LoadLeveler 4.1.1.4 [May 27, 2011]</b></p>
<ul class="ibm-bullet-list">
 <li>The llctl command will now check to make sure the Schedd daemon's port is available to be used before starting up LoadLeveler.
 <li>A new keyword, restart, is implemented for the class stanza in the admin configuration.  
 <li>If a value is not set for the keyword max_starters in database configuration mode, the default value used for max_starters will be adjusted when the count of classes specified in the keyword class is changed.
 <li>Absolute paths containing http/https are changed to relative paths for the configuration editor to run.
<li><b>Resource Manager only:</b>
    <ul class="ibm-bullet-list">
    <li>Loadleveler will now set the right environment variables when executing the user epilog script.
	<li>The llmkres command should now be able to create the reservations consistently without hitting the timing error message 2512-856.
	<li>In a multicluster environment, the llq -s command will now invoke the correct query command on the remote cluster.
    </ul>
<li><b>Scheduler only:</b>
    <ul class="ibm-bullet-list">
    <li>Modifying the recurring reservation's attribute will now be seen in the first occurrence's attribute value under the llqres -l command.
	<li>A unique security issue has been identified for TWS LoadLeveler Web User Interface that could potentially compromise your system.  It is recommended that you apply this update to protect your system.
    </ul>
</ul>
<br/>

<p><b>Problems fixed in LoadLeveler 4.1.1.3 [March 25, 2011]</b></p>
<ul class="ibm-bullet-list">
 <li>The ability to set the name_server in LoadLeveler is now disabled. The setting under LoadLeveler will now always be set to DNS.
 <li>When configuring class limits using the config editor adding or updating when there is more than one class limit will fail.  Now the config editor can be used to update class limits or add new hard and soft limits. 
 <li>If the class-user sub-stanzas in the "default" class stanza are not defined in alphabetical order, the class-user sub-stanzas might incorrectly inherit the wrong values from the default class.  LoadLeveler will now inherit the default values for the class-user sub-stanzas from the "default" class stanza correctly.
 <li>On Linux/P nodes, jobs requesting memory affinity with MCM_MEM_NONE, the job will always consume memory from the local MCM and will start paging once memory on the local MCM is over consumed; even though memory is available on other MCMs on the node.  Now, if a job is submitted with memory affinity option, MCM_MEM_NONE, the task will be bounded to all the MCMs on the node and the memory will be consumed from all the MCMs on the node.
 <li>An incorrect spelling prevented the class stanza keyword striping_with_minimum_networks from being set when DB configuration was used. The spelling of the column name in the database is now corrected.
 <li>LoadLeveler schedd may ignore jobs if the job queue contains invalid job keys.  Now, LoadLeveler schedd will collect the correct job data when scanning the job queue files.  
 <li>The llrstatus -a reports "No adapters are available" after issuing the llrctl reconfig command. When a machine running a Resource Manager or Region Manager daemon is reconfigured, information about adapters on other machines was being wiped out. The configuration processing code in Resource Manager and Region Manager has been fixed so that existing adapter information will remain intact.
 <li>When configuring the resources=keyword(all) in the machine group stanza in database mode, the llstatus -R command will show no resources being set.  Resources will now become effective when setting the resources=keyword(all) in the machine group stanza in database mode.
 <li>The schedd can core dump when a scale-across multi-cluster environment is configured incorrectly. This can happen if scale-across multi-cluster is configured and the same cluster stanza is specified as local for more than one cluster.  LoadLeveler is changed to protect the schedd from core dumping the same cluster stanza is configured as local for more than one cluster in a scale-across multi-cluster environment.

<li><b>Resource Manager only:</b>
    <ul class="ibm-bullet-list">
	<li>The LoadL_startd daemon leaks memory due to a failure to release memory allocated for data structures to hold switch table data for a job step.  The LoadL_startd daemon is corrected to release all memory allocated for data structures to hold switch table data for a job step, when the job step data structure is de-allocated.
	<li>A crash may occur in either the resource manager daemon or the negotiator daemon if those daemons received incorrect routing data during an update from startd.  This could have happened when the feature keyword was used in the machine_group stanza under the administration file or database setup.  The correct bits are now set by the startd daemon so that routing of the data will not cause the resource manager or the central manager to core dump. 
    </ul>
<li><b>Scheduler only:</b>
    <ul class="ibm-bullet-list">
 	<li>LoadLeveler will occasionally show the wrong number of class resource slots or even miss some classes from the llclass output if too many class query requests come in simultaneously.  LoadLeveler is now fixed to show the correct class resources in the llclass output.
	<li>When maxidle is used for a given user within a class, dependent steps can be queued at a higher priority than non-dependent steps.  Dependent steps are not given a new qdate when they are put onto the idle queue, while steps at the maxidle limit for a given user within a class are given a new qdate and a new sysprio based on that qdate. A change was made so that dependent steps are also counted as "queued" steps for the purposes of enforcing maxqueued and maxidle limits, and so a dependent step which is at the maxidle limit will get a new qdate.
    </ul>
</ul>
<br/>

<p><b>Problems fixed in LoadLeveler 4.1.1.2 [January 28, 2011]</b></p>
<ul class="ibm-bullet-list">
 <li> The LoadLeveler startd drain status will be lost if the negotiator daemon restarts. Fixed the startd drain status to be stored onto each individual startds.  When the negotiator daemon restarts, the startd drain information will be restored from all the startds.
 <li> The llsummary command might crash if the default class requirement value doesn't match the job requirement value. Fixed the llsummary command to select the correct requirement value from the default class list if there is no job class specified in job command file.
 <li> The llsummary command will fail when it tries to access invalid data memory in the job history file. Fixed the llsummary command to be able to ignore the bad data areas and just report the valid data in the job history file.
 <li> LoadLeveler schedd may ignore jobs if the job queue contains invalid job keys. The schedd will now collect the correct job data when scanning the job queue files.
 <li> The LoadLeveler command, llmodify, has a limitation where the startdate and wall_clock_limit job attributes cannot be modify for idle jobs. llmodify is now enhanced to be able to modify the startdate and wall_clock_limit job attributes for idle jobs.
 <ul>
New documentation:
 <li>In the LoadLeveler Command and API Reference, SC23-6701-00, under Chapter 1. Commands, llmodify - Change attributes of a submitted job step,
 <ul>
 <li>New keyword wall_clock_limit for the -k option: Changes the wall clock limit of a job step. The value of the specified wall clock limit must be longer than the value of the current wall clock limit. This is a LoadLeveler administrator only option.
 <li>New keyword startdate for the -k option: Changes the start time of a idle-like job step. This is a LoadLeveler administrator only option.
 </ul>
 </ul>
<li><b>Resource Manager only:</b>
    <ul class="ibm-bullet-list">
 <li> User jobs will not be launched on AIX if the group name did not match the one from the job submission.  Fixed the job launch program so it does not need to verify the group name so jobs will be executed using the submitting GID number.
 <li> A crash may occur in either the LoadL_resource_mgr daemon or the LoadL_negotiator daemon when the feature keyword is used in the machine_group stanza under the administration file or database setup. A fix has been made in supporting the specifying of the feature keyword in the machine_group stanza in the administration file or in the database.
    </ul>
<li><b>Scheduler only:</b>
    <ul class="ibm-bullet-list">
 <li> LoadLeveler machines and jobs may have the wrong state if some startd are down and the region manager is enabled.  Fixed LoadLeveler to handle machines and jobs status correctly when the region manager detects a machine to be down.
 <li> LoadLeveler was trying to load the network table for jobs with job_type=MPICH and the job will fail to run if the network table can not be loaded.  Since jobs with a job_type=MPICH do not require the loading of the network table.  LoadLeveler will not load the network table with this job type specified in the job command file.
    </ul>
</ul>
<br/>

 
<p><b>Problems fixed in LoadLeveler 4.1.1.1 [December 10, 2010]</b></p>
<ul class="ibm-bullet-list">
<li> Fixed the schedd daemon so it will not crash if the job's output file path contains the "%" character.
<li> Fixed the -s and -e options in the llsummary command to report all the jobs that match the filter requirement. In the TWS LoadLeveler documentation, Command and API Reference and the llsummary.l manual page, the -s and -e options will state the accounting data report will contain information about every job that contains at least one step that falls within the specified range.


<li><b>Resource Manager only:</b>
    <ul class="ibm-bullet-list">
 <li>Fixed the processor affinity environment to be setup correctly for jobs to run in when the job prolog is configured in LoadLeveler.
    </ul>

<li><b>Scheduler only:</b>
    <ul class="ibm-bullet-list">
 <li>Fixed the llclass command to show the correct value for the "Free Slots" field when LoadLeveler is configured to use the LL_DEFAULT scheduler.
 <li>Fixed the llchres command to check requested node additions to make sure that those nodes have no jobs running on them or already assigned to another reservation.  If no idle nodes can be found, the llchres command will fail.
 <li>Fixed LoadLeveler to correctly reserve the reservation's resources after the central manager daemon restarts so that jobs with overlapping resources with the reservations will not be allowed to start.
 <li>Fixed the central manager to make sure pending status changes to the machines are properly locked so that jobs being scheduled to the down machines will no longer crash the central manager daemon.
    </ul>
</ul>
<br/>

</div>
</div>


<table cellspacing=0 cellpadding=0 border class=ibm-data-table width=100%>
<caption><em><a name=APARlist></a>TWS LoadLeveler Corrective Fix listing</em></caption>
<tr><th>Fix Level</th><th>APAR numbers</th></tr>

<tr>
<td><b>LL 4.1.1.5</b></td>
<td><a name=LL4115></a><b>AIX</b>: resource manager: IV00833 IV01116 IV01321 IV01332 IV02937 IV03232 IV03277 IV03299 IV03304 
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4115></a><b>Linux</b>: resource manager: </td>
</tr>

<tr>
<td><b>LL 4.1.1.5</b></td>
<td><a name=LL4115></a><b>AIX</b>: scheduler: IV00813 IV00834 IV01325 IV01333 IV01390 IV02945 IV03233 IV03278 IV03300 IV03303 IV03305 IV03309 
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4115></a><b>Linux</b>: scheduler: IZ99118 IV01036</td>
</tr>


<tr>
<td><b>LL 4.1.1.4</b></td>
<td><a name=LL4114></a><b>AIX</b>: resource manager: IV00027 IV00031 IV00037 IV00277 IV00304 IV00462 IZ93228 IZ99666 
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4114></a><b>Linux</b>: resource manager: </td>
</tr>

<tr>
<td><b>LL 4.1.1.4</b></td>
<td><a name=LL4114></a><b>AIX</b>: scheduler: IV00028 IV00029 IV00032 IV00280 IV00299 IV00463 
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4114></a><b>Linux</b>: scheduler: </td>
</tr>


<tr>
<td><b>LL 4.1.1.3</b></td>
<td><a name=LL4113></a><b>AIX</b>: resource manager: IZ93225 IZ93259 IZ93267 IZ94345 IZ94801 IZ96421 IZ96428 IZ96430
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4113></a><b>Linux</b>: resource manager: </td>
</tr>

<tr>
<td><b>LL 4.1.1.3</b></td>
<td><a name=LL4113></a><b>AIX</b>: scheduler: IZ89344 IZ93154 IZ93226 IZ94800 IZ96422 IZ96423 IZ96425 IZ96431 IZ96433
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4113></a><b>Linux</b>: scheduler: </td>
</tr>


<tr>
<td><b>LL 4.1.1.2</b></td>
<td><a name=LL4112></a><b>AIX</b>: resource manager: IZ89829 IZ90705 IZ90707 IZ91597 IZ91599 IZ92052 IZ92374
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4112></a><b>Linux</b>: resource manager: IZ91715</td>
</tr>

<tr>
<td><b>LL 4.1.1.2</b></td>
<td><a name=LL4112></a><b>AIX</b>: scheduler: IZ90487 IZ90706 IZ90708 IZ90875 IZ91596 IZ91598 IZ91600 IZ92375
</td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4112></a><b>Linux</b>: scheduler: </td>
</tr>

<tr>
<td><b>LL 4.1.1.1</b></td>
<td><a name=LL4111></a><b>AIX</b>: resource manager: IZ88502 IZ88504 IZ89257 IZ89260 </td>
</tr>
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4111></a><b>Linux</b>: resource manager: </td>
</tr>
 
<tr>
<td><b>LL 4.1.1.1</b></td>
<td><a name=LL4111></a><b>AIX</b>: scheduler: IZ88503 IZ88506 IZ88509 IZ88511 IZ88513 IZ88681 IZ89259 </td>
</tr>
 
<tr>
<td>&nbsp;</b></td>
<td><a name=LL4111></a><b>Linux</b>: scheduler: </td>
</tr>
 
</table>


</div>
</li>
</ul>
</div>
</div>

</div>
<br>
<br>
<a name="Copyright and trademark information"><font size="4"><b>Copyright and trademark information</b></font></a>
<br>
<br>
<a href="http://www.ibm.com/legal/copytrade.shtml">
<br>
	 http://www.ibm.com/legal/copytrade.shtml
     </a>
<br>
      
<p>
<b>Notices</b><br/>
<br/>
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some jurisdictions do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this
statement may not apply to you.
<br/>
<br/>
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
<br/>
<br/>
Microsoft, Windows, and Windows Server are trademarks of Microsoft 
Corporation in the United States, other countries, or both.
<br/>
<br/>
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, 
Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and 
Pentium are trademarks or registered trademarks of Intel Corporation or its 
subsidiaries in the United States and other countries.
<br/>
<br/>
Other company, product, or service names may be trademarks or
service marks of others.
<br/>
<br/>

<b>THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION</b>
<br/>
<br/>
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices
and other information IBM must provide to you under its license
to certain software code. The relevant terms and conditions,
notices and other information are provided or referenced below. 
Please note that any non-English version of the licenses below is
unofficial and is provided to you for your convenience only.  The
English version of the licenses below, provided as part of the
English version of this file, is the official version.
<br/>
<br/>
Notwithstanding the terms and conditions of any other agreement
you may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified
below are "Excluded Components" and are subject to the following
terms and conditions:
<br/>
<ul>
<li>the Excluded Components are provided on an "AS IS" basis

<li>IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
   CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING,
   BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR
   INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF
   MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

<li>IBM will not be liable to you or indemnify you for any claims
   related to the Excluded Components

<li>IBM will not be liable for any direct, indirect, incidental,
   special, exemplary, punitive or consequential damages with
   respect to the Excluded Components.
</ul>

</p>

       
    <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>
