Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.4.0 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Summary of PowerExchange New Features and Changes
  3. PowerExchange Installation and Upgrade
  4. PowerExchange Agent
  5. PowerExchange Client for PowerCenter
  6. PowerExchange Condense
  7. PowerExchange Listener
  8. PowerExchange Logger for Linux, UNIX, and Windows
  9. PowerExchange Navigator
  10. PowerExchange Monitoring and Tuning
  11. PowerExchange Utilities
  12. PowerExchange for Adabas
  13. PowerExchange for CA Datacom
  14. PowerExchange for DB2 for i
  15. PowerExchange for DB2 for Linux, UNIX, and Windows
  16. PowerExchange for DB2 for z/OS
  17. PowerExchange for CA IDMS
  18. PowerExchange for IMS
  19. PowerExchange for Microsoft SQL Server
  20. PowerExchange for MySQL
  21. PowerExchange for Oracle
  22. PowerExchange for PostgreSQL
  23. PowerExchange for VSAM and Flat Files
  24. PowerExchange ODBC

Release Guide

Release Guide

Back Next

CICS/VSAM ECCR Support for VSAM ESDS Data Sets

CICS/VSAM ECCR Support for VSAM ESDS Data Sets

Beginning in PowerExchange 10.0, the CICS/VSAM ECCR can capture change data from VSAM entry-sequenced data sets (ESDSs) in an online CICS Transaction Server (CICS TS) environment. In prior PowerExchange releases, only the Batch VSAM ECCR could capture change data from ESDSs.
The CICS/VSAM ECCR can capture change data from ESDS data sets that use both the 32-bit relative byte addressing (RBA) and 64-bit extended relative byte addressing (XRBA). However, the ECCR does not capture change data for the following types of ESDS items:
  • Spanned ESDSs
  • Paths defined over ESDSs
  • Alternate Index (AIX) that points to an ESDS base cluster
To handle backouts for recoverable ESDS data sets that are registered for change data capture, PowerExchange requires additional exit programs at the following CICS global user exit (GLUE) points:
  • XFCBOUT
    . At this GLUE point, define the PowerExchange EDMKBO
    nn
     exit program. This program captures the before image of each record in a recoverable ESDS that is to be backed out because of a transaction abend or syncpoint rollback.
  • XFCLDEL
    . At this GLUE point, define the following exit programs:
    • An exit program that you define to mark backout records as logically deleted and to write them back to the ESDS data set. You must logically delete backout records because CICS TS does not provide a mechanism to delete individual records from an ESDS data set and VSAM does not support this action. To define this user exit program, use the sample program in the DFH$LDEL member of the CICS SAMPLIB library as a basis.
    • The PowerExchange EDMKLD
      nn
      exit program. This program retrieves the after image of a backout record that was logically deleted and then generates an UPDATE record that contains both the before and after images. The generated record is written to the Change Capture Log. The CICS/VSAM ECCR can then process the logically deleted record as an UPDATE to prevent transaction backout failures and the generation of numerous error messages. This program must be enabled last at the XFCLDEL exit point.
PowerExchange also requires a CICS task-related user exit (TRUE) program to capture relevant syncpoints and UOW information for each task that updates a registered data set. The ECCR uses this information to coordinate syncpoint processing with the PowerExchange Logger for MVS and to handle requirements related to CICS shutdown processing.
By default, change data capture for ESDSs is disabled. To enable change capture for ESDSs and override some default CDC options for ESDSs, specify the //EDMKOVRD DD statement or data set in the CICS startup procedure. In the //EDMKOVRD DD statement or data set, you can enter the following CDC override options for ESDSs:
  • CAPTURE_ESDS={ON|
    OFF
    }
    . You must specify ON to enable capture data capture for ESDS data sets.
  • BACKOUTRC={
    OVERRIDE
    |NOOVERRIDE}
    . Controls whether to override the return codes from exit programs that run at the XFCLDEL exit point prior to the EDMKLD
    nn
     program.
  • ESDSFAIL={YES|
    NO
    }
    . For recoverable ESDS data sets from which change data is captured, controls whether backouts are allowed to fail after a transaction abend or rollback. By default, the exit programs that you define at the XFCBOUT and XFCLDEL exit points handle the backouts as updates with before and after images so that the change can be processed during CDC.
To override any of these CDC override settings for a specific ESDS data set, use the
DSN
 option with the appropriate keywords.
Also, this feature adds or enhances the following CICS/VSAM ECCR commands that are issued with the EDMC transaction code:
  • DISPLAY or DISP
    .
    Changed
    . This command has been enhanced to display information for ESDS data sets.
  • OPTIONS or OPTS
    .
    New
    . Displays the CDC override options that are defined in the
    //EDMKOVRD DD
     statement or data set.
  • REFRESH or REFR
    .
    New
    . Re-reads and validates the CDC override options that are defined the
    //EDMKOVRD DD
     statement or data set.
  • RESTART or REST
    .
    New
    . Re-initializes the CICS/VSAM ECCR in the CICS region by issuing the EDMC TERM command followed by the EDMC INIT command. Use this keyword after changing any of the CDC override options in the EDMKOVRID DD statement or data set for your changes to take effect.
  • EXITPGMS or XPGM
    .
    New
    . Lists all of the exit programs that are defined at the CICS GLUE points and TRUE program that PowerExchange uses for CICS/VSAM CDC.
If you previously used the Batch VSAM ECCR to capture change data from ESDSs, you can optionally migrate to the CICS/VSAM ECCR.
For more information about migrating to the CICS/VSAM ECCR, the GLUE points and TRUE program, and all of the
//EDMKOVRD DD
 override options, see the "CICS/VSAM Change Data Capture" chapter in the
PowerExchange CDC Guide for z/OS
.
For more information about the new CICS/VSAM ECCR commands, see the "CICS/VSAM ECCR Commands" chapter in the
PowerExchange Command Reference
.
0 COMMENTS
We’d like to hear from you!