IBM Support

OA50845: NEW FUNCTION - WLM SUPPORT FOR THE "IBM Z/OS PLATFORM FOR APACHESPARK"

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • New Function
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS 2.1 (HBB7790) and above    *
    ****************************************************************
    * PROBLEM DESCRIPTION: New Function - WLM Support for the "IBM *
    *                      z/OS Platform for Apache Spark"         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    SPARK work can demand significant processor capacity and thus
    can negatively impact traditional workload running on regular
    CPs.
    Likewise, SPARK work can use up a significant amount of memory
    and thus also negatively impact traditional workload.
    
     APSPARKF/K    SMFREC/K
    

Problem conclusion

Temporary fix

Comments

  • This APAR introduces two new functions:
    1. WLM Specialty Engines Containment (also known as
    "HonorPriority by Service Class") and
    2. Memory Capping.
    
    HonorPriority by Service Class:
    Spark work is eligible to mainly run on specialty processors,
    zAAPs or zIIPs.
    The new function in this APAR allows WLM administrators to
    prevent overflow from zAAPs or zIIPs to regular CPs for work in
    individual service classes.
    
    New field 'Honor Priority' is added to the Create and Modify a
    Service Class panels. The Honor Priority field is used to
    specify whether work in this service class is allowed to
    overflow to standard processors when there is insufficient
    specialty engine capacity for the workload demand in this
    service class.
    
    With Supervisor APAR OA50953, the z/OS dispatcher implements the
    containment by preventing "needs-help" processing by regular
    CPs. Thus SPARK work running in such service classes cannot
    negatively impact traditional workload running on regular CPs.
    
    Memory Capping:
    This new function in this APAR allows WLM
    administrators to specify an upper memory limit for resource
    groups and associate address spaces with these resource groups
    through classification.
    
    New field 'Memory Limit' is added to the Create and Modify a
    Resource Group panels.  The Memory Limit field is used to limit
    the amount of memory capacity available to one or more service
    classes on system level.  The field contains the maximum amount
    of memory in giga bytes that address spaces associated with the
    resource group through classification may consume on the local
    system.
    
    This function introduces the following new SRM messages.
    IRA450E is issued when a Memory Pool has reached its defined
    upper limit.
    IRA452I is issued after IRA450E, when the used storage of a
    Memory Pool is below its defined upper limit again.
    IRA459I is issued to inform about various possible problems with
    the use of a Memory Pool.
    
    With RSM apar OA51171, RSM will enforce the defined upper limit
    for the set of address spaces associated with the resource
    group. Thus SPARK work running in such address spaces can be
    limited in its real memory consumption.
    
    For a description how to use these functions, please refer to
    OA50845.pdf. available at:
    http://publibz.boulder.ibm.com/zoslib/pdf/OA50845.pdf
    There, the use of the new functions is described within the
    existing structure of the affected WLM publications:
    SC34-2662-xx -- z/OS MVS Planning: Workload Managementent
    GA32-0937-xx -- z/OS V2R1 MVS Data Areas Volume 3
    GA32-0938-xx -- z/OS V2R1 MVS Data Areas Volume 4
    SA38-0667-xx -- z/OS MVS System Management Facilities (SMF)
    SA38-0676-xx -- z/OS MVS System Messages, Vol 9 (IGF-IWM)
    
    Important Note: Coexistence Considerations For this new
    function, the WLM Administrative Application level changes from
    30 to 31.  WLM Administrative Application LEVEL031 is only
    available with z/OS V2R1 and above when APAR OA50845 is applied.
    The functionality level of a service definition changes to 31 as
    soon as value NO is specified for the new Honor Priority
    attribute for any service class on the service class definition
    or the service class override panels, or a memory limit is
    specified for any resource group on the resource group
    definition or the resource group override panels.  The new
    functionality LEVEL031 for the WLM service definitions is
    introduced into mapping macros IWMSVAEA, IWMSVDCR, IWMSVDEF,
    IWMSVNPA and IWMSVPOL.
    
    A WLM service definition with functionality level LEVEL031
    cannot be extracted, displayed, modified, installed or activated
    from a z/OS V1R13 system or from a z/OS V2R1 or V2R2 system
    without APAR OA50845 applied. Once the functionality level of
    the WLM service definition increases to LEVEL031, all actions
    must be taken from a z/OS V2R1 or V2R2 system with APAR OA50845
    applied.
    Once a functionality LEVEL031 service definition is installed
    and activated, it will run on all systems in a mixed sysplex.
    However, the new attributes will not be honored on a z/OS V1R13
    system or on a z/OS V2R1 or V2R2 system without APAR OA50845
    applied. The new functionality is tolerated on the back-level
    systems, but not exploited.  zPage information:
    
    On systems with APAR OA50845 applied, the following
    inconsistency exists even if none of the new functions is used.
    The WLM service definition can be stored in ISPF tables, or in
    XML format. With this APAR structural changes to the ISPF tables
    are required. In that case, the WLM Administrative Application
    automatically updates the ISPF table structure when you save the
    service definition in ISPF table format, even if you do not
    exploit the new functionality. If this occurs, the saved service
    definition cannot be read by older levels of the WLM
    Administrative Application, or the IWMINSTL sample job.  This
    problem does not exist if you save the updated service
    definition in XML format. Therefore, it is recommended to always
    use XML format when saving service definitions. If using ISPF
    table format, it is recommended to start updating a WLM policy
    with a higher level of administrative application only when you
    are sure that you do not have to update that policy data set
    with a lower level of administrative application anymore.
    

APAR Information

  • APAR number

    OA50845

  • Reported component name

    WORK LOAD MANAG

  • Reported component ID

    5752SCWLM

  • Reported release

    790

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2016-07-06

  • Closed date

    2017-03-16

  • Last modified date

    2017-06-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UA91357 UA91358 UA91359 UA91360

Modules/Macros

  • IEAVNP10 IRABASMF IRACPSRP IRAEVCRM IRAEVCVL IRAEVENQ IRAEVIRS
    IRAEVJIA IRAEVJJT IRAEVMCR IRAEVMDL IRAEVQCN IRAEVQSC IRAEVREQ
    IRAMSBLD IRAMSBL2 IRAOPCAN IRAOPRES IRAOUCB  IRAPAASC IRAPAAUP
    IRAPABQD IRAPACAL IRAPACA3 IRAPACRM IRAPACTC IRAPACT2 IRAPADGM
    IRAPADRV IRAPAHK4 IRAPAHK7 IRAPAHK8 IRAPAHSK IRAPAIHK IRAPAINP
    IRAPALPC IRAPALSD IRAPANVO IRAPAQP2 IRAPASMF IRAPASM2 IRAPASRE
    IRAPASSB IRAPASS1 IRAPASS2 IRAPASS3 IRAPASS4 IRAPASS5 IRAPASS6
    IRAPASS7 IRAPASS8 IRAPAS2D IRAPATCD IRARADRV IRARAMON IRARAMP3
    IRARASD  IRARMASD IRARMCA  IRARMCAP IRARMCBS IRARMCPM IRARMCTL
    IRARMER4 IRARMEVT IRARMFMO IRARMFMP IRARMFMT IRARMLNK IRARMMSG
    IRARMPLI IRARMPRP IRARMRM3 IRARMSBS IRARMSET IRARMSMF IRARMSOP
    IRARMSTM IRARMST2 IRARMST3 IRARMSWP IRARMWL1 IRARMWL2 IRARMWL4
    IRARMWTO IRARQSRV IRASAMSU IRASMF99 IRASRCD  IRASRMEN IRASRMJP
    IRASRPST IRASRRSM IRASTASM IRASTFXS IRASWCT  IRATXCHP IRATXCH2
    IWMAM32  IWMAM52  IWMAPAB  IWMAPLGO IWMAP3D  IWMAP3J  IWMAP4J
    IWMAP5D  IWMAP5J  IWMAP5K  IWMAP5V  IWMAP58  IWMARDCF IWMARIDM
    IWMARIN1 IWMARI2X IWMARX2I IWMARZFL IWMAR01  IWMAR3D  IWMAR5D
    IWMAS41  IWMAS54  IWMA2SD1 IWMA2SD2 IWMA2SD3 IWMA2SD5 IWMA3MEW
    IWMC4SMF IWMHT31  IWMH3DR  IWMH5DE  IWMH7DN  IWMI2RIM IWMP2ACT
    IWMP2ECR IWMP2EXT IWMP2FDP IWMP2PRQ IWMP2RAP IWMP2REQ IWMP2RE2
    IWMP2RSD IWMP2SPC IWMP2TIN IWMP2VDR IWMP2VPR IWMP2VSA IWMP2VSD
    IWMP2VSP IWMP2WSD IWMSVAEA IWMSVDCR IWMSVDEF IWMSVNPA IWMSVPOL
    IWMWRQAA IWMW2BCL IWMW2BGR IWMW2CL4 IWMW3MLD IWMZ2MST IWMZ2SVP
    IWMZ2VCH IWMZ2VCR IWMZ2VPH IWMZ2VPO
    

Publications Referenced
SC34266202 SC34266204 SA38067603 GA32093702 GA32093703
SA38067606 GA32093802 GA32093803 SA38067703 SA38067707

Fix information

  • Fixed component name

    WORK LOAD MANAG

  • Fixed component ID

    5752SCWLM

Applicable component levels

  • R7AJ PSY UA91359

       UP17/03/29 P F703

  • R7A0 PSY UA91357

       UP17/03/29 P F703

  • R79J PSY UA91360

       UP17/03/29 P F703

  • R790 PSY UA91358

       UP17/03/29 P F703

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: z/OS family

Software version: 790

Operating system(s): MVS, z/OS

Reference #: OA50845

Modified date: 07 June 2017


Translate this page: