PK93127: ERE IMS STOPPED AREA WHICH FDBR DETECTED ADS I/O ERROR.

APAR status

• Closed as program error.

Error description

• We are using MADS under data sharing and FDBR environment.
  Initially, ADS open error occurred on FDBR region for IMP5 then
  the AREA stopped globally with DFS3764I.
  After FDBR recovery completed, "/STA AREA xxxx GLOBAL." command
  was entered and the ADS was recovered by ADS create utility on
  IMP1. After /ERE has been completed on IMP5, the AREA has
  stopped locally with no message.
  The AREA has been available on the data-sharer IMP1.
  ----------------------------------------------------------------
    < SCENARIO >
       <A-IMS>        <C FDBR>       <C-IMS>
     1.OPEN CMFL01                   OPEN CMFL01
     2.                              DDLT(GHU/REPL/WTOR/SYNC)
                                      => WTOR
     3.               RESERVE --->
     4.                              REPLY WTOR
     5.               V Sec-ADS,OFFLINE
     6.                              F IMS,STOP
     7.               FDBR RECOVERY
                       => DFS2503W DYNAMIC ALLOCATION   FAILED FOR
                          DFS3702I AREA/ADS OPEN FAILED FDR5
                          DFS3702I REASON CODE=17 AREA=CMFL01
                            DD=CMFL0102 ALLOCATION FAI
                       => DFS3764I
        ** GLOBAL AREA STOP **
     8. /STA AREA CMFL01 GLOBAL.
     9. CMFL0102 DELDEF/UMIN0
    10. ADS CREATE
         => OK
    11.                              S IMS
                                     /ERE
    12. /DIS AREA CMFL01             /DIS AREA CMFL01
         => NOT STOP                  => STOPPED         <===  !!!
    13.                              /STA AREA CMFL01.
                                     DDLT => OK
  FDBR region wrote next log records;
    5922 RECORD - CMFL0101 : ADSCF221 on
    5922 RECORD - CMFL0102 : ADSCF221+ADSCF2IO
  ----------------------------------------------------------------
  During /ERE, PROC5922 in DBFEROC0 processed above type5922 log
  records. When the 1st 5922 log processed, DMACADSN became 1.
  When the 2nd 5922 log processed, DMACADSN became 0. => Last ADS.
  Due to the last ADS was closed, PROC5922 cleaned up some DMAC
  fields. Then it set DMACF1ST and DMACF2IO because the last ADS
  in type5922 log had DOCLF2IO flag.
  FDBR region did not write type5957 log record after type5922.
  So, it became final status of the AREA. => DMACF1ST on.
  But no message was issued to show why the AREA was stopped.
  If ADS I/O error happened in FDBR region on the first ADS,
  the 1st 5922 log had DOCLF2IO and the 2nd 5922 did not, then
  AREA is not stopped. This is inconsistent.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V9 Fast Path users                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: ADS got I/O error in the process        *
  *                      of 5922 in FDBR recovery. After         *
  *                      DB recovery utility, Data sharing       *
  *                      IMS started this AREA but AREA got      *
  *                      stopped without any message.            *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  ADS became unavailable in the process of 5922 in FDBR recovery.
  After DB recovery utility, Data sharing IMS started this AREA
  but AREA got stopped without any message. This was caused by
  two 5922 logs and available ADS became zero.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  DBFEROC0
  
  Restored original logic which was introduced by PN34452.
  

Temporary fix

Comments

APAR Information

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

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

  PK93409 PK93410 UK50044

Modules/Macros

• DBFEROC0
  

Fix information

• Fixed component name

  IMS V9

• Fixed component ID

  5655J3800

Applicable component levels

• R900 PSY UK50044

     UP09/09/17 P F909