IBM Support

OA54871: NEW FUNCTION: GDPR SUPPORT - DSNEXPIRE(BLOCK) AND CHANGEDATASET FORCEXPIRE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • With this APAR the following functionality will be added to
    DFSMSrmm.  This support is being added to satisfy the new
    European GDPR legislation. The intent is to restrict access
    to certain data sets that have expired, but still exist on
    tape volumes that have yet to be scratched.  After installing
    the APAR it will be possible for RMM to prohibit reading or
    writing to all data sets that have expired, and are no longer
    retained by a Vital Record Specification.  This new function
    will also allow access to be manually blocked for individual
    data sets using the CHANGEDATASET subcommand with the
    FORCEEXPIRE operand in DFSMSrmm.
    
    
    
    
    ADDITIONAL KEYWORDS:
    GENERAL DATA PROTECTION REGULATION DATASET
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of DFSMSrmm.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * With this APAR new functionality has                         *
    * been added to RMM to provide support                         *
    * for the new European GDPR legislation.                       *
    * The intent is to restrict access to                          *
    * certain data sets that reside on tape                        *
    * volumes that have not yet been                               *
    * returned to scratch status.                                  *
    * After installing this APAR it will be                        *
    * possible for RMM to prohibit reading or                      *
    * writing all data sets that are expired,                      *
    * and are no longer retained by a Vital                        *
    * Record Specification.                                        *
    * Also, the RMM CHANGEDATASET subcommand                       *
    * has been extended with the new operand                       *
    * FORCEEXPIRE to provide users with the                        *
    * ability to manually block access to                          *
    * individual data sets.                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the applicable PTF(s)                                  *
    ****************************************************************
    This APAR provides support for blocking access to tape
    data sets based on their expiration and retention status, and
    for manually blocking and uncataloging selected data sets.
    The provided functionality is available using the DFSMSrmm
    command-line interface.
    

Problem conclusion

Temporary fix

Comments

  • The program has been enhanced to support controlling access to
    tape data sets that are expired and no longer retained by RMM
    but reside on a volume that has not yet been returned to scratch
    status.
    
    The book "DFSMSrmm Implementation and Customization Guide
    (SC23-6874)" has been updated as shown:
    
    Chapter "Using the parmlib member EDGRMMxx" has been updated:
    in the article "OPTION command syntax":
    
    | -----'--------------------------'------------>
    |     |                          |
    |     |         '-NONE-----'     |
    |     |         |          |     |
    |     +DSNEXPIRE-----------------
    |               |          |
    |               '-BLOCK----'
    
    in the article "OPTION command operands":
    
    | DSNEXPIRE(BLOCK|NONE)
    |      The DSNEXPIRE option allows for blocking access to data
    |      sets that are expired.
    |    NONE
    |       Data sets that are no longer retained and which have an
    |       expiry date in the past are still accessible until the
    |       volume on which they reside on is scratched.
    |       Data sets modified using the RMM CHANGEDATASET
    |       subcommand with the FORCEEXPIRE operand are
    |       not accessible even when DSNEXPIRE(NONE) is srt.
    |    BLOCK
    |       RMM will block access to data sets that are expired and
    |       not retained by a Vital Record Specification.  Newly
    |       created data sets that are not VRSELEXCLUDED are not
    |       blocked until VRSEL housekeeping has a chance to retain
    |       them.
    |       For NL (not labeled) tapes, a data set that is expired
    |       will be blocked even if the JCL has the wrong data set
    |       name, as long as the sequence number of the data set
    |       matches the value stored in the RMM CDS.
    |       BLP (bypass label processing) cannot be used to read or
    |       write expired data sets when DSNEXPIRE(BLOCK) is set.
    |
    |    Note:  Instead of using DSNEXPIRE(BLOCK), you can manually
    |           block selected data sets using the RMM CHANGEDATASET
    |           subcommand with the FORCEEXPIRE operand.
    |           Such data sets will show "(ForceExpire)" next to
    |           their expiration date in the RMM LISTDATASET
    |           subcommand output.
    |
    |    Default: DSNEXPIRE(NONE)
    
    
    The book "DFSMSrmm Managing and Using Removable Media
    (SC23-6873)",  Chapter "Using RMM TSO subcommands"  has
    been updated as  shown:
    
    in the article "CHANGEDATASET: Changing data set information" :
    
    | >--.----------.--.----------------.---------------->
    |    |      (3) |  |                |
    |    '-FORCE----'  '-FORCEEXPIRE----'
    |                  |             (1)|
    |                  '-REMOVEEXPIRE---'
      ...
    
    |  FORCEEXPIRE
    |     Use FORCEEXPIRE to block access to a data set and
    |     uncatalog it.  The result of the uncatalog call will
    |     depend on the setting of the UNCATALOG RMM PARMLIB
    |     option.
    |
    |     UNCATALOG(NO) will prevent FORCEEXPIRE from uncataloging
    |     the data set.
    |     UNCATALOG(YES) will ensure that the FORCEEXPIRE operand
    |     uncatalogs the data set.
    |     UNCATALOG(SCRATCH) will only uncatalog data sets on
    |     scratch volumes.
    |
    |     FORCEEXPIRE will cause "(ForceExpire)" to appear next to
    |     the expiration date in the RMM LISTDATASET subcommand
    |     output.
    |
    |     All attempts to read or write to the data set will fail
    |     with ABEND S413.
    |
    |     For NL (not labeled) tapes, a data set that has the
    |     FORCEEXPIRE bit set will be blocked even if the JCL has
    |     the wrong data set name, as long as the sequence number
    |     of the data set matches that stored in the RMM CDS.
    |     BLP (bypass label processing) cannot be used to read or
    |     write data sets that have the FORCEEXPIRE bit set.
    |
    |     FORCEEXPIRE does not change the actual expiration date
    |     of the data set or the volume on which it resides.
    |     FORCEEXPIRE can affect the retention of the volume if
    |     WHILECATALOG is used.
    |
    |     The RMM CHANGEDATASET subcommand specified with the
    |     REMOVEEXPIRE and FORCE operands is the only way
    |     to regain access to the data set after a FORCEEXPIRE.
    |     You can specify the REMOVEEXPIRE operand if you are
    |     authorized to use the FORCE operand.
    
    
    ...
    
    | REMOVEEXPIRE
    |     Resets the FORCEEXPIRE flag for the data set, allowing
    |     it to be accessed.  You must specify the FORCE operand
    |     with REMOVEEXPIRE.
    
    
    Chapter DFSMSrmm return codes and reason codes"  has
    been updated as  shown:
    
    in the table "DFSMSrmm reason codes":
      +--------+--------+---------+---------+------------------+
      | Return | Reason | Message | Issuing | Description      |
      | code   | code   | number  | command |                  |
      +--------+--------+---------+---------+------------------+
    | | 04     | 289    | EDG3377 | CD      | Data set already |
    | |        |        |         |         | has FORCEEXPIRE  |
    | |        |        |         |         | set.             |
    | |        |        |         |         | Uncatalog not    |
    | |        |        |         |         | attempted.       |
      +--------+--------+---------+---------+------------------+
    
    Chapter "DFSMSrmm REXX variables"  has
    been updated as  shown:
    
    in the table "TSO subcommand variables by name", for
    release V2R3:
      +-----------+-------------+-----------+------------------+
      | Variable  | Abbrev      | Contents  | Format           |
      | Name      | Subcommands |           |                  |
      +-----------+-------------+-----------+------------------+
      | EDG@CTRT  | LD          | Catalog   | blank,           |
      |           | LV          | Retained  | 'KeptByCatalog', |
      |           |             |           | 'UntilExpired',  |
    | |           |             |           | 'ForceExpire'    |
      +-----------+-------------+-----------+------------------+
    
     ...
     in the table "TSO subcommand variables by name", for
     releases V2R1, V2R2, and V2R3:
      +-----------+-------------+-----------+------------------+
    | | EDG@DSXP  | LC OPT      | DSNEXPIRE | NONE,            |
      |           |             | option    | BLOCK            |
      +-----------+-------------+-----------+------------------+
    
    
    
    The book "z/OS DFSMSrmm Application Programming Interface
    (SC23-6872)",  Chapter "Processing the output data in the
    output buffer"  article "LISTCONTROL structured field
    introducers" has been updated as  shown:
    
      <NWCT - Default WHILECATALOG, RM=: 1, bin(8) >
      <CTLD - Catalog Days : 4, bin(31) >
    | <DSXP- DSNEXPIRE: 1, bin(8) >
      <End OPTION Group>
    
    Appendix "Structured field introducers for subcommand
    output data", article "Structured field introducers for
    subcommand output data" has been updated as shown:
    For release V2R3:
      +----------+------+-------+-------+-------------+--------+
      | SFI      | SFI  | SFI   | SFI   | Data        | Sub-   |
      | Number   | Name | Length| Data  | Description | command|
      |          |      |       | Type  |             |        |
      +----------+------+-------+-------+-------------+--------+
      | X'81A400'| CTRT | 9     | Binary| Catalog     | LD,LV, |
      |          |      |       | (8)   | Retained    | SD(e), |
      |          |      |       |       | status for  | SV(e)  |
      |          |      |       |       | data set    |        |
      |          |      |       |       | or volume   |        |
      |          |      |       |       |             |        |
      |          |      |       |       | 0=Off       |        |
      |          |      |       |       | 1=          |        |
      |          |      |       |       | KeptByCatlg |        |
      |          |      |       |       | 2=          |        |
      |          |      |       |       | UntilExpired|        |
    | |          |      |       |       | 3=          |        |
    | |          |      |       |       | ForceExpire |        |
      +----------+------+-------+-------+-------------+--------+
    For releases V2R1, V2R2, and V2R3:
      +----------+------+-------+-------+-------------+--------+
    | | X'82B500'| DSXP | 9     | Binary| DSNEXPIRE   | LC     |
    | |          |      |       | (8)   | 0=None      |        |
    | |          |      |       |       | 1=Block     |        |
      +----------+------+-------+-------+-------------+--------+
    
    
    Appendix "Structured field introducers by subcommand"
    has been updated as shown:
      +-------------+---------------------------------------------+
      | Subcommand  | Structured field introducers                |
      +-------------+---------------------------------------------+
      | LISTCONTROL | ACCT AUD BLP BKPP CATS CDS CMDD CMDO        |
      | OPTION      | CRP DRP DSPD                                |
      |             | DSPM                                        |
    | |             |      DSXP                                   |
      |             |           DTE EXRB GDGC GDGD IPL JDS JRNF   |
      |             | JRNT LCT LCTK                               |
      |             | LRED MCAT MDS MEDN MOP MRP MSGF MVBY OPM NOT|
      |             | PDAC PDA PDAC PDAL PDAS PSFX PSF2 RC RCF    |
      |             | RM RTBY RUBSID SLM SMP SMUC SMUE SMUS SOSP  |
      |             | SRHN SRIP SRPN SRTKSSM SSTY TVXD TVXP UNC   |
      |             | VACT VCHG VDRA VDRC VDRPVMIN VREA VREC      |
      |             | VREP VRJ VRSL XDRA XDRC XDRP                |
      +-------------+---------------------------------------------+
    
    
    The book "System Messages Volume 5 (EDG - GFS) (SA38-0672)" has
    been extended with the new messages EDG3377I, EDG4066I, and
    EDG4067I:
    
    | EDG3377I FORCEEXPIRE FOR DATA SET IS ALREADY SET
    |
    | Explanation:  The FORCEEXPIRE flag for the
    | data set has already been set previously using the
    | RMM CHANGEDATASET subcommand with the FORCEEXPIRE operand.
    |
    | System action: Uncatalog processing is not performed.
    | Operator response: None.
    | Source: DFSMSrmm
    | Detecting Module: EDGMTSO
    | Routing Code: 11
    | Descriptor Code: 7
    
    
    | EDG4066I VOLUME volser REJECTED. DATA SET BLOCKED BY
    |   DSNEXPIRE.  IT IS EXPIRED AND NOT RETAINED BY A VITAL
    |    RECORD SPECIFICATION.
    |
    | Explanation: The DSNEXPIRE(BLOCK) DFSMSrmm option is in
    | effect. Reading or writing data sets that are not retained
    | and the expiration date for which has passed is prohibited.
    |
    | In the message text:
    |     volser
    |            The volume serial number of the requested volume.
    |
    | System action: If DFSMSrmm is operating in warning
    | mode, the volume specified in this message can be
    | used and DFSMSrmm issues message EDG4004I. If
    | DFSMSrmm is operating in protect mode, DFSMSrmm
    | issues message EDG4005E or EDG4006E.
    |
    | Operator response: None.
    | Source: DFSMSrmm
    | Detecting Module: EDGSOCE
    | Routing Code: 2,3,11
    | Descriptor Code: 3
    
    
    | EDG4067I VOLUME volser REJECTED. DATA SET BLOCKED BY
    |          FORCEEXPIRE
    |
    | Explanation: You attempted to access a data set that was
    | blocked using the RMM CHANGEDATASET subcommand with the
    | FORCEEXPIRE operand.  Reading or writing such data sets is
    | prohibited.
    |
    | In the message text:
    |  volser
    |      The volume serial number of the requested volume.
    |
    | System action: If DFSMSrmm is operating in warning
    | mode, the volume specified in this message can be
    | used and DFSMSrmm issues message EDG4004I. If
    | DFSMSrmm is operating in protect mode, DFSMSrmm
    | issues message EDG4005E or EDG4006E.
    |
    | Operator response: None.
    |
    | System programmer response:
    | If you need to regain access to the data set, run the
    | RMM CHANGEDATASET subcommand specifying both the REMOVEEXPIRE
    | and FORCE operands.
    | Source: DFSMSrmm
    | Detecting Module: EDGSOCE
    | Routing Code: 2,3,11
    | Descriptor Code: 3
    |
    |
    
    
    &#215;**** PE18/05/22 FIX IN ERROR. SEE APAR OA55518  FOR DESCRIPTION
    &#215;**** AE18/05/22 FIX IN ERROR. SEE APAR OA55518  FOR DESCRIPTION
    &#215;**** PE18/06/01 FIX IN ERROR. SEE APAR OA55518  FOR DESCRIPTION
    &#215;**** PE18/09/28 FIX IN ERROR. SEE APAR OA56204  FOR DESCRIPTION
    &#215;**** PE18/09/27 FIX IN ERROR. SEE APAR OA56204  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA54871

  • Reported component name

    DFSMSRMM

  • Reported component ID

    5695DF186

  • Reported release

    220

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2018-02-08

  • Closed date

    2018-04-27

  • Last modified date

    2018-10-19

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

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

    UA96063 UA96064 UA96065

Modules/Macros

  • EDGXMLAP EDGXMOV  EDGTSO   EDGMFIC  EDGXHINT EDGDOC   EDGMTSO
    EDGXHCLL EDGMCMD  EDGOECM  EDGDATE  EDGMTAB  EDGSOCE  EDGTSORT
    EDGRMMCD EDGXSF   EDGAPISR EDGMFIO  EDGPARM  EDGXSFT  EDGXSFB
    

Publications Referenced
SC23687400SC23687300SC23687200SA38067200SC23687401
SC23687301SC23687201SA38067201SC23687430SC23687330
SC23687230SA38067230   

Fix information

  • Fixed component name

    DFSMSRMM

  • Fixed component ID

    5695DF186

Applicable component levels

  • R210 PSY UA96064

       UP18/05/05 P F805  

  • R220 PSY UA96065

       UP18/05/05 P F805  

  • R230 PSY UA96063

       UP18/05/05 P F805  

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:
19 October 2018