OA52541: NEW FUNCTION - EDM VOLUME ATTRIBUTE SUPPORT

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• EDM roll-down to lower releases
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DFSMSrmm users that use tapes controlled *
  *                 by an External Data Manager.                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFSMSrmm provides an additional         *
  *                      protection for tapes created by         *
  *                      programs that provide their own tape    *
  *                      management. Such tapes are referred as  *
  *                      EDM-managed, that means controlled by   *
  *                      External Data Manager. This additional  *
  *                      protection affects the DFSMShsm,        *
  *                      DFSMSdfp OAM and IBM Spectrum Protect   *
  *                      components by preventing tapes from     *
  *                      being accidentally released by users    *
  *                      they do not belong to.                  *
  ****************************************************************
  * RECOMMENDATION: Apply the applicable PTF(s).                 *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

• The program has been changed to give an additional protection
  for tapes created by programs that provide their own tape
  management.
  
  ==============================================================
  "z/OS DFSMSrmm Implementation and Customization Guide
  (SC23-6874)" changes
  ==============================================================
  
  1. Chapter "Using the parmlib member EDGRMMxx", topic "Defining
  system options: OPTION", figure "Parmlib member EDGRMMxx OPTION
  command syntax" has been changed to add the diagram for
  the EDM operand.
  
  |>--+-------------------------+--+-----------------+---- >
  |   |         |-MASTER DD-|   |  |      |--NO--|   |
  |   |-DSNAME(-|-----------|-)-|  |-EDM(-|------|-)-|
  |             |-name------|             |--YES-|
  
  2. Chapter "Using the parmlib member EDGRMMxx", topic "Defining
  system options: OPTION", subtopic "OPTION command operands"
  has been changed to add the description of the EDM operand and
  its values.
  
  |EDM(NO | YES)
  
  |Specifies this operand to control whether the dynamic setting
  |of the volume EDM attribute occurs.
  
  |NO     Specify NO to avoid dynamic setting of the volume EDM
  |attribute at OPEN time when a volume is written by the programs
  |ANZSRVR, ANRSERV, ARCCTL, ARCWCTL, CBROAM, DSMSERV unless
  |a non-permanent expiration date is specified in the DD
  |statement. All other EDM functions (ineligibility for
  |expiration, the dynamic resetting of the volume EDM attribute,
  |possibility to set and reset the attribute via RMM
  |CHANGEVOLUME, disability to release a EDM-managed volume)
  |are in effect despite the operand value.
  
  |YES    Specify YES to allow dynamic setting of the volume EDM
  |attribute. It occurs at OPEN time when a volume is written by
  |the programs ANZSRVR, ANRSERV, ARCCTL, ARCWCTL, CBROAM, DSMSERV
  |unless a non-permanent expiration date is specified in the DD
  |statement.
  
  |Default: EDM(NO).
  
  3. Chapter "Creating inventory management reports", topic
  "Running expiration processing" has been change in
  the following passage:
  
   Identifies volumes not required for vital records that
  |not held by the HOLD attribute or not having the EDM attribute
  |set on, that are ready to expire by checking the expiration
   date and seeing if the volume holds any data sets that are
   kept by catalog status.
  
  4. Chapter "Performing inventory management", topic "How
  expiration processing works" has been changed
  in the following passages:
  
   Expiration processing can be either on all volumes or a subset
   based on the EXPROC command in the SYSIN file. DFSMSrmm checks
   the expiration date for volumes not retained by a vital record
  |specification, not held by the HOLD attribute and not having
  |the EDM attribute set on. If the expiration date has been
   reached, the volume does not contain any data sets that are
   kept by their catalog status, and the EXPDTDROP limit and
   action settings do not require the volume to be retained,
   DFSMSrmm changes the volume status to pending release.
  
   When a data set is no longer retained by a vital record
   Specifically, DFSMSrmm releases the volume on which the data
   set resides only if no data set on the volume is retained by
  |a vital record specification, the volume is not held by the
  |HOLD attribute and not having the EDM attribute set on. If
   you use the RMM ADDVRS RELEASE(EXPIRYDATEIGNORE)
   operand, DFSMSrmm ignores the volume expiration date and uses
   information in a vital record specification to control
   retention.
  
  ============================================================
  "z/OS DFSMSrmm Managing and Using Removable Media
  (SC23-6873)" changes
  ============================================================
  
  1. Chapter "Getting started with DFSMSrmm",
  topic "Using volumes". The following addition subtopic has
  been added in the end of the topic.
  
  |"Using tapes created by programs providing their own tape
  |management"
  
  |DFSMSrmm provides an additional protection for tapes created
  |by programs that provide their own tape management. Such tapes
  |are referred as EDM-managed, that means controlled by External
  |Data Manager. This additional protection affects the DFSMShsm,
  |DFSMSdfp OAM and IBM Spectrum Protect components by preventing
  |tapes from being accidentally released by users they do not
  |belong to. This includes:
  |v  Setting of the special EDM volume attribute at
  |       the OPEN time when a volume is written by the programs
  |       ANZSRVR, ANRSERV, ARCCTL, ARCWCTL, CBROAM, DSMSERV and
  |       the expiration date specified in the DD-statement is
  |       1999/365, 1999/366 or it is not specified at all.
  |v  The ability to set and reset the EDM attribute with
  |       the RMM CHANGEVOLUME subcommand.
  |v  Resetting of the EDM attribute when a volume is purged
  |       via DFSMSrmm EDGTVEXT or EDGDFHSM programming interface.
  |v  Considering the volumes with the EDM attribute not to
  |       be eligible for DFSMSrmm expiration processing.
  
  
  2. Chapter "Defining your resources using the DFSMSrmm ISPF
  dialog", topic "Defining volumes", subtopic "Rules for
  changing volume information", article "Changing volume
  information based on volume status" has been changed as
  follows:
  
  These operands can be used only if the volume is in master or
  user status.
     ACCESS
     ADDUSERS
     COMPACTION
     DELUSERS
     DESCRIPTION
     DSNAME
  |  EDM/NOEDM
     EXPDT
     EXPTM
     FEATCD
  . . . . . .
  
  3. Chapter "Defining your resources using the DFSMSrmm ISPF
  dialog", topic "Defining volumes", subtopic "Reclaiming
  volumes from pending status or scratch status" has been
  changed as follows:
  
  You must have CONTROL access to the STGADMIN.EDG.MASTER
  resource to change these operands:
     ASDATE
     ASTIME
     AUTOMOVE
     BIN
     CONFIRMMOVE
     CONTAINER
     CRDATE
     CRSYSID
     CRTIME
  |  EDM/NOEDM
     EJECT
     HOME
     LOANLOC
     LOCATION
  . . . . . .
  
  4. Chapter "Requesting and releasing volumes", topic
  "Releasing volumes" has been changed as follows:
  
   A master volume or user volume defined to DFSMSrmm is
   eligible for release when you run expiration processing
   and DFSMSrmm determines that:
    v     All data sets residing on the volume have expired.
    v     The expiration date set for the volume has been
          reached or you have requested that DFSMSrmm should
          ignore the expiration date. You can request that
          DFSMSrmm should ignore the expiration date by
          specifying the RMM ADDVRS RELEASE(EXPIRYDATEIGNORE)
          operand.
    v     Neither the volume nor any of the data sets on
          the volume are being retained by one or more
          vital record specifications.
    v     The volume is not held by its HOLD attribute.
  | v     The volume is not kept by its EDM attribute.
  
  5. Chapter "Using RMM TSO subcommands", topic
  "CHANGEVOLUME: Changing volume information", suptopic
  "Format" has been changed to add EDM and NOEDM operands
  to the CHANGEVOLUME diagram.
  
  |>-----+-----------+-- >
  |      |    (1) (4)|
  |      |---EDM-----|
  |      |    (1) (4)|
  |      |---NOEDM---|
  
  6. Chapter "Using RMM TSO subcommands", topic
  "CHANGEVOLUME: Changing volume information", suptopic
  "Parameters" has been changed to add the descriptions
  for the EDM and NOEDM operands.
  
  |EDM
  |   Use the EDM (External Data Manager) operand to mark
  |   the volume as EDM-managed. Setting the EDM
  |   attribute prevents the volume from being expired
  |   during DFSMSrmm expiration processing.
  |   Authorization requires CONTROL access to
  |   STGADMIN.EDG.MASTER. The EDM operand is only
  |   valid for non-scratch, non-pending release
  |   volumes.
  |   The RETAINBY(SET) option does not consider
  |   the EDM attribute; each volume needs to be set
  |   to EDM-managed separately.
  |NOEDM
  |   Use the NOEDM operand to reset the EDM attribute.
  |   EDM and NOEDM are mutually exclusive and can be
  |   applied to volumes with both EXPDT and VRSEL
  |   retention methods.
  |   When the External Data Manager calls the
  |   EDGTVEXT or EDGDFHSM exit to release the tape,
  |   the EDM attribute is reset.
  |   Be aware that resetting the EDM attribute
  |   for a volume that is still controlled  by
  |   the External Data Manager may eventually
  |   cause data loss because DFSMSrmm will be
  |   allowed to release the volume earlier than
  |   expected.
  
  7. Chapter "Using RMM TSO subcommands", topic
  "DELETEVOLUME: Deleting volume information",
  subtopic "Purpose" has been changed in
  the following passage:
  
  |Note: If the volume HOLD or EDM attribute
  has been set for the volume, DFSMSrmm will
  not release the volume.
  
  8. Chapter "Using RMM TSO subcommands", topic
  "DELETEVOLUME: Deleting volume information",
  subtopic "Parameters" has been changed in
  the following passage:
  
  RELEASE
     Specifies releasing the volume according
     to the release actions set for the volume.
     You can use RELEASE only for logical
     and physical volumes for which the volume
  |  HOLD or EDM attribute has not been set.
  
  9. Chapter "DFSMSrmm REXX variables", table
  "TSO subcommand variables by RMM subcommand"
  has been changed to add the EDG@EDM variable
  to the LISTCONTROL OPTION and LISTVOLUME VOL
  rows.
  
  10. Chapter "DFSMSrmm REXX variables", table
  "TSO subcommand variables by name" has been
  changed to add a new variable.
  
  ------------------------------------------------------
   Variable | Abbrev      | Contents      | Format
   Name     | Subcommands |               |
  ----------|-------------|---------------|-------------
  |EDG@EDM  | LC, LV      | EDM attribute | 1 character:
  |         |             |               | N or Y
  ------------------------------------------------------
  
  ====================================================
  "z/OS DFSMSrmm Application Programming
  Interface (SC23-6872)" changes
  ====================================================
  
  1. "Appendix A: Structured field introducers (SFIs)",
  table "Structured field introducers for subcommand
  output data" has been changed to add the new SFI:
  
  SFI number       X82D700,
  SFI Name         EDM
  SFI Length       9
  SFI Data Type    Bynary(8)
  Data Description 0  EDM=N
                   1  EDM=Y
  Subcommand       LC OPT, LV VOL, SV(e)
  
  2. "Appendix B. Structured field introducers by
  subcommand", table "Structured field introducers
  by subcommand" has been changed to add EDM to
  the LISTCONTROL OPTION and LISTVOLUME rows.
  
  ===============================================================
  "z/OS System Messages Volume 5 (EDG - GFS) (SA38-0672)" changes
  ===============================================================
  
  Chapter "EDG Messages", topic "EDG Messages" has been changed
  to add EDM to the EDG3023E message explanation:
  
   EDG3023E VOLUME IS PENDING RELEASE
   Explanation: Either the RMM DELETEVOLUME subcommand specified
   with the RELEASE operand failed because the volume to be
   deleted is already released, or the RMM CHANGEVOLUME subcommand
  |specified a storage location, the HOLD or EDM operand and
   the volume is already released.
   System action: The request fails.
   Operator response: None.
   Programmer response: Check to see that you are processing
   the correct volume.
   Source: DFSMSrmm
   Module: EDGMTSO
   Routing code: 11
   Descriptor code: 7
  

APAR Information

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

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

  UA92173 UA92174 UA92175 UA92176

Modules/Macros

• EDGAUTH  EDGDOC   EDGHC21S EDGHC210 EDGHT11V
  EDGHT110 EDGHT320 EDGHT410 EDGMTAB  EDGMTSO  EDGPARM  EDGPC200
  EDGPT110 EDGPT310 EDGPT410 EDGRFSAR EDGRMMCV EDGRTCHA EDGRTREL
  EDGSOCE  EDGSVREC EDGTSO   EDGT11   EDGXHCLL EDGXMLAP EDGXSF
  EDGXSFT  EDGXSFTX
  

Fix information

• Fixed component name

  DFSMSRMM

• Fixed component ID

  5695DF186

Applicable component levels

• R21K PSY UA92174

     UP17/07/08 P F707

• R210 PSY UA92173

     UP17/07/08 P F707

• R22K PSY UA92176

     UP17/07/08 P F707

• R220 PSY UA92175

     UP17/07/08 P F707

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.