IBM Support

PI82389: XRF NEW ACTIVE IMS ISSUED DFS4604I RC=30 AFTER TAKEOVER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem-1:
    While DEDB Alter - ALTERAREA is running, XRF TAKEOVER happened.
    Then new active IMS issued DFS4604I DBRC ALTER EOJ ERROR with
    RC=00000030. RC=30 is hex; decimal 48 = INVALID_PARM.
    From DBRC trace, I found the reason code was 06:
    => Reorganization time not specified.
    ALTREOJ STATUS=NORMAL was issued in DBFEDA00 from LFF_UP_EOJ
    routine, but it is missing to specify TIME= on DFSBRLSC macro.
    In case of ALTREOJ NORMAL, REORG TIME is required.
    ----------------------------------------
    There are several concerns related this problem.
    1. Active IMS issued DFSBRLSC FUNC=ALTREOJ,STATUS=NORMAL already
     and wrote 596107 before ABEND.
     But DBFEDA00 issued ALTREOJ,STATUS=NORMAL again under
     CASE255_PARTIAL -> LFF_UP_EOJ routine.
     CASE255_PARTIAL routine should not call LFF_UP_EOJ around
     DBFEDA00 line#7103. Many routines in DBFEDA00 calls LFF_UP_EOJ,
     but they are incorrect too.
     Even if it is called for fail_safe, next problem exist (2 & 3).
    2. LFF_UP_EOJ routine is missing to specify TIME= of DFSBRLSC
     FUNC=ALTREOJ,STATUS=NORMAL.
     Then it fails with RC=48 and RSN=06. If we correct this, next
     problem exist(3).
    3. If we re-issue correct ALTREOJ twice, DBRC DSPADSDA returns
     RC=04 (ALTER is not in progress).
     In this case, DBFEDA00 should not issue DFS4604I message.
     This is same concern as PI82280.
    4. Messages and Codes manual is missing for explanation about
     RCs and Reason codes for ALTRINIT, ALTREOJ, ALTRQRY
    5. Module prologue of DSPADSDA has explanation about RC and
     Reason code. But RC for ALTRQRY is not correct.
      RC=00 should be 'Alter not in progress'
      RC=04 should be 'Alter is in progress'
    6. DBFDAU70 has DFSBRLSC FUNC=ALTREOJ around line#1465 and it
     missing to specify TIME= too.
     But this is a dead code. How about delete it?
    7. DFS4604I message has no reason code. Without Reason code, it
     is difficult to understand the reason.
    8. DBFEDA00 has next 4 types of DFS4604I message for ALTER EOJ
     ERROR.
        M004604A for ALTREOJ NORMAL - AREA
        M004604C for ALTREOJ NORMAL - DEDB
        M004604B for ALTREOJ ABNORMAL - AREA
        M004604E for ALTREOJ ABNORMAL - DEDB
     But these messages do not have word 'NORMAL' or 'ABNORMAL'.
     M004604A and M004604C should have 'NORMAL'.
     M004604B and M004604D should have 'ABNORMAL'.
    Problem-2; Unexpected DFS4606I RC=133 RSN=02 during XRF TAKEOVER
    During XRF TAKEOVER, unexpected DFS4606I RC=133 RSN=02 was
    received. In old active IMS, DEDB Alter - ALTERAREA was running
    in COPY phase. We are using ACBSHR=N. So, active IMS and
    Alternate IMS have different ACBLIB data set(ACBLIB1 & ACBLIB2).
    RC=133 is I/O error. RSN=02 is DELENC(delete Encrypted member).
    DEDB Alter in old active IMS copied encrypted member from
    staging ACBLIB into it's own active ACBLIB(ACBLIB1) before down.
    During XRF TAKEOVER, UNDO_COPY_COPYBLKS routine in DBFEDA00 was
    called. It tried to delete encrypted member from alternate
    IMS's ACBLIB(ACBLIB2). But ACBLIB2 does not have encrypted
    member and RC=133 was set by DBFMOLS0.
    In case of ACBSHR=N and XRF TAKEOVER or FDBR, CASE99 routine
    should not call UNDO_MOLC nor UNDO_COPYBLKS, I think.
    If it calls these routine for fail safe, DFS4606I message should
    not be issued.
    -----------------------------------------------------
    Concerns;
    1. Unexpected DFS4606I RC=133 RSN=02 ???
    2. There is no explanation about RC and RSN in Messages and
     Codes manual under DFS4606I.
    3. How can we delete enchrypted member in old active IMS's
     ACBLIB?  Is it user's responsibility when using ACBSHR=N?
     If so, we will need to issue any warning message anyway...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IMS V14 FP DEDB ALTER utility users                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * XRF NEW ACTIVE IMS ISSUED DFS4604I RC=133 AFTER TAKEOVER     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
    ****************************************************************
    

Problem conclusion

  • DBFEDA00
    
    Added TIME= parameter to ALTREOJ  which is required
    
    Made CASE99 not call UNDO_COPYBLKS and UNDO_MOLC when XRF
    takeover and FDBR and ACBSHR=N
    
    When duplicate ALTEREOJ is issued, DFS4604I message is not
    issued
    
    Made CASE255_PARTIAL rooutine not call LFF_UP_EOJ
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI82389

  • Reported component name

    IMS V14

  • Reported component ID

    5635A0500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-31

  • Closed date

    2018-04-05

  • Last modified date

    2018-05-01

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

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

    PI95561 UI55029

Modules/Macros

  • DBFEDA00
    

Fix information

  • Fixed component name

    IMS V14

  • Fixed component ID

    5635A0500

Applicable component levels

  • R400 PSY UI55029

       UP18/04/07 P F804

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":"14.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 December 2023