IBM Support

OA67869: AFTER RESTORING A ZFS MOUNT FAILS WITH MSGBPXF135E RC8A, RSNEF186058

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SMS-managed zFS is defined with 5823 cylinders.  Extended
    addressability is not set, EATTR=OPT is specified.
    The data set is allocated on a non-EAV volume with 87345 tracks.
    HARBA/HURBA are 4293181439 which is just under 4 GB limit.
    The zFS is unmounted then DFSMSdss physical dump captured:
    DUMP DS(INC(SUE.TEST.ZFS)) -
          PHYSINDD(DD2)   -
          OUTDD(OUT) ALLDATA(*)
    Then RESTORE is done on another system to a storage group with
    EAV volumes:
     RESTORE DATASET(INCLUDE(SUE.TEST.ZFS)) -
    
         REPLACEU CATALOG SPHERE -
    
         ODY(ZSSMSA) -
    
         STORCLAS(SCDEFLT            ) -
    
         INDDNAME(DUMP) -
    
         RENAMEU((SUE.TEST.ZFS -
    
                  SUE.TEST.EAV.ZFS.NEW))
    
    The zFS is re-cataloged and LISTCAT shows it is now allocated in
    CMS(Cylinder Managed Space) causing the allocation to be 87570
    tracks which pushes the data set just over the 4GB limit.
    HARBA/HURBA are still 4293181440 which is incorrect.
    Mount fails with MSGBPXF135E RC8A, RSNEF186058
    

Local fix

  • BYPASS/CIRCUMVENTION:
    force the data set to go to non-EAV or alter dataclass so
    EATTR=NO is specified.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users performing physical data set DUMP  *
    *                 and RESTORE of non-extended addressable      *
    *                 VSAM data sets that are just under 4 GB      *
    *                 in size.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Physical data set RESTORE was performed *
    *                      on a non-extended addressable SMS       *
    *                      managed zFS that was just under the     *
    *                      4GB maximum size.  After the RESTORE    *
    *                      to an EAV, the resulting target was     *
    *                      allocated in the extended-addressable   *
    *                      space and grew to just over the 4GB     *
    *                      limit. The zFS could not be mounted.    *
    ****************************************************************
    See Problem Description.
    

Problem conclusion

  • DFSMSdss has been modified to correct the problem.
    
    KEYWORDS:
    EAV/K
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA67869

  • Reported component name

    DFSMSDSS, ISMF

  • Reported component ID

    5695DF175

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-05-06

  • Closed date

    2025-06-06

  • Last modified date

    2025-07-02

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

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

    UJ97367 UJ97368 UJ97370

Modules/Macros

  • ADRSB100
    

Fix information

  • Fixed component name

    DFSMSDSS, ISMF

  • Fixed component ID

    5695DF175

Applicable component levels

  • R250 PSY UJ97370

       UP25/06/17 P F506

  • R310 PSY UJ97368

       UP25/06/17 P F506

  • R320 PSY UJ97367

       UP25/06/17 P F506

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":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"310"}]

Document Information

Modified date:
02 July 2025