IBM Support

OA57119: UNDERALLOCATION WHEN EXTENDING A DATA SET TO A NEW VOLUME WHERE THE VOLUME DOES NOT HAVE SUFFICIENT SPACE TO SATISFY THE REQUEST

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • User is attempting to create and allocate a data set using
    SPACE=(CYL,(1,4000)).  Storage group has two volumes, TESTMY and
    TESTMZ with 1310 and 1325 cylinders available, respectively.
    Space Constraint Relief is set to YES and REDUCE SPACE UP to is
    10%.
    The job runs, creates the data set with
    1 cylinder on TESTMY then begins writing data to the data set.
    EXTEND is done and 4000 cylinders are requested on TESTMY which
    fails in DADSM with DIAG 041A014D.  The allocation is redriven
    to TESTMZ where 1325 cylinders are allocated.  SMS accepts this
    allocation causing an underallocation on the second volume.
    The allocation should fail with MSGIGD17273I since there
    is not enough cylinders on either volume.
    The result is an underallocation when extending to a new volume
    when the volume(s) do not have sufficient space.
    

Local fix

  • reduce the space required or add more volumes to the storage
    group with sufficient space
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *  HDZ2220 USERS AND ABOVE                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *  SEE ERROR DESCRIPTION                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    SUMMARY: WHEN EXTENDING A NON-VSAM DATA SET TO A NEW VOLUME, A
    SECONDARY SPACE AMOUNT IS USED. AFTER THE ALLOCATION FAILED
    BECAUSE OF INSUFFICIENT SPACE ON THE NEW VOLUME, SMS WOULD
    REDRIVE THE ALLOCATION IF SPACE CONSTRAINT RELIEF IS SET TO YES.
    
    HOWEVER, AFTER THE SPACE WAS ALLOCATED FOR SPACE CONSTRAINT
    RELIEF PHASE, SMS COMPARED THE ALLOCATED SPACE WITH THE
    PRIMARY SPACE AMOUNT, WHICH WAS A WRONG CHECK. THIS CAUSED THE
    UNDER-ALLOCATION OCCURED ON THE NEW VOLUME.
    

Problem conclusion

  • THE LOGIC HAS BEEN CORRECTED TO CHECK THE SECONDARY SPACE AMOUNT
    WHEN EXTENDING A NON-VSAM DATA SET TO A NEW VOLUME.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA57119

  • Reported component name

    STORAGE MGMT SU

  • Reported component ID

    5695DF101

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-14

  • Closed date

    2019-04-17

  • Last modified date

    2019-06-03

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

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

    UA99109 UA99110

Modules/Macros

  • IGDVTSDA
    

Fix information

  • Fixed component name

    STORAGE MGMT SU

  • Fixed component ID

    5695DF101

Applicable component levels

  • R230 PSY UA99109

       UP19/05/11 P F905

  • R220 PSY UA99110

       UP19/05/11 P F905

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 June 2019