Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange Change Data Capture Introduction
  3. Part 2: CDC Components Configuration and Management
  4. Part 3: CDC Sources Configuration and Management
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: CDC for z/OS Troubleshooting
  8. Appendix B: DTL__CAPXTIMESTAMP Time Stamps

Using the CHKPT_FILE_CTL Parameter

Using the CHKPT_FILE_CTL Parameter

Use the CHKPT_FILE_CTL parameter to specify the template file that contains the IDCAMS DEFINE CLUSTER control statements for checkpoint files.
You can customize DEFINE CLUSTER control statements to control allocation attributes for checkpoint files. For example, you might want to customize the following control statements:
  • If you use SMS, customize the DATACLASS, STORAGECLASS, and MANAGEMENTCLASS statements based on the SMS data classes, storage classes, and management classes that are defined at your site.
  • To change the default suffix of .D for the Data component, customize the DATA statement.
  • To change the default suffix of .I for the Index component, customize the INDEX statement.
  • To override the default control interval size of 32768, customize the CONTROLINTERVALSIZE statement.
The following sample template is provided in the TMLCHKPT member in the RUNLIB library:
/* template for PowerExchange chkpt definition */ /* max 35 lines cols 2-80 only, Lines of comments do not count */ /* NAME(<<name>> should occur three times */ /* must otherwise be valid define of cluster */ /* KEYS(40 0) is required for smooth running */ DEFINE CLUSTER - (NAME(<<
name
>>) - KEYS(40 0) - RECORDSIZE(4096 32756) - DATACLASS(
dataclas
) - STORAGECLASS(
storclas
) - MANAGEMENTCLASS(
mgmtclas
) - TRACKS (5 5) - VOLUMES(
volser
) - REUSE - FREESPACE (20 20) - SHAREOPTIONS (2 3)) - DATA - (NAME(<<
name
>>.D)) - INDEX - (NAME(<<
name
>>.I))
The PowerExchange installer adds the initial DATACLASS, STORAGECLASS, MANAGEMENTCLASS, and VOLUMES values based on the values that you enter in the z/OS Installation Assistant. You can customize these values in the TMLCHKPT member.
If you customize the template, use the following guidelines:
  • Make sure that the DEFINE CLUSTER control statements are valid IDCAMS control statements because PowerExchange passes these statements to IDCAMS as is, with the exception of the NAME control statements.
  • Use uppercase to define the DEFINE CLUSTER control statements.
  • Do not start control statements in column 1.
    The maximum number of lines is 35 lines.
  • You must define the <<
    name
    >> variable in the NAME parameter of the DEFINE CLUSTER, DATA, and INDEX control statements. PowerExchange populates this variable with the value that you specify in the EXT_CAPT_MASK parameter of the CAPTPARM member. Make sure that the EXT_CAPT_MASK prefix, when combined with any changes made to the suffix for the DATA and INDEX statements, does not exceed 44 characters.
  • Specify the KEYS parameter exactly as shown in the template.
  • Start comments with a forward slash and an asterisk (/*) and consistently place them before or after the control statements.

0 COMMENTS

We’d like to hear from you!