IBM Support

OA50355: POSSIBLE OVERWRITE OF DATA WHEN OPENRULE NORMM IGNORE ANYUSE IS SPECIFIED AND THE WRONG VOLUME IS MOUNTED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When EDGRMMXX contains an OPENRULE for TYPE(NORMM) with
    IGNORE(ANYUSE) the volume validation to check that the
    mounted volume is the requested volume is bypassed. In
    the case where a volume would normally be rejected with
    a label error or prompted for the correct volser to be
    mounted, with this combination of parm settings RMM allows
    the mount. A subsequent write can then overwrite existing
    data on the tape volume that was incorrectly mounted.
    Additional Keywords:
      DFSMSrmm DFRMM RMM DATALOSS
    

Local fix

  • Mount the requested volume.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DFSMSrmm users using the OPENRULE        *
    *                 parmlib command to ignore volumes.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: When OPENRULE for TYPE(NORMM) with      *
    *                      IGNORE for a specific mount request     *
    *                      is in effect, an incorrect volume       *
    *                      mounted by mistake for a specific       *
    *                      mount request may be overwritten,       *
    *                      while in this case the volume should    *
    *                      be rejected and the operator should     *
    *                      be prompted to mount the correct        *
    *                      volser.                                 *
    ****************************************************************
    * RECOMMENDATION: Apply the applicable PTF(s).                 *
    ****************************************************************
    The program does not provide correct processing in this case.
    

Problem conclusion

  • The problem has been fixed.
    

Temporary fix

  • *********
    * HIPER *
    *********
    ++APAR FIX FOR R210 IS AVAILABLE UPON REQUEST.
    APPLY THE PTF WHEN AVAILABLE.
    

Comments

  • ×**** PE17/09/14 FIX IN ERROR. SEE APAR OA53707  FOR DESCRIPTION
    ×**** PE17/08/22 FIX IN ERROR. SEE APAR OA53707  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA50355

  • Reported component name

    DFSMSRMM

  • Reported component ID

    5695DF186

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-22

  • Closed date

    2016-07-26

  • Last modified date

    2018-04-20

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

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

    UA82308 UA82315 UA82316

Modules/Macros

  • EDGIX100
    

Fix information

  • Fixed component name

    DFSMSRMM

  • Fixed component ID

    5695DF186

Applicable component levels

  • RD10 PSY UA82308

       UP16/08/02 P F608 Ž

  • R210 PSY UA82315

       UP16/08/02 P F608 Ž

  • R220 PSY UA82316

       UP16/08/02 P F608 Ž

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

Document Information

Modified date:
20 April 2018