IBM Support

OA60354: EXPIRATION DATE SET FROM EDGRMMXX RETPD INSTEAD OF MC CLASS VALUE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • In an RMM environment where MCATTR is set to ON or VRSELXDI, the
    expiration date can be set invalidly in cases where the
    expiration date would be taken from the Management class
    settings. When the RETPD value in EDGRMMxx is greater that the
    EXPIRE AFTER DAYS VALUE in the MC class, the RETPD value can get
    applied in error which sets a longer expiration date than was
    intended by the Management Class settings.
    
    
    ADDITIONAL KEYWORDS:
    RETENTION PERIOD METHOD VITAL RECORD VRSEL
    

Local fix

  • BYPASS/CIRCUMVENTION:
    Expiration date may be manually set with RMM CV volser EXPDT
    command. The management class can also be changed to have a
    longer value for EXPIRE AFTER DAYS than the EDGRMMxx RETPD or
    the RETPD can be reduced to have a shorter value that the EXPIRE
    AFTER DAYS value.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DFSMMrmm users having option MCATTR set to ALL or        *
    * VRSELXDI in their EDGRMMxx parmlib member.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A data set is assigned a management class by an ACS routine. *
    * If the EXPIRE AFTER DAYS value specified in that Management  *
    * Class is less than the RETPD option in the EDGRMMxx parmlib  *
    * member, then the expiration date can be incorrectly set      *
    * based on the RETPD value rather than on the Management Class *
    * EXPIRE AFTER DAYS value.                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This FIN is reversed and fixed with APAR OA63281.
    

Temporary fix

Comments

  • This APAR is being closed FIN with the concurrence from the
    submitting customer.  This means that a solution to this APAR is
    expected to be delivered from IBM in a release (if any) to be
    available within the next 36 months.
    CONTROL NUMBER: 391437
    

APAR Information

  • APAR number

    OA60354

  • Reported component name

    DFSMSRMM

  • Reported component ID

    5695DF186

  • Reported release

    230

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-19

  • Closed date

    2020-11-20

  • Last modified date

    2022-06-06

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"230"}]

Document Information

Modified date:
07 June 2022