IBM Support

OA48709: NEW FUNCTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • New Function
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of D/T2107 storage subsystems.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: New Function: Extent Space Efficient    *
    *                      (Thin Provisioning) support for CKD     *
    *                      on z/OS                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

  • New Function:
    This PTF provides base support for Extent Space Efficient CKD
    Volumes (Thin Provisioning).
    Extent Space Efficient is the replacement on the DS8000
    family of storage controllers for the track space efficient
    FlashCopy support provided in 2007 and sunset with the
    DS8880 (R8.0) delivery.
    
    Physical space for extent space efficient volumes is allocated
    on an extent (21 cylinders) directly from the volume's extent
    pool rather than on a track by track basis from a space
    efficient repository, improving the performance of space
    efficient volumes.
    
    The new Extent Space Efficient volumes are not limited to
    FlashCopy targets and FlashCopy is not limited to NOCOPY
    Relationships like it was for Track Space Efficient.
    Also, there are no special keywords required in order to
    create FlashCopy or PPRC relationships to Extent Space
    Efficient volumes.
    
    
    Exploitation of this new function on the D/T2107 storage
    subsystem requires this PTF and a microcode (LMC) upgrade.
    For minimum microcode levels and current maintenance required
    to exploit this new function, refer to the Technical
    Information section of announcement letter ENUS116-072 which
    can be located by using the following website:
    http://www-01.ibm.com/common/ssi
    Enter Type of content: Announcement Letter
    and Keywords: ENUS116-072
    Note that if you have never used this website, you may need
    to do some initial setup, like language selection.
    Or, you can contact IBM Hardware support for the current
    D/T2107 LMC.
    Installation of this PTF will preserve existing function when
    run with existing supported LMC.
    
    
    The following updates will be reflected in a future revision
    of z/OS MVS System Messages, Volume 1(ABA-AOM)(SA38-0668):
    The following Return and reason codes will be added:
    RQST_PESTPAIR_VOL_TYPE_ERROR      EQU 7223      X'1C37'
    *
    *   Meaning:  For a PESTPAIR request a System Data
    *   Mover request handler detected an error.
    *   The combination of the volume types specified
    *   are restricted from participating in a Copy
    *   Services relationship with the installed level of microcode.
    *   The reason code will indicate the specific
    *   restriction.
    *
    *   Action:  Take the action shown in the reason code
    *   documentation. For any reasons not listed,
    *   contact your hardware representative for the
    *   reason that the command failed.
    *
    RQST_PESTPAIR_VOL_TYPE_REAS1      EQU 0001  X'0001'
    *
    *   Meaning: Establish Peer-to-Peer Remote Copy Pair
    *   specified a restricted volume type combination.
    *   The specified secondary volume is an Extent Space
    *   Efficient volume.
    *
    *   Action: Specify volumes of a compatible type.
    *
    RQST_PESTPAIR_VOL_TYPE_REAS3      EQU 0003  X'0003'
    *
    *   Meaning: Establish Peer-to-Peer Remote Copy Pair
    *   specified a restricted volume type combination.
    *   The specified primary volume is an Extent Space
    *   Efficient volume.
    *
    *   Action: Specify volumes of a compatible type.
    *
    
    The following reason code will be added to return code
    7705 (X'1E19') in table 1 of section "System data mover
    return and reason codes"
    
    (X'0F9F') The Space Efficient Repository or Space Efficient
    Extent Pool is out of space.
    
    The following new messages will be added:
    
    ANTP0278E PPRC CESTPAIR COMMAND FAILED FOR DEVICE DEVICE-INFO.
    RESTRICTED VOLUME TYPE COMBINATION, RSN= xx
    Explanation: FCESTABL command failed because the combination of
    the volume types specified are restricted from participating in
    a Copy Services relationship with the installed level of
    microcode.
    Reason code xx indicates the reason for the error:
    01 Establish Peer-to-Peer Remote Copy Pair specified a
    restricted volume type combination. The specified secondary
    volume is an Extent Space Efficient volume.
    03 Establish Peer-to-Peer Remote Copy Pair specified a
    restricted volume type combination. The specified primary
    volume is an Extent Space Efficient volume.
    Source: Peer-To-Peer Remote Copy (PPRC).
    System action: CESTPAIR command fails.
    System programmer response: Refer to the reason code
    description in the explanation.
    
    ANTF0560E FLASHCOPY WITHDRAW RELEASE ALLOCATED TARGET SPACE
    FAILED
    Explanation: The FlashCopy WITHDRAW  command  completed
    successfully but the release allocated target space
    failed due to a condition detected in the Space Efficient
    Repository or Space Efficient Extent Pool.
    
    System action: Command processing ends.
    Operator response: None.
    System programmer response: To release the allocated target
    space you can reinitialize the target volume using the INIT
    command.
    
    ...
    The following updates will be reflected in a future revision
    of the z/OS DFSMS Advanced Copy Services manual (SC23-6847):
    
    Mentions of "Space Efficient" will be changed to
    "Track Space Efficient" or "Extent Space Efficient" where
    appropriate
    
    New section on volume types will be added with the following
    text
    
    Volume Types
    Standard volumes are volumes that have all physical storage
    allocated to them at the time that the volume is defined.
    Standard volumes are also known as Fully Provisioned volumes
    (FP).
    
    Track Space Efficient (TSE) volumes are volumes that have no
    physical space allocated to them until the first write is done
    to the volume.  The physical space is allocated to the volume
    in tracks from the Space Efficient repository, which is a
    separate volume, defined in each extent pool, used only for TSE
    volume physical space, and not accessible directly from any
    host.  TSE volumes will be phased out with the introduction of
    ESE volumes.
    
    Extent Space Efficient (ESE) volumes, also commonly called
    Thin Provisioned (TP) volumes, will have no physical space
    allocated to them until the first write is done to the
    volume.  Physical space is allocated on demand to the volume
    in extents (21 cylinders at a time) directly from the extent
    Pool where the volume is defined, rather than on a track
    by track basis from a space efficient repository, improving
    the performance of space efficient volumes. ESE volumes differ
    From TSE volumes in behavior as they are not limited to only
    Being FlashCopy targets and when used for FlashCopy, the
    Relationships are not limited to NOCOPY.  There are no
    special keywords required in order to create FlashCopy or PPRC
    relationships with Extent Space Efficient volumes.
    
    
    The following update will be made to Appendix C and D
    describing the existing SPACEREL keyword
    
    , SPACEREL=spacerel | NO
    This parameter is the name (RS-type) or address in register
    (2)-(12) of a three-character field that specifies whether
    the space-efficient volumes are released. This keyword applies
    to both Track Space Efficient and Extent Space Efficient
    volumes  The specified character value is left-justified
    and padded on the right with blanks.
    
    NO Indicates that the space is not released if
    the volume is space efficient. This is the default.
    
    
    YES Indicates that, if the target volume is a space-efficient
    volume, when the withdraw is complete, any physical space for
    the space efficient volume is released.
    
    Note:
    1. If YES is specified and the target is not a space-efficient
     volume, the SPACEREL keyword is ignored.
    2. If the request with SPACEREL(YES) is issued to a simplex
    volume that is an track space-efficient volume, any physical
    space for the volume is released.
    3. If the request with SPACEREL(YES) is issued to a simplex
    volume that is an extent space-efficient volume, physical
    space will not be released.
    4. The allocated space is released asynchronously so may not be
    reported immediately.
    5. If it is a sub-volume request, and the controller does
    not support partial volume space release, this keyword will
    be ignored.
    6. If it is a sub-volume request, and the controller supports
    partial volume space release, space aligned on an extent
    boundary will be released.
    
    
    The following change affects PPRC CQUERY:
    
    A new PPRC suspend state was added as part of this support.
    This new state will be reflected in the formatted CQUERY volume
    report. The section "Querying PPRC volumes" under
    "Fields in formatted output"  will be updated to include a new
    value of "n" = 11
    That value of n
    (11) Copy is suspended due to secondary device detecting media
    errors.
    
    KEYWORDS: D/T2107 FLASHCPY/K GLBLMIR/K PPRC/K
    

APAR Information

  • APAR number

    OA48709

  • Reported component name

    SYSTEM DATA MOV

  • Reported component ID

    5695DF117

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-19

  • Closed date

    2016-07-18

  • Last modified date

    2016-08-02

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

    OA48707

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

    UA82287 UA82288

Modules/Macros

  • ANTDRVRS ANTFQMAP ANTFQURY ANTPADPR ANTPCQRY
    ANTPFQRY ANTPPMSG ANTPPMS2 ANTPQMAP ANTPQMP2 ANTRQSTL ANTS4906
    ANTS4919 ANTS4933 ANTS6003
    

Publications Referenced
SA380668XXSC236847XX   

Fix information

  • Fixed component name

    SYSTEM DATA MOV

  • Fixed component ID

    5695DF117

Applicable component levels

  • R210 PSY UA82287

       UP16/07/27 P F607

  • R220 PSY UA82288

       UP16/07/27 P F607

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:
02 August 2016