PK93417: ADS UNAVAIL AGAIN EVEN AFTER RECOVERED BY ADS CREATE UTILITY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• We are using MADS under data sharing and FDBR environment.
  Initially, ADS severe error happened on IMP1 with DFS3713A, and
  it sent internal STO ADS commands to Data Sharing IMSs via IRLM.
  At this time, FDBR region for IMP5 started recovery and received
  this NOTIFY message. processed it and wrote type 5923 log
  record with ADSCF2IO flag on.
  IMP1 was working with single ADS mode.
  After FDBR region successfully completed but prior to /ERE of
  IMP5, the ADS was recovered by ADS create utility on IMP1, and
  AREA was resume as MADS mode.
  Later /ERE on IMP5 was done. It read previous 5923 log record
  and the ADS made UNAVAIL again, and the AREA was stopped
  globally with DFS3764I message.
  This is not suitable.
  We think that FDBR region should not process notified STOP ADS
  command during FDBR recovery phase and should not write type5923
  log record.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V11 Fast Path Users                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: ADS made unavailable and AREA stopped   *
  *                      globally with DFS3764I message when     *
  *                      /ERE read in with type 5923 log record. *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  ADS made unavailable and AREA stopped globally with DFS3764I
  message when /ERE read in with type 5923 log record which
  was written by FDBR. FDBR region processed the notified STOP
  ADS command during FDBR recovery phase and written type 5923
  record and set ADSCF2IO flag.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  DBFARD20
  
  The fix will not let FDBR region to write type 5923 log.
  Instead, it will only send back the response of the
  notification.
  

Temporary fix

Comments

APAR Information

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

  PK93033

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

  UK50375

Modules/Macros

• DBFARD20
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK50375

     UP09/09/29 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.