Maui 3.2.5

  FairShare

  Support for 'old style' fs.cfg fairshare specification removed
    see http://supercluster.org/documentation/maui/324/6.3fairshare.html


  Resource Managers

  The index for the 'RM*' parameters is now a resource manager 'name' 
  rather than an integer.  Consequently, the RMNAME parameter is now disabled.  
  Under 3.2.5, resource manager configuration can be specified using either 
  the the 'rmcfg' parameter or the set of 'RM*' parameters. 

  For Loadleveler systems, specify the TYPE value 'LL' for all Loadleveler
  versions, not LL1, LL2, etc.


  QOS

  While QOS facility still supports the 'IGN*' flags to allow ignoring of
  various throttling policies, it actually provides more flexible management
  of these policies through the use of 'override' throttling policies.  For
  example, the parameter 'QOSCFG[special]  OMAXPROC=20' can be specified to
  set the MAXPROC limit of any job using the 'special' QOS to 20 regardless 
  of any other credential based job limits.

  The QOS 'FLAGS' attribute has now been separated into two distinct attributes,
  'QFLAGS' and 'JOBFLAGS'.  QFLAGS specifies aspects of the QOS and the 
  privileges it allows, such as 'NOBF', 'IGNPROCPERUSER', or 'PREEMPTOR'.  The
  'JOBFLAGS' attribute specifies the job default job flags which should be set
  on jobs using this QOS.  Examples of these values include 'SPAN', 'ADVRES',
  etc.


  Priority Specification

  Maui 3.2.5 supports a full two stage hierarchical priority scheme consisting 
  of priority components and subcomponents all with their own weights and caps.


  Reservations

  Standing reservations will no longer 'float' by default.  Floating allowed 
  reservation to 'relocate' when nodes went down or when a migration would 
  improve overall system utilization.  With the current version, the standing
  reservation FLAGS attribute must be set to SPACEFLEX to enable this feature.

  Further, the SR* parameters (SRTASKCOUNT, SRHOSTLIST, etc) are now deprecated 
  being replaced by the SRGCFG parameter.  If these parameters are used, the
  'SRNAME' value should be specified as the array index (ie, 'SRTASKCOUNT[bigjobs] 32').
  Because of this change, the SRNAME parameter is no longer supported.


  Scheduling Policies

  NODEACCESSPOLICY no longer accepts 'DEDICATED' as a valid value.  Legal values 
  are now 'SHARED', 'SINGLEJOB', 'SINGLETASK', and 'SINGLEUSER'.
 

  Other trivia:

  The parameter RESOURCEWEIGHT is not supported.  RESWEIGHT is a component weight.  
  To adjust priority based on a job's requested processors, specify

---
RESWEIGHT  1
PROCWEIGHT 100
---

  The parameter URGENCYWEIGHT is not supported.  TARGETWEIGHT is a component weight.
  To adjust priority based on a job's service target, the parameter TARGETXFACTORWEIGHT
  and/or TARGETQUEUETIMEWEIGHT must be specified.

  QOSWEIGHT, USERWEIGHT, etc, are now subcomponents of the CRED priority component and
  should be specified in conjunction with the CREDWEIGHT parameter, ie
   
---
CREDWEIGHT     2
ACCOUNTWEIGHT  10
QOSWEIGHT      20
---

  (See http://supercluster.org/documentation/maui/324/5.1jobprioritization.html)