IBM Support

OA55518: EDG4066I VOLUME VOLSER REJECTED, DATA SET ACCESS IS BLOCKED BY DSNEXPIRE, BUT THE SPECIFIED EXPDT IS A 18/06/01 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With the PTFs for OA54871 applied the EDGRMMxx option
    DSNEXPIRE(BLOCK) is preventing access to data sets with an
    expiration date of 12/31/1999.  This is a special date in RMM
    that should set the data set to never expire.
    .
    As an example, allocating a new data set via JCL with
    EXPDT=99365 can result in RMM not allowing access to the data
    set by incorrectly comparing the current date to the
    expiration date and not honoring 1999/365 as a 'never expire'
    value if VITAL RECORD SELECTION(VRSEL) has not yet been run
    and no RETENTION DATE has been set.
    
    
    
    ADDITONAL KEYWORDS:
    MSGEDG4066I IEC145I 413 08 OPEN MACRO MSGIEC145I GDPR GLOBAL
    DATA PRIVACY REGULATION
    

Local fix

  • Remove DSNEXPIRE(BLOCK) from the EDGRMMxx parmlib member and
    restart DFRMM with F DFRMM,M=xx where XX is your parmlib suffix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DFSMSrmm users who have PTFs for APAR                    *
    * OA54871 applied and the RMM parmlib option                   *
    * DSNEXPIRE(BLOCK) is in effect.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * After applying the PTFs for APAR                             *
    * OA54871 and defining DSNEXPIRE(BLOCK)                        *
    * in the EDGRMMxx parmlib member, data                         *
    * sets that were read or written with                          *
    * EXPDT=99365 or EXPDT=99366 specified                         *
    * in the JCL become blocked from access.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the applicable PTF(s)                                  *
    ****************************************************************
    The program does not provide the correct processing for the
    case described.
    

Problem conclusion

  • The problem has been fixed.
    

Temporary fix

  • A ++APAR FIX IS AVAILABLE UPON REQUEST
    

Comments

APAR Information

  • APAR number

    OA55518

  • Reported component name

    DFSMSRMM

  • Reported component ID

    5695DF186

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-22

  • Closed date

    2018-06-01

  • Last modified date

    2018-07-02

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

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

    UA96384 UA96387 UA96388

Modules/Macros

  • EDGSOCE
    

Fix information

  • Fixed component name

    DFSMSRMM

  • Fixed component ID

    5695DF186

Applicable component levels

  • R210 PSY UA96387

       UP18/06/08 P F806 ­

  • R220 PSY UA96388

       UP18/06/16 P F806 ­

  • R230 PSY UA96384

       UP18/06/16 P F806 ­

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":"220","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 July 2018