IBM Support

OA57172: NEW FUNCTION: FLASHCOPY ONTO GLOBAL MIRROR PRIMARIES

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 systems.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * New Function: FlashCopy onto Global Mirror primary devices   *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This PTF is in support of FlashCopy onto Global Mirror
    primaries on the D/T2107 storage system.
    
    When enabled, Global Mirror primary volumes will be considered
    capable of becoming FlashCopy target volumes.
    
    To fully enable this support, you must install the appropriate
    PTF for OA57173 along with all other PTFs required during the
    installation of OA57173 PTF
    
    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 What?s new section of
    the DS8000 knowledge center which can be located by using the
    following website:
    https://www.ibm.com/support/knowledgecenter/ST5GLJ
    Select version 8.5.4
    Select What?s new
    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 publication will contain the changes
      z/OS DFSMS Advanced Copy Services (SC23-6847)
      z/OS MVS System Messages, Vol 1 (AMA-AOM) (SC38-0668)
    ****************************************************************
    z/OS DFSMS Advanced Copy Services (SC23-6847)
    
    New volume incapable and preserve mirror incapable reason codes
    are added to the list of reason codes described in the ANTQFRVL
    macro section.
    
    When ANTRQST returns to the caller, and the RETINFO return and
    reason code are zero, and the ANTQFRVL header return code is
    zero, each volume entry has one of the following values:
    
    Add the following volume capability and reason code:
    ****************************************************************
    +---------+-----------+----------------------------------------+
    | Volume  |   Volume  |                                        |
    | Capable |   Reason  |                                        |
    +---------+-----------+----------------------------------------+
    |    0    |   26-27   | Reserved for common incapable reason   |
    |         |(x'1A-1B') | codes FlashCopy incapable, PPRC Remote |
    |         |           | Pair FlashCopy incapable, and XRC      |
    |         |           | Remote Pair FlashCopy incapable        |
    +---------+-----------+----------------------------------------+
    |    0    | 28(x'1C') | FlashCopy onto a Global Mirror target  |
    |         |           | cannot be performed because a Global   |
    |         |           | Mirror force Consistency Group is in   |
    |         |           | progress.                              |
    +---------+-----------+----------------------------------------+
    |    0    |   29-63   | Reserved for common incapable reason   |
    |         |(x'1D-3F') | codes FlashCopy incapable, PPRC Remote |
    |         |           | Pair FlashCopy incapable, and XRC      |
    |         |           | Remote Pair FlashCopy incapable        |
    +---------+-----------+----------------------------------------+
    
    Add the following Preserve Mirror reason codes:
    +---------+-----------+----------------------------------------+
    | Preserve|  Preserve |                                        |
    | Mirror  |   Mirror  |                                        |
    | Capable |   Reason  |                                        |
    +---------+-----------+----------------------------------------+
    |    0    |   26-27   | Reserved for common incapable reason   |
    |         |(x'1A-1B') | codes FlashCopy incapable, PPRC Remote |
    |         |           | Pair FlashCopy incapable, and XRC      |
    |         |           | Remote Pair FlashCopy incapable        |
    +---------+-----------+----------------------------------------+
    |    0    | 28(x'1C') | FlashCopy onto a Global Mirror target  |
    |         |           | cannot be performed because a Global   |
    |         |           | Mirror force Consistency Group is in   |
    |         |           | progress.                              |
    +---------+-----------+----------------------------------------+
    |    0    |   29-63   | Reserved for common incapable reason   |
    |         |(x'1D-3F') | codes FlashCopy incapable, PPRC Remote |
    |         |           | Pair FlashCopy incapable, and XRC      |
    |         |           | Remote Pair FlashCopy incapable        |
    +---------+-----------+----------------------------------------+
    
    z/OS MVS System Messages, Vol 1 (AMA-AOM) (SC38-0668)
    
    Changed Message:
    
    ANTF0421I FCQUERY Relationship -2
    DEVN SSID LSS CCA CU      SERIAL     ACT  MAX XC PC
      CC RV SE SEQNUM
    devn ssid lss cca cyty serialnumber  act  max xc pc
      cc rv se sequence
    RELATIONSHIP DETAIL STARTING TRACK: aaaaaaaa
    DEVICE LONG BUSY FOR CG: bbb  WRITE INHIBITED: ccc
    DEVICE IN SAFEGUARDED COPY RELATIONSHIP: www
    ----------------------------------------------------
      PARTNER    SOURCE   TARGET   S F C C P C T S F P R S R W
    LSS CCA SSID START    START    O V O A E R W E L M A G R P
    --- --- ---- -------- -------- - - - - - - - - - - - - - -
     dd  ee ffff gggggggg hhhhhhhh i j k l m n o p q r s t u v
         NO. OF TRACKS: numtrcks
         TRACKS TO COPY: trks2cpy
         ESTABL: yyyy/mm/dd hh:mm:ss
         LAST INCR:  yyyy/mm/dd hh:mm:ss
    
    
    Several fields in the query report are modified or updated.
    Only the added or modified fields are displayed here.
    
    The information displayed is as follows:
    
    act is the current number of FlashCopy relationships that the
    device has. This value is indicated in decimal format.
    Safeguarded copy relationships and safeguarded copy recovery
    relationships will be included in this number.  Safeguarded copy
    will be considered a single relationships for this value,
    regardless of the number of consistency groups that have been
    captured.
    
    www is the status of the safeguarded relationship for the
    queried volume and will contain one of the following values:
    NO
    Indicates that there is no SGC relationship.
    YES
    Volume is in a Safeguarded Copy Relationship
    
    dd is partner LSS for the relationship. If this is a source
    relationship, the partner LSS is the target LSS of the
    relationship.  If this is a target relationship, the partner
    LSS is the source LSS  of the relationship.  If this is a
    safe guarded copy relationship, the LSS display dashes ??'
    
    ee is partner channel connection address (CCA) for the
    relationship. If this is a source relationship, the partner CCA
    is the target CCA of the relationship.  If this is a target
    relationship, the partner CCA is the source CCA  of the
    relationship.  If this is a safe guarded copy relationship,
    the LSS display dashes ??'
    
    ffff is the subsystem ID for the LSS of the partner device in
    the relationship. If this is a target relationship, this is the
    SSID for the source device. If this is a source relationship,
    this is the SSID for the target device.  If this is a SGC
    relationship, the SSID will display as dashes (?----?).
    
    s is one of the following values:
    Y
    Indicates that the relationship is a SGC Active Consistency
    Group Reservation.
    N
    Indicates that the relationship is not a SGC Consistency
    Group Reservation.
    
    t represents the SGC state of the relationship entry and will be
    one of the following values:
    Y
    Indicates that this is a SGC relationship. When this field is
    'Y', the target LSS, CCA, and SSID values will display dashes
    '-' because the target of the SGC relationship is not known to
    the host nor addressable in traditional manners.  Also, when
    this field is ?Y?, the source start track address and the
    target start track address will be all zeros.
    N
    Indicates that this is not a SGC relationship.
    
    u represents the SGC recovery relationship state of the
    relationship entry and will be one of the following values:
    Y
    Indicates that this is a SGC recovery relationship
    and the target start track address will be all zeros.
    N
    Indicates that this volume is not in a SGC recovery
    relationship.
    
    v is one of the following values:
    Y
    Indicates that the relationship is in a withdraw pending state.
    N
    Indicates that the relationship is not currently in a withdraw.
    pending state
    
    numtrks is the number of contiguous tracks in this relationship.
    
    trks2cpy is the number of tracks yet to be copied for the
    relationship.
    
    ESTABL displays control unit time stamp when the relationship
    was first established.
    
    LAST INCR displays the control unit time stamp when the last
    increment was taken, if change recording was active.
    
    The data for each relationship spans three lines. The second and
    third lines are indented to differentiate from the start of a
    new relationship table entry.
    
    If there are no relationships to be displayed, the results of
    the FCQUERY displays the first five lines. Instead of
    relationship detail information after the first dashed line,
    the following message will be displayed:
    NO RELATIONSHIPS FOUND FOR SPECIFIED DEVICE OR STARTING ADDRESS
    
    Changed Message:
    
    ANTF0447E FLASHCOPY ESTABLISH DEVICE device-number IS IN AN
    INVALID STATE
    
    Explanation
    The FlashCopy establish request issued to device number
    device-number failed because the current state of the existing
    FlashCopy relationship does not allow the establish to complete.
    
    The following reason code xx will be added:
    
    26 A FlashCopy Establish command was not successful because
    Global Mirror is forcing a consistency group which prevents the
    use of FlashCopy
    
    New Message:
    ANTF0518E FLASHCOPY ESTABLISH COMMAND FAILED FOR DEVICE device.
    PRESERVE MIRROR GLOBAL MIRROR FORCE CONSISTENCY GROUP IN
    PROGRESS
    
    Explanation:
    A FlashCopy Establish request was entered as a remote or
    Preserve Mirror Required operation, but it was not successful at
    the secondary control unit because Global Mirror is forcing a
    consistency group.
    
    System action
    FlashCopy command fails.
    
    System programmer response
    Re-try the request.
    
    Source
    ESS FlashCopy
    
    
    A new FlashCopy establish reason code is added to the ANTRQST
    API.
    
    Add the following reason code after the
    RQST_FCESTABLISH_REAS_CLOUD_ERROR reason code description:
    
    RQST_FCESTABLISH_REAS_FORCE_CG          EQU 0204  X'00CC'
     *
     *   Meaning: A FlashCopy Establish Request with preserve mirror
     *   would result in a FlashCopy onto a Global Mirror target and
     *   Global Mirror force Consistency Group is in progress.
     *
     *   Action: Re-submit the command after the
     *   Global Mirror consistency group has formed.
     *
    

Temporary fix

Comments

  •  KEYWORDS: D/T2107 FLASHCPY/K GLBLMIR/K PPRC/K
    

APAR Information

  • APAR number

    OA57172

  • Reported component name

    SYSTEM DATA MOV

  • Reported component ID

    5695DF117

  • Reported release

    220

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2019-03-22

  • Closed date

    2019-09-09

  • Last modified date

    2019-10-01

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

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

    PH10073 OA57173 OA57174 OA57175 UJ00775 UJ00776 UJ00777

Modules/Macros

  • ANTFQURY ANTS4934 ANTFQMAP ANTRQSTL ANTPPMSG ANTS4931 ANTQFRVL
    ANTFESTP
    

Publications Referenced
SC236847XXSC380668XX   

Fix information

  • Fixed component name

    SYSTEM DATA MOV

  • Fixed component ID

    5695DF117

Applicable component levels

  • R240 PSY UJ00776

       UP19/09/27 P F909  

  • R230 PSY UJ00775

       UP19/09/27 P F909  

  • R220 PSY UJ00777

       UP19/09/27 P F909  

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:
01 October 2019