PM57894: HYPERSWAP SUSPEND NOT HANDLED CORRECTLY BY TPC-R

APAR status

• Closed as program error.

Error description

• TPC-R is not handling the HyperSwap suspend properly which
  caused one of the H1-H2 pairs not in'  'target available' state,
  which causes an 0F12 error.
  
  TPC-R interprets the pairs as simplex and attempts to try to
  recreate the pprc pair, but they are not simplex.
  
  Appears there is a race condition between the thread processing
  the HyperSwap and the thread processing the suspend event.
  
  As a result of this, the pair ends up suspended instead of
  Target Available.
  
  Then, when the start command is issued, since the pair is
  suspended, TPC-R issues a resync instead of a failback command.
  
  This results in first a 0x0F11, followed by a 0x0F12.
  
  
  RECREATE STEPS:
  Run hyperswap command to target
  
  ________________________________________________________________
  
  DB2 Version used for Server:
  The defect is against component: 5608TRMZ0
  Server/Manager build/release (TPC): 4.2.2.x
  Agent build/release (TPC):
  Server/Manager (OS): Z/oS
  Agent (OS):
  ________________________________________________________________
  
  Problem as described by customer:  IWNR2108E with return code
  0F12
  Initial customer impact (low/med/high):  med
  

Local fix

• Local Fix: TBD
  

Problem summary

• The Hypserswap suspend if failing with 0f11 and 0f12 errors
  because one pair in the session is still in "Target Available"
  state.
  

Problem conclusion

• The fix will be to get the latest state of the pair.
  

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:

Fix information

• Fixed component name

  TPC FOR REPL Z/

• Fixed component ID

  5608TRMZ0

Applicable component levels

• R42B PSY

     UP