PK34376: DFS3770W FOR SHVSO SYNC JUST AFTER /ERE COMPLETED.

Obtain the fix for this APAR

APAR status

• Closed as program error.

Error description

• After XRF TAKEOVER failure, IMS was restarted with /ERE.
  But, just after /ERE completed, DFS3770W messages were issued
  repeatedly for SHVSO SYNC. There was no problem in data sharing
  IMS. From the dump, IOT EEQE purge was called under DFSCST00
  ITASK, and SVSO AREA was opened from DBFTOPU0. Then DBFVXOP0
  issued type-3 SVSO NOTIFY but it didn't complete.
  ----------------------------------------------------------------
  << Save Area Flow >>
  SAP AT 1A89B200 FLG-D01F0000 40080000 DPNO-00041084
  POST-80CAB1DB ECB-00CB0060 TYPE-CST
  DFSCST00+910+20050411+14.11PQ99233 A +093E
  UNLOCK00 +????
  UNKNOWN +????
  DFSTOPR0-10/30/03 +12F8
  DBFTOPU0-08/05/04-16.05PQ90087 A +00B8
  TOPUOPEN +00D4
  DBFMLOP007/10/0614.23PK25255 ABCDEFGHJK +09C0
  DBFCMOC705/31/0514.22PQ87302 A +00DA
  DBFVSOP008/13/0414.51PQ90228 AB +00A8
  DBFVXOP003/18/0508.11PK01995 ABCEFGHI +067C
  DBFNOTM003/18/0514.04PK00329 ABC +058A
  DFSIWAIT
  ---------------------------------------------------------------
  From FT Trace, DBFICLI0 got response NOTIFY from partner IMS
  correctly. But DBFICLI0 ignored it because DBFICLI0 cannot
  validate issuers EPST. In this case, Type-3 NOTIFY was issued
  under DFSCST00 ITASK and PST of DFSCST00 ITASK belong to PST
  POOL. DBFICLI0 checks only APST and DPST, and couldn't validate
  EPST of DFSCST00 ITASK.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMSFP R910 users with shared VSO areas. *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message DFS3770W SYNCHRONIZING PROCESS *
  * TIME EXCEEDED - SHVSO SYNC issued *
  * repeatedly after XRF takeover and the *
  * new active IMS /ERE completed. *
  * The affected IMS eventually hung. *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF *
  ****************************************************************
  IOT EEQE purge was called under a DFSCST00 ITASK,
  and the shared VSO (SVSO) AREA was opened from DBFTOPU0.
  Then DBFVXOP0 issued a type-3 SVSO NOTIFY but it didn't
  complete because DBFICLIO could not validate the issuers EPST.
  DBFICLI0 received the notify but it only checks the APST
  and DPST but not the EPST of the DFSCST00 ITASK.
  As a result of this IOT EEQEs remained without being purged.
  In IMS V7, DBFICLI0 checked the PST and the DPST so this
  problem did not exist. This problem exists in V8 and above.
  

Problem conclusion

• AIDS: RIDS/FP RIDS/DEDB FP DEDB
  DEP: NONE
  GEN:
  
  *** END IMS KEYWORDS ***
  
  Code has been added to the following modules :
  
  DBFICLI0 - Code has been added to address the PST and check if
  DFSCST00's PST(SCDCSECB) is the same as the waiting
  EPST(FNCBREPS).
  
  DBFCSTS2 - The waitepstval routine has been changed to now check
  the correct NCB field FNCBEPST, PST ITASK instead of
  FNCBREPS which is the waiting EPST for RESPONSE.
  

Temporary fix

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

Comments

APAR Information

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

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

Modules/Macros

DBFCSTS2

DBFICLI0

Fix information

• Fixed component name

  IMS V9

• Fixed component ID

  5655J3800

Applicable component levels

• R900 PSY UK23276

     UP07/03/30 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.