IBM Support

PI76855: ABENDU0598 DUE TO MSDBCP VOLID INCONSISTENT DURING /ERE BACKUP IN XRF ALTERNATE SYSTEM.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In MSDB and IMS XRF system, IMS /ERE BACKUP was failed due to
    abendU0598 after the recovery from MSDBCP error due to dasd
    volume failure.
    .
     DFS3889A SYSTEM DATASETS INCONSISTENT - MSDBCP
     DFS629I IMS RST TCB ABEND - IMS 0598
     DFS629I PSW AT ERROR = 077C1000 99E7ED6A  IMP2
     DFS629I MODID = NRST0598A         EPA = 1724AAF4  IMP2
    .
    -------------------------------------------------------------
    <> Flow of the problem:
    (A)
    IMP1 (IMS ALT)   | IMP2  (IMS ACT)
      ----------- MSDB Pair -----------
       MSDBCP1       |    MSDBCP3
       MSDBCP2       |    MSDBCP4
    ----------------------------------------
    1) FORCE OFFINE for MSDBCP3 from IMP2 system.
    2) F STOP command for IMS New Active IMP2
    3) TAKEOVER to IMP1 (IMSALT)
    (B)
    IMP1 (IMS ACT)   | IMP2  (IMS ALT)
      ----------- MSDB Pair -----------
       MSDBCP1       |    MSDBCP3 (Offilne)
       MSDBCP2       |    MSDBCP4
    ----------------------------------------
    4) RECOVERY MSDBCP3 (create MSDBCP3 to different
        volume by copy from MSDBCP4.
    5) /ERE BU for IMSPA2
    6) GOT abendU0598
    .
    <> Explanation:
    Problem scenario;
    Act:ims2(using MSDBCP3,4)  Alt:ims1(using MSDBCP1,2)
    1) VARY OFFLINE xxxx,FORCE for the DASD-VOL which is
       MSDBCP3 d/s.
    2) Stop Act IMS(F ims2,stop) and TKO (Act:ims2->ims1)
    3) Create MSDBCP3 d/s in other volume and copy from MSDBCP4
    4) Restart ims2 as Alternate (/ERE BU)
    ->ABEND U0598
    ---
    this problem doesn't occur above scenario when
    Act:ims1(using MSDBCP1,2) Alt:ims2(using MSDBCP3,4).
    .
    ------------------------------------------------------------
    The MSDBCP3 is not for active IMS pair,
    the current IMS active MSDBCP pair is 01/02.
    So the U0598 due to VOLID inconsistent for MSDBCP3
    should not be occurred at /ERE BU in XRF Alternate system.
    .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IMSFP V15 MSDB with XRF users.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ABENDU0598 DUE TO MSDBCP VOLID                               *
    * INCONSISTENT DURING /ERE BACKUP                              *
    * IN XRF ALTERNATE SYSTEM.                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
    ****************************************************************
    In MSDB and IMS XRF system, IMS /ERE BACKUP failed with
    abendU0598 after the recovery from MSDBCP error due to DASD
    volume failure.
    The scenario as followed:
    1: FORCE OFFINE for MSDBCP3 from IMP2 system.
    2: F STOP command for IMS New Active IMP2
    3: TAKEOVER to IMP1 (IMSALT)
    (B)
    IMP1 (IMS ACT)   | IMP2  (IMS ALT)
    ----------- MSDB Pair -----------
    MSDBCP1       |    MSDBCP3 (Offline)
    MSDBCP2       |    MSDBCP4
    4: RECOVERY MSDBCP3 -create MSDBCP3 to different
    volume by copy from MSDBCP4.
    5: /ERE BU for IMSPA2
    6: GOT abendU0598
    Since the current IMS active MSDBCP pair is 01/02,
    the U0598 due to VOLID inconsistent for MSDBCP3
    should not be issued for /ERE BU in XRF Alternate system.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The following change has been made to correct the reported
    problem:
    DBFNRST0:  Corrected the code that does MSDBCP 1/2, and
               MSDBCP 3/4 consistency checking.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI76855

  • Reported component name

    IMS V15

  • Reported component ID

    5635A0600

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-17

  • Closed date

    2017-03-02

  • Last modified date

    2017-10-06

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

    PI72481

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

    UI45231

Modules/Macros

  • DBFNRST0
    

Fix information

  • Fixed component name

    IMS V15

  • Fixed component ID

    5635A0600

Applicable component levels

  • R500 PSY UI45231

       UP17/03/04 P F703 ¢

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPH2","label":"IMS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"15","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
22 December 2023