anchor.diff:  
   See [Basic Suspend and Resume Transaction Example](transaction_suspend_resume_example.html) for a sample code fragment that suspends and resumes a transaction.
   
  -## Using Cache Writer and Cache Listener Plug-Ins
  +## <a id="concept_ysx_nf1_wk" class="no-quick-link"></a>Using Cache Writer and Cache Listener Plug-Ins
   
   All standard <%=vars.product_name%> application plug-ins work with transactions. In addition, the transaction interface offers specialized plug-ins that support transactional operation.
   
  
positive.code: 
  A typical usage scenario would be to use the transaction writer to prepare the commit on the external database. Then in a transaction listener, you can apply the commit on the database.
  
  ## Transaction Listeners
  
  When the transaction ends, its thread calls the transaction listener to perform the appropriate follow-up for successful commits, failed commits, or voluntary rollbacks. The transaction that caused the listener to be called no longer exists by the time the listener code executes.
  
  
negative.code: 
      -   Run the transactions from the member in which expiration is configured.
  
  ## <a id="transactions_and_consistency" class="no-quick-link"></a>Transactions and Consistent Regions
  
  A transaction that modifies a region in which consistency checking is enabled generates all necessary version information for region updates when the transaction commits.
  
  