IBM Support

OA66036: PFA_WLM_ADDR_SPACE_VELOCITY PFA_JES2_RESOURCE_EXHAUSTION MODEL FAILURE AIR053I JVM HEAP TOO SMALL

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The PFA_WLM_ADDR_SPACE_VELOCITY (WAV) or the
    PFA_JES2_RESOURCE_EXHAUSTION (JRE) check may fail modeling with
    message AIR053I due to the JAVA VM heap space running out of
    memory.  Analysis shows that it was
    consumed with expected data from the jobs being tracked under
    these checks.
    
    The default heap Size for PFA is 128MB which is not sufficient
    for all configurations.
    
    VERIFICATION STEPS:
    For the WAV check:
    Review the javacore.xxxxxxx.txt file generated
    - The Java callstack:  should show that the out of memory
    occurred in DataSource.readDataFromFile.
     at
     com/ibm/zos/pfa/cart/DataSource.readDataFromFile(DataSource.j
    avaCode))at
    com/ibm/zos/pfa/cart/CartMain.main(CartMain.java:478) No
    native callstack available on this platform
    
    For the JRE check
    Review the javacore.xxxxxxx.txt file generated
    - The Java callstack:  should show that the out of memory
    occurred in the systeName.5day.All.Data file
    at
    com.ibm.zos.pfa.chk.MergeStorage.identifyTopContributors(MergeS
    torage.java:868)
    
    - The JVM options in the javacore.txt file should show the
    
    UserArgs passed:
    1CIUSERARGS    UserArgs:
    .
    .
    .
    2CIUSERARG               -Xms64M
    2CIUSERARG               -Xmx128M
    2CIUSERARG               -Xss128M
    

Local fix

  • BYPASS/CIRCUMVENTION:
    - Modify the size for the JVM heap to be used. By creating a
    pfaopts file
    
    pfaopts file instructions
    
    ---------------------------
    
    The options file must be created in the check's directory for
    each check, must be named pfaopts, and must have 755 as the
    permission bits
    
    For example, the pathname for the file for this issue would be
    for the PFA_WLM_ADDR_SPACE_VELOCITY check would be
    
    pfa_directory/PFA_WLM_ADDR_SPACE_VELOCITY/pfaopts
    
    
    If the file exists and is not empty (with file size 0), PFA will
    
    add the options file as the last option when creating the JVM
    and will log additional information to the check's
    systemName.launcher.log.
    
    One method of creating the file is to do the following:
    
    1. Change directory in omvs to a check directory
    (pfa_directory/PFA_WLM_ADDR_SPACE_VELOCITY for example)
    cd /u/pfa/PFA_WLM_ADDR_SPACE_VELOCITY/
    
    
    2. oedit pfaopts
    
    
    3. Add following on separate LINEs of this file and save it:
    -XmsYm
    -XmxZm
    *NOTE* replace Y/Z with decimal value of megabyte for the PFA
           heap size.  Y is for the minimum size, Z is for the
           maximum size.
    ie:    -Xms64m
     -Xmx192m
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all z/OS 2.5 (HBB77DO) and above PFA                         *
    * environments                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PFA_WLM_ADDR_SPACE_VELOCITY                                  *
    * health check issues Java Out Of                              *
    * Memory                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Insufficient max allowed JVM Heap size
    for various PFA checks
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA66036

  • Reported component name

    Z/OS PFA

  • Reported component ID

    5752SCPFA

  • Reported release

    7D0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-01-19

  • Closed date

    2025-06-24

  • Last modified date

    2025-08-02

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

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

    UJ97465 UJ97466 UJ97471

Modules/Macros

  • AIRJCART AIRLMARC AIRJCHK  AIRLCSAC
    

Fix information

  • Fixed component name

    Z/OS PFA

  • Fixed component ID

    5752SCPFA

Applicable component levels

  • R7E0 PSY UJ97465

       UP25/07/09 P F507

  • R7D0 PSY UJ97471

       UP25/07/09 P F507

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.

[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7D0"}]

Document Information

Modified date:
02 August 2025