IBM Support

PH11538: RECOVERY EXPERT 3.2 - MAY 2019 PTF

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1) Generic message ARYS118E is replaced by more specific
    messages.
    2) Miscellaneous ISPF UI fixes for System Level Backups and
    Disaster Recovery
    3) Miscellaneous fixes for Combined System Level Backups.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 Recovery Expert for z/OS.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Variable '&USERID' in the 'Data Set     *
    *                      Name Prefix' value have to be replaced  *
    *                      by the actual id of current user.       *
    *                      TCZ generated job ARYCF1UP contains     *
    *                      incorrect 'SET DB2 SSID = <data sharing *
    *                      group name>' statement for data sharing *
    *                      group members instead of 'SET DB2 SSID  *
    *                      = <subsystem name>' if "Use DB2 group   *
    *                      attach" is set to Yes.                  *
    *                                                              *
    *                      The problem may occur during the        *
    *                      Disaster Recovery based on Image Copies *
    *                      and performed for Db2 V12R1M100.        *
    *                      Utility incorrectly looks for           *
    *                      DSNDB06.SYSCOPY tablespace not existing *
    *                      in Db2 V12.  The "On Disk" parameter    *
    *                      on the "Restore System Display" panel   *
    *                      remains "Yes" after completion of the   *
    *                      offload, but there is no backup on disk *
    *                      because Flashcopy Nocopy is used.       *
    *                                                              *
    *                      Miscellaneous problems with incremental *
    *                      System Level Backup:                    *
    *                                                              *
    *                      #1 First full SLB with START-           *
    *                      INCREMENTAL works fine, but then        *
    *                      incremental SLB fails with error        *
    *                      message:                                *
    *                                                              *
    *                      ARYS418E - An Incremental FlashCopy is  *
    *                      requested but there is no existing      *
    *                      incremental relationship.               *
    *                                                              *
    *                      #2 SLB profile and used copypool may    *
    *                      have different incremental status after *
    *                      HSM failure.                            *
    *                      For example, after the HSM failure,     *
    *                      copypool is deleted via FRDELETE        *
    *                      command (outside of the product).       *
    *                      The first backup after that, leads to   *
    *                      the creation of a copypool with         *
    *                      INCREMENTAL=N, but the profile status   *
    *                      is still incremental.                   *
    *                                                              *
    *                      Command "F CATALOG" may be repeatedly   *
    *                      issued multiple times and cause         *
    *                      significant problems with accessing the *
    *                      catalog.                                *
    *                      Dependent objects may be missed from    *
    *                      the Log Based Data Recovery if any      *
    *                      ALTER was performed right before the    *
    *                      DROP (in the same second).              *
    *                      System Level Backup Db2 profile with    *
    *                      WAIT_FOR_BACKGROUND_COPY parameter set  *
    *                      to S doesn't wait for the background    *
    *                      copy is finished.                       *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    Variable '&USERID' in the 'Data Set Name Prefix' value have to
    be replaced by the actual id of current user.
    TCZ generated job ARYCF1UP contains incorrect 'SET DB2 SSID =
    <data sharing group name>' statement for data sharing group
    members instead of 'SET DB2 SSID = <subsystem name>' if "Use
    DB2 group attach" is set to Yes.
    The problem may occur during the Disaster Recovery based on
    Image Copies and performed for Db2 V12R1M100. Utility
    incorrectly looks for DSNDB06.SYSCOPY tablespace not existing in
    Db2 V12.
    The "On Disk" parameter on the "Restore System Display" panel
    remains "Yes" after completion of the offload, but there is no
    backup on disk because Flashcopy Nocopy is used.
    
    Miscellaneous problems with incremental System Level Backup:
    #1 First full SLB with START-INCREMENTAL works fine, but then
    incremental SLB fails with error message:
    
    ARYS418E - An Incremental FlashCopy is requested but there is
    no existing incremental relationship.
    
    #2 SLB profile and used copypool may have different incremental
    status after HSM failure.
    For example, after the HSM failure, copypool is deleted via
    FRDELETE command (outside of the product).
    The first backup after that, leads to the creation of a copypool
    with INCREMENTAL=N, but the profile status is still incremental.
    
    Command "F CATALOG" may be repeatedly issued multiple times and
    cause significant problems with accessing the catalog.
    Dependent objects may be missed from the Log Based Data Recovery
    if any ALTER was performed right before the DROP (in the same
    second).
    System Level Backup Db2 profile with WAIT_FOR_BACKGROUND_COPY
    parameter set to S doesn't wait for the background copy is
    finished.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH11538

  • Reported component name

    DB2 REC EXPERT

  • Reported component ID

    5697H7400

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-26

  • Closed date

    2019-05-30

  • Last modified date

    2019-07-01

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

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

    UI63292

Modules/Macros

  • ARY#BKUP ARY#GIO  ARY#LSQL ARY#PDSN ARY#SMS  ARY#YCTL ARY$ADM2
    ARY$APMN ARY$BBLD ARY$BPRU ARY$BSAU ARY$BUTD ARY$CG00 ARY$CGAD
    ARY$CGGL ARY$CGSL ARY$CGUP ARY$CGXD ARY$DPRC ARY$DPRU ARY$MAIN
    ARY$OPRC ARY@BACK ARY@BAKE ARY@BAKO ARY@BAKV ARY@BLDB ARY@CGBK
    ARY@DISC ARY@IMCE ARY@IMCP ARY@IVP  ARY@IVP2 ARY@MSGS ARY@OCPR
    ARY@OCPY ARY@OFLD ARY@ORST ARY@RSTE ARY@RVSM ARY@SCPB ARY@SCPY
    ARY@SFQY ARY@SIMG ARY@SOIC ARY@SQUE ARY@YDRM ARYBABCK ARYBABIP
    ARYBABOB ARYBABOI ARYBABOS ARYBABSC ARYBABTB ARYBABTP ARYBABTS
    ARYBABUR ARYBABUT ARYBACSA ARYBADMA ARYBAICG ARYBAIDM ARYBAIPM
    ARYBALA  ARYBAMRR ARYBAOBM ARYBAOEN ARYBARPD ARYBARPS ARYBASEI
    ARYBATA  ARYBATAS ARYBATDM ARYBBADM ARYBBALS ARYBBASL ARYBBBOS
    ARYBBCAI ARYBBCDM ARYBBCFO ARYBBCK  ARYBBCLS ARYBBCNS ARYBBCOM
    ARYBBCOS ARYBBCSL ARYBBDBS ARYBBDDM ARYBBDSG ARYBBDSL ARYBBDTM
    ARYBBDTS ARYBBERS ARYBBGOA ARYBBGOC ARYBBGRJ ARYBBGRP ARYBBIDM
    ARYBBINS ARYBBIPM ARYBBIPS ARYBBISL ARYBBIST ARYBBJOB ARYBBKSG
    ARYBBLD  ARYBBLRJ ARYBBOBM ARYBBOBS ARYBBOCN ARYBBOCR ARYBBODM
    ARYBBOPS ARYBBOSC ARYBBOSV ARYBBPAS ARYBBPCA ARYBBPCJ ARYBBPCO
    ARYBBPCV ARYBBPDM ARYBBPLM ARYBBPLN ARYBBPLS ARYBBPRS ARYBBPSL
    ARYBBPSO ARYBBQTA ARYBBQTJ ARYBBRA  ARYBBRDM ARYBBRDS ARYBBRLS
    ARYBBRMA ARYBBROM ARYBBROS ARYBBRPC ARYBBRSL ARYBBRTS ARYBBSAM
    ARYBBSAS ARYBBSDM ARYBBSES ARYBBSGD ARYBBSGS ARYBBSQS ARYBBSSL
    ARYBBSST ARYBBSYM ARYBBSYS ARYBBTBS ARYBBTDM ARYBBTPM ARYBBTPS
    ARYBBTRG ARYBBTRM ARYBBTRS ARYBBTSJ ARYBBTSL ARYBBTSM ARYBBTSO
    ARYBBTSS ARYBBUCD ARYBBUCI ARYBBUCL ARYBBUCO ARYBBUCR ARYBBUDC
    ARYBBUES ARYBBUGC ARYBBULA ARYBBULD ARYBBUPR ARYBBUPV ARYBBUQU
    ARYBBURB ARYBBURC ARYBBURD ARYBBURL ARYBBURP ARYBBURV ARYBBUSR
    ARYBBUSS ARYBBUTH ARYBBUTM ARYBBVAS ARYBBVDM ARYBBVDS ARYBBVRP
    ARYBBVSL ARYBCOAS ARYBCRAS ARYBDSF  ARYBDSUT ARYBDT@  ARYBGRAR
    ARYBGRCA ARYBGRDD ARYBGRDG ARYBGRDL ARYBGRGR ARYBGRGU ARYBGRMD
    ARYBGRML ARYBGRMR ARYBGRMT ARYBGRPL ARYBGRRI ARYBGRRR ARYBGRSF
    ARYBGRSR ARYBGUS  ARYBJGBC ARYBJGCS ARYBJGDA ARYBJGID ARYBJGIM
    ARYBJGNT ARYBJGSB ARYBJGSD ARYBJGWD ARYBLAQ  ARYBLEJ  ARYBLFS
    ARYBOROD ARYBOVCS ARYBOVID ARYBPCJ  ARYBRMOQ ARYBRMOS ARYBRMRS
    ARYBRROT ARYBSGSL ARYBSLBS ARYBSLJ  ARYBSLRJ ARYBTPST ARYBTSA
    ARYBTSAS ARYBTSJ  ARYBTSJB ARYBUIPS ARYBUSGB ARYBUSGJ ARYBVCCR
    

Publications Referenced
SC19254802    

Fix information

  • Fixed component name

    DB2 REC EXPERT

  • Fixed component ID

    5697H7400

Applicable component levels

  • R320 PSY UI63292

       UP19/06/04 P F906

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":"BU048","label":"IBM Software"},"Product":{"code":"SSCVQTW","label":"Db2 Recovery Expert"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2019