CDC Installation

IBMInfoSphere Change Data Capture

InfoSphere Change Data Capture for z/OS, Version 6.2End-User Documentation

Version 6.2

��

IBMInfoSphere Change Data Capture

InfoSphere Change Data Capture for z/OS, Version 6.2End-User Documentation

Version 6.2

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 667.

First edition, first revision

This edition applies to version 6, release 2, fix pack 1 of IBM InfoSphere Change Data Capture (product number5655-U96) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2008, 2009.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

IBM InfoSphere Change Data Captureinstallation or upgrade . . . . . . . . 1InfoSphere CDC overview . . . . . . . . . . 1Minimum requirements. . . . . . . . . . . 2Before you install . . . . . . . . . . . . . 2

What is on the tape cartridge? . . . . . . . 2About the InfoSphere CDC program directory . . 3Customizing your InfoSphere CDC installation . . 3Evaluating z/OS and DB2 configurationparameters prior to InfoSphere CDC installation . 3Prerequisite program products . . . . . . . 5Required storage devices . . . . . . . . . 5Required SMP/E target and distribution libraries 5Choosing system or private libraries . . . . . 5Should you install InfoSphere CDC resident? . . 5Obtaining up-to-date maintenance duringinstallation . . . . . . . . . . . . . . 5Considerations for upgrading from releases priorto InfoSphere CDC for z/OS version 5.4 . . . . 5

Installing InfoSphere CDC . . . . . . . . . . 7Installing InfoSphere CDC . . . . . . . . . 8Tape distribution media . . . . . . . . . 8Internet distribution media . . . . . . . . 8The initial SMP/E installation jobs . . . . . . 9Completing the installation using the distributedsample jobs . . . . . . . . . . . . . . 9

Introduction to modifying the InfoSphere CDCconfiguration control data set . . . . . . . . 21Linking Transformation Server user exits forInfoSphere CDC . . . . . . . . . . . . . 23

Link editing Transformation Server notificationuser exits for InfoSphere CDC . . . . . . . 24Link editing Transformation Server expressionuser exits for InfoSphere CDC . . . . . . . 25Link editing Transformation Server table-leveluser exits and row-level user exits for InfoSphereCDC. . . . . . . . . . . . . . . . 26Link editing Transformation Server conflictresolution user exits for InfoSphere CDC . . . 26

Modifying general product configuration controlstatements . . . . . . . . . . . . . . . 27

CONFIG . . . . . . . . . . . . . . 27Modifying communications configuration controlstatements . . . . . . . . . . . . . . . 43

TCP/IP. . . . . . . . . . . . . . . 44Modifying DBMS configuration control statements 49

DB2 . . . . . . . . . . . . . . . . 49Modifying DB2 LOAD configuration controlstatements . . . . . . . . . . . . . . . 65

DB2LOADER . . . . . . . . . . . . . 65Modifying UCS configuration control statements . . 70

UCS . . . . . . . . . . . . . . . . 71CCSIDMAP . . . . . . . . . . . . . 71CONVERSION . . . . . . . . . . . . 72IANAMAP . . . . . . . . . . . . . 73

Executing InfoSphere CDC . . . . . . . . . 74Estimating InfoSphere CDC’s requirements forhiperspaces and auxiliary storage . . . . . . . 75

Staging resources calculations . . . . . . . 76BUFTHRESHOLD keyword considerations . . . . 76

Specifying BUFTHRESHOLD . . . . . . . 77BUFTHRESHOLD value considerations . . . . 77

Installing and running multiple InfoSphere CDCinstances . . . . . . . . . . . . . . . 80Reverting to InfoSphere CDC for z/OS version 5.4 81

Downgrading metadata DB2 tables . . . . . 82Downgrading with user exits . . . . . . . 86Downgrading and the product administration log 87Downgrading configuration parameters . . . . 87

Upgrading from DB2 version 7.1 toDB2 version 8.1 . . . . . . . . . . . 89Running the CHCPGRN6 job . . . . . . . . 90Running the CHCCRMTD job . . . . . . . . 90Running the CHCPGCP6 job . . . . . . . . 90Running the CHCBNDPL job . . . . . . . . 90

InfoSphere CDC commands . . . . . 91System configuration . . . . . . . . . . . 91Communication commands . . . . . . . . . 92

SHUTDOWN—Stop InfoSphere CDC addressspace . . . . . . . . . . . . . . . 92START—Start InfoSphere CDC address space . . 94STOP—Stop InfoSphere CDC address space . . 97STRTSCOM—Initialize communicationsenvironment . . . . . . . . . . . . . 98STRTSDBM—Initialize database managementsystem . . . . . . . . . . . . . . . 99

Replication commands . . . . . . . . . . 102STRTSMIR—Start mirroring . . . . . . . 102ENDTSMIR—End mirroring . . . . . . . 104STRTSRSH—Start refresh . . . . . . . . 106ENDTSRSH—End refresh . . . . . . . . 108

Table mapping commands . . . . . . . . . 110SETMIRSTS—Set mirroring status . . . . . 110SETRSHSTS—Set refresh status . . . . . . 113

Other Commands . . . . . . . . . . . . 116COMMAND—Process InfoSphere CDCcommands . . . . . . . . . . . . . 116DSPACT—Display activity . . . . . . . . 117ENDUR—End unit of recovery . . . . . . 120REPORT—Generate report . . . . . . . . 122SETLOGPOS—Set log position . . . . . . 123STGMGR—Storage Manager . . . . . . . 125STRTSDSC—Describe source tables tosubscription . . . . . . . . . . . . . 125TRACE—Trace InfoSphere CDC tasks . . . . 127TRACEDEST—Set trace destination . . . . . 132

Code page conversion services . . . 135

© Copyright IBM Corp. 2008, 2009 iii

Introduction . . . . . . . . . . . . . . 135Unicode Conversion Services . . . . . . . . 135Language Environment Code Page Conversiontables . . . . . . . . . . . . . . . . 136

DB2 performance considerations . . . 137Static versus dynamic SQL . . . . . . . . . 137%GETCOL and %SELECT function calls andprocessing efficiency . . . . . . . . . . . 140User exits and efficiency. . . . . . . . . . 141

Automatic restart and schemaevolution . . . . . . . . . . . . . 143Automatic restart . . . . . . . . . . . . 143

Persistency . . . . . . . . . . . . . 143Direct and indirect requests . . . . . . . 144DB2 unavailability. . . . . . . . . . . 145

Schema evolution . . . . . . . . . . . . 145Restarting replication . . . . . . . . . . . 145

Bookmark viewer. . . . . . . . . . 147Submitting the CHCMDPRT batch job on a targetenvironment. . . . . . . . . . . . . . 147Batch job result . . . . . . . . . . . . . 148Sample bookmark viewer output . . . . . . . 148

CHCMTAUT Utility . . . . . . . . . 151Invoking the CHCMTAUT utility. . . . . . . 151CHCMTAUT commands . . . . . . . . . 151

END . . . . . . . . . . . . . . . 152HELP . . . . . . . . . . . . . . . 152LIST . . . . . . . . . . . . . . . 152LOADER . . . . . . . . . . . . . . 153PERSISTENCY . . . . . . . . . . . . 155QUIT . . . . . . . . . . . . . . . 155REFRESHISOLATION . . . . . . . . . 156UCASE . . . . . . . . . . . . . . 156CLEAR . . . . . . . . . . . . . . 157

Supported DB2 for z/OS data types 159Supported data types. . . . . . . . . . . 159Supported mappings . . . . . . . . . . . 159

Numeric types . . . . . . . . . . . . 159Character types. . . . . . . . . . . . 160Date and time types . . . . . . . . . . 160DBCS types . . . . . . . . . . . . . 160Row Identifier types . . . . . . . . . . 160

Management Console tutorial tables 161

InfoSphere CDC metadata tables . . . 163Source environment metadata tables. . . . . . 163Target environment metadata tables . . . . . . 163General metadata tables . . . . . . . . . . 164

InfoSphere CDC user exits . . . . . 165About table-level user exit and row-level user exitprograms . . . . . . . . . . . . . . . 165

Predefined entry data structures for table-leveluser exits and row-level user exits . . . . . 165Load module specification in ManagementConsole . . . . . . . . . . . . . . 166Sample table-level and row-level user exitprograms . . . . . . . . . . . . . . 166Performance considerations. . . . . . . . 166

Working with table-level and row-level user exitprograms . . . . . . . . . . . . . . . 166

Defining and invoking programs at thetable-level user exit and row-level user exitpoints . . . . . . . . . . . . . . . 167Writing table-level user exit programs androw-level user exit programs . . . . . . . 167Running the DB2 precompiler . . . . . . . 172Compiling and linking table-level user exit androw-level user exit programs . . . . . . . 172Binding the Database Request Module (DBRM) 173Predefined entry data structures (table-level orrow-level user exits) . . . . . . . . . . 174

About expression user exits . . . . . . . . 180The %USER function . . . . . . . . . . 180Predefined entry data structures for expressionuser exits . . . . . . . . . . . . . . 181Sample expression user exit programs . . . . 181Performance considerations. . . . . . . . 182

Working with expression user exit programs . . . 182Defining and invoking user exit programswithin an expression . . . . . . . . . . 183Writing expression user exit programs . . . . 183Running the DB2 precompiler . . . . . . . 187Compiling and linking expression user exitprograms . . . . . . . . . . . . . . 187Binding the Database Request Module (DBRM) 189Predefined entry data structures . . . . . . 189

About conflict resolution user exits . . . . . . 192Predefined entry data structures for conflictresolution user exits . . . . . . . . . . 192Load module specification in ManagementConsole . . . . . . . . . . . . . . 192Performance considerations for conflictresolution user exits . . . . . . . . . . 192

Working with conflict resolution user exitprograms . . . . . . . . . . . . . . . 193

Defining and invoking programs at the conflictresolution user exit points . . . . . . . . 193Writing conflict resolution user exit programs 193Running the DB2 precompiler . . . . . . . 197Compiling and linking conflict resolution userexit programs . . . . . . . . . . . . 197Binding the Database Request Module (DBRM) 198Predefined entry data structures . . . . . . 199

Conflict resolution audit table . . . . . . . . 206Row image format. . . . . . . . . . . 208Truncated images . . . . . . . . . . . 208

About notifications user exits . . . . . . . . 209Notifications. . . . . . . . . . . . . 209Predefined entry data structures for notificationsuser exits . . . . . . . . . . . . . . 209Sample notifications user exit program . . . . 209Performance considerations. . . . . . . . 209

iv InfoSphere Change Data Capture: End-User Documentation

Working with Notifications user exit programs . . 210Defining and invoking Notifications user exitprograms . . . . . . . . . . . . . . 210Writing notifications user exit programs . . . 210Compiling and linking notifications user exitprograms . . . . . . . . . . . . . . 213Predefined entry data structures . . . . . . 214

SMF Record Layout. . . . . . . . . 219SMF record header . . . . . . . . . . . 219

InfoSphere CDC SMF record header . . . . . 220InfoSphere CDC SMF performance segmentheader. . . . . . . . . . . . . . . 220InfoSphere CDC SMF performance segments 222

Actual SMF performance records written byInfoSphere CDC . . . . . . . . . . . . 229

The system SMF performance record . . . . 229The log cache performance record . . . . . 230The source subscription mirror performancerecord . . . . . . . . . . . . . . . 231The target subscription mirror performancerecord . . . . . . . . . . . . . . . 231

Event messages reference. . . . . . 233Introduction to event messages . . . . . . . 233

Message identifier format . . . . . . . . 233Message descriptions . . . . . . . . . . 234

Event message identifier changes . . . . . . . 235CHC00 messages . . . . . . . . . . . . 238

CHC0012W . . . . . . . . . . . . . 239CHC0015I . . . . . . . . . . . . . 239CHC0023W . . . . . . . . . . . . . 239CHC0024W . . . . . . . . . . . . . 240CHC0025W . . . . . . . . . . . . . 240CHC0026W . . . . . . . . . . . . . 241CHC0027W . . . . . . . . . . . . . 241CHC0029E . . . . . . . . . . . . . 241CHC0030E . . . . . . . . . . . . . 242CHC0031E . . . . . . . . . . . . . 242CHC0040I . . . . . . . . . . . . . 243CHC0044I . . . . . . . . . . . . . 243CHC0046I . . . . . . . . . . . . . 243CHC0047I . . . . . . . . . . . . . 244CHC0050E . . . . . . . . . . . . . 244CHC0051W . . . . . . . . . . . . . 245CHC0052W . . . . . . . . . . . . . 246CHC0055I . . . . . . . . . . . . . 246CHC0056I . . . . . . . . . . . . . 247CHC0057I . . . . . . . . . . . . . 248CHC0058E . . . . . . . . . . . . . 248CHC0059E . . . . . . . . . . . . . 249CHC0060I . . . . . . . . . . . . . 249CHC0061E . . . . . . . . . . . . . 250CHC0068E . . . . . . . . . . . . . 250CHC0069E . . . . . . . . . . . . . 251CHC0071E . . . . . . . . . . . . . 251CHC0072W . . . . . . . . . . . . . 252CHC0073W . . . . . . . . . . . . . 252CHC0075E . . . . . . . . . . . . . 253CHC0077E . . . . . . . . . . . . . 253

CHC0078E . . . . . . . . . . . . . 254CHC0079E . . . . . . . . . . . . . 254CHC0080E . . . . . . . . . . . . . 254CHC0081E . . . . . . . . . . . . . 255CHC0082I . . . . . . . . . . . . . 255CHC0083I . . . . . . . . . . . . . 256CHC0095E . . . . . . . . . . . . . 256CHC0099I . . . . . . . . . . . . . 256

CHC01 messages . . . . . . . . . . . . 257CHC0100W . . . . . . . . . . . . . 257CHC0101I . . . . . . . . . . . . . 258CHC0102E . . . . . . . . . . . . . 258CHC0104E . . . . . . . . . . . . . 258CHC0105E . . . . . . . . . . . . . 259CHC0107I . . . . . . . . . . . . . 259CHC0108E . . . . . . . . . . . . . 260CHC0109E . . . . . . . . . . . . . 260CHC0110E . . . . . . . . . . . . . 260CHC0112E . . . . . . . . . . . . . 261CHC0113E . . . . . . . . . . . . . 261CHC0115W . . . . . . . . . . . . . 261CHC0116E . . . . . . . . . . . . . 262CHC0117W . . . . . . . . . . . . . 262CHC0118E . . . . . . . . . . . . . 263CHC0119E . . . . . . . . . . . . . 263CHC0120I . . . . . . . . . . . . . 264CHC0121I . . . . . . . . . . . . . 264CHC0122I . . . . . . . . . . . . . 264CHC0123I . . . . . . . . . . . . . 264CHC0129I . . . . . . . . . . . . . 265CHC0130I . . . . . . . . . . . . . 265CHC0136I . . . . . . . . . . . . . 266CHC0137I . . . . . . . . . . . . . 267CHC0143E . . . . . . . . . . . . . 267CHC0144E . . . . . . . . . . . . . 268

CHC02 messages . . . . . . . . . . . . 268CHC0211E . . . . . . . . . . . . . 269CHC0212E . . . . . . . . . . . . . 270CHC0213E . . . . . . . . . . . . . 270CHC0220I . . . . . . . . . . . . . 270CHC0221I . . . . . . . . . . . . . 271CHC0222I . . . . . . . . . . . . . 271CHC0223I . . . . . . . . . . . . . 272CHC0224W . . . . . . . . . . . . . 272CHC0225E . . . . . . . . . . . . . 272CHC0226I . . . . . . . . . . . . . 273CHC0227I . . . . . . . . . . . . . 273CHC0228E . . . . . . . . . . . . . 274CHC0231I . . . . . . . . . . . . . 274CHC0232E . . . . . . . . . . . . . 275CHC0233E . . . . . . . . . . . . . 276CHC0235W . . . . . . . . . . . . . 276CHC0236E . . . . . . . . . . . . . 276CHC0237W . . . . . . . . . . . . . 277CHC0238E . . . . . . . . . . . . . 277CHC0240E . . . . . . . . . . . . . 278CHC0244I . . . . . . . . . . . . . 278CHC0246I . . . . . . . . . . . . . 279CHC0247E . . . . . . . . . . . . . 279CHC0248E . . . . . . . . . . . . . 280CHC0254I . . . . . . . . . . . . . 281

Contents v

CHC0255I . . . . . . . . . . . . . 281CHC0256I . . . . . . . . . . . . . 282CHC0257I . . . . . . . . . . . . . 282CHC0263I . . . . . . . . . . . . . 282CHC0264I . . . . . . . . . . . . . 283CHC0265I . . . . . . . . . . . . . 283CHC0266I . . . . . . . . . . . . . 284CHC0272I . . . . . . . . . . . . . 284CHC0273I . . . . . . . . . . . . . 285CHC0274I . . . . . . . . . . . . . 285CHC0275I . . . . . . . . . . . . . 285CHC0281I . . . . . . . . . . . . . 286CHC0282I . . . . . . . . . . . . . 286CHC0283I . . . . . . . . . . . . . 287CHC0289I . . . . . . . . . . . . . 287CHC0290I . . . . . . . . . . . . . 287CHC0291I . . . . . . . . . . . . . 288

CHC03 messages . . . . . . . . . . . . 289CHC0300I . . . . . . . . . . . . . 290CHC0305E . . . . . . . . . . . . . 291CHC0309E . . . . . . . . . . . . . 291CHC0310E . . . . . . . . . . . . . 292CHC0311E . . . . . . . . . . . . . 292CHC0312E . . . . . . . . . . . . . 292CHC0313E . . . . . . . . . . . . . 293CHC0314I . . . . . . . . . . . . . 293CHC0315I . . . . . . . . . . . . . 294CHC0316I . . . . . . . . . . . . . 294CHC0317I . . . . . . . . . . . . . 294CHC0318I . . . . . . . . . . . . . 295CHC0319E . . . . . . . . . . . . . 295CHC0320W . . . . . . . . . . . . . 296CHC0321W . . . . . . . . . . . . . 296CHC0322W . . . . . . . . . . . . . 297CHC0324E . . . . . . . . . . . . . 297CHC0325E . . . . . . . . . . . . . 298CHC0326E . . . . . . . . . . . . . 298CHC0327E . . . . . . . . . . . . . 298CHC0328I . . . . . . . . . . . . . 299CHC0330E . . . . . . . . . . . . . 299CHC0331E . . . . . . . . . . . . . 300CHC0332E . . . . . . . . . . . . . 300CHC0333W . . . . . . . . . . . . . 301CHC0334W . . . . . . . . . . . . . 301CHC0335I . . . . . . . . . . . . . 302CHC0336E . . . . . . . . . . . . . 302CHC0337W . . . . . . . . . . . . . 303CHC0339I . . . . . . . . . . . . . 304CHC0340E . . . . . . . . . . . . . 304CHC0341E . . . . . . . . . . . . . 304CHC0342E . . . . . . . . . . . . . 305CHC0344W . . . . . . . . . . . . . 305CHC0346I . . . . . . . . . . . . . 306CHC0347E . . . . . . . . . . . . . 306CHC0348E . . . . . . . . . . . . . 307CHC0350E . . . . . . . . . . . . . 307CHC0351I . . . . . . . . . . . . . 308CHC0352I . . . . . . . . . . . . . 308CHC0353I . . . . . . . . . . . . . 308CHC0354I . . . . . . . . . . . . . 309CHC0355E . . . . . . . . . . . . . 309

CHC0356E . . . . . . . . . . . . . 310CHC0357E . . . . . . . . . . . . . 310CHC0358E . . . . . . . . . . . . . 311CHC0359E . . . . . . . . . . . . . 311CHC0360W . . . . . . . . . . . . . 312CHC0361E . . . . . . . . . . . . . 312CHC0364E . . . . . . . . . . . . . 313CHC0365W . . . . . . . . . . . . . 313CHC0366E . . . . . . . . . . . . . 314CHC0367E . . . . . . . . . . . . . 314CHC0368I . . . . . . . . . . . . . 315CHC0369I . . . . . . . . . . . . . 315CHC0371W . . . . . . . . . . . . . 315CHC0374E . . . . . . . . . . . . . 316CHC0375E . . . . . . . . . . . . . 316CHC0376W . . . . . . . . . . . . . 317CHC0377W . . . . . . . . . . . . . 317CHC0378W . . . . . . . . . . . . . 317CHC0379W . . . . . . . . . . . . . 318CHC0380W . . . . . . . . . . . . . 318CHC0381W . . . . . . . . . . . . . 319CHC0382W . . . . . . . . . . . . . 320CHC0383W . . . . . . . . . . . . . 320CHC0384W . . . . . . . . . . . . . 321CHC0385I . . . . . . . . . . . . . 321CHC0386E . . . . . . . . . . . . . 322CHC0387I . . . . . . . . . . . . . 322CHC0388E . . . . . . . . . . . . . 323CHC0389E . . . . . . . . . . . . . 323CHC0390I . . . . . . . . . . . . . 323CHC0391I . . . . . . . . . . . . . 324CHC0392I . . . . . . . . . . . . . 324CHC0393I . . . . . . . . . . . . . 324CHC0394I . . . . . . . . . . . . . 325CHC0395E . . . . . . . . . . . . . 325CHC0396I . . . . . . . . . . . . . 325

CHC04 messages . . . . . . . . . . . . 326CHC0401W . . . . . . . . . . . . . 326CHC0402I . . . . . . . . . . . . . 327CHC0403W . . . . . . . . . . . . . 327CHC0404E . . . . . . . . . . . . . 328CHC0405W . . . . . . . . . . . . . 328CHC0407E . . . . . . . . . . . . . 329CHC0408E . . . . . . . . . . . . . 329CHC0409E . . . . . . . . . . . . . 330CHC0410W . . . . . . . . . . . . . 330CHC0411E . . . . . . . . . . . . . 331CHC0412E . . . . . . . . . . . . . 331CHC0418W . . . . . . . . . . . . . 331CHC0419W . . . . . . . . . . . . . 332CHC0420W . . . . . . . . . . . . . 332CHC0421W . . . . . . . . . . . . . 333CHC0422W . . . . . . . . . . . . . 333CHC0428E . . . . . . . . . . . . . 334CHC0429E . . . . . . . . . . . . . 334CHC0430E . . . . . . . . . . . . . 335CHC0431E . . . . . . . . . . . . . 335CHC0432E . . . . . . . . . . . . . 336CHC0495E . . . . . . . . . . . . . 336CHC0496E . . . . . . . . . . . . . 336

CHC05 messages . . . . . . . . . . . . 337

vi InfoSphere Change Data Capture: End-User Documentation

CHC0502E . . . . . . . . . . . . . 338CHC0503E . . . . . . . . . . . . . 339CHC0511I . . . . . . . . . . . . . 339CHC0512I . . . . . . . . . . . . . 339CHC0513I . . . . . . . . . . . . . 340CHC0514I . . . . . . . . . . . . . 340CHC0515I . . . . . . . . . . . . . 341CHC0516I . . . . . . . . . . . . . 341CHC0517I . . . . . . . . . . . . . 341CHC0518I . . . . . . . . . . . . . 342CHC0519I . . . . . . . . . . . . . 342CHC0529E . . . . . . . . . . . . . 343CHC0530E . . . . . . . . . . . . . 343CHC0531E . . . . . . . . . . . . . 344CHC0532E . . . . . . . . . . . . . 344CHC0533E . . . . . . . . . . . . . 344CHC0535E . . . . . . . . . . . . . 345CHC0536E . . . . . . . . . . . . . 345CHC0537E . . . . . . . . . . . . . 346CHC0538E . . . . . . . . . . . . . 346CHC0539E . . . . . . . . . . . . . 347CHC0540E . . . . . . . . . . . . . 347CHC0541E . . . . . . . . . . . . . 348CHC0543E . . . . . . . . . . . . . 348CHC0545E . . . . . . . . . . . . . 348CHC0546E . . . . . . . . . . . . . 349CHC0547E . . . . . . . . . . . . . 349CHC0548E . . . . . . . . . . . . . 349CHC0549E . . . . . . . . . . . . . 350CHC0550E . . . . . . . . . . . . . 350CHC0551E . . . . . . . . . . . . . 351CHC0552E . . . . . . . . . . . . . 351CHC0553E . . . . . . . . . . . . . 351CHC0554E . . . . . . . . . . . . . 352CHC0555E . . . . . . . . . . . . . 352CHC0556I . . . . . . . . . . . . . 353CHC0557E . . . . . . . . . . . . . 353CHC0558E . . . . . . . . . . . . . 354CHC0560E . . . . . . . . . . . . . 354CHC0561E . . . . . . . . . . . . . 354CHC0562E . . . . . . . . . . . . . 355CHC0564E . . . . . . . . . . . . . 355CHC0565E . . . . . . . . . . . . . 356CHC0566E . . . . . . . . . . . . . 356CHC0567W . . . . . . . . . . . . . 356CHC0568W . . . . . . . . . . . . . 357CHC0569W . . . . . . . . . . . . . 357CHC0570E . . . . . . . . . . . . . 358CHC0571W . . . . . . . . . . . . . 358CHC0572E . . . . . . . . . . . . . 359CHC0573E . . . . . . . . . . . . . 359CHC0574E . . . . . . . . . . . . . 360CHC0575E . . . . . . . . . . . . . 360CHC0576E . . . . . . . . . . . . . 361CHC0577W . . . . . . . . . . . . . 361CHC0579E . . . . . . . . . . . . . 362CHC0580E . . . . . . . . . . . . . 362CHC0581W . . . . . . . . . . . . . 363CHC0582E . . . . . . . . . . . . . 363CHC0583E . . . . . . . . . . . . . 363CHC0584E . . . . . . . . . . . . . 364

CHC0595I . . . . . . . . . . . . . 364CHC0596I . . . . . . . . . . . . . 365CHC0598W . . . . . . . . . . . . . 365CHC0599W . . . . . . . . . . . . . 366

CHC06 messages . . . . . . . . . . . . 366CHC0600I . . . . . . . . . . . . . 367CHC0602W . . . . . . . . . . . . . 367CHC0604W . . . . . . . . . . . . . 368CHC0605E . . . . . . . . . . . . . 368CHC0662E . . . . . . . . . . . . . 369CHC0663E . . . . . . . . . . . . . 369CHC0669W . . . . . . . . . . . . . 369CHC0670W . . . . . . . . . . . . . 370CHC0676I . . . . . . . . . . . . . 371CHC0677I . . . . . . . . . . . . . 371CHC0683I . . . . . . . . . . . . . 371CHC0684I . . . . . . . . . . . . . 372CHC0685I . . . . . . . . . . . . . 372CHC0686I . . . . . . . . . . . . . 372CHC0687I . . . . . . . . . . . . . 373CHC0688I . . . . . . . . . . . . . 373CHC0689I . . . . . . . . . . . . . 374CHC0690I . . . . . . . . . . . . . 374

CHC07 messages . . . . . . . . . . . . 374CHC0701I . . . . . . . . . . . . . 376CHC0702I . . . . . . . . . . . . . 376CHC0703I . . . . . . . . . . . . . 376CHC0704I . . . . . . . . . . . . . 377CHC0705I . . . . . . . . . . . . . 377CHC0706I . . . . . . . . . . . . . 378CHC0707I . . . . . . . . . . . . . 378CHC0708I . . . . . . . . . . . . . 378CHC0709I . . . . . . . . . . . . . 379CHC0711I . . . . . . . . . . . . . 379CHC0712I . . . . . . . . . . . . . 380CHC0713I . . . . . . . . . . . . . 380CHC0714I . . . . . . . . . . . . . 380CHC0715I . . . . . . . . . . . . . 381CHC0716I . . . . . . . . . . . . . 381CHC0717I . . . . . . . . . . . . . 382CHC0718I . . . . . . . . . . . . . 382CHC0719I . . . . . . . . . . . . . 382CHC0721I . . . . . . . . . . . . . 383CHC0722I . . . . . . . . . . . . . 383CHC0723I . . . . . . . . . . . . . 384CHC0724I . . . . . . . . . . . . . 384CHC0725I . . . . . . . . . . . . . 385CHC0726I . . . . . . . . . . . . . 385CHC0727I . . . . . . . . . . . . . 385CHC0728I . . . . . . . . . . . . . 386CHC0729E . . . . . . . . . . . . . 386CHC0731I . . . . . . . . . . . . . 387CHC0732I . . . . . . . . . . . . . 387CHC0733I . . . . . . . . . . . . . 388CHC0734I . . . . . . . . . . . . . 388CHC0735I . . . . . . . . . . . . . 388CHC0736E . . . . . . . . . . . . . 389CHC0741I . . . . . . . . . . . . . 389CHC0742I . . . . . . . . . . . . . 389CHC0743I . . . . . . . . . . . . . 390CHC0744I . . . . . . . . . . . . . 390

Contents vii

CHC0745I . . . . . . . . . . . . . 391CHC0746I . . . . . . . . . . . . . 391CHC0747I . . . . . . . . . . . . . 392CHC0751I . . . . . . . . . . . . . 392CHC0752I . . . . . . . . . . . . . 393CHC0753I . . . . . . . . . . . . . 393CHC0755I . . . . . . . . . . . . . 393CHC0761I . . . . . . . . . . . . . 394CHC0762I . . . . . . . . . . . . . 394CHC0763I . . . . . . . . . . . . . 394CHC0764E . . . . . . . . . . . . . 395CHC0765E . . . . . . . . . . . . . 395CHC0772I . . . . . . . . . . . . . 395CHC0779W . . . . . . . . . . . . . 396CHC0782I . . . . . . . . . . . . . 396CHC0783I . . . . . . . . . . . . . 396CHC0788W . . . . . . . . . . . . . 397CHC0791I . . . . . . . . . . . . . 397CHC0792I . . . . . . . . . . . . . 398CHC0793I . . . . . . . . . . . . . 398CHC0799W . . . . . . . . . . . . . 399

CHC08 messages . . . . . . . . . . . . 399CHC0800W . . . . . . . . . . . . . 400CHC0801W . . . . . . . . . . . . . 400CHC0802W . . . . . . . . . . . . . 401CHC0803W . . . . . . . . . . . . . 402CHC0804W . . . . . . . . . . . . . 402CHC0805W . . . . . . . . . . . . . 403CHC0811E . . . . . . . . . . . . . 403CHC0821E . . . . . . . . . . . . . 404CHC0824E . . . . . . . . . . . . . 404CHC0825E . . . . . . . . . . . . . 405CHC0826E . . . . . . . . . . . . . 405CHC0831E . . . . . . . . . . . . . 406CHC0839W . . . . . . . . . . . . . 406CHC0844I . . . . . . . . . . . . . 407CHC0845I . . . . . . . . . . . . . 407CHC0846I . . . . . . . . . . . . . 408CHC0847I . . . . . . . . . . . . . 408CHC0848I . . . . . . . . . . . . . 409CHC0859E . . . . . . . . . . . . . 409

CHC10 messages . . . . . . . . . . . . 410CHC1019E . . . . . . . . . . . . . 410

CHC11 messages . . . . . . . . . . . . 410CHC1100E . . . . . . . . . . . . . 411CHC1101E . . . . . . . . . . . . . 411CHC1102W . . . . . . . . . . . . . 412CHC1103E . . . . . . . . . . . . . 412CHC1104E . . . . . . . . . . . . . 413CHC1106I . . . . . . . . . . . . . 413CHC1107I . . . . . . . . . . . . . 413CHC1108I . . . . . . . . . . . . . 414CHC1109E . . . . . . . . . . . . . 414CHC1110E . . . . . . . . . . . . . 414CHC1111E . . . . . . . . . . . . . 415CHC1113I . . . . . . . . . . . . . 415CHC1114I . . . . . . . . . . . . . 415CHC1115I . . . . . . . . . . . . . 416CHC1116E . . . . . . . . . . . . . 417CHC1117E . . . . . . . . . . . . . 417CHC1118W . . . . . . . . . . . . . 417

CHC1119I . . . . . . . . . . . . . 418CHC1120I . . . . . . . . . . . . . 418CHC1121E . . . . . . . . . . . . . 419

CHC12 messages . . . . . . . . . . . . 419CHC1232E . . . . . . . . . . . . . 419CHC1251I . . . . . . . . . . . . . 420CHC1252I . . . . . . . . . . . . . 420CHC1258I . . . . . . . . . . . . . 420CHC1259I . . . . . . . . . . . . . 421

CHC14 messages . . . . . . . . . . . . 421CHC1400E . . . . . . . . . . . . . 422CHC1401E . . . . . . . . . . . . . 422CHC1402E . . . . . . . . . . . . . 423CHC1403E . . . . . . . . . . . . . 423CHC1404E . . . . . . . . . . . . . 424CHC1405E . . . . . . . . . . . . . 424CHC1406E . . . . . . . . . . . . . 425CHC1408E . . . . . . . . . . . . . 425CHC1410W . . . . . . . . . . . . . 425CHC1411W . . . . . . . . . . . . . 426CHC1412E . . . . . . . . . . . . . 427CHC1413E . . . . . . . . . . . . . 427CHC1414E . . . . . . . . . . . . . 428CHC1415E . . . . . . . . . . . . . 428CHC1416E . . . . . . . . . . . . . 428CHC1417E . . . . . . . . . . . . . 429CHC1418E . . . . . . . . . . . . . 429CHC1419E . . . . . . . . . . . . . 430CHC1420E . . . . . . . . . . . . . 430CHC1421E . . . . . . . . . . . . . 431CHC1422E . . . . . . . . . . . . . 431CHC1423E . . . . . . . . . . . . . 432CHC1424E . . . . . . . . . . . . . 432CHC1425E . . . . . . . . . . . . . 433CHC1426E . . . . . . . . . . . . . 433CHC1432W . . . . . . . . . . . . . 434CHC1433W . . . . . . . . . . . . . 434

CHC15 messages . . . . . . . . . . . . 435CHC1501E . . . . . . . . . . . . . 435CHC1502E . . . . . . . . . . . . . 436CHC1503E . . . . . . . . . . . . . 436CHC1504I . . . . . . . . . . . . . 437CHC1505I . . . . . . . . . . . . . 437CHC1508W . . . . . . . . . . . . . 437CHC1511I . . . . . . . . . . . . . 438CHC1514W . . . . . . . . . . . . . 438CHC1515W . . . . . . . . . . . . . 439CHC1517E . . . . . . . . . . . . . 439CHC1518E . . . . . . . . . . . . . 440CHC1520E . . . . . . . . . . . . . 441CHC1521E . . . . . . . . . . . . . 441CHC1522E . . . . . . . . . . . . . 442CHC1524E . . . . . . . . . . . . . 442CHC1527E . . . . . . . . . . . . . 443CHC1531W . . . . . . . . . . . . . 443CHC1532W . . . . . . . . . . . . . 443CHC1533W . . . . . . . . . . . . . 444CHC1539E . . . . . . . . . . . . . 444CHC1540E . . . . . . . . . . . . . 445CHC1541E . . . . . . . . . . . . . 445CHC1542E . . . . . . . . . . . . . 445

viii InfoSphere Change Data Capture: End-User Documentation

CHC1543I . . . . . . . . . . . . . 446CHC1544I . . . . . . . . . . . . . 446CHC1545I . . . . . . . . . . . . . 447CHC1551I . . . . . . . . . . . . . 447CHC1552I . . . . . . . . . . . . . 448CHC1553I . . . . . . . . . . . . . 448CHC1559W . . . . . . . . . . . . . 449CHC1560W . . . . . . . . . . . . . 449

CHC16 messages . . . . . . . . . . . . 449CHC1600I . . . . . . . . . . . . . 450CHC1602E . . . . . . . . . . . . . 451CHC1603E . . . . . . . . . . . . . 451CHC1604E . . . . . . . . . . . . . 451CHC1605E . . . . . . . . . . . . . 452CHC1606E . . . . . . . . . . . . . 452CHC1607E . . . . . . . . . . . . . 453CHC1608E . . . . . . . . . . . . . 453CHC1609E . . . . . . . . . . . . . 454CHC1610E . . . . . . . . . . . . . 454CHC1611E . . . . . . . . . . . . . 454CHC1612E . . . . . . . . . . . . . 455CHC1613E . . . . . . . . . . . . . 455CHC1614E . . . . . . . . . . . . . 456CHC1615E . . . . . . . . . . . . . 456CHC1616E . . . . . . . . . . . . . 457CHC1617E . . . . . . . . . . . . . 457CHC1618E . . . . . . . . . . . . . 458CHC1619E . . . . . . . . . . . . . 458CHC1620E . . . . . . . . . . . . . 459CHC1621E . . . . . . . . . . . . . 459CHC1622E . . . . . . . . . . . . . 460CHC1623E . . . . . . . . . . . . . 460CHC1624E . . . . . . . . . . . . . 460CHC1625E . . . . . . . . . . . . . 461CHC1626E . . . . . . . . . . . . . 461CHC1627E . . . . . . . . . . . . . 462CHC1628E . . . . . . . . . . . . . 462CHC1629E . . . . . . . . . . . . . 463CHC1630E . . . . . . . . . . . . . 463CHC1631E . . . . . . . . . . . . . 464


CHC19 messages . . . . . . . . . . . . 465CHC1902E . . . . . . . . . . . . . 465CHC1904E . . . . . . . . . . . . . 466CHC1905E . . . . . . . . . . . . . 466CHC1906E . . . . . . . . . . . . . 467CHC1907E . . . . . . . . . . . . . 467CHC1908E . . . . . . . . . . . . . 467CHC1909E . . . . . . . . . . . . . 468CHC1910E . . . . . . . . . . . . . 468CHC1914E . . . . . . . . . . . . . 469CHC1915E . . . . . . . . . . . . . 469CHC1921E . . . . . . . . . . . . . 469CHC1922E . . . . . . . . . . . . . 470CHC1923E . . . . . . . . . . . . . 470CHC1924E . . . . . . . . . . . . . 471

CHC20 messages . . . . . . . . . . . . 471CHC2000E . . . . . . . . . . . . . 471CHC2001I . . . . . . . . . . . . . 472CHC2002I . . . . . . . . . . . . . 472

CHC2007I . . . . . . . . . . . . . 473CHC30 messages . . . . . . . . . . . . 473

CHC3001E . . . . . . . . . . . . . 474CHC3002E . . . . . . . . . . . . . 474CHC3004I . . . . . . . . . . . . . 475CHC3005I . . . . . . . . . . . . . 475CHC3007E . . . . . . . . . . . . . 475CHC3008W . . . . . . . . . . . . . 476CHC3009I . . . . . . . . . . . . . 476CHC3010W . . . . . . . . . . . . . 477CHC3011E . . . . . . . . . . . . . 477CHC3012I . . . . . . . . . . . . . 478CHC3013I . . . . . . . . . . . . . 478CHC3014I . . . . . . . . . . . . . 478CHC3015I . . . . . . . . . . . . . 479CHC3016I . . . . . . . . . . . . . 479CHC3101E . . . . . . . . . . . . . 479CHC3102E . . . . . . . . . . . . . 480CHC3103E . . . . . . . . . . . . . 481CHC3104E . . . . . . . . . . . . . 481CHC3105E . . . . . . . . . . . . . 482CHC3106E . . . . . . . . . . . . . 482CHC3107E . . . . . . . . . . . . . 483CHC3138W . . . . . . . . . . . . . 483CHC3139W . . . . . . . . . . . . . 484CHC3140E . . . . . . . . . . . . . 484CHC3142W . . . . . . . . . . . . . 485CHC3157W . . . . . . . . . . . . . 485CHC3174E . . . . . . . . . . . . . 486CHC3175E . . . . . . . . . . . . . 486CHC3176E . . . . . . . . . . . . . 487CHC3177E . . . . . . . . . . . . . 487CHC3178E . . . . . . . . . . . . . 488CHC3179E . . . . . . . . . . . . . 488CHC3180E . . . . . . . . . . . . . 489CHC3181E . . . . . . . . . . . . . 490CHC3182E . . . . . . . . . . . . . 490CHC3183E . . . . . . . . . . . . . 491CHC3184E . . . . . . . . . . . . . 491CHC3185E . . . . . . . . . . . . . 492CHC3186E . . . . . . . . . . . . . 492

CHC50 messages . . . . . . . . . . . . 492CHC5002I . . . . . . . . . . . . . 493CHC5003I . . . . . . . . . . . . . 493CHC5099I . . . . . . . . . . . . . 494CHC5101I . . . . . . . . . . . . . 494CHC5102E . . . . . . . . . . . . . 494CHC5103E . . . . . . . . . . . . . 495CHC5108E . . . . . . . . . . . . . 495CHC5109E . . . . . . . . . . . . . 496CHC5110E . . . . . . . . . . . . . 496CHC5111E . . . . . . . . . . . . . 496CHC5112E . . . . . . . . . . . . . 497CHC5118I . . . . . . . . . . . . . 497CHC5119I . . . . . . . . . . . . . 498CHC5120I . . . . . . . . . . . . . 498CHC5121I . . . . . . . . . . . . . 498CHC5127E . . . . . . . . . . . . . 499CHC5128E . . . . . . . . . . . . . 499CHC5129E . . . . . . . . . . . . . 500CHC5135E . . . . . . . . . . . . . 500

Contents ix

CHC5136E . . . . . . . . . . . . . 500CHC5137E . . . . . . . . . . . . . 501CHC5143I . . . . . . . . . . . . . 501CHC5144I . . . . . . . . . . . . . 501

CHC60 messages . . . . . . . . . . . . 502CHC6104I . . . . . . . . . . . . . 504CHC6105I . . . . . . . . . . . . . 505CHC6106E . . . . . . . . . . . . . 505CHC6107E . . . . . . . . . . . . . 506CHC6108E . . . . . . . . . . . . . 506CHC6113E . . . . . . . . . . . . . 507CHC6114E . . . . . . . . . . . . . 507CHC6117E . . . . . . . . . . . . . 508CHC6118E . . . . . . . . . . . . . 508CHC6119E . . . . . . . . . . . . . 508CHC6120E . . . . . . . . . . . . . 509CHC6121E . . . . . . . . . . . . . 509CHC6122E . . . . . . . . . . . . . 510CHC6123E . . . . . . . . . . . . . 510CHC6124E . . . . . . . . . . . . . 510CHC6125E . . . . . . . . . . . . . 511CHC6201E . . . . . . . . . . . . . 511CHC6202E . . . . . . . . . . . . . 512CHC6203E . . . . . . . . . . . . . 512CHC6204E . . . . . . . . . . . . . 512CHC6205E . . . . . . . . . . . . . 513CHC6207E . . . . . . . . . . . . . 513CHC6208I . . . . . . . . . . . . . 514CHC6209I . . . . . . . . . . . . . 514CHC6210E . . . . . . . . . . . . . 514CHC6301W . . . . . . . . . . . . . 515CHC6302E . . . . . . . . . . . . . 515CHC6303E . . . . . . . . . . . . . 516CHC6304E . . . . . . . . . . . . . 516CHC6307E . . . . . . . . . . . . . 516CHC6308E . . . . . . . . . . . . . 517CHC6309E . . . . . . . . . . . . . 517CHC6314E . . . . . . . . . . . . . 518CHC6315E . . . . . . . . . . . . . 518CHC6317E . . . . . . . . . . . . . 518CHC6318E . . . . . . . . . . . . . 519CHC6320E . . . . . . . . . . . . . 519CHC6321E . . . . . . . . . . . . . 520CHC6323W . . . . . . . . . . . . . 520CHC6402E . . . . . . . . . . . . . 520CHC6403E . . . . . . . . . . . . . 521CHC6404I . . . . . . . . . . . . . 521CHC6405I . . . . . . . . . . . . . 522CHC6406I . . . . . . . . . . . . . 522CHC6407E . . . . . . . . . . . . . 523CHC6408I . . . . . . . . . . . . . 523CHC6410I . . . . . . . . . . . . . 524CHC6411I . . . . . . . . . . . . . 524CHC6412I . . . . . . . . . . . . . 524CHC6413I . . . . . . . . . . . . . 525CHC6414I . . . . . . . . . . . . . 525CHC6415W . . . . . . . . . . . . . 526CHC6416W . . . . . . . . . . . . . 526CHC6417W . . . . . . . . . . . . . 527CHC6418W . . . . . . . . . . . . . 527CHC6419E . . . . . . . . . . . . . 528

CHC6420E . . . . . . . . . . . . . 528CHC6421E . . . . . . . . . . . . . 528CHC6422I . . . . . . . . . . . . . 529CHC6423I . . . . . . . . . . . . . 529CHC6424E . . . . . . . . . . . . . 530CHC6425I . . . . . . . . . . . . . 530CHC6426E . . . . . . . . . . . . . 530CHC6429I . . . . . . . . . . . . . 531CHC6430W . . . . . . . . . . . . . 531CHC6431W . . . . . . . . . . . . . 532CHC6432W . . . . . . . . . . . . . 532CHC6433W . . . . . . . . . . . . . 533CHC6434W . . . . . . . . . . . . . 533CHC6435W . . . . . . . . . . . . . 534CHC6436W . . . . . . . . . . . . . 534CHC6437W . . . . . . . . . . . . . 534CHC6438W . . . . . . . . . . . . . 535CHC6439E . . . . . . . . . . . . . 535CHC6440W . . . . . . . . . . . . . 536CHC6445I . . . . . . . . . . . . . 536CHC6446I . . . . . . . . . . . . . 537CHC6448W . . . . . . . . . . . . . 537CHC6451E . . . . . . . . . . . . . 538CHC6452E . . . . . . . . . . . . . 538CHC6453W . . . . . . . . . . . . . 539CHC6454E . . . . . . . . . . . . . 539CHC6455E . . . . . . . . . . . . . 540CHC6456E . . . . . . . . . . . . . 540CHC6457W . . . . . . . . . . . . . 541CHC6458E . . . . . . . . . . . . . 541CHC6459E . . . . . . . . . . . . . 542CHC6460I . . . . . . . . . . . . . 542CHC6465W . . . . . . . . . . . . . 543CHC6466E . . . . . . . . . . . . . 543CHC6467W . . . . . . . . . . . . . 544CHC6468E . . . . . . . . . . . . . 545CHC6471I . . . . . . . . . . . . . 545CHC6472W . . . . . . . . . . . . . 546CHC6473E . . . . . . . . . . . . . 546CHC6501I . . . . . . . . . . . . . 547CHC6502I . . . . . . . . . . . . . 547CHC6503E . . . . . . . . . . . . . 547CHC6504E . . . . . . . . . . . . . 548CHC6505E . . . . . . . . . . . . . 548CHC6506E . . . . . . . . . . . . . 549CHC6509W . . . . . . . . . . . . . 549CHC6511E . . . . . . . . . . . . . 550CHC6512E . . . . . . . . . . . . . 550CHC6513E . . . . . . . . . . . . . 550CHC6514E . . . . . . . . . . . . . 551CHC6515E . . . . . . . . . . . . . 551CHC6516I . . . . . . . . . . . . . 552CHC6801E . . . . . . . . . . . . . 552CHC6802E . . . . . . . . . . . . . 553CHC6803E . . . . . . . . . . . . . 553CHC6804I . . . . . . . . . . . . . 554CHC6903E . . . . . . . . . . . . . 554CHC6995E . . . . . . . . . . . . . 555CHC6998E . . . . . . . . . . . . . 555


x InfoSphere Change Data Capture: End-User Documentation

CHC7053E . . . . . . . . . . . . . 557CHC7054E . . . . . . . . . . . . . 557CHC7055E . . . . . . . . . . . . . 558CHC7057E . . . . . . . . . . . . . 559CHC7058E . . . . . . . . . . . . . 559CHC7059E . . . . . . . . . . . . . 560CHC7060E . . . . . . . . . . . . . 560CHC7061E . . . . . . . . . . . . . 561CHC7064E . . . . . . . . . . . . . 561CHC7065E . . . . . . . . . . . . . 561CHC7069E . . . . . . . . . . . . . 562CHC7070E . . . . . . . . . . . . . 562CHC7071E . . . . . . . . . . . . . 563CHC7072E . . . . . . . . . . . . . 563CHC7073E . . . . . . . . . . . . . 563CHC7074E . . . . . . . . . . . . . 564CHC7075I . . . . . . . . . . . . . 564CHC7077I . . . . . . . . . . . . . 565CHC7078I . . . . . . . . . . . . . 565CHC7079I . . . . . . . . . . . . . 565CHC7081E . . . . . . . . . . . . . 566CHC7082E . . . . . . . . . . . . . 566CHC7083E . . . . . . . . . . . . . 567CHC7084E . . . . . . . . . . . . . 567CHC7085E . . . . . . . . . . . . . 567CHC7086E . . . . . . . . . . . . . 568CHC7087E . . . . . . . . . . . . . 568CHC7088E . . . . . . . . . . . . . 569CHC7089W . . . . . . . . . . . . . 569CHC7094E . . . . . . . . . . . . . 570CHC7095I . . . . . . . . . . . . . 570CHC7099E . . . . . . . . . . . . . 571

CHC90 messages . . . . . . . . . . . . 571CHC9101I . . . . . . . . . . . . . 575CHC9102I . . . . . . . . . . . . . 576CHC9104I . . . . . . . . . . . . . 576CHC9105I . . . . . . . . . . . . . 576CHC9106I . . . . . . . . . . . . . 577CHC9107I . . . . . . . . . . . . . 577CHC9110T . . . . . . . . . . . . . 577CHC9155E . . . . . . . . . . . . . 578CHC9201I . . . . . . . . . . . . . 578CHC9204W . . . . . . . . . . . . . 579CHC9205I . . . . . . . . . . . . . 579CHC9208I . . . . . . . . . . . . . 579CHC9209I . . . . . . . . . . . . . 580CHC9210E . . . . . . . . . . . . . 580CHC9212E . . . . . . . . . . . . . 580CHC9213E . . . . . . . . . . . . . 581CHC9214E . . . . . . . . . . . . . 581CHC9217E . . . . . . . . . . . . . 582CHC9218E . . . . . . . . . . . . . 582CHC9219E . . . . . . . . . . . . . 582CHC9220W . . . . . . . . . . . . . 583CHC9221W . . . . . . . . . . . . . 583CHC9222W . . . . . . . . . . . . . 584CHC9228I . . . . . . . . . . . . . 584CHC9229I . . . . . . . . . . . . . 584CHC9230I . . . . . . . . . . . . . 585CHC9231I . . . . . . . . . . . . . 585CHC9500E . . . . . . . . . . . . . 586

CHC9502W . . . . . . . . . . . . . 586CHC9504E . . . . . . . . . . . . . 587CHC9506E . . . . . . . . . . . . . 587CHC9510W . . . . . . . . . . . . . 588CHC9512I . . . . . . . . . . . . . 588CHC9514W . . . . . . . . . . . . . 589CHC9516W . . . . . . . . . . . . . 589CHC9518W . . . . . . . . . . . . . 589CHC9521I . . . . . . . . . . . . . 590CHC9522I . . . . . . . . . . . . . 590CHC9523I . . . . . . . . . . . . . 591CHC9524I . . . . . . . . . . . . . 591CHC9525I . . . . . . . . . . . . . 592CHC9526I . . . . . . . . . . . . . 592CHC9527I . . . . . . . . . . . . . 593CHC9528I . . . . . . . . . . . . . 593CHC9600I . . . . . . . . . . . . . 594CHC9601I . . . . . . . . . . . . . 594CHC9605I . . . . . . . . . . . . . 595CHC9606W . . . . . . . . . . . . . 595CHC9607I . . . . . . . . . . . . . 595CHC9608I . . . . . . . . . . . . . 596CHC9609I . . . . . . . . . . . . . 596CHC9610I . . . . . . . . . . . . . 597CHC9611I . . . . . . . . . . . . . 597CHC9612I . . . . . . . . . . . . . 597CHC9613I . . . . . . . . . . . . . 598CHC9614I . . . . . . . . . . . . . 598CHC9615I . . . . . . . . . . . . . 598CHC9616W . . . . . . . . . . . . . 599CHC9618W . . . . . . . . . . . . . 600CHC9619W . . . . . . . . . . . . . 600CHC9650E . . . . . . . . . . . . . 600CHC9651E . . . . . . . . . . . . . 601CHC9652E . . . . . . . . . . . . . 601CHC9653E . . . . . . . . . . . . . 601CHC9654E . . . . . . . . . . . . . 602CHC9655E . . . . . . . . . . . . . 602CHC9656I . . . . . . . . . . . . . 603CHC9657I . . . . . . . . . . . . . 603CHC9659E . . . . . . . . . . . . . 604CHC9660W . . . . . . . . . . . . . 604CHC9661I . . . . . . . . . . . . . 605CHC9662I . . . . . . . . . . . . . 605CHC9664I . . . . . . . . . . . . . 605CHC9665I . . . . . . . . . . . . . 606CHC9666E . . . . . . . . . . . . . 606CHC9667E . . . . . . . . . . . . . 606CHC9669E . . . . . . . . . . . . . 607CHC9670W . . . . . . . . . . . . . 607CHC9671W . . . . . . . . . . . . . 608CHC9672I . . . . . . . . . . . . . 608CHC9673E . . . . . . . . . . . . . 609CHC9674E . . . . . . . . . . . . . 609CHC9675E . . . . . . . . . . . . . 609CHC9676W . . . . . . . . . . . . . 610CHC9677W . . . . . . . . . . . . . 610CHC9679W . . . . . . . . . . . . . 610CHC9680W . . . . . . . . . . . . . 611CHC9681I . . . . . . . . . . . . . 612CHC9683W . . . . . . . . . . . . . 612

Contents xi

CHC9684W . . . . . . . . . . . . . 613CHC9685W . . . . . . . . . . . . . 613CHC9686W . . . . . . . . . . . . . 614CHC9690E . . . . . . . . . . . . . 615CHC9691E . . . . . . . . . . . . . 615CHC9692I . . . . . . . . . . . . . 616CHC9693I . . . . . . . . . . . . . 616CHC9694W . . . . . . . . . . . . . 616CHC9695W . . . . . . . . . . . . . 617CHC9696E . . . . . . . . . . . . . 617CHC9698I . . . . . . . . . . . . . 618CHC9699E . . . . . . . . . . . . . 618CHC9700E . . . . . . . . . . . . . 619CHC9702E . . . . . . . . . . . . . 619CHC9703E . . . . . . . . . . . . . 619CHC9705E . . . . . . . . . . . . . 620CHC9706E . . . . . . . . . . . . . 621CHC9712E . . . . . . . . . . . . . 621CHC9713E . . . . . . . . . . . . . 621CHC9714W . . . . . . . . . . . . . 622CHC9715E . . . . . . . . . . . . . 622CHC9719E . . . . . . . . . . . . . 623CHC9720E . . . . . . . . . . . . . 624CHC9721E . . . . . . . . . . . . . 624CHC9722E . . . . . . . . . . . . . 625CHC9723E . . . . . . . . . . . . . 625CHC9733I . . . . . . . . . . . . . 626CHC9742I . . . . . . . . . . . . . 626CHC9743E . . . . . . . . . . . . . 627CHC9744E . . . . . . . . . . . . . 627CHC9745E . . . . . . . . . . . . . 628CHC9746E . . . . . . . . . . . . . 628CHC9751I . . . . . . . . . . . . . 628CHC9753I . . . . . . . . . . . . . 629CHC9756E . . . . . . . . . . . . . 629CHC9757E . . . . . . . . . . . . . 630CHC9758E . . . . . . . . . . . . . 630CHC9764E . . . . . . . . . . . . . 630CHC9765E . . . . . . . . . . . . . 631CHC9766E . . . . . . . . . . . . . 631CHC9767E . . . . . . . . . . . . . 632CHC9768E . . . . . . . . . . . . . 632CHC9769E . . . . . . . . . . . . . 632CHC9770E . . . . . . . . . . . . . 633CHC9776I . . . . . . . . . . . . . 633CHC9777I . . . . . . . . . . . . . 634CHC9778I . . . . . . . . . . . . . 634CHC9779I . . . . . . . . . . . . . 635CHC9780I . . . . . . . . . . . . . 636

CHC9786I . . . . . . . . . . . . . 636CHC9787I . . . . . . . . . . . . . 637CHC9788I . . . . . . . . . . . . . 638CHC9789I . . . . . . . . . . . . . 638CHC9795L . . . . . . . . . . . . . 639CHC9796L . . . . . . . . . . . . . 639CHC9798E . . . . . . . . . . . . . 640CHC9799I . . . . . . . . . . . . . 640CHC9800I . . . . . . . . . . . . . 641CHC9801I . . . . . . . . . . . . . 641CHC9802I . . . . . . . . . . . . . 642CHC9803I . . . . . . . . . . . . . 643CHC9804I . . . . . . . . . . . . . 644CHC9805I . . . . . . . . . . . . . 645CHC9812E . . . . . . . . . . . . . 646CHC9813E . . . . . . . . . . . . . 646CHC9814E . . . . . . . . . . . . . 647CHC9815E . . . . . . . . . . . . . 647CHC9816E . . . . . . . . . . . . . 647CHC9817I . . . . . . . . . . . . . 648CHC9818I . . . . . . . . . . . . . 648CHC9819I . . . . . . . . . . . . . 649CHC9830I . . . . . . . . . . . . . 649CHC9831I . . . . . . . . . . . . . 650CHC9832I . . . . . . . . . . . . . 651CHC9833I . . . . . . . . . . . . . 651CHC9834I . . . . . . . . . . . . . 652CHC9835I . . . . . . . . . . . . . 652CHC9840I . . . . . . . . . . . . . 653CHC9841I . . . . . . . . . . . . . 654CHC9842I . . . . . . . . . . . . . 655CHC9843I . . . . . . . . . . . . . 655CHC9844I . . . . . . . . . . . . . 656CHC9845I . . . . . . . . . . . . . 657CHC9846I . . . . . . . . . . . . . 657CHC9847I . . . . . . . . . . . . . 658CHC9853I . . . . . . . . . . . . . 659CHC9854I . . . . . . . . . . . . . 660CHC9855I . . . . . . . . . . . . . 661CHC9856I . . . . . . . . . . . . . 662CHC9857I . . . . . . . . . . . . . 663CHC9858I . . . . . . . . . . . . . 664CHC9859I . . . . . . . . . . . . . 665CHC9860I . . . . . . . . . . . . . 666

Notices . . . . . . . . . . . . . . 667Trademarks . . . . . . . . . . . . . . 669

xii InfoSphere Change Data Capture: End-User Documentation

IBM InfoSphere Change Data Capture installation or upgrade

This section describes how to install IBM® InfoSphere™ Change Data Capture, orsimply, InfoSphere CDC, on a z/OS® system in a source or target environment. Itassumes that you are familiar with z/OS environments and SMP/E.

Note: To migrate a Transformation Server for z/OS version 4.x installation toversion 5.4, you can contact your IBM representative for information on themigration services that are available to assist you.

In this section, you will learn:“InfoSphere CDC overview”“Minimum requirements” on page 2“Before you install” on page 2“Installing InfoSphere CDC” on page 7“Introduction to modifying the InfoSphere CDC configuration control data set”on page 21“Linking Transformation Server user exits for InfoSphere CDC” on page 23“Modifying general product configuration control statements” on page 27“Modifying communications configuration control statements” on page 43“Modifying DBMS configuration control statements” on page 49“Modifying DB2 LOAD configuration control statements” on page 65“Modifying UCS configuration control statements” on page 70“Executing InfoSphere CDC” on page 74“Estimating InfoSphere CDC’s requirements for hiperspaces and auxiliarystorage” on page 75“BUFTHRESHOLD keyword considerations” on page 76“Installing and running multiple InfoSphere CDC instances” on page 80“Reverting to InfoSphere CDC for z/OS version 5.4” on page 81

InfoSphere CDC overviewInfoSphere CDC allows you to replicate DB2® data on a z/OS system to supportedtarget databases. In addition, data from supported source databases can bereplicated to DB2 on a z/OS system. InfoSphere CDC is intended for organizationsthat want to replicate DB2 data to or from a z/OS system. More specifically,InfoSphere CDC provides the necessary support to implement data distribution,data sharing, or data transformation.

InfoSphere CDC’s front-end functionality is provided through ManagementConsole. Management Console allows you to work with tables and databases insource and target environments in order to configure, start, and monitorreplication. Management Console communicates with InfoSphere CDC to supportthe sending and receiving of DB2 table data.

© Copyright IBM Corp. 2008, 2009 1

Minimum requirementsInfoSphere CDC requires a z/OS system with the following minimumconfiguration:

Hardware Requirements

v Disk Space—40 cylinders of a 3390 DASD device or equivalent for installingand maintaining InfoSphere CDC. Additional space requirements for data setsused during execution are determined by the installer.

Software Requirements

v Client Interface—Management Console version 6.3 or greater.v Operating System—z/OS Version 1 Release 7 or greaterv zSeries® or z/Architecture® Database—DB2 for z/OS Version 8, or DB2 for z/OS

Version 9v SMP/E—z/OS Version 1 Release 7 or greaterv LE/390—z/OS Version 1 Release 7 or greaterv Communications Server—z/OS Version 1 Release 7 or greater

Before you installThis section contains information about the tasks that should be performed prior toinstalling InfoSphere CDC on your z/OS system.

See also:“What is on the tape cartridge?”“About the InfoSphere CDC program directory” on page 3“Customizing your InfoSphere CDC installation” on page 3“Evaluating z/OS and DB2 configuration parameters prior to InfoSphere CDCinstallation” on page 3“Prerequisite program products” on page 5“Required storage devices” on page 5“Required SMP/E target and distribution libraries” on page 5“Choosing system or private libraries” on page 5“Should you install InfoSphere CDC resident?” on page 5“Obtaining up-to-date maintenance during installation” on page 5“Considerations for upgrading from releases prior to InfoSphere CDC for z/OSversion 5.4” on page 5

What is on the tape cartridge?The usual distribution medium is a tape cartridge. The tape cartridge is writtenwith data sets that contain object text used to create executable code, sample JCL,and additional data sets organized and written in a manner suitable for aninstallation process using SMP/E.

Additionally, InfoSphere CDC is distributed from the Internet. Instructions areincluded on how to upload the distribution data from the local media to a z/OSsystem, and how to reformat it so that it can be processed by SMP/E. If theInternet distribution method is used, this documentation still provides necessaryinformation about how to manage the SMP/E installation, how to prepareInfoSphere CDC’s metadata DB2 tables, and so on.

2 InfoSphere Change Data Capture: End-User Documentation

About the InfoSphere CDC program directoryIncluded with the distribution tape cartridge is a Program Directory thatcompletely describes the contents of the distribution medium and provides explicitinstructions on how to start the InfoSphere CDC installation.

Customizing your InfoSphere CDC installationThe series of jobs that install InfoSphere CDC are straightforward, and should berun in the sequence documented (there are no customization capabilities availableat this time). However, before any of the jobs can be executed, certaininstallation-dependent values must be specified in the JCL and control statements.These installation values are represented by ″substitution placeholders″. Asubstitution placeholder is a text string that is usually contained within anglebrackets (″<″ and ″>″), contained within single quotes or preceded by a pound sign(#).

Not all substitution placeholders will appear in every job. Each job contains ablock of comments that lists the substitution placeholders that must be replacedwithin that job, and describes the values that should be used for each substitution.Additionally, where possible, the substitution placeholders are visually indicatedusing comments, making it easier to locate all instances of the substitutionplaceholders that need to be replaced.

Evaluating z/OS and DB2 configuration parameters prior toInfoSphere CDC installation

The following issues need to be considered:“ECSA”“Expanded storage, hiperspaces, and storage above the bar”“DB2 batch connections and allied threads” on page 4“DB2 log buffers” on page 4

ECSAInfoSphere CDC uses the DB2 Instrumentation Facility Interface (IFI) to obtaincopies of the changes made to database tables from the DB2 Log. The IFI requiresthat the application program (InfoSphere CDC) supply a storage buffer located inthe z/OS ECSA with storage key 7. A buffer (approximately 72KB in size or 288KBin size if a DB2 Data Sharing Group is being used) is required for each active IFIconnection. InfoSphere CDC will maintain an active IFI connection for eachsubscription for which it is actively mirroring data. InfoSphere CDC will alsomaintain one active IFI connection for the Log Cache, if it is configured. This mayrequire a reassessment of the size of ECSA as configured using z/OS IPLparameters, and will require an IPL if the value configured needs to be changed.

Expanded storage, hiperspaces, and storage above the barInfoSphere CDC uses hiperspaces for staging data that it has read from the DB2Log, until it reads a COMMIT DB2 Log record. Hiperspaces are stored in z/OSCentral Storage that is above the bar (64-bit addressable storage), and may bepaged to z/OS Auxiliary Storage if the page frames in Central Storage are stolenby z/OS on behalf of another address space. Accordingly, the amount of DASDstorage assigned to page or swap data sets may need to be increased in order toaccommodate the additional requirements from InfoSphere CDC. Above the barstorage used by hiperspaces is exempt from the limit imposed by the STG64LIMITkeyword.

IBM InfoSphere Change Data Capture installation or upgrade 3

InfoSphere CDC uses storage above the bar (64 bit addressable storage) to cachechanges on the target. As the changes are received from the source environment,they are cached and applied to the target tables. When the applied changes arecommitted, the cached changes are purged. If DB2 backs out the logical unit ofwork before the changes can be committed (for example, due to a deadlock ortimeout condition), then InfoSphere CDC will read the changes from the cache andreapply them. The allocation of storage above the bar is controlled by theMEMLIMIT JCL parameter. The sample JCL used to run InfoSphere CDC specifiesa REGION parameter with a value of 0M. This implies a default value forMEMLIMIT of “NOLIMIT”, meaning that there will be no restriction on the use ofstorage above the bar. If you change the value specified for the REGION parameterto anything other than 0M, then you must provide an explicit, nonzero value forthe MEMLIMIT parameter as well. Failure to do so will cause subscriptions to failwhen they cannot acquire any storage above the bar. Above the bar storage used tocache changes received from the source is also subject to the limit imposed by theSTG64LIMIT keyword.Related concepts

“Estimating InfoSphere CDC’s requirements for hiperspaces and auxiliary storage”on page 75

DB2 batch connections and allied threadsWhile it is executing, InfoSphere CDC opens several DB2 plans under separatesub-tasks. Each DB2 plan is opened using the DB2 batch Call Attach Facility, andso each opened DB2 plan requires a DB2 batch connection and represents a DB2user. Running InfoSphere CDC may require an adjustment to the maximumnumber of batch connections and allied threads (users) that DB2 can support. Inorder to determine what these adjustments (if any) are, you will need to know themaximum number of open plans that InfoSphere CDC will require. InfoSphereCDC keeps its DB2 plans open only as long as they are required, and closes themas soon as they are no longer needed. Accordingly, you will need to know themaximum number of concurrent replication and support activities that can beongoing at one time.

The following is a set of guidelines to help you determine these numbers:v When InfoSphere CDC starts, it opens three DB2 plans. If the Log Cache is

configured, InfoSphere CDC opens one additional DB2 plan.v For each agent that is connected, and for the duration of that connection,

InfoSphere CDC opens one DB2 plan.v For each ongoing describe (describes are usually very quick), InfoSphere CDC

opens two DB2 plans. The first plan is closed shortly after the second plan isopened. This is true whether InfoSphere CDC is the transmitter or receiver ofthe described data.

v For each source subscription that is refreshing a table, InfoSphere CDC openstwo DB2 plans. The first plan is closed shortly after the second plan is opened.

v For each source subscription that is mirroring a table, InfoSphere CDC opensthree DB2 plans. The first plan is closed shortly after the second plan is opened.

v For each target subscription that is receiving table changes from a sourceenvironment refresh or mirror activity, InfoSphere CDC opens two plans. Thefirst plan is closed shortly after the second plan is opened, but is brieflyreopened each time the source sends a bookmark during mirroring.

DB2 log buffersInfoSphere CDC uses the DB2 IFI to obtain DB2 Log data when it is mirroringtable changes. The DB2 IFI will retrieve and present DB2 Log data from the


archived DB2 Log data sets, from the active DB2 Log data sets, or from the DB2Log buffers. The DB2 IFI presents data from these sources preferentially, based onthe speed with which it can obtain the data. The DB2 Log buffer is the mostpreferred, and archived DB2 Log data sets are the least preferred. When InfoSphereCDC is mirroring table changes in real time (Continuous Mirroring), it attempts toobtain DB2 Log data as soon as it has been written. If, for any number of reasons,InfoSphere CDC should fall behind, it will eventually catch up to the ″end″ of theDB2 Log again (assuming that table changes can be replicated faster than data isbeing written to the DB2 Log). The larger the number if DB2 Log buffers, the moreoften DB2 will find the DB2 Log data being requested within the DB2 Log buffers,and the quicker the DB2 IFI will be able to deliver DB2 Log data to InfoSphereCDC. This will improve InfoSphere CDC’s ability to catch up to the ″end″ of theDB2 Log and maintain a low latency when it is mirroring. It is suggested that youreview and possibly increase the number of DB2 Log buffers before runningInfoSphere CDC for mirroring.

Prerequisite program productsFor more information, see your Program Directory document.

Required storage devicesFor more information, see your Program Directory document.

Required SMP/E target and distribution librariesFor more information, see your Program Directory document.

Choosing system or private librariesNo system libraries are required. Only private data sets are used.

Should you install InfoSphere CDC resident?InfoSphere CDC does not require any of its modules to be loaded into the LinkPack Area.

Obtaining up-to-date maintenance during installationFor more information, see the Program Directory document.

Considerations for upgrading from releases prior toInfoSphere CDC for z/OS version 5.4

If you are planning an upgrade from Transformation Server for z/OS version 5.3or below, then it is recommended that you upgrade to InfoSphere CDC for z/OSversion 5.4 before beginning the upgrade to InfoSphere CDC version 6.2.

This section outlines considerations for an upgrade from Transformation Server forz/OS version 5.3 (or below) that are additional to the upgrade from InfoSphereCDC version 5.4. These considerations are the result of a change in the 3-letterproduct ID code that identified InfoSphere CDC for z/OS when version 5.4 wasreleased. The product-ID prefix change has been carried over to InfoSphere CDC,so you must take these changes into consideration when upgrading to InfoSphereCDC version 6.2.


The product ID is used by InfoSphere CDC as a prefix for almost everythingexcept the DB2 metadata tables. This includes the names of programs, DB2 plans,DD statements, configuration dataset members, and samples provided with theproduct.

See also:“JCL changes”“Configuration statements”“Messages”“Security and authorization”“Operational procedures” on page 7“Expressions and journal control fields” on page 7“Other considerations” on page 7

JCL changesThe sample JCL stored procedure name has changed from that in TransformationServer for z/OS version 5.3 TSDPROC is now CHCPROC. If you are using thesample procedure name to run InfoSphere CDC, then you will have to customizethe new procedure to suit the installation requirements (dataset names, forexample) and make it available to the Job Entry System by adding it to a dataset inthe PROCLIB concatenation.

You can also reuse the existing procedure name in order to minimize operationaland security changes. If you are reusing the same procedure, then you mustchange the JCL to accommodate the following product differences:v DD names for files have changed from TSDxxxxx to CHCxxxxx.v Program names have changed from TSDxxxxx to CHCxxxxx. For example,

PGM=TSDMIT must be changed to PGM=CHCMIT.

If InfoSphere CDC is run as a started task using the z/OS Start command, you canalter the existing procedure or change the name in the supplied sample rather thanusing the new name. Changing the name of the InfoSphere CDC started task nameintroduces additional implications for both operational procedures and theassignment of security identifiers (user IDs) to the InfoSphere CDC task. See theappropriate sections below for additional details.

Configuration statementsThere are no changes to the configuration statements themselves, but theconfiguration member names have changed. The existing configuration statementswill need to be renamed or copied to new members with the new names. Forexample, TSDCFGxx is renamed to CHCCFGxx.

MessagesThe InfoSphere CDC message prefix has changed from TSD to CHC. Anyoperational procedures, including those performed by automated operations tools,will need to be updated to reflect the new message format.

Note that the InfoSphere CDC Notifications feature uses the numeric identifier ofthe message and is not sensitive to the prefix. No changes are necessary forNotifications configuration.

Security and authorizationNote the following regarding security and authorization in InfoSphere CDC:


v Any security system controls that restrict access to programs based on the nameof the program will need to be updated or replaced to reflect the changedprogram names.

v If a changed JCL procedure name is used as a started task, then you may needto define a new security ID. Even if the procedure name is changed, it may bepossible to assign the existing user ID to the new task name, which is thepreferred approach.

v If you are assigning a new user ID to the renamed InfoSphere CDC task, thenadditional security-related changes are required:– In order to satisfy the restriction that the metadata tables must be owned by

the InfoSphere CDC user, you must recreate the InfoSphere CDC DB2metadata tables with the new user ID as the owner.

– DB2 permissions (as specified in the installation instructions) must be grantedto the user ID.

– Resource and system access rules must be altered to allow the new user idaccess to the resources (datasets, programs, etcetera).

Related concepts

“JCL changes” on page 6“Messages” on page 6

Operational proceduresNote the following regarding operational procedures in InfoSphere CDC:v You must review procedures that depend on the recognition of messages issued

by InfoSphere CDC. If there is any dependence on recognizing a message IDstarting with TSD, then you must update the procedure to account for the factthat message IDs will now start with the characters CHC.

v You must review all procedures that control InfoSphere CDC (start, stop, orissue commands to). If the task name of InfoSphere CDC is changed, then youmust update these procedures.

v z/OS user exits such as IEFUSI that may rely upon program names must beupdated to check for the program name CHCMIT instead of TSDMIT.

Expressions and journal control fieldsSince the value provided for the &PROGRAM journal control field is the planname in effect when the change was logged, any processes that depend on the thisjournal control field may require changes:v During refresh, the plan provided to the target system is the plan name from

InfoSphere CDC, so it will appear to the refresh target system as if a differentprogram is performing the update.

v In a cascading replication (where a target table is also a source table in adifferent target), the program performing the cascaded updates will be different.

Other considerationsThe DB2 plan names for InfoSphere CDC have changed to begin with CHC. Youmust update any DB2 access controls (such as permissions to use the plans) orother business processes that depend on recognizing the plan names starting withTSD.

Installing InfoSphere CDCThis section contains the sequence of steps that should be followed to installInfoSphere CDC on your z/OS server.


Note: If you are upgrading InfoSphere CDC to version 6.2 Fix Pack 1, you are alsorequired to upgrade Management Console and Access Server to version 6.3 FixPack 2

In this section, you will learn:“Installing InfoSphere CDC”“Tape distribution media”“Internet distribution media”“The initial SMP/E installation jobs” on page 9“Completing the installation using the distributed sample jobs” on page 9

Installing InfoSphere CDCInfoSphere CDC version 6.2 will delete and supersede any previous installation ofInfoSphere CDC for z/OS from the SMP/E CSI database. While this will notremove the software from existing execution libraries, it will result in the inabilityto install PTFs on that existing version. If you want to install a version ofInfoSphere CDC for testing without impacting an existing installation, create aseparate SMP/E CSI for the installation.

Tape distribution mediaThe Program Directory document that accompanies the distribution tape containsan example of JCL that can be used to load a CNTL partitioned data set withsamples of the jobs needed to start the installation process. Once similar JCL hasbeen used to load the sample jobs from the distribution tape, the sample jobs canbe used to start the InfoSphere CDC installation.

These sample jobs can also be used to:v Create an autonomous SMP/E environment and execute the SMP/E utility to

RECEIVE the contents of the distribution tape and any cumulative maintenance.v Create SMP/E Target and DLIB Zones and data sets, and APPLY the base

Function Sysmod and any cumulative maintenance into the Target Zone andTarget data sets.

Internet distribution mediaAlternatively, if an Internet download is being used as the distribution medium,then a readme.txt file included in the distribution describes how to transfer thedistributed files to data sets on DASD, rather than to tape volumes. In this case, aCNTL partitioned data set will also have been created, containing samples of thejobs needed to start the installation process.

These sample jobs can also be used to:v Create an autonomous SMP/E environment and execute the SMP/E utility to

RECEIVE the distribution data and any cumulative maintenance as it exists onDASD.

v Create SMP/E Target and DLIB Zones and data sets and APPLY the baseFunction Sysmod and any cumulative maintenance into the Target Zone andTarget data sets.

The sample jobs are virtually the same jobs obtained from the distribution tape iffollowing the procedure outlined in Tape Distribution Media.


Related concepts

“Tape distribution media” on page 8

The initial SMP/E installation jobsThe Program Directory document contains a description of those sample jobs thatcan be used to perform the SMP/E-related portion of the installation process.Follow the description in that document to complete the SMP/E portion of theinstallation, then return to this document to complete the installation process.

Completing the installation using the distributed sample jobsAfter the CHCAPPLY job has been successfully used to APPLY the base productFunction Sysmod, the maintenance from the CUM tape, and any up-to-datemaintenance, the SCHCCNTL data set will contain sample jobs using the mostcurrent JCL. These sample jobs can be used to complete the SMP/E portion of theinstallation process, as well as perform the complete DB2 portion of theinstallation. Other sample data, such as sample configuration control statementswill also be available in other SMP/E Target data sets.

As soon as the CHCAPPLY job has been successfully completed, the SCHCCNTLSMP/E Target Library should be used as the source of the remaining installationjobs. Although the installation jobs are accessible in the SCHCCNTL data set, datain this data set should not be modified by any program other than SMP/E. If youmake changes to any of the SMP/E Target libraries, they will be lost when futuremaintenance updates the members of the Target data sets. If a member from any ofthe SMP/E Target data sets is to be used to produce an installation job,configuration member, and so on, it should be copied from the SMP/E Target dataset to a modifiable data set, where it can be adapted as necessary.

The following jobs can be found in the SCHCCNTL data set after the CHCAPPLYjob has been executed:v CHCALA—JCL to define an SMP/E CSI VSAM data set containing a GLOBAL

Zone.v CHCALB—JCL to allocate general purpose SMP/E data sets and create the

Target and DLIB Zones that will be used by InfoSphere CDC.v CHCALLOC—JCL to allocate the InfoSphere CDC Target and DLIB library data

sets.v CHCDDDEF—JCL to create the SMP/E DDDEFs in the Target and DLIB Zones,

used for locating the Target and DLIB library data sets.v CHCRECEV—JCL to load the distribution tape and cumulative maintenance

tape into an SMP/E environment.v CHCAPPLY—JCL to execute an SMP/E APPLY CHECK or APPLY process to

install InfoSphere CDC into the SMP/E Target libraries.v CHCACCEP—JCL to execute an SMP/E ACCEPT CHECK or ACCEPT process

to copy the InfoSphere CDC SMPTLIBs into the SMP/E DLIB libraries.v CHCDFPAL—JCL to define and initialize the InfoSphere CDC product

administration log (PAL).v CHCDFMTD—JCL to define and initialize the InfoSphere CDC metadata VSAM

cluster.v CHCMDCHK—JCL to validate metadata that was created by a previous release

of InfoSphere CDC for z/OS.v CHCPGMTD—JCL to upgrade InfoSphere CDC for z/OS metadata from version

6.2 format to version 6.2 fix pack 1 format.


v CHCPGRN5—JCL to rename InfoSphere CDC for z/OS metadata that wascreated by version 5.4 of InfoSphere CDC for z/OS.

v CHCCRMTD—JCL to create DB2 tables that will contain the part of InfoSphereCDC version 6.2 metadata that resides in DB2 tables.

v CHCPGCP5—JCL to copy InfoSphere CDC for z/OS version 5.4 metadata to theInfoSphere CDC for z/OS version 6.2 metadata.

v CHCGRNTA—JCL to grant DB2 authorities to the security identifier assigned tothe InfoSphere CDC address space, and, optionally, to set the DATA CAPTURECHANGES attribute on certain DB2 Catalogue tables.

v CHCBNDPL—JCL to bind the DB2 Plans that will be used by InfoSphere CDCto access the DB2 Log, metadata tables, and application data tables that are to bereplicated.

v CHCCRCCH—JCL to create the VSAM data set containing the Level 2 DB2 Logcache and the cache control data set that maintains a summarization of the datain the cache.

v CHCPROC—JCL to execute the InfoSphere CDC product. This JCL can be storedin a procedure library to be invoked as either a started task or a batch job.

v CHCLGANU—JCL to execute the InfoSphere CDC for z/OS DB2 Log AnalyzerUtility. This JCL need not be executed during the installation process. It can beused any time that analysis of the content of a DB2 Log is required for purposesof configuration and tuning of InfoSphere CDC

v CHCMTAUT—JCL to configure features of InfoSphere CDC for z/OS that cannot be configured using Management Console.

v CHCMDPRT—JCL to execute the InfoSphere CDC Metadata Print Utility. ThisJCL need not be executed during the installation process. It is used if a report onthe content of the InfoSphere CDC metadata is required for problem analysis orother purposes.

v CHCBLTTL—JCL to create and load DB2 tables that will contain the InfoSphereCDC tutorial tables. This JCL need not be executed during the installationprocess. It can be used at a later time if the tutorial is required.

v CHCPGRN6—JCL to rename existing InfoSphere CDC metadata DB2 tables afterchanging DB2 version 8.1 to full-function mode from compatibility mode.

v CHCPGCP6—JCL to copy the data from InfoSphere CDC metadata DB2 tablescreated in DB2 version 7.1 format to metadata DB2 tables created in the formatrequired to provide full DB2 version 8.1 functionality.

v CHCDNGRD—JCL to revert to the original InfoSphere CDC for z/OS version5.4 metadata while preserving the contents of the InfoSphere CDC for z/OSversion 6.2 metadata, after having upgraded.

To continue the installation process, these jobs must be run in order. For a newinstallation of InfoSphere CDC for z/OS version 6.2 fix pack 1, you must runCHCDFPAL, CHCDFMTD, CHCCRMTD, CHCGRNTA, CHCBNDPL, andCHCCRCCH. For an upgrade from InfoSphere CDC for z/OS version 5.4 toversion 6.2 fix pack 1, you must run CHCMDCHK, CHCPGRN5, CHCCRMTD,CHCBNDPL, CHCPGCP5, CHCPGMTD, and CHCGRNTA. For an upgrade fromInfoSphere CDC for z/OS version 6.2 to version 6.2 fix pack 1, you must runCHCPGMTD, CHCBNDPL and CHCGRNTA. Not all the distributed sample jobsneed to be run to complete the install. The CHCALA, CHCALB, CHCALLOC,CHCDDDEF, CHCRECEV, CHCAPPLY, CHCACCEP jobs (which will have alreadybeen run), the CHCGLANU, CHCMDPRT, CHCBLTTL, CHCPGRN6, CHCPGCP6,and CHCDNGRD jobs (which are not necessary for the installation process) are notneeded during either an initial install or an upgrade install.


See also:“Authorizing the execution load library”“Initial install of InfoSphere CDC or upgrade to InfoSphere CDC” on page 12“Creating the configuration control data set” on page 12“Creating the user exit load library” on page 13“Preparing DB2 for z/OS version 8 or DB2 for z/OS version 9 for InfoSphereCDC” on page 13“Preparing Communications Server for use by InfoSphere CDC” on page 20

Related concepts

“Running the CHCDFPAL job” on page 16“Running the CHCDFMTD job” on page 16“Running the CHCMDCHK job” on page 16“Running the CHCPGRN5 job” on page 16“Running the CHCCRMTD job” on page 17“Running the CHCPGCP5 job” on page 19“Running the CHCPGMTD job” on page 19“Running the CHCGRNTA job” on page 19“Running the CHCBNDPL job” on page 18“Running the CHCCRCCH job” on page 20“Executing InfoSphere CDC” on page 74“Management Console tutorial tables” on page 161

Authorizing the execution load libraryAfter the CHCAPPLY job has successfully completed, the InfoSphere CDC SMP/ETarget Library (SCHCLOAD) will contain executable load modules. SCHCLOADcould be used as the load library to execute InfoSphere CDC but this is stronglydiscouraged. In this scenario, if maintenance is applied while InfoSphere CDC isrunning, you run the risk of a new version of a load module being loaded fromSCHCLOAD that is incompatible with an older load module that had been loadedby InfoSphere CDC before the maintenance was applied. If this happens, resultsare unpredictable; InfoSphere CDC could terminate abnormally, cause datacorruption, or behave in any number of other undesirable ways. It is imperative toallocate a new execution load library data set and copy the contents ofSCHCLOAD to this new load library, which will be used as the load library toexecute InfoSphere CDC. Future maintenance can then be safely applied toSCHCLOAD. When you are ready to recycle the InfoSphere CDC address spaceafter applying new maintenance, you will shut down InfoSphere CDC, copy thecontents of SCHCLOAD to the execution load library, and then restart InfoSphereCDC.

The sample JCL provided in the SCHCCNTL data set (CHCPROC member)contains a STEPLIB DD statement that names the execution load library data set as#hlqual.LOAD. Using TSO/ISPF or batch JCL, allocate such a data set (afterresolving the #hlqual placeholder) using the same DSNTYPE, DCB attributes andspace allocation as the SCHCLOAD data set. Copy the contents of the SCHCLOADdata set to the #hlqual.LOAD data set.

InfoSphere CDC must execute in an APF Authorized address space. During theprocess of installing InfoSphere CDC, the #hlqual.LOAD data set must be set APFAuthorized. Setting APF Authorization must occur before any of the loadmodules are executed.


APF Authorizing the #hlqual.LOAD data set must be performed by personnelauthorized to update ’SYS1.PARMLIB’ or enter a z/OS SETPROG consolecommand. This must be done for each server that will be used to execute theInfoSphere CDC product. The SCHCCNTL data set does not contain a sample jobthat can be used to change the APF Authorization of the execution load library.

Initial install of InfoSphere CDC or upgrade to InfoSphere CDCAt this point in the installation process, the tasks to be completed differ, dependingon whether or not InfoSphere CDC for z/OS version 5.4 or version 6.2 or neitherhas already been installed at the site.

If a previous release of InfoSphere CDC for z/OS (version 5.x) has already beeninstalled and is being used, then the existing metadata stored in DB2 tables mayrepresent a significant investment of time and effort. Therefore, it should bepreserved and used by the new installation of InfoSphere CDC. Configurationchanges to Communications Server for the previously version need to be preservedas well for future use. The remaining tasks will upgrade the metadata tables, andInfoSphere CDC for z/OS version 6.2 will be able to employ the facilities andresources that were used by the previously installed release.

If InfoSphere CDC for z/OS version 6.2 is the first copy of InfoSphere CDC to beinstalled at the site, then the remaining tasks will prepare facilities and resourcesrequired for InfoSphere CDC to execute successfully. This will include creating newmetadata tables in a DB2 table space, and configuring the communicationsresources for use.

In the following sections, references will be made to differences in the procedure,depending of whether an initial installation or an upgrade is being performed. Thelabels Initial Install, Upgrade, Upgrade from version 5.4 and Upgrade from 6.2identify different courses of action. Consider and choose the appropriate actionwhen such a distinction is encountered.

Creating the configuration control data setInfoSphere CDC requires that certain configurable settings be specified prior to itsexecution, so that they can be read and processed during initialization of theInfoSphere CDC address space. These configurable settings are specified as valuesof keywords in statements in the InfoSphere CDC Configuration Control data set.

The sample JCL provided in the SCHCCNTL data set (CHCPROC member)contains a CHCCNTRL DD statement that names the configuration control data setas #hlqual.DATA. Using TSO/ISPF or batch JCL, allocate such a data set (afterresolving the #hlqual placeholder) using the same DCB attributes and spaceallocation as the SCHCDATA data set.

Initial install—Copy the CHCCFGxx, CHCCMMxx, CHCDBMxx, CHCLDRxx, andCHCUCSxx members from the SCHCDATA data set to the #hlqual.DATA data set.

Upgrade—Copy the CHCCFGxx, CHCCMMxx, CHCDBMxx, CHCLDRxx, andCHCUCSxx members from the SCHCDATA data set from version 5.4 or version6.2, or the TSDCFGxx, TSDCMMxx, TSDDBMxx, TSDLDRxx, and TSDUCSxxmembers from the STSDDATA data from version 5.3 or earlier, renaming themfrom TSDcccxx to CHCcccxx. Modify these members as required for version 6.2 fixpack 1.


Note: If you wish to be able to revert to the earlier version from version 6.2, it isimportant that you do not alter the value of the SSID keyword found in the earlierversion’s CHCDBMxx (or TSDDBMxx) member.Related concepts

“Introduction to modifying the InfoSphere CDC configuration control data set” onpage 21

Creating the user exit load libraryInfoSphere CDC provides for extension of its capabilities to meet your specialrequirements by calling your user exits. User exits can be used to modify theApply process, enhance the processing within expressions and row filteringexpressions, or implement additional channels for the Notifications feature.Although InfoSphere CDC executes in an APF Authorized address space, it drivesany user exits in an unauthorized environment. This increases the security andstability of InfoSphere CDC’s execution. For this reason, user exit load modulesmust be separated from the authorized InfoSphere CDC load modules. If user exitswill be used, then a separate user exits load library must be allocated. This loadlibrary should be of similar attributes as the #hlqual.LOAD data set, but it shouldnot be APF Authorized. Provide the name of the user exit load library toInfoSphere CDC by substituting its name for the <UserExitLoadLib> keyword inthe CHCPROC sample JCL procedure.

Initial install—Using TSO/ISPF or batch JCL, allocate a user exit load library, andreplace the <UserExitLoadLib> placeholder in the CHCPROC sample JCL with thename of the data set.

Upgrade from version 5.4—The user exit interface in InfoSphere CDC version 6.2fix pack 1 has been updated incompatibly with versions 5.4 and earlier. You canexamine your user exits, and rewrite them to process the predefined entrystructures that are provided by InfoSphere CDC 6.2 fix pack 1. Even if no logicchanges are required, you can recompile the user exit source code to use theInfoSphere CDC predefined entry data structures.

As a convenience, InfoSphere CDC provides a mechanism whereby your existinguser exits from versions 5.4 and earlier can be used without being recompiled. Youwill need to link-edit your existing user exits with the InfoSphere CDC providedinterface module that will provide this backwardly compatible interface.Performance will be worse with the backward compatible interface than with thenative interface.

Upgrade from version 6.2—User exits that function with InfoSphere CDC version6.2 will continue to function with version 6.2 fix pack 1. No changes are required.Related concepts

“Linking Transformation Server user exits for InfoSphere CDC” on page 23

Preparing DB2 for z/OS version 8 or DB2 for z/OS version 9 forInfoSphere CDCAn InfoSphere CDC address space uses DB2 for z/OS version 8 and DB2 for z/OSversion 9 facilities that require DB2 Authorization. Accordingly, the personperforming the installation must ensure that InfoSphere CDC has controlled accessto the DB2 subsystem and to the InfoSphere CDC metadata that is kept in the DB2Subsystem. Controlled access requires the definition of a security identifier for theuse of the InfoSphere CDC address space, using whatever security and accesscontrol facility (such as RACF®, ACF2 or Top Secret) that is installed on the server.This security identifier will then be specified in the CHCCRMTD, CHCGRNTA,


and CHCBNDPL jobs to assign ownership to the InfoSphere CDC metadata tablesand DB2 Plans, and to GRANT DB2 authority to the InfoSphere CDC addressspace. The person performing the installation will need to assign as many securityidentifiers as there will be InfoSphere CDC address spaces. Only one InfoSphereCDC for z/OS address space can use an assigned security identifier, within thesame DB2 Subsystem or Data Sharing Group of DB2 Subsystems.

Assigning one or more security identifiers must be performed by the administratorof the access control facility in use at the installation. Once a security identifier hasbeen assigned for a single instance of an address space, it must be substituted forthe <CHCUserID> substitution placeholder in the sample jobs.

You must use the same name for both the InfoSphere CDC execution securityidentifier and as the owner qualification of InfoSphere CDC’s metadata tables, asspecified in the CHCCRMTD sample job. Failure to do so will cause InfoSphereCDC’s initialization to fail. An error message will be issued and InfoSphere CDCwill terminate prematurely. Note that this requirement supports the %GETCOLcolumn function. %GETCOL provides a mechanism for use in expressions and rowfiltering expressions to obtain current data from an application table, which is thenused in the evaluation of the expression. When processing a %GETCOL functioncall, InfoSphere CDC prepares and executes SQL to obtain the data specified. Suchad hoc SQL can be very inefficient, depending on the access path that DB2 will usewhen the SQL is executed. To address this exposure, InfoSphere CDC issues a DB2EXPLAIN statement against the SQL at the time that the %GETCOL function isentered into or changed in an expression or row filtering expression. DB2 storesthe results of the EXPLAIN statement in a PLAN_TABLE, where it is accessed andexamined by InfoSphere CDC. If the ad hoc SQL uses an inefficient access path,then an appropriate warning message is issued, which permits you to take steps toimprove the access path and therefore improve the efficiency of the %GETCOLfunction.

The requirement arises from DB2’s choice of the PLAN_TABLE. DB2 uses thePLAN_TABLE called <SAFUserID>.PLAN_TABLE where <SAFUserID> is theexecution security identifier being used by InfoSphere CDC. However, duringinstallation, the CHCCRMTD sample job will have created a<CHCUserID>PLAN_TABLE and it is this PLAN_TABLE that InfoSphere CDC willaccess in order to assess the SQL statements. To eliminate this problem, InfoSphereCDC requires that <SAFUserID> and <CHCUserID> be the same.

Security identifiers that will be creating, administrating or operating sourcesubscriptions will require SELECT access to every table in the subscriptions forwhich they are responsible. Security identifiers that will be creating, administratingor operating target subscriptions will require INSERT, UPDATE and DELETEaccess to every table in the subscriptions for which they are responsible. Mostoften, this access will be controlled by SQL GRANT and REVOKE statements,which will modify the DB2 catalog tables. However, if there exists a DB2 ACM(Access Control Module) Exit, InfoSphere CDC will automatically load and usethat exit to determine which security identifiers have access to which tables, just asDB2 itself does. The DB2 ACM Exit is an executable named DSNX@XAC found inthe STEPLIB concatenation. If the DB2 ACM Exit is in use, then security identifiersmust be given access to the DB2 tables they will need using RACF, ACF2, TopSecret or whatever other facility is employed by the DB2 ACM Exit. If the DB2ACM Exit indicates that it cannot determine what access a security identifier has toa table, InfoSphere CDC will fall back on the information in the DB2 catalog tables,just as DB2 itself does.


Initial install—Obtain a new security identifier for use by InfoSphere CDC.

Upgrade—Determine whether the security identifier already in use by an executingcopy of the previous release of InfoSphere CDC for z/OS can be used by the newinstallation.

The CHCCRMTD and CHCGRNTA sample jobs use a program called DSNTIAD.This program is distributed with DB2 for z/OS version 8 and DB2 for z/OSversion 9 as a sample program, and will have been generated during the DB2installation process. If it is no longer accessible, and cannot be regenerated usingthe JCL created during the installation of DB2, then consult a DB2 Administratorabout executing the SQL contained in these jobs using DB2 SPUFI (or some otherinteractive SQL interface) instead.

Due to the nature of the changes that the CHCCRMTD, CHCGRNTA, andCHCBNDPL jobs will make to the DB2 Subsystem, it may be required that a DB2Administrator run these jobs.

During the configuration of replication activities, InfoSphere CDC for z/OS mustdetermine how the DB2 application tables that are the source or target ofreplication activities are defined. This information is available in the DB2 SystemCatalogue Tables. InfoSphere CDC for z/OS accesses the DB2 System CatalogueTables using standard SQL to obtain the definitions of the subject DB2 applicationtables. In this respect, the DB2 System Catalogue Tables are treated as (read-only)application data by InfoSphere CDC. In particular, access and performanceconsiderations that normally apply to application data tables also apply to the DB2System Catalogue Tables with respect to the accesses performed by InfoSphereCDC. Some of these considerations are:v The DB2 System Catalogue may require reorganization to ensure that the

indexes can be efficiently accessed. The DB2 Administrator should be able todetermine if this is the case, and if so, attend to it.

v The RUNSTATS utility should be run against the DB2 System Catalogue tablespaces to ensure that current statistics are available to the DB2 Optimizer whenthe InfoSphere CDC for z/OS DB2 Plans are being bound. It should also be runagainst the table space that contains the InfoSphere CDC metadata, after themetadata tables have been created, and before the InfoSphere CDC DB2 Planshave been bound. From time to time, as the amount of data being storedchanges, the RUNSTATS utility should be rerun and the InfoSphere CDC DB2Plans rebound. This will ensure the most efficient access to the DB2 SystemCatalogue table spaces and the InfoSphere CDC metadata tables.

Backup and restore considerations

InfoSphere CDC stores most of its metadata in DB2 tables. The installation jobscreate a table space that will contain these metadata tables, and this table spaceshould be dedicated to the exclusive use of InfoSphere CDC. Still, from DB2’sperspective, the metadata tables and their containing table space are applicationdata. It is the your responsibility to ensure that proper procedures are in place totake regular backups of the table space, and to write and test procedures to restorethe contents of the table space, in preparation for any situation where the contentsof the table space may be lost or compromised.

See also:“Running the CHCDFPAL job” on page 16“Running the CHCDFMTD job” on page 16


“Running the CHCMDCHK job”“Running the CHCPGRN5 job”“Running the CHCCRMTD job” on page 17“Running the DB2 RUNSTATS utility” on page 18“Running the CHCBNDPL job” on page 18“Running the CHCPGCP5 job” on page 19“Running the CHCPGMTD job” on page 19“Running the CHCGRNTA job” on page 19“Running the CHCCRCCH job” on page 20

Running the CHCDFPAL job: Initial install—Modify the CHCDFPAL job,according to the comment block in its JCL. Run the job, which will use the AMSUtility program to define a Product Administration Log VSAM cluster. This VSAMcluster will contain a log of messages produced during replication activities thatcan be displayed through Management Console.

Upgrade—Do not run the CHCDFPAL job. The definition of the ProductAdministration Log VSAM cluster is unchanged between InfoSphere CDC forz/OS version 5.4, version 6.2 and version 6.2 fix pack 1.

Running the CHCDFMTD job: Initial install—Modify the CHCDFMTD job,according to the comment block in its JCL. Run the job, which will use the AMSUtility program to define a VSAM cluster that will contain the InfoSphere CDCmetadata not kept in DB2 tables. The job will use standard IBM utilities to load themetadata cluster with a minimal set of records.

Upgrade—Do not run the CHCDFMTD job. The InfoSphere CDC for z/OSmetadata VSAM cluster can be used without any change.

Running the CHCMDCHK job: Initial install—Do not run the CHCMDCHK jobfor an initial installation. The CHCMDCHK job selects rows meeting certaincriteria from existing InfoSphere CDC for z/OS metadata DB2 tables . For an initialinstallation, no such DB2 tables should exist, and so the CHCMDCHK job shouldnot be run.

Upgrade from version 5.4—Modify the CHCMDCHK job according to thecomment block in its JCL. Run the job, which will select any rows from theInfoSphere CDC for z/OS version 5.4 metadata tables that prevent the copying ofthe data to the version 6.2 metadata DB2 tables in a later step in the upgradeinstallation process. If any of the SQL SELECT statements completes with aSQLCODE of other than +100, the offending rows will have to be manuallyupdated so that the contents will be acceptable for use.

Upgrade from version 6.2—Do not run the CHCMDCHK job.Related concepts

“Running the CHCPGCP5 job” on page 19

Running the CHCPGRN5 job: Initial install—Do not run the CHCPGRN5 jobfor an initial installation. The CHCPGRN5 job renames the InfoSphere CDC forz/OS metadata DB2 tables using DB2 ALTER SQL statements. For an initialinstallation, no such DB2 tables should exist, and so the CHCPGRN5 job shouldnot be run.


Upgrade from version 5.4—The CHCPGRN5 job renames the InfoSphere CDC forz/OS version 5.4 metadata DB2 tables using DB2 ALTER SQL statements. This isnecessary because InfoSphere CDC version 6.2 fix pack 1 requires metadata DB2tables with the same name and owner as version 5.4, but the table definitions areincompatible with those used by version 6.2 fix pack 1. The version 5.4 metadatatables contain a significant amount of valuable information that is difficult toreproduce if it is lost, so this step preserves the information by allowing thecreation of the version 6.2 fix pack 1 metadata tables, which will have the samename as the version 5.4 tables.

Upgrade from version 6.2—Do not run the CHCPRGRN5 job.

Running the CHCCRMTD job: Initial install—Modify the CHCCRMTD job, asis deemed appropriate for the installation’s use of DB2. For example, theCHCCRMTD job contains SQL statements that will create a DB2 storage group, adatabase and a table space. The person performing the installation may decide touse a preexisting storage group, database or table space instead. Edit these SQLstatements to make the installation job conform to your DB2 environment.

A separate DB2 table space should be dedicated for the InfoSphere CDC metadataDB2 tables only. This will avoid deadlocks that can occur at the table space levelwhen InfoSphere CDC is attempting to update its metadata while replicating datawithin the same table space.

Do not change the CREATE TABLE, CREATE INDEX or the INSERT SQLstatements that appear in the CREATE step of the CHCCRMTD job. After valuesfor all the substitution placeholders have been resolved and adjustments to theSQL statements have been made, run the CHCCRMTD job to create and initializethe metadata tables. The CHCCRMTD job may require the DB2 authority of a DB2Administrator, because of the nature of the resources it is creating.

The last step in the CHCCRMTD job, called BLDINDEX, creates an index over aDB2 System Catalogue table. This index is required in order to provide an accesspath for SQL in InfoSphere CDC. This access path provides efficient access to theSYSIBM.SYSTABAUTH table when InfoSphere CDC is determining which tableswill be displayed in Management Console. Without this index, opening theManage Publications and Assign Destination Table dialog boxes could result in atable space scan of a DB2 System Catalogue table space. This table space scancould have a negative impact in these InfoSphere CDC activities (causingtimeouts), as well as creating problems for other processes that are attempting toaccess the SYSIBM.SYSTABAUTH DB2 Catalogue table.

You can execute this SQL to create a new index over the SYSIBM.SYSTABAUTHDB2 Catalogue table. After such an index has been created, it does not need to becreated again. For example, the CHCCRMTD job may need to be rerun, perhaps tocreate another set of InfoSphere CDC metadata DB2 tables for an additionalinstance of InfoSphere CDC. If such a rerun creates InfoSphere CDC metadata DB2tables within the same DB2 Catalogue in which the index was created, then thesubsequent execution need not include the BLDINDEX step. This is so becausemultiple InfoSphere CDC address spaces using the same DB2 subsystem (or DB2Data Sharing Group) can share the same index over the SYSIBM.SYSTABAUTHDB2 Catalogue table.

Upgrade from version 5.4—The CHCCRMTD job must be run. For an upgradefrom InfoSphere CDC version 5.4 to version 6.2 fix pack 1, but only after the


CHCPGRN5 job has been run to rename the version 5.4 metadata DB2 tables. Afterrunning the CHCPGRN5 job, follow the instructions for running the CHCCRMTDjob for an initial install.

Upgrade from version 6.2—Do not run the CHCCRMTD job.Related concepts

“Running the CHCPGCP5 job” on page 19

Running the DB2 RUNSTATS utility: Initial install—All statements in thissection apply to an initial installation.

Upgrade—All statements in this section apply to an upgrade.

You can execute the DB2 RUNSTATS utility at this point in the installation process.The execution of RUNSTATS should specify both TABLESPACE and INDEX foreach table space that contains DB2 System Catalogue Tables. This will ensure thatup-to-date information about the organization of the DB2 System Catalogue Tablesis being used by the DB2 Optimizer when it chooses access paths for InfoSphereCDC for z/OS’s DB2 Plans.

RUNSTATS should also be invoked by specifying TABLESPACE and INDEX forthe table space that contains the InfoSphere CDC for z/OS metadata. Again, thisensures that the DB2 Optimizer will be able to choose an efficient access path forthe InfoSphere CDC metadata stored in DB2 tables.

A job to execute the DB2 RUNSTATS utility is not provided with the otherinstallation jobs in the SCHCCNTL data set. A description of the required JCLcontrol statements can be obtained from the appropriate DB2 documentation. TheRUNSTATS utility may require the DB2 authority of a DB2 Administrator toexecute successfully.

Running the CHCBNDPL job: InfoSphere CDC uses DB2 Plans to access the DB2Log, InfoSphere CDC metadata that is stored in DB2 tables, and application datatables that are being replicated (refreshed). These DB2 Plans are associated with theInfoSphere CDC metadata. More than one instance of InfoSphere CDC may becommunicating with the same DB2 Subsystem. Such ″sibling″ InfoSphere CDCaddress spaces cannot use the same metadata, so separate metadata tables, andhence separate DB2 Plans, are necessary for each InfoSphere CDC address space.Separate DB2 Plans are distinguished by appending a user-supplied suffix to thenames of the distributed DB2 DBRMs. This plan suffix must be two characters,consisting of any combination of UPPER CASE alphabetic characters and numbers,chosen according to the requirement of the person performing the installation. Thisplan suffix is provided to the CHCBNDPL job as the <PlanSuffix> substitutionplaceholder, to complete the names of the DB2 Plans. The names of the DB2 Plansmust be made known to an InfoSphere CDC address space. To accomplish this, the<PlanSuffix> value should be coded as the value of the PLANSUFFIX keyword inthe CHCDMBxx member of the Configuration Control data set.

Initial install—After the DB2 RUNSTATS utility has successfully executed againstthe DB2 System Catalogue Tables’ table spaces and indices, run the CHCBNDPLjob to bind the InfoSphere CDC DB2 Plans. When the CHCBNDPL job hascompleted successfully, several DB2 Plans will have been created from thedistributed DBRMs. These DB2 Plans will enable exclusive access by theInfoSphere CDC address space to the proper metadata that is assigned to thespecific security identifier.


Upgrade—Even when upgrading, the DB2 Plans distributed with InfoSphere CDCmust be bound or rebound.Related reference

“PLANSUFFIX” on page 59

Running the CHCPGCP5 job: Initial install—Do not run the CHCPGCP5 job foran initial installation. The CHCPGCP5 job copies the contents of the InfoSphereCDC for z/OS metadata DB2 tables into the metadata tables for the new version.For an initial installation, no such InfoSphere CDC for z/OS DB2 tables shouldexist, and so the CHCPGRN5 job should not be run.

Upgrade from version 5.4—The CPCPGCP5 job copies the contents of theInfoSphere CDC for z/OS version 5.4 metadata DB2 tables that were renamed bythe CHCPGRN5 job into the version 6.2 fix pack 1 metadata DB2 tables created bythe CHCCRMTD job.

Modify the CHCPGCP5 job, according to the comment block in the JCL. Run thejob, which will copy the contents of the InfoSphere CDC for z/OS version 5.4metadata DB2 tables into the newly defined version 6.2 metadata DB2 tables usingINSERT SQL statements, then upgrade the copied contents. In order to ensure thatthe version 6.2 fix pack 1 metadata DB2 table contents exactly correspond with theinformation in the version 5.4 metadata tables, the job first deletes the contents ofthe version 6.2 fix pack 1 metadata tables. The INSERT SQL statements useSELECT clauses against the version 5.4 metadata DB2 tables that were renamed bythe CHCPGRN5 job.

The final step in the job updates the contents of certain columns of the metadata toaccount for encoding differences between version 5.4 and version 6.2. Messageswill be issued to record the progress of the upgrade processing.

Upgrade from version 6.2—Do not run the CHCPGCP5 job.Related concepts

“Running the CHCPGRN5 job” on page 16“Running the CHCCRMTD job” on page 17

Running the CHCPGMTD job: Initial install—Do not run the CHCPGMTD jobfor an initial install.

Upgrade from version 5.4—Modify the job according to the comment block in theJCL. Run the job, which will add new columns to the metadata tables. CHCPGCP5must be run first.

Upgrade from version 6.2—Modify the job according to the comment block in theJCL. Run the job, which will add new columns to the metadata tables.

Running the CHCGRNTA job: Initial install—Run the CHCGRNTA job toGRANT the proper DB2 Authority to the security identifiers that will be used bythe InfoSphere CDC address spaces and to set the DATA CAPTURE CHANGESattribute on certain DB2 Catalogue tables. This will enable InfoSphere CDC to readbut not change some of the DB2 Catalogue Tables, and give InfoSphere CDC theauthority to start a DB2 Monitor for DB2 Log activity. It will also allow DB2 Logrecords to be read. If access to DB2 tables is being controlled by the DB2 ACMExit, then you must grant appropriate authority to the security identifiers byRACF, ACF2, Top Secret or whatever facility is used by the DB2 ACM Exit.


The CHCGRNTA job may require the DB2 authority of a DB2 Administrator,because of the level of authority (SYSCTRL) that it grants to the security identifier.

Upgrade—The CHCGRNTA job does not have to be run unless a different securityidentifier is being used for InfoSphere CDC than was used by previous versions.

Running the CHCCRCCH job: To cache DB2 Log records for performancereasons, you must create a VSAM data set to hold the Level 2 DB2 Log cache. Youmust also create a cache control data set to maintain a summarization of the datain the cache. You can create both data sets by running the CHCCRCCH job. Youmust edit the JCL to replace all occurrences of the string <CACHE.QUALIFIER>with the high-level qualifier that you want for the cache data set names. Inaddition, you can change a setting to increase or decrease the amount of disk spaceused for the data set holding the Level 2 cache.

The size of the data set holding the Level 2 cache must be at least one block largerthan the Level 1 cache. If the data set is not at least this large, the DB2 Log Cachewill fail to initialize.

Initial install—To cache DB2 Log records, you must run the CHCCRCCH jobbefore starting InfoSphere CDC.

Upgrade—You do not have to run the CHCCRCCH job as a result of upgrading. IfDB2 Log caching was not enabled in the previous InfoSphere CDC for z/OSversion and you want to enable it for the new release, run the job any time afterupgrading. You can also run the CHCCRCCH job just to increase or decrease thesize of the data set holding the Level 2 cache. However, if you run the job for thispurpose, you lose any existing DB2 Log data in the Level 2 cache.Related reference

“CACHEBLOCKSIZE” on page 52“CACHELEVEL1SIZE” on page 53

Preparing Communications Server for use by InfoSphere CDCInfoSphere CDC uses TCP/IP to communicate with other InfoSphere CDC forz/OS servers and with Management Console. TCP/IP services are provided by theCommunications Server product. Communications Server should have itsconfiguration updated to include knowledge of the TCP/IP resources that will beused by InfoSphere CDC for z/OS.

Initial install—An InfoSphere CDC address space must have exclusive assignmentof one TCP port number and one UDP port number, which it uses for the servicesit provides to other InfoSphere CDC servers and to Management Console. TheseTCP and UDP port numbers are reserved by updating the ’TCPIP.ETC.SERVICES’data set (this data set may not have this specific name, but ’TCPIP.ETC.SERVICES’is the default data set name under z/OS). The TCP/IP network systemprogrammer must select a TCP port and a UDP port, having the same number.These ports can be assigned to unique service names in the ’TCPIP.ETC.SERVICES’data set.

The TCP port will be used to accept communications requests from ManagementConsole and from other instances of InfoSphere CDC. The UDP port will be usedby the autodiscovery feature (for more information, see your Management Consoledocumentation). The UDP port number must be the same as the TCP port number.The unique TCP service name should then be specified as the value of theSERVICENAME keyword in the CHCCMMxx member of the configuration control


data set, so that it is known to the InfoSphere CDC address space. The followingtable identifies the use and value ranges for the TCP and UDP ports assigned.

Ports PortsPurpose Value Range

TCP Accepts Management Console Clientconnections.

Accepts source-target connections.

1024–65535

UDP Autodiscovery communications withAccess Servers .

TCP and UDP port numbers must havethe same value.

InfoSphere CDC for z/OS uses the TCP/IP KEEPALIVE feature to detect the lossof network or remote server resources that support a TCP Socket connection. TheKEEPALIVE feature is fully described in the appropriate Communications Serverdocumentation and so will not be described in this document. KEEPALIVE uses aninactivity interval to help detect the inability to communicate with the remoteserver or application. On most TCP/IP stacks, the inactivity interval is defaulted to2 hours. This default value is inappropriate for the timely detection of server andnetwork outages, and should be reconsidered. The value chosen will affect allproducts that employ TCP/IP and activate KEEPALIVE monitoring on their TCPSocket connections. You can set a value that is more suitable than 2 hours forreacting to network and remote server outages.

Upgrade—InfoSphere CDC version 6.2 fix pack 1 implements a feature calledautodiscovery. This feature uses UDP datagrams to exchange configuration databetween the datastore (embedded in InfoSphere CDC) and the Access Server. AUDP port number must be reserved for each executing InfoSphere CDC addressspace. The UDP port number must coincide with the TCP port number chosen forthe datastore. If the TCP port numbers from a previous release of InfoSphere CDCfor z/OS will be used in version 6.2 fix pack 1, the network system programmermust reserve the UDP port number that corresponds to the TCP port number beingused by the datastore, and specified in the ’TCPIP.ETC.SERVICES’ data set. TheUDP port number should be assigned the ″udp″ protocol.

Introduction to modifying the InfoSphere CDC configuration controldata set

This section describes the settings that must be configured prior to executingInfoSphere CDC on your z/OS servers.

InfoSphere CDC requires that certain configurable settings be specified prior to itsexecution, so that they can be read and processed during initialization of theInfoSphere CDC address space. These configurable settings are specified as valuesof keywords in statements in the InfoSphere CDC configuration control data set.

Note: Comments are allowed in any statement in the configuration control dataset. Comments are indicated by an asterisk (’*’) in column 1, or by enclosing theentire comment between the ’/*’ and ’*/’ symbols. Blank lines in statements areignored.

During the installation process, the configuration control data set will have beenallocated, and populated with sample configuration control data set members.

Each of the sample configuration control data set members has a two-charactersuffix of xx. These suffixes should be replaced with the value assigned to the


<ConfigSuffix> placeholder. For example, if the <ConfigSuffix> placeholder hasbeen assigned a value of 01, then rename CHCCFGxx, CHCCMMxx, CHCDBMxx,CHCLDRxx, and CHCUCSxx to CHCCFG01, CHCCMM01, CHCDBM01,CHCLDR01, and CHCUCS01, respectively.

Although these members may have been renamed through the above example toincorporate the value of the <ConfigSuffix> placeholder into their names, thefollowing sections will continue to refer to them with the original, distributednames. In other words, CHCCFGxx, CHCCMMxx, CHCDBMxx, CHCLDRxx, andCHCUCSxx.

Each member provides configuration settings to different components ofInfoSphere CDC. The members are:v CHCCFGxx—Contains general product configuration control statements.v CHCCMMxx—Contains communications configuration control statements. This

member provides InfoSphere CDC with information about how it will employTCP/IP for communication

v CHCDBMxx—Contains DBMS configuration control statements. This memberprovides InfoSphere CDC with information about how it will locate and employthe DB2 Subsystem to and from which it will replicate data.

v CHCLDRxx—Contains a DB2LOADER configuration control statement. Thismember provides InfoSphere CDC with default values for use on a DB2 LOADUtility control statement that InfoSphere CDC target environment will use whenit is internally invoking the DB2 LOAD Utility to load data into a table that isbeing Refreshed.

v CHCUCSxx—Contains configuration control statements necessary to work withUnicode Conversion Services (UCS). This member provides InfoSphere CDCwith information about using Unicode Conversion Services when performingtranslation of text data from the code page of the source server to the code pageof the target server.

v CHCCVFxx—Contains control statements that determine how TCP/IPcommunications tests are conducted. This member provides InfoSphere CDCwith information about TCP/IP communications tests initiated from the localserver. Tests are started by invoking the STRTSCVF console command. Forinformation about the command and its associated control statements, contactyour IBM representative.

If more than one copy of InfoSphere CDC will be executed, then additional copiesof the configuration control data set members can be produced, each setdistinguished with a different, common suffix. Each distinct set can providetailored configurable settings to a different copy of InfoSphere CDC that isaccessing them. All copies of InfoSphere CDC can access the same configurationcontrol data set, but use a different set of configuration control data set members.

The two character suffix (xx) should be changed to the value of the <ConfigSuffix>placeholder. The <ConfigSuffix> placeholder will also appear in the CHCPROCmember of the SCHCCNTL data set. Replacing the <ConfigSuffix> placeholder inthis member will provide InfoSphere CDC with the information it needs to locateand process the proper CHCCFGxx member of the configuration control data set.

If a keyword in a statement is assigned an invalid value, the default value for thatkeyword is used where applicable.


Upgrade from version 5.4—InfoSphere CDC version 6.2 fix pack 1 has added anew statement type for UCS configuration. In addition, some keywords may havedifferent default values, or new keywords may have been added to an existingstatement. The following table identifies the configuration statement changes inInfoSphere CDC for z/OS version 6.2 fix pack 1, compared to version 5.4.

Membername Statement

Changed or removedkeywords in version 6.2 fixpack 1

Added keywords inversion 6.2 fix pack 1

CHCCFGxx CONFIG HEARTBEATTIMEOUT STG64LIMIT

CHCCMMxx TCP/IP None KEEPALIVETIMEOUT

CHCDBMxx DB2 SECURITY ONSCHEMACHANGE

REPLTIMESTAMP

CHCUCSxx IANAMAP(NewStatement)

Upgrade from version 6.2—InfoSphere CDC version 6.2 fix pack 1 has added andremoved keywords on the DB2 statement. The following table identifies theconfiguration statement changes in InfoSphere CDC for z/OS version 6.2 fix pack1, compared to version 6.2.

Membername Statement

Changed or removedkeywords in version 6.2 fixpack 1

Added keywords inversion 6.2 fix pack 1

CHCDBMxx DB2 SECURITY ONSCHEMACHANGE

REPLTIMESTAMP

Related concepts

“Creating the configuration control data set” on page 12

Linking Transformation Server user exits for InfoSphere CDC

Note: This section only applies to an upgrade of InfoSphere CDC version 5.4 orearlier. If you are upgrading from version 6.2 of InfoSphere CDC, your user exitswill continue to work as they are. User exits from 5.4 and earlier are referred to asTransformation Server® user exit, and will not work without either rewriting themas InfoSphere CDC user exits or re-linking them with the backward compatibilityinterface.

If you have created any user exits to provide special processing in TransformationServer for z/OS, and you choose not to reimplement them to use the InfoSphereCDC provided user exit interface, you can continue to use your existing exits bytaking advantage of the backward compatible user exit interface available inInfoSphere CDC.

For the most part, the user exit processing in InfoSphere CDC is the same as wasprovided in Transformation Server for z/OS. The types of exits available, thecalling sequence, and return code processing is unchanged. With the exception ofnotifications user exits, the user exit naming convention is also unchanged.


The principle difference between a Transformation Server for z/OS user exit andan InfoSphere CDC user exit is the content and structure of the defined user exitdata structures passed to your exits. With a few exceptions, all the character datapassed to an InfoSphere CDC user exit, will be encoded in UTF-8 (a standardrepresentation of Unicode™ characters). In Transformation Server for z/OS, mostdata was passed in standard EBCDIC encoding. The backward compatible user exitinterface is enabled by binding (link-editing) your user exit module together withthe InfoSphere CDC user exit interface backward-compatibility interface module.The interface module will act as a ″front end″ to your exit, converting theInfoSphere CDC provided data entry structures, and the encoding scheme ofcharacter data to the Transformation Server for z/OS user exit data structureformats. These conversions and translations will allow your existing user exits tocontinue to function, with the limitation that any identifiers passed to the user exit,such as a subscription name, or table name, must be representable in the EBCDIC(CCSID 1047) code page.

Every Transformation Server for z/OS user exit must be link-edited.

See also:“Link editing Transformation Server notification user exits for InfoSphere CDC”“Link editing Transformation Server expression user exits for InfoSphere CDC”on page 25“Link editing Transformation Server table-level user exits and row-level userexits for InfoSphere CDC” on page 26“Link editing Transformation Server conflict resolution user exits for InfoSphereCDC” on page 26

Link editing Transformation Server notification user exits forInfoSphere CDC

One of the differences between Transformation Server user exits and InfoSphereCDC user exits is that InfoSphere CDC notifications user exits must use a specificentry point name, where Transformation Server user exits allowed you to chooseany entry point name. In order to use a Transformation Server notifications userexit, you must use the z/OS Binder (Linkage Editor) to change your existing entrypoint name to the defined entry point required by InfoSphere CDC. The followingare the link-edit statements necessary to produce a function notifications user exitfrom a compiled Transformation Server user exit.//SYSIN DD *CHANGE CHCCMPLV(CHCUEXL0)INCLUDE SYSLIB(CHCTEXIT)CHANGE <entryname>(ALRMXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)/*

Replace:

<entryname> with the entry point name of your Transformation Server notificationsuser exit

<objmodule> with the name of the user exit object module produced from by thecompiler. If more than one object module is required, insert an additionalINCLUDE statement for each object module.


<loadmodule> with the name of the load module that is produced from thelink-edit and is specified in Management Console. This name must not be the sameas any load module provided with InfoSphere CDC. To be certain of this, it is bestnot to use a load module name that starts with ″CHC″.

Note: When link-editing, the RENT (reentrant) and AMODE=31 (31 bit addressingmode) linkage editor options must be specified.

The output from the linkage-editor is a load module, which is written to the loadlibrary that is allocated to the linkage-editor by the SYSLMOD DD statement. Thisload library, or a copy of it, must be made accessible to InfoSphere CDC using aCHCUXLIB DD statement in the InfoSphere CDC execution JCL. This load librarymust not be APF Authorized.

User exit programs must be successfully link-edited before proceeding.

Link editing Transformation Server expression user exits forInfoSphere CDC

The following are the link-edit statements necessary to produce a functionalInfoSphere CDC expression (%USER) user exit from a compiled TransformationServer user exit://SYSIN DD *

CHANGE CHCCMPLV(CHCUEXL0)INCLUDE SYSLIB(CHCTEXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)

/*

Replace:v <objmodule> with the name of the user exit object module produced from by the

compiler. If more than one object module is required, insert an additionalINCLUDE statement for each object module.

v <loadmodule> with the name of the load module that is produced from thelink-edit and is specified in the %USER function call. This name must not be thesame as any load module provided with InfoSphere CDC. To be certain of this,it is best not to use a load module name that starts with ″CHC″.


The output from the linkage-editor is a load module, which is written to the loadlibrary that is allocated to the linkage-editor by the SYSLMOD DD statement. Thisload library, or a copy of it, must be made accessible to InfoSphere CDC using aCHCUXLIB DD statement in InfoSphere CDC’s execution JCL. This load librarymust not be APF Authorized.



Link editing Transformation Server table-level user exits androw-level user exits for InfoSphere CDC

The following are the link-edit statements necessary to produce a functionalInfoSphere CDC table-level user exit and row-level user exit from a compiledTransformation Server user exit//SYSIN DD *CHANGE CHCCMPLV(CHCUEXL0)INCLUDE SYSLIB(CHCTEXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)/*

Replace:

<objmodule> with the name of the user exit object module produced from by thecompiler. If more than one object module is required, insert an additionalINCLUDE statement for each object module.

<loadmodule> with the name of the load module that is produced from thelink-edit and is specified in the user exit alert handler. This name must not be thesame as any load module provided with InfoSphere CDC. To be certain of this, it isbest not to use a load module name that starts with ″CHC″.




Link editing Transformation Server conflict resolution userexits for InfoSphere CDC

The following are the link-edit statements necessary to produce a functionalInfoSphere CDC conflict resolution user exit from a compiled TransformationServer user exit://SYSIN DD *

CHANGE CHCCMPLV(CHCUEXL0)INCLUDE SYSLIB(CHCTEXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)

/*

Replace:v <objmodule> with the name of the user exit object module produced from by the

compiler. If more than one object module is required, insert an additionalINCLUDE statement for each object module.

v <loadmodule> with the name of the load module that is produced from thelink-edit and is specified in the resolution method using Management Console.


This name must not be the same as any load module provided with InfoSphereCDC. To be certain of this, it is best not to use a load module name that startswith ″CHC″




Modifying general product configuration control statementsInfoSphere CDC reads general product configuration control statements when it isbeing initialized. These statements are read from the CHCCFGxx configurationcontrol data set member. The CHCCFGxx member is the first member of theconfiguration control data set that InfoSphere CDC reads during initialization. TheCONFIG statements in the CHCCFGxx member should be modified for yourworking environment.

In this section, you will learn:“CONFIG”

CONFIGThe CONFIG statement is optional. The figure below illustrates the general syntaxfor this statement.

The CONFIG statement is optional, but it must be coded if any of the keywordspecifications are provided. If the CONFIG statement does not appear in theconfiguration control dataset member, no errors will be reported, and the contentsof the member will be ignored.

Note: Keyword specifications in the CONFIG statement must be separated bycommas.

The following keywords are supported:“ADMININACTTIMEOUT” on page 28“AUTODEASSIGN” on page 29“AUTORESTARTINTERVAL” on page 30“CASCADE” on page 30“CODEPAGECONVERSION” on page 31“COMMAND” on page 31“COMMCONFIG” on page 32“DBMSCONFIG” on page 32“DEADBANDPERCENT” on page 33


“ENDONERROR” on page 35“HEARTBEATTIMEOUT” on page 36“PALCLEANUPTIME” on page 36“PALLIMITS” on page 37“PALRETPD” on page 37“REPORTPOSITIONINTERVAL” on page 38“REPSTATSINTERVAL” on page 39“SDUMPLIMIT” on page 39“SMFINTERVAL” on page 40“SMFTYPE” on page 40“SMFSID” on page 41“STG64LIMIT” on page 41“TRACE” on page 42“TRACEDEST” on page 42“UCSCONFIG” on page 43

ADMININACTTIMEOUT

Specifies the maximum amount of time, in minutes, a Management Console userconnection with a datastore can be inactive before an automatic disconnection isinitiated on the zSeries server.

An inactive Management Console user connection to a datastore running in anInfoSphere CDC address space prevents that address space from being shut downin a controlled manner. This setting lets you establish a timeout period for inactiveconnections to a datastore so that an attempt on the server to shut down theaddress space in a controlled manner will eventually be successful. After thetimeout period has expired, InfoSphere CDC ends the datastore connectionautomatically. InfoSphere CDC replication that was activated before the datastoredisconnection continues normally.

Note: The timeout period defined by this keyword is not the same as a datastoretimeout setting in Management Console. The latter determines the maximumamount of time for an Management Console process to successfully establish aconnection with a datastore running on a server. The former, which is anInfoSphere CDC for z/OS setting, determines the maximum amount of time anagent can be inactive after an agent connection has been successfully established.

After a timeout period expires, InfoSphere CDC generates a message (CHC0556I)in the product administration log indicating that an automatic disconnection willbe performed.

ADMININACTTIMEOUT=0 means that no timeout period is established for inactiveManagement Console user connections with the datastore. This behavior isconsistent with previous InfoSphere CDC versions, which means that a singleconnection can remain inactive for any length of time. Any positive integer


assigned to ADMININACTTIMEOUT that is within the acceptable range enables atimeout and specifies the length of the timeout period.

Tip: The Management Console user is not likely to be aware that a timeout isabout to occur. Therefore, if a timeout period needs to be specified, the timeoutshould be sufficiently long to accommodate normal pauses and periods ofinactivity when working with Management Console to configure and initiatereplication. A short timeout period, such as five minutes, could result in frequentdisconnections that disrupt the flow of work in Management Console. As aguideline, you may want to set the timeout period to be consistent with the z/OSsession timeout defined on your server.

This keyword is optional.

Default Setting—0 minutes

Minimum (Non-Zero) Setting—5 minutes

Maximum Setting—1440 minutes (1 day)

AUTODEASSIGN

Specifies the action that is taken during a describe operation when a source tabledefined in the metadata is not one of the described tables.

Normally, when describing source tables selected for replication, any table that isnot described and not mapped to a target table is removed from the target. Incertain environments, it is desired that target metadata generated from previousdescribe operations be removed for tables that are not described regardless of theirassignment status.

AUTODEASSIGN=NO indicates that existing target metadata is removed for sourcetables that are not described and not currently mapped to target tables. This is thedefault product behavior that maintains the replication configuration you havedefined for mapped tables.

AUTODEASSIGN=YES indicates that existing target metadata is removed for tables thatare not described, regardless of whether or not the tables invoked are mapped to atable. In other words, existing metadata for mapped tables is removed. This actiondismantles the replication configuration for mapped tables and should be chosenwhen a universal removal of tables not described is desired.

When this keyword is read during initialization, its current value is written to theTSAUDIT SPOOL data set. If AUTODEASSIGN=YES and existing target metadata formapped source tables is removed during a describe operation, a report containingconfiguration information for each source table (for example, user exit settings,value translations, and so on) is placed in the CHCREPRT SPOOL data set. Inaddition, an InfoSphere CDC message (CHC1511I) is generated to indicate that areport has been written. You can use this report to restore the replicationconfiguration in the event that the keyword has been mistakenly set to YES.



Default Setting—NO

AUTORESTARTINTERVAL

Specifies the amount of time, in minutes, between consecutive attempts toautomatically restart continuous mirroring after normal or abnormal termination ofcommunications or target servers in your replication configuration. Attempts torestart continuous mirroring apply only to persistent subscriptions.

InfoSphere CDC can automatically restart continuous mirroring for persistentsubscriptions after normal or abnormal termination of communications or targetservers in your replication configuration. When communications or target servertermination causes continuous mirroring for persistent subscriptions to end,InfoSphere CDC attempts to automatically restart continuous mirroring at regularintervals. This keyword lets you define the time period between consecutiveattempts.

AUTORESTARTINTERVAL=0 means that an automatic restart of continuous mirroringfor all persistent subscriptions is disabled. In other words, no attempts are made torestart continuous mirroring. You must manually restart continuous mirroring forthese targets.



Minimum Setting—0 minutes

Maximum Setting—60 minutesRelated concepts

“Automatic restart and schema evolution” on page 143

CASCADE

Specifies the default action when InfoSphere CDC, when installed on the sourceenvironment, obtains data for mirroring that was applied to the data repository byitself (the same instance of InfoSphere CDC when installed on the targetenvironment).

CASCADE=YES indicates that InfoSphere CDC will mirror such self-applied data tothe target servers for which it is publishing the data. CASCADE=NO indicates that


InfoSphere CDC ignores such self-applied data, and not mirror the changed data tothe target servers for which it is publishing the data.

This keyword sets the default action for InfoSphere CDC when it encountersself-applied data. As the default, the setting of the CASCADE keyword can beoverridden by the behavior specified for any subscription that mirrors the data inquestion. These overriding behaviors are specified on a per-subscription basisusing Management Console.

CASCADE=YES is the required setting to implement a cascaded multilevel replicationconfiguration. CASCADE=NO is the required setting to implement a fully bidirectionalreplication configuration.


Default Setting—YES

CODEPAGECONVERSION

Specifies whether code page conversion of character data is to take place on thesource or target system.

If CODEPAGECONVERSION=SOURCE, code page conversion of character data will beperformed by the source system, if possible. If the source system cannot performthe code page conversion but the target system can, then code page conversionwill be performed by the target system despite the setting of this keyword.

If CODEPAGECONVERSION=TARGET, code page conversion of character data will beperformed by the target system, if possible. If the target system cannot perform thecode page conversion but the source system can, then code page conversion will beperformed by the source system despite the setting of this keyword.


Default Setting—SOURCE

COMMAND

Specifies the suffixes of the CHCCMDxx members (in the CHCCNTRL data set)containing one or more InfoSphere CDC console commands that are issued afterthe InfoSphere CDC address space has been fully initialized.

Any InfoSphere CDC for z/OS console command (including COMMAND) can bespecified in a CHCCMDxx member. Commands specified in a member must omitthe MODIFY, F, <procname>, and <identifier> elements.



Default Setting—No console commands are issued after InfoSphere CDC addressspace initialization.Related concepts

“InfoSphere CDC commands” on page 91

COMMCONFIG

Specifies the suffix that is used to locate the CHCCMMxx member containing theCommunications Configuration Control statements.

<CommSuffix> must consist of two characters, and can be any combination ofUPPERCASE alphabetic characters and numbers. For example, if COMMCONFIG=A1 isspecified, then the member named CHCCMMA1 in the configuration control dataset is read by InfoSphere CDC to obtain its communications configuration controlstatements.


Default Setting—The suffix used for the CHCCFGxx member in the configurationcontrol data set. In other words, the value of the <ConfigSuffix> placeholderresolved in the CHCPROC JCL procedure.

DBMSCONFIG

Specifies the suffix that is used to locate the CHCDBMxx member containing theDBMS configuration control statements.

<DBMSSuffix> must consist of two characters, and can be any combination ofUPPER CASE alphabetic characters and numbers. For example, if DBMSCONFIG=B2 isspecified, then the member named CHCDBMB2 in the configuration control dataset is read by InfoSphere CDC to obtain its DBMS configuration control statements.




DEADBANDPERCENT

Identifies the size of the range around each latency threshold setting.

Based on latency threshold settings defined in Management Console, InfoSphereCDC generates a latency message when latency rises above or falls below athreshold. InfoSphere CDC calculates latency at every COMMIT.

Note: InfoSphere CDC issues a COMMIT when it receives a COMMIT from thesource, or when it receives a Report Position Message.

You can configure notifications in Management Console in response to a generatedlatency message.

This system parameter, which is expressed as a percentage, lets you pad athreshold equally on both sides to create a range around the threshold. Byadjusting this system parameter, you can increase or decrease the range around thethreshold, and make the threshold itself larger or smaller. InfoSphere CDC onlygenerates a latency message when latency rises above the upper limit of the rangeor falls below the lower limit of the range. By changing the value assigned to thissystem parameter, you can control the number of latency messages placed in theevent log.

For example, assume that a latency threshold has been set in Management Consolefor 5 minutes and you have set this system parameter to 10. In this scenario,InfoSphere CDC applies a 10% range around the 5 minute threshold and performsthe following calculations to determine the lower and upper limits (in minutes) ofthe range around the threshold:

Padding equals 10% of 5 minutes equals 0.5 minutes (rounded up to 1 minute)

Padding is rounded up or down to the nearest whole minute.

Upper limit of range equals 5 minutes plus 1 minute (padding) equals 6 minutes

Lower limit of range equals 5 minutes minus 1 minute (padding) equals 4 minutes

As a result, InfoSphere CDC generates a latency message only when latency risesabove 6 minutes or falls below 4 minutes.

Latency is calculated every minute over a ten minute duration. Based on thesecalculations, InfoSphere CDC generates three latency messages.

Latency Message Generation—10% Setting


Based on the above figure, if you set this system parameter to 0 (the defaultsetting), then InfoSphere CDC does not apply padding to the latency threshold.InfoSphere CDC generates a latency message each time latency crosses over thethreshold of 5 minutes. Because latency is calculated every minute in the figureabove, InfoSphere CDC generates 5 latency messages when you set this systemparameter to 0.

Latency Message Generation—0% Setting

If the number of latency messages generated over the ten minute period for the10% (3 latency messages) and 0% (5 latency messages) settings are averages, anadditional 288 latency messages are generated each day if this system parameter isnot changed from its default setting to 10%.

Since there are two latency threshold settings in Management Console (a warningthreshold and a problem threshold), two separate ranges are defined when


padding is at least one minute. In this case, each range is attached to its threshold,and the two ranges can overlap with no change in behavior.

If a value smaller than the minimum setting or larger than the maximum setting isspecified, the default setting is used.


Default Setting—0%

Minimum Setting—0%

Maximum Setting—100%

ENDONERROR

Specifies the default action when InfoSphere CDC encounters a nonrecoverableerror during replication.

This keyword contains three value parameters. The first value parameter representsthe default action during refresh operations, the second value parameter representsthe default action during mirroring, and the last value represents the default actionduring auditing when LiveAudit™ is active (target only). To stop one or more ofthe InfoSphere CDC operations when a nonrecoverable error is encountered,specify a value of YES in the appropriate positions. To continue one or more of theoperations after encountering a nonrecoverable error, specify a value of NO in theappropriate positions.

Note: This keyword allows you to specify just the first value parameter (refresh),the first and second value parameters (refresh and mirroring), or all three valueparameters (refresh, mirroring, and auditing). A value cannot be specified forrefresh and auditing (first and third parameters) without specifying a value formirroring (second parameter).

To set the maximum number of messages that can be generated for nonrecoverableerrors, use the MAXSQLERRMSG keyword in the DB2 configuration controlstatement.


Default Setting—(YES, YES, YES)


Related reference

“MAXSQLERRMSG” on page 56

HEARTBEATTIMEOUT

Specifies whether or not heartbeat is enabled. If heartbeat is enabled, this keywordalso specifies the heartbeat timeout period.

When heartbeat is enabled, InfoSphere CDC automatically detects failure betweena source environment and target environment and performs a graceful shutdownso that you do not have to terminate replication on the server that did not fail.

The source environment and target environment exchange heartbeat requestmessages. Either the source environment or target environment must respondwithin a specified timeout period by sending any message (heartbeat or any othertype of message). If the source environment or target environment does not receivea message within the specified timeout period, then a communication or serverfailure is declared, and replication ends in a controlled manner.

HEARTBEATTIMEOUT=0 disables heartbeat. Any positive integer assigned toHEARTBEATTIMEOUT that is within the acceptable range enables heartbeat andspecifies the heartbeat timeout period in minutes. To automatically detect failure,heartbeat must be enabled on both the source environment and targetenvironment. For non-z/OS servers, consult the appropriate InfoSphere CDCdocumentation for information about supported heartbeat settings and whether itis necessary to enable heartbeat explicitly.



Minimum (Non-Zero) Setting—3 minutes

Maximum Setting—999 minutes

PALCLEANUPTIME

Specifies the time at which InfoSphere CDC will initiate a daily cleanup of theevent log. Messages older than the number of days specified using PALRETPD willbe deleted.


Default Setting—If this keyword is not specified, no daily cleanup will beperformed.


Minimum Setting—00:00

Maximum Setting—23:59Related reference

“PALRETPD”

PALLIMITS

Specifies the maximum number of lines that an InfoSphere CDC task can place inthe CHCPRINT, CHCAUDIT, and CHCREPRT data sets, respectively.

Use this keyword to establish limits on the amount of information in these datasets for each InfoSphere CDC address space. If the number of lines in a data sethas reached the maximum as defined by this keyword, and an attempt is made towrite another line, InfoSphere CDC inserts a final line in the data set indicatingthat the limit has been exceeded. To add more rows to the data set, you must stopand restart the InfoSphere CDC address space.

Since three values are assigned to this keyword, a different limit can be establishedfor each data set (CHCPRINT, CHCAUDIT, and CHCREPRT). A value of zeroindicates that there is no limit on the number of lines that can be placed in aspecific data set.


Default Setting—(0, 0, 0) - No limit is imposed on the number of lines in all datasets.

PALRETPD

Specifies the retention period, in days, for messages contained in the InfoSphereCDC Product Administration Log VSAM cluster.

These messages are viewed using the Event Log Viewer in Management Console.


The value of this keyword represents the number of days that messages areretained in the InfoSphere CDC Product Log since the date that they were issued.Messages that exceed this retention period are purged from the ProductAdministration Log VSAM cluster the next time that InfoSphere CDC is initialized.Purging of messages only occurs during address space initialization.


Default Setting—14 days

Minimum Setting—1 day

Maximum Setting—9999 days

REPORTPOSITIONINTERVAL

Specifies how often, in seconds, the source environment informs the targetenvironment about its position in the DB2 Log during idle periods after startingmirroring.

In the target environment, a bookmark is a value that represents the last processedDB2 Log position on the source environment. During idle periods, when there areno log entries to read, the source environment informs the target environment ofits current position in the log so that the target environment can advance itsbookmarks accordingly. By decreasing the setting for this keyword, the targetenvironment can reflect more accurately how far mirroring has progressed. Inaddition, regularly synchronizing the bookmarks with the source environment canreduce the number of entries that have to be read again when mirroring isrestarted.

CAUTION:The value assigned to this keyword affects the information presented in specificmessages and in the Monitoring perspective of Management Console. Increasingthis setting may result in information that is not up-to-date.


Default Setting—5 seconds

Minimum Setting—1 second

Note: If you specify a value smaller than the minimum setting or larger than themaximum setting, then InfoSphere CDC uses the default value.

Maximum Setting—300 seconds


REPSTATSINTERVAL

Specifies the period of time, in minutes, between consecutive messages thatprovide status information about DB2 Log scraping activities on the source server.

The messages pertaining to DB2 Log scraping allow monitoring of data mirroringon the source server. Messages are placed in the product administration log andcan be viewed through the Management Console Event Log Viewer.

Note: An overhead is incurred when messages are generated to monitor mirroringactivities. The frequency of message generation determines the amount of overheadthat is incurred as a whole

REPSTATSINTERVAL=0 indicates that you want to disable the generation of DB2 Logscraping messages. If a nonzero value is assigned to REPSTATSINTERVAL, theinterval pertains to the specific message that regularly reports the latest DB2 Logscrape (CHC0130I). A nonzero setting does not apply to other relevant messages(CHC0046I, CHC0047I, and CHC0049I) that provide information about thebeginning and end of scraping activities as well as the first mirrored change.



Minimum (Non-Zero) Setting—1 minute

Maximum Setting—1440 minutesRelated reference

“CHC0130I” on page 265“CHC0046I” on page 243“CHC0047I” on page 244

SDUMPLIMIT

Specifies the maximum number of SVCDUMPs that an active InfoSphere CDCaddress space can initiate.

InfoSphere CDC requests that an SVCDUMP be generated by the server each timean internal problem is encountered. Use this keyword to limit the number ofSVCDUMPs initiated by an active InfoSphere CDC address space.



Default Setting—3 SVCDUMPs

Minimum Setting—0 SVCDUMPs

Maximum Setting—32767 SVCDUMPs

SMFINTERVAL

Specifies the interval, in minutes, at which InfoSphere CDC will write SMFperformance records. A value of zero (the default) means that InfoSphere CDC willnot write SMF performance records.

In addition, if the value specified for SMFTYPE is zero, InfoSphere CDC will notwrite any SMF records. If a value smaller than the minimum setting or larger thanthe maximum setting is specified, the default setting is used.



Minimum (Non-Zero) Setting—1 minute

Maximum Setting—1440 minutes (1 day)Related concepts

“SMF Record Layout” on page 219Related reference

“SMFTYPE”

SMFTYPE

Specifies the SMF record type that InfoSphere CDC may use when writing SMFrecords.

All SMF records written by InfoSphere CDC will be of the specified type. A valueof zero (the default) means that InfoSphere CDC may not write SMF records. If avalue smaller than the minimum setting or larger than the maximum setting isspecified, the default setting is used.


Default Setting—0

Minimum (Non-Zero) Setting—128


Maximum Setting—255Related concepts

“SMF Record Layout” on page 219

SMFSID

Specifies the text string that InfoSphere CDC will use to populate the SMFSID fieldof the SMF record header of all SMF records written by InfoSphere CDC. Thismust be a text string of 1 to 4 characters in length. If a string longer than this isspecified, the default value will be used.


Default Setting—DMTSRelated concepts

“SMF Record Layout” on page 219

STG64LIMIT

Specifies the maximum total amount of above the bar (64–bit) storage that can beused by all components of InfoSphere CDC for z/OS. The size can be specified inmegabytes (M), gigabytes (G) or terabytes (T).

A special value of 0 can be specified to indicate no above the bar storage is to beused.

If 0 is specified or the maximum is reached, the Storage Manager will allocatestorage from below the bar to satisfy requests for storage.

Care should be taken to specify a MEMLIMIT value in the InfoSphere CDC JCLlarge enough to accommodate the amount specified.


Default Setting—2G

Minimum Setting—50MB

Maximum Setting—2,147,483,648MB


TRACE

Specifies the suffixes of the CHCTRCxx members (in the CHCCNTRL data set)containing one or more TRACE commands performed when the InfoSphere CDCaddress space is initialized.

CAUTION:Tracing of InfoSphere CDC tasks through the use of the TRACE commandshould only be performed when requested by IBM Technical Support.

The TRACE command allows you to activate and deactivate specified trace pointsin InfoSphere CDC tasks for troubleshooting purposes. The command can bedefined in CHCTRCxx members or submitted through the console. Activation ordeactivation of trace points through TRACE commands is cumulative if thespecified task and trace point combinations do not coincide. If the same task andtrace point combination is specified in more than one TRACE command, the latestcommand invocation overrides previous invocations. To determine the trace pointsthat are currently active, use the option provided with the TRACE command thatlists active trace points.


Default Setting—TRACE commands in CHCTRCxx members are not performed.Related reference

“TRACE—Trace InfoSphere CDC tasks” on page 127

TRACEDEST

Specifies the default destination of InfoSphere CDC tracing information that isproduced as a result of using the TRACE command.

CAUTION:Tracing of InfoSphere CDC tasks through the use of the TRACE commandshould only be performed when requested by IBM Technical Support.

TRACEDEST=GTF indicates that tracing information is directed to IBM’s GeneralizedTrace Facility (GTF). When InfoSphere CDC tracing information is written to GTF,log records are stamped with a GTF user event identifier (EID) of 300. In order forthis tracing information to be accepted by GTF, the GTF TRACE and USRparameters must be set in the following manner:

TRACE=USRP


USR=(300)

Before activating trace types through the TRACE command, the GTF should beconfigured and activated. If GTF is not activated before invoking the TRACEcommand, a message is issued to indicate that the gathering of data on traceevents begins when GTF is started. For more information about GTF, consult theappropriate IBM documentation.

TRACEDEST=SYSOUT indicates that tracing information is directed to a SPOOL dataset. To direct tracing information to GTF and a SPOOL data set, specifyTRACEDEST=BOTH.


Default Setting—GTFRelated reference

“TRACE—Trace InfoSphere CDC tasks” on page 127

UCSCONFIG

Specifies the suffix that is used to locate the CHCUCSxx member containing theInfoSphere CDC UCS configuration control statement.

<UCSSuffix> must consist of two characters, and can be any combination ofUPPERCASE alphabetic characters and numbers. For example, if UCSCONFIG=D4 isspecified, then the member named CHCUCSD4 in the configuration control dataset is read by InfoSphere CDC to obtain its UCS configuration control statements.



Modifying communications configuration control statementsInfoSphere CDC reads communications configuration control statements whencommunications are being initialized. These statements are read from theCHCCMMxx configuration control data set member. The sample communicationsconfiguration data set member is copied to the configuration control data setduring the installation process, and should be modified for your workingenvironment.

In this section, you will learn:“TCP/IP” on page 44


TCP/IP

TCP/IP is used for communications with other servers running InfoSphere CDCfor z/OS and client workstations running Management Console applications. TheTCP/IP statement must appear in the CHCCMMxx control statement partitioneddata set member. If omitted, an error message is issued and InfoSphere CDC doesnot initialize properly.

The TCP/IP statement contains a number of keywords. The syntax for eachsupported keyword (<Keyword>) in TCP/IP is provided with the keyworddescription in the following sections. Therefore, to specify the TCP/IP statementcorrectly, substitute <Keyword> with the syntax diagram for each keyword youwant to specify in the statement.

Note: Keyword specifications in the TCP/IP statement must be separated bycommas.

The following keywords are supported:“ACCESSSERVERPORT”“AUTODISCEXCLUDE” on page 45“CTRLQUEUESIZE” on page 46“DATAQUEUESIZE” on page 46“ENCRYPT” on page 47“GETHOSTRETRYLIMIT” on page 47“KEEPALIVETIMEOUT” on page 48“SERVICENAME” on page 48“SUBSYSTEM” on page 48

ACCESSSERVERPORT

Specifies the TCP port numbers used as the target of broadcasts to the AccessServers for autodiscovery. This keyword allows a list of UDP port numbers to bespecified.

Autodiscovery enables the transparent propagation of configuration informationassociated with new datastores to existing Access Servers, or the propagation ofconfiguration information associated with existing datastores to new AccessServers. Datastores enabled for autodiscovery broadcast UDP datagrams duringinitialization over the local subnet to UDP port numbers that are recognized byAccess Servers. It is possible that more than one Access Server exists in a network,in which case different UDP port numbers may be used by different AccessServers.


When autodiscovery broadcasts are sent, they are sent to all specified AccessServer UDP port numbers over each defined (but not excluded) IP interface.


Default Setting—10101 - This is the default UDP port number used when AccessServer is installed. For more information, see your InfoSphere CDC AccessManager documentation.

Minimum Setting—1024

Maximum Setting—65535

AUTODISCEXCLUDE

Specifies the IP interfaces (and associated subnets) that should not be used forautodiscovery broadcasting.

It is possible that some IP interfaces should not be used for UDP broadcasting byautodiscovery. For example, an IP interface that connects to the Internet through afirewall may be unsuitable for UDP broadcasting. In this example, Access Serversshould not be configured by datastores over the Internet. Such attempts couldresult in error messages generated from the firewall or information about theconfiguration of a datastore propagated undesirably across the Internet.

Either an IP Interface Name (<IPI/FName>) or an IP Address (<IPAddress>) indotted quad notation can be used to identify an IP interface that should beexcluded from autodiscovery broadcasts. This keyword allows for a list of IPinterfaces to be specified.

Alternatively, * (asterisk) can be specified as the single value for this keyword,meaning that all IP interfaces are to be excluded from autodiscovery broadcasting.Specifying * effectively disables the autodiscovery feature without having toexplicitly exclude every IP interface.

If an IP Interface Name is specified, it is matched against the defined IP interfaces.If an IP Address is specified, the dotted quad notation is validated and matchedagainst the defined IP interfaces. If an IP interface is incorrectly specified, an errormessage is issued. Incorrectly specifying IP interfaces may result in autodiscoverybroadcasting over an undesired IP interface.


Default Setting—Autodiscovery broadcasts UDP datagrams over all defined IPinterfaces. In other words, over all connected subnets.


CTRLQUEUESIZE

Specifies the number of bytes allocated for the queue used by the controlcommunications link.

The control communications link is used for message transfers that coordinate thereplication of data between servers. Set the size of the queue for this link so that itis not as high as the size of the queue for the data communications link.

For this keyword, identify the number of kilobytes (K or k) or megabytes (M orm).


Default Setting—64K

Minimum Setting—64K

Maximum Setting—1MRelated reference

“DATAQUEUESIZE”

DATAQUEUESIZE

Specifies the number of bytes allocated for the queue used by the datacommunications link.

The data communications link is used for the transmission of replicated databetween servers. Since the volume of data replicated by InfoSphere CDC can besignificant, set the size of the queue for this link so that it is greater than the sizeof the queue for the control communications link.

For this keyword, identify the number of kilobytes (K or k) or megabytes (M orm).


Default Setting—1M

Minimum Setting—64K


Maximum Setting—1024MRelated reference

“CTRLQUEUESIZE” on page 46

ENCRYPT

Specifies whether or not to apply lightweight encryption to data replicated byInfoSphere CDC using TCP/IP.

To encrypt data, encryption must be enabled on both the source environment andtarget environment. For non-z/OS servers, contact your IBM representative forinformation about enabling encryption.

ENCRYPT=0 disables encryption, while ENCRYPT=1 enables encryption.


Default Setting—0

GETHOSTRETRYLIMIT

Specifies the maximum number of attempts InfoSphere CDC performs to retrievethe host name or IP address during initialization of communications.

A failure to retrieve the host name or IP address is indicated when the TCP/IPgethostbyaddr or gethostbyname service returns an error. If the host name or IPaddress cannot be retrieved after the specified number of attempts, thecommunication environment in the InfoSphere CDC address space is not initializedcorrectly.


Default Setting—4 attempts

Minimum Setting—1 attempt

Maximum Setting—100 attempts


KEEPALIVETIMEOUT

Specifies the time that InfoSphere CDC will allow a socket to remain idle beforesending a pulse message on the socket. This feature is useful for preventingfirewalls from closing sockets that have been idle for some time but will still berequired in order to InfoSphere CDC to function. If the keyword is not specified, orif an illegal value is specified, the default value is used.



Minimum Setting—5 seconds


SERVICENAME

Specifies the name of the TCP/IP service that the InfoSphere CDC address spaceprovides to Management Console and to other InfoSphere CDC servers thatrequire replication services.

The value of this keyword identifies the service name for the datastore imbeddedin InfoSphere CDC (see your Management Console documentation for moreinformation about datastore), and it is also the service name assigned to theInfoSphere CDC address space’s replication services. Either a symbolic servicename that has been defined to Communications Server, or a numeric TCP portnumber (between 1024 and 65535) that does not conflict with already assigned TCPport numbers can be specified.

Additionally, this value specifies the UDP port number that is used by thedatastore to accept UDP datagrams (addressed or broadcast) that are necessary tosupport autodiscovery. Since a single service name is specified, the assigned TCPand UDP port numbers must be numerically the same.

This is a required keyword that cannot be omitted from the TCP/IP statement.

SUBSYSTEM


Specifies the TCP/IP Subsystem (stack) address space that is used by InfoSphereCDC for communications between itself and other instances of InfoSphere CDC, orbetween itself and Management Console.

It is possible to have more than one TCP/IP Subsystem address space executingconcurrently on the same image of z/OS. This is called running multiple stacks.

<TCP/IPSubsys> is the name of the z/OS address space in which TCP/IP isexecuting. If * (asterisk) is specified or defaulted, then the first z/OS address spacefound in which a TCP/IP stack is executing is used. Since it is unpredictable whichof the multiple stacks is found first, it is suggested that you avoid specifying (ordefaulting to) * unless there is only one TCP/IP Subsystem address spaceexecuting at any time.


Default Setting—* - The first TCP/IP Subsystem address found is used.

Modifying DBMS configuration control statementsInfoSphere CDC reads DBMS configuration control statements when DBMSrepositories are being initialized. These statements are read from the CHCDBMxxconfiguration control data set member. The suffix on the CHCDBMxx member isspecified through the DBMSCONFIG keyword in the CHCCFGxx Generalconfiguration control statement member. The sample DBMS configuration data setmember is copied to the configuration control data set during the installationprocess, and should be modified for your working environment.

In this section, you will learn:“DB2”

Related reference

“DBMSCONFIG” on page 32

DB2DB2 Statement in CHCDBMxx

The DB2 statement contains a number of keywords. The syntax for each supportedkeyword (<Keyword>) in DB2 is provided with the keyword description in thefollowing sections. Therefore, to specify the DB2 statement correctly, substitute<Keyword> with the syntax diagram for each keyword you want to specify in thestatement.

Note: Keyword specifications in the DB2 statement must be separated by commas.

The following keywords are supported:“ALLOWSQL” on page 50“BUFSIZE” on page 50“BUFTHRESHOLD” on page 51“CACHELEVEL1RESERVED” on page 51


“CACHEBLOCKSIZE” on page 52“CACHELEVEL1SIZE” on page 53“DEST” on page 54“FLUSHONSHUTDOWN” on page 54“LOADERDEFAULTS” on page 55“LOGPOLLINTERVAL” on page 55“LOGPROFILE” on page 56“MAXSQLERRMSG” on page 56“MAXSUBSCRSTAGESIZE” on page 57“ONSCHEMACHANGE” on page 58“OPENCOMMITWARNAGE” on page 58“PLANSUFFIX” on page 59“RECOVERYRETRYLIMIT” on page 59“REPLMETADATA” on page 60“REPLTIMESTAMP” on page 60“RETRYCACHESIZE” on page 61“SQLWHEREROWSEL” on page 61“SSID” on page 62“TIMEOUTRECOVERYDELAY” on page 62“COMMITFREQ” on page 63“USELOADER” on page 64

ALLOWSQL

Specifies if a user can enter After Refresh and After Clear SQL statements. If youset the keyword to YES, then InfoSphere CDC enables the Additional SQL featurein Management Console and lets the user define compound and arbitrary SQLstatements. InfoSphere CDC executes these statements after a successful refresh ortable clear operation on the target table.



BUFSIZE

Specifies the size, in kilobytes, of the IFC-managed buffer that receives the DB2trace data.


The size assigned to this keyword must be within the acceptable range in 4 KBincrements starting from the minimum setting. If you specify a size that is outsideof the acceptable range, the closest minimum or maximum is used.


Default Setting—132 KB

Minimum Setting—8KB

Maximum Setting—1024 KB

BUFTHRESHOLD

Specifies the percentage of the IFC-managed buffer that must contain data beforeDB2 informs InfoSphere CDC that the buffer contains DB2 Log data to beprocessed.

The value assigned to this keyword represents a percentage of the value specifiedthrough the BUFSIZE keyword. The value assigned (or defaulted) to this keywordcan have an impact on server resource utilization and replication latency.


Default Setting—1% of the value specified for BUFSIZE

Minimum Setting—1% of the value specified for BUFSIZE

Maximum Setting—99% of the value specified for BUFSIZERelated concepts

“BUFTHRESHOLD keyword considerations” on page 76

CACHELEVEL1RESERVED

Specifies the size, in megabytes, of the reserved portion of the Level 1 DB2 Logcache that maintains records recently placed in the DB2 Log.

InfoSphere CDC can use two caches (Level 1 and Level 2) to improve performancewhen multiple subscriptions are used to replicate multiple streams of data at thesame time.

The Level 1 cache resides in memory. This cache is used to rapidly retrieve DB2Log records during replication. The reserved part of this cache maintains recordsthat have recently been placed in the DB2 Log. This keyword determines how


much of the Level 1 cache is used for this purpose. Allocating approximately 80%of the Level 1 cache for the reserved part should be the setting for most workingenvironments. In addition, consider the following when setting the size of thereserved part of the Level 1 cache:v The size of the reserved part must be at least 5 megabytes. If you specify a size

between 1 and 4 megabytes inclusively, InfoSphere CDC sets the size of thereserved part to 5 megabytes.

v The size of the reserved part must occupy at least one block of the Level 1cache. Otherwise, InfoSphere CDC sets the size of the reserved part to thedefault value for the CACHELEVEL1RESERVED keyword.

v The size of the reserved part cannot occupy all blocks in the Level 1 cache. Inother words, at least one block must be allocated for the other part of the cache.Otherwise, InfoSphere CDC sets the size of the reserved part to the default valuefor the CACHELEVEL1RESERVED keyword.

v The size of the reserved part must be an exact multiple of the cache block size. Ifnecessary, InfoSphere CDC sets the size of the reserved part by rounding downthe CACHELEVEL1RESERVED keyword setting to the closest exact multiple ofthe cache block size.

If any of the keywords for defining the Level 1 and Level 2 caches(CACHEBLOCKSIZE, CACHELEVEL1RESERVED, and CACHELEVEL1SIZE) areset to zero, DB2 Log records are not cached.


Default Setting—0

Minimum Setting—10Related concepts

“Running the CHCCRCCH job” on page 20Related reference

“CACHEBLOCKSIZE”

CACHEBLOCKSIZE

Specifies the size, in megabytes, of each block in the Level 1 and Level 2 DB2 Logcaches.


This setting determines how much data is transferred when a block is movedbetween the two caches. In addition, the size of the Level 1 and Level 2 caches, asdefined by the CACHELEVEL1SIZE keyword, must be an exact multiple of theblock size. A block size of 1 or 2 megabytes is sufficient for most workingenvironments.



Note: If you change the block size, the records in the Level 2 cache are clearedwhen you restart the InfoSphere CDC address space. After InfoSphere CDC hasbeen restarted, those records will be read from the DB2 Log.


Default Setting—0Related concepts


“CACHELEVEL1SIZE”

CACHELEVEL1SIZE

Specifies the size, in megabytes, of the Level 1 DB2 Log cache.


The Level 1 cache resides in memory. This cache is used to rapidly retrieve DB2Log records during replication. The size of the Level 1 cache should be set tominimize paging of the cache to disk. A cache size of 1000 megabytes or lessshould be the setting for most working environments. Do not set the cache size toohigh so that sufficient memory cannot be allocated. In addition, consider thefollowing when setting the size of the Level 1 cache:v The size of the Level 1 cache must be at least 10 megabytes. If you specify a

cache size between 1 and 9 megabytes inclusively, InfoSphere CDC sets thecache size to 10 megabytes

v The size of the Level 1 cache must be at least twice the cache block size asdefined by the CACHEBLOCKSIZE keyword. Otherwise, InfoSphere CDC setsthe cache size to the default value for the CACHELEVEL1SIZE keyword.

v The size of the Level 1 cache must be an exact multiple of the cache block size.If necessary, InfoSphere CDC sets the cache size by rounding down theCACHELEVEL1SIZE keyword setting to the closest exact multiple of the cacheblock size.



Default Setting—0


Related concepts


“CACHEBLOCKSIZE” on page 52

DEST

Specifies the buffer in which the DB2 trace output is recorded.

The value specified through this keyword is used in the DB2 START TRACEcommand that specifies which DB2 Trace Buffer is used for capturing DB2 Logrecords.

Either a specific destination (for example, buffer OP1, OP2, OP3, OP4, OP5, OP6,OP7, or OP8) or a generic destination (OPX) can be assigned using this keyword. Ifa generic destination is specified, the first free buffer that DB2 allows to beassigned is used. This could be an OP buffer that is currently being used for otherpurposes (for example, gathering DB2 performance data). Sharing a buffer in thismanner could interfere with InfoSphere CDC’s ability to obtain Log data fromDB2. For this reason, it is suggested that an available, unused OP buffer beselected for use by the InfoSphere CDC address space, and assigned using one ofthe specific values (OP1 through OP8) of the DEST keyword. Note that all traces toan OPX destination must be stopped before the buffer is considered as being nolonger in use. Traces that are started to an OPX buffer overwrite previous traceswritten to the same buffer.


Default Setting—OPX

FLUSHONSHUTDOWN

Specifies whether or not InfoSphere CDC forces DB2 Log entries to be read whenreplication is stopped in a controlled manner.

If there is very little DB2 Log activity during replication, there may not be enoughentries in the log to cause log reads to occur frequently. If replication is stopped ina controlled manner under these conditions, a lengthy delay is incurred before theoperation is completed.

If FLUSHONSHUTDOWN=YES, InfoSphere CDC forces the DB2 Log to be read whenreplication is stopped in a controlled manner. Given the conditions as described in


the previous paragraph, the result is a faster shutdown as compared to whenFLUSHONSHUTDOWN=NO. If FLUSHONSHUTDOWN=NO, replication is stopped in a controlledmanner, but the amount of time to complete the operation under the sameconditions is likely to be longer. If it is necessary to reduce the amount of the timeit takes to end replication in a controlled manner in your environment, set thiskeyword to YES.


Default Setting—YESRelated reference

“SHUTDOWN—Stop InfoSphere CDC address space” on page 92

LOADERDEFAULTS

Specifies the suffix that is used to locate the CHCLDRxx member containing theDB2 LOAD configuration control statement.

<LoadSuffix> must consist of two characters, and can be any combination of UPPERCASE alphabetic characters and numbers. For example, if LOADERDEFAULTS=C3 isspecified, then the member named CHCLDRC3 in the configuration control dataset is read by InfoSphere CDC to obtain its DB2 LOAD configuration controlstatement.


Default Setting—The suffix used for the CHCDBMxx member in the configurationcontrol data set.

LOGPOLLINTERVAL

Note: This keyword only applies when InfoSphere CDC operates in a DB2 DataSharing Group (DSG) and when a member of the DSG has low DB2 Log activity. Ithas no purpose if the DB2 subsystem to which InfoSphere CDC is connected is nota member of a DB2 Data Sharing Group.

Specifies how frequently the log profiling task performs unprompted reads in aDB2 Data Sharing Group when the local DB2 Log is idle (that is, it is not activelybeing extended by DB2 activity).

The value for this keyword is the number of seconds the local DB2 Log must havebeen idle before the log profiling task autonomously requests additional DB2 Logdata.




Minimum Setting—5 seconds


LOGPROFILE

Specifies the manner in which the InfoSphere CDC log profiling task builds andmaintains its profile of the DB2 Log.

LOGPROFILE=FULL indicates that the task retrieve and analyze the controlinformation of every record that it receives from the DB2 Log. The task does notneed the application data during profiling, and so compressed DB2 Log data is notdecompressed. As the task examines each record, it searches for those records thatidentify the following:v The locations of table space drain activities, which usually occur during REORG

utility executions.v Changes to the DB2 user authorization system tables.

In terms of server resource consumption, fully profiling the DB2 Log isapproximately equivalent to running continuous mirroring on a singlesubscription.

LOGPROFILE=FULL is appropriate in mirroring scenarios that include onlinereorganization of table spaces containing mirrored tables. When these table spacesare reorganized, subscriptions that are mirroring data do not have to be stoppedmanually. In other words, online reorganizations can be handled transparently byInfoSphere CDC.

LOGPROFILE=NONE indicates that you want to disable the log profiling task. None ofthe benefits supported under full profiling are provided, and server resourceconsumption as a result of DB2 Log profiling is nil. This keyword setting ensuresbehavior is consistent with previous InfoSphere CDC versions. LOGPROFILEshould be set to NONE when compressed table spaces containing mirrored tablesare reorganized through manually stopping and restarting mirroring.


Default Setting—FULL

MAXSQLERRMSG


Specifies the maximum number of messages that can be generated fornonrecoverable errors during replication (refresh, mirroring, and auditing) for asingle subscription.

This keyword applies only to implementations where refresh, mirroring, orauditing is allowed to continue after the first nonrecoverable error has occurred.

If MAXSQLERRMSG=0, no limit is imposed on the number of messages that can begenerated for nonrecoverable errors. This setting effectively disables the limit onthe number of messages generated.


Default Setting—25 messages

Minimum Setting—0 messagesRelated concepts

“CONFIG” on page 27Related reference

“ENDONERROR” on page 35

MAXSUBSCRSTAGESIZE

Specifies the maximum size of the staging space that is used to stage replicatedchanges for commit groups (DB2 Units of Recovery) for a single subscription andthe maximum number of completed non-empty commit groups to keep in thestaging space at one time.

The first value provides a means of limiting the use of z/OS’s real storageresources by InfoSphere CDC when it is mirroring tables. The staging space isbacked by a z/OS Hiperspace™, which is stored in z/OS Central Storage andpaged to z/OS Auxiliary Storage. Extremely large commit groups can causeInfoSphere CDC to store large volumes of data in the staging space, consumingcorresponding amounts of central storage and auxiliary storage. While it isexpected that good application design will limit the size of commit groups, theMAXSUBSCRSTAGESIZE keyword provides a means of stopping InfoSphere CDCfrom using excessive resources if this is not the case.

A staging space is associated with each subscription created in ManagementConsole. If the content of a staging space nears capacity, InfoSphere CDC generates


a warning message (CHC1532W). If this message is seen, you should considerincreasing the maximum size to reduce the risk of reaching the limit. If the contentof a staging space reaches the maximum size, InfoSphere CDC generates an errormessage (CHC1524E), and automatically ends replication for the subscription.

When specifying the first value, you identify the maximum number of kilobytes (Kor k), megabytes (M or m), gigabytes (G or g), or bytes (the default unit if arecognized letter is not specified) that can be stored in a staging space.

The second value indicates the maximum number of completed non-empty commitgroups to keep in the staging space at one time. This allows InfoSphere CDC tocontinue to stage commit groups while simultaneously transmitting a completedcommit group.


Default Setting—(2147483632, 10)

Minimum Setting (for second value)—1 commit group

Maximum Setting—(2147483632, 255)Related reference

“CHC1524E” on page 442“CHC1532W” on page 443

ONSCHEMACHANGE

Specifies what action to take when the schema of a source table being mirrored ischanged such that changes to the table can no longer be correctly replicated.

If ONSCHEMACHANGE=STOP, the subscription ends abnormally.

If ONSCHEMACHANGE=IDLE, the table whose schema changes is idled (no longerreplicated). Any other tables in the subscription continue to be replicated normally.This can cause transactional integrity to be broken.


Default Setting—STOP

OPENCOMMITWARNAGE

Specifies the maximum age, in minutes, of the oldest open commit group that canexist in a staging space without a warning message being generated.


InfoSphere CDC checks each staging space every 15 minutes to determine the ageof the oldest open commit group. If the age exceeds the number of minutesassigned to the OPENCOMMITWARNAGE keyword, a warning message(CHC0051W) is generated. Commit groups in a staging space that have been leftopen for some period of time may eventually result in a staging space running outof space, and replication being stopped. If CHC0051W is generated, you shouldinvestigate the reasons for the open commit groups, and take appropriate actions.

If OPENCOMMITWARNAGE=0, warnings about open commit groups in a staging spaceare not generated. If a value outside the acceptable range is specified, the closestminimum or maximum value is used.



Minimum Setting—0 minutes

Maximum Setting—525600 - The total number of minutes in a non-leap year.Related reference

“CHC0051W” on page 245

PLANSUFFIX

Specifies the two characters that ensure the names of the DB2 plans are unique.

These plans are used to identify the owner of InfoSphere CDC metadata tables. Bychanging the suffix, you can refer to different metadata tables. The plans must becreated by the DB2 BIND process executed by the CHCBNDPL job.


Default Setting—The suffix of the CHCDBMxx member (the charactersrepresented by xx) that contains this keyword.Related concepts

“Running the CHCBNDPL job” on page 18

RECOVERYRETRYLIMIT

Specifies the maximum number of retry attempts after a DBMS recoverable failure(deadlock, timeout or resource unavailable) has prevented an operation fromcompleting successfully.


If RECOVERYRETRYLIMIT=0, then no attempt is made after encountering a recoverablefailure. If all retry attempts are unsuccessful, the recoverable failure is escalated toa nonrecoverable failure and handled according to the ENDONERROR keywordsetting.

Note: For deadlocks, there is no time delay between consecutive retries. In otherwords, the value of the TIMEOUTRECOVERYDELAY keyword is not considered.Recovery from deadlocks is more likely when retries are performed consecutivelywithout delay.


Default Setting—0 attempts

Minimum Setting—0 attempts

Maximum Setting—65535 attemptsRelated reference

“ENDONERROR” on page 35

REPLMETADATA

Specifies whether or not InfoSphere CDC metadata tables can be included in atable mapping for replication in Management Console.

If REPLMETADATA=NO, metadata tables are not available for mapping in ManagementConsole.

If REPLMETADATA=YES, metadata tables are available for mapping and can bereplicated by InfoSphere CDC. Replication of the InfoSphere CDC metadata tablesrequires that the DB2 attribute CHANGE DATA CAPTURE be set for the tables. Bydefault, the metadata DB2 tables are created with this attribute. If for some reasonthe tables do not have this attribute, then the attribute will have to be set beforethe tables can be accessed in Management Console. The InfoSphere CDC addressspace has to be shut down before this attribute can be set.



REPLTIMESTAMP

Specifies how the DB2 log timestamp is to be formatted during replication. TheDB2 log timestamp for a change made to a source table records the time at whichthat change was made to the table.


If REPLTIMESTAMP=LOCAL, the DB2 log timestamp is formatted in the source system’slocal time.

If REPLTIMESTAMP=UTC, the DB2 log timestamp is formatted in the UTC (UniversalCoordinated Time).

This keyword affects the value of the &TIMESTAMP journal control field for bothrefresh and mirroring. It also affects the timestamps formatted in messages thatreport on the DB2 log timestamp, such as start and stop mirroring messages andreplication status messages.


Default Setting—LOCAL

RETRYCACHESIZE

Specifies the maximum size of the cache used by each target server to store acommit group if the Deadlock/Timeout Retry feature is active. The size can bespecified in Megabytes (M) or Gigabytes (G).

This keyword is only relevant if the RECOVERYRETRYLIMIT keyword wasspecified with a value greater than zero.

The retry cache is allocated through the Storage Manager. Care should be taken tospecify a large enough value on the STG64LIMIT keyword to accommodate thecaches used by all target subscriptions.


Default Setting—1G

Minimum Setting—1M

Maximum Setting—9999GRelated reference

“RECOVERYRETRYLIMIT” on page 59

SQLWHEREROWSEL

Specifies whether or not row filtering expressions can be treated as SQL WHEREclauses in SELECT statements that implement data refreshes.


Treating a row filtering expression as an SQL WHERE clause can improve refreshperformance. In particular, significant improvements can occur when a smallpercentage of the rows in a large table are selected for refresh.

If SQLWHEREROWSEL=YES, InfoSphere CDC generates a message (CHC0792I) toindicate whether or not a row filtering expression can be used as an SQL WHEREclause.

In order to be used as an SQL WHERE clause, the expression must be a correctlyformed as a standard InfoSphere CDC row filtering expression and also asyntactically correct search-condition operand of the ″WHERE″ keyword in an SQLWHERE clause.


Default Setting—NORelated reference

“CHC0792I” on page 398

SSID

Specifies the DB2 Subsystem or data sharing group containing the metadata andthe tables that are the source or target of replicated data.

The value assigned to this keyword is the z/OS Subsystem Identifier of the DB2region or the group attach name of the DB2 data sharing group. When executingon a data sharing group, the group attach name is the preferred value.


Default Setting—The value specified in the DSNHDECP member of theSDSNEXIT data set.

TIMEOUTRECOVERYDELAY

Specifies the amount of time (expressed in seconds) InfoSphere CDC waits beforeattempting to retry an operation after a DBMS recoverable failure due to a timeoutor resource unavailable has prevented an operation from completing successfully.

Note: This setting only applies to timeouts. It does not apply to deadlocks.Recovery from timeouts is more likely when there is a significant time delaybetween consecutive attempts.

This keyword should be set to a value between 75% and 150% of the DB2 locktimeout delay setting.




COMMITFREQ

Specifies how frequently mirrored changes received from the source server will becommitted to the subscription database.

This keyword is set to a triplet of three mandatory values:v The first value is the number of changes that can be applied to tables before a

COMMIT is triggered.v The second value is the number of seconds that must pass since the last

COMMIT was applied before a COMMIT is triggered.v The third value is the number of commit groups that must be received from the

source since the last COMMIT before a COMMIT is triggered.

If commitment control is not in effect, a COMMIT will be performed immediatelywhenever either of the first two conditions (number of changes or number ofseconds) is satisfied.

If commitment control is in effect, a COMMIT will be performed when the nextcomplete commit group is received after any of the three conditions is met. Thereis an exception if commitment control is in effect and the specified number ofseconds passes and the last thing received from the source was a complete commitgroup. In this case, a COMMIT will be performed immediately.

When COMMIT is performed, the change counter, timer, and commit groupcounter are all reset.

The COMMITFREQ settings apply to each subscription separately. Changes orcommit groups received for one subscription do no affect when COMMIT isperformed for any other subscription. Similarly, each subscription has its owncommit timer, which is not necessarily synchronized with any other subscription’scommit timer.

The higher the settings for the COMMITFREQ keyword, the greater the increase inthroughput that will be achieved. However, the increased throughput will beobtained at the cost of increasing the number, level of, and duration of DBMS locksthat are acquired when the changes are being applied and an increased cost ofhandling deadlock/timeout retry situations.

For example, if COMMITFREQ=(1000,60,1) and commitment control is not in effect.COMMIT will be performed after 1000 changes are received or 60 seconds pass,whichever occurs first. Since commitment control is not in effect, no commitgroups should be received.

In another example, if COMMITFREQ=(10000,300,10) and commitment control is ineffect. COMMIT will be performed at the end of the next commit group after 10000


changes are received, at the end of the next commit group after 60 seconds pass, orafter 10 complete commit groups are received. In addition, if, after 60 seconds pass,the last thing received was a complete commit group (no partial commit group),COMMIT will be performed.

Note: If commitment control is in effect, setting the third value of COMMITFREQto 1 (the default) ensures that every commit group is committed as it is received.

Note the following considerations for this keyword:v Performance improvements are directly proportional to the size of the commit

groups that you replicate.v Commit group integrity is never compromised by this feature.v Once commit groups have been grouped to the point that 500 or more changes

are being made between commits, no further performance gains are possible.


Default Setting—(200 (records), 30 (seconds), 1 (commit group))

USELOADER

Specifies whether or not DB2 LOAD is employed by InfoSphere CDC to refreshtables.

The default behavior (USELOADER=NO) is to use the standard InfoSphere CDC refreshoperation.

USELOADER determines the use of DB2 LOAD at the system level. By using theCHCMTAUT utility, DB2 LOAD use can be set at the datastore and table levels. Inthis case, the USELOADER setting is overridden.

Note: The following requirements must be met in order to use DB2 LOAD torefresh a target table in an InfoSphere CDC replication configuration:v Use of the DB2 LOAD utility must have been requested.v The mapped target table must be the only one in the table space.v The mapped target table cannot be included in a cascading replication

configuration. For general information about cascading replication, see yourManagement Console documentation.

v The total length of all columns in the mapped target table cannot exceed 32,760bytes minus the number of columns in the table.

v If user exit programs have been configured for the mapped target table, the cleartable operation cannot be disabled.

v A row identifier cannot be defined for the mapped target table.v Auditing of source table changes (LiveAudit) cannot be enabled when

configuring the mapped target table. For information about configuringLiveAudit, see your Management Console documentation.


If the DB2 LOAD utility has been enabled (through USELOADER or CHCMTAUT),but one or more of these requirements have not been met, an attempt to refresh atable in Management Console generates a warning message and the standardInfoSphere CDC refresh is used instead of DB2 LOAD.


Default Setting—NORelated concepts

“CHCMTAUT Utility” on page 151“InfoSphere CDC user exits” on page 165

Modifying DB2 LOAD configuration control statementsInfoSphere CDC reads a DB2 LOAD configuration control statement before startingto refresh tables. This statement is read from the CHCLDRxx configuration controldata set member. The suffix on the CHCLDRxx member is specified through theLOADERDEFAULTS keyword in the CHCDBMxx DBMS configuration controlstatement member.

The suffix can also be specified using the CHCMTAUT utility, but it defines aCHCLDRxx member at the datastore or table level. LOADERDEFAULTS is aserver-wide setting that can be overridden by appropriate use of the CHCMTAUTutility.

A sample DB2 LOAD Configuration data set member is copied to the configurationcontrol data set during the installation process, and should be modified for yourworking environment.

In this section, you will learn:“DB2LOADER”

Related reference

“LOADERDEFAULTS” on page 55

DB2LOADER

The DB2LOADER statement contains a number of keywords that defineserver-level settings referenced by the DB2 LOAD utility. Some of the keywords inthe statement correspond to keywords in the IBM DB2 utility LOAD DATAstatement. For information about the LOAD DATA statement, see the appropriateIBM documentation.

DB2LOADER Statement in CHCLDRxx

The syntax for each supported keyword (<Keyword>) in DB2LOADER is providedwith the keyword description in the following sections. Therefore, to specify theDB2LOADER statement correctly, substitute <Keyword> with the syntax diagramfor each keyword you want to specify in the statement.


Note: Keyword specifications in the DB2LOADER statement must be separated bycommas.

The following keywords are supported:“DISCARDS”“DSNDEVT”“DSNHLQ” on page 67“ENFORCE” on page 67“KEEPDICTIONARY” on page 67“LOG” on page 68“PREFORMAT” on page 68“REUSE” on page 68“SORTKEYS” on page 69“SORTNUM” on page 69“SORTDEVT” on page 69“SYSUT1SIZE/SORTOUTSIZE/SYSERRSIZE/SYSMAPSIZE/SYSDISCSIZE” onpage 70

DISCARDS

This keyword corresponds to the DISCARDS keyword supported in the IBM DB2utility LOAD DATA statement.

If it is specified and assigned a positive value, the DISCARDS keyword and itssetting are processed by DB2 LOAD.


Default Setting—DISCARDS is not processed by DB2 LOAD.

DSNDEVT

Specifies the device type to use when allocating DB2 LOAD utility work data sets.

Generic or actual device names can be specified.


Default Setting—SYSDA


DSNHLQ

Specifies the high level qualifier used when allocating the DB2 LOAD utility workdata sets.

The qualifier cannot exceed 11 characters in length. InfoSphere CDC builds data setnames by concatenating the keyword setting, the name of the replication agent, thecurrent date and time, and the default DD name of the data set specified in theDB2 LOAD utility documentation. InfoSphere CDC requires sufficient authority toallocate, write to, read from, and delete these data sets.


Default Setting—The authorization identifier of the InfoSphere CDC addressspace.

ENFORCE

This keyword corresponds to the ENFORCE keyword supported in the IBM DB2utility LOAD DATA statement.

If it is specified, the ENFORCE keyword and its setting are processed by DB2LOAD.


Default Setting—CONSTRAINTS

KEEPDICTIONARY

This keyword corresponds to the KEEPDICTIONARY keyword supported in theIBM DB2 utility LOAD DATA statement.

If KEEPDICTIONARY=YES, the KEEPDICTIONARY keyword is processed by DB2LOAD.




LOG

This keyword corresponds to the LOG keyword supported in the IBM DB2 utilityLOAD DATA statement.

If LOG=YES, the LOG keyword is processed by DB2 LOAD.


Default Setting—YES

PREFORMAT

This keyword corresponds to the PREFORMAT keyword supported in the IBMDB2 utility LOAD DATA statement.

If PREFORMAT=YES, the PREFORMAT keyword is processed by DB2 LOAD.



REUSE

This keyword corresponds to the REUSE keyword supported in the IBM DB2utility LOAD DATA statement.

If REUSE=YES, the REUSE keyword is processed by DB2 LOAD.




SORTKEYS

This keyword corresponds to the SORTKEYS keyword supported in the IBM DB2utility LOAD DATA statement.

If it is specified and assigned a positive value, the SORTKEYS keyword and itssetting are processed by DB2 LOAD.


Default Setting—SORTKEYS is not processed by DB2 LOAD.

SORTNUM

This keyword corresponds to the SORTNUM keyword supported in the IBM DB2utility LOAD DATA statement.

If it is specified with SORTDEVT, the SORTNUM keyword and its setting are notprocessed by DB2 LOAD.


Default Setting—SORTNUM are not processed by DB2 LOAD.Related reference

“SORTDEVT”

SORTDEVT

This keyword corresponds to the SORTDEVT keyword supported in the IBM DB2utility LOAD DATA statement.

If it is specified, the SORTDEVT keyword and its setting are processed by DB2LOAD.


Default Setting—The SORTDEVT and SORTNUM keywords are not processed byDB2 LOAD, even though SORTNUM may be specified.


SYSUT1SIZE/SORTOUTSIZE/SYSERRSIZE/SYSMAPSIZE/SYSDISCSIZE

Identifies the sizes (expressed in number of cylinders) of the corresponding DB2LOAD utility work data sets. Both a primary and secondary allocation can bespecified.

These keywords are required, but they can be omitted if they have been specifiedat a higher level. For example, if the server-level CHCLDRxx member specifiesSYSUT1SIZE, CHCLDRxx members at the datastore and table levels can omitSYSUT1SIZE. The members at the datastore and table levels inherit the settingfrom the server-level. If the secondary allocation is omitted for any keyword, thedefault is zero.

Modifying UCS configuration control statementsInfoSphere CDC’s UCS configuration control statements are read when UnicodeConversion Services is being initialized. These statements are read from theCHCUCSxx configuration control data set member. The suffix on the CHCUCSxxmember is specified through the UCSCONFIG keyword in the CHCCFGxx Generalconfiguration control statement member. The sample UCS Configuration data setmember should be copied to the configuration control data set during theinstallation process and modified for your working environment.

In this section, you will learn:“UCS” on page 71“CCSIDMAP” on page 71“CONVERSION” on page 72“IANAMAP” on page 73


Related reference

“UCSCONFIG” on page 43

UCS

The UCS statement contains one keyword:“DDASIZE”

DDASIZE

Specifies the size, in bytes, of the Dynamic Data Area used by the UnicodeConversion Services.

Note: The value of the DDASIZE may have an impact on server performance.Therefore, you should use the default value for this keyword.


Default Setting—4096 bytes

CCSIDMAP

The CCSIDMAP statement specifies a relationship between a Unicode ConversionServices CCSID and a corresponding code set name.

This relationship needs to be specified because Unicode Conversion Services canonly recognize Coded Character Set Identifiers (CCSIDs), whereas other conversionsystems may only recognize code set name text strings.

The CCSIDMAP statement contains one keyword. A default set of CCSIDMAPstatements is provided in the CHCUCSxx sample member. This member should becopied to the configuration control data set and renamed to contain a valid suffix.

You can add, modify, or delete CCSIDMAP statements. You can specify as manyCCSIDMAP statements as you want.

The following keyword is supported:“CODESET”

CODESET

Specifies the relationship between CCSIDs and their code set names.

This keyword is set to a pair of mandatory values. The first value specifies theCCSID that is mapped to a code set name. This value must have a numeric datatype. CCSIDs are the numbers used by Unicode Conversion Services to represent


single-byte and double-byte code pages. For example, 1047 is the CCSID for theEBCDIC single-byte code page used on American English z/OS servers.

The second value specifies the code set name assigned to the CCSID identified inthe first parameter. This parameter must have a character data type and amaximum length of 19 characters. For example, IBM-1047 is the code set nameused for CCSID 1047 and is the name that can be exchanged with other non-z/OSservers.

CONVERSION

The CONVERSION statement specifies the Coded Character Set Identifier (CCSID)conversions that have been installed on Unicode Conversion Services.

The list of installed conversions can be obtained by entering the z/OS consolecommand ″D UNI,ALL″. The information displayed after issuing this commandcan be used to create the CONVERSION statements required for InfoSphere CDC.InfoSphere CDC’s CONVERSION statement is similar to the Unicode ConversionServices CONVERSION statement that is coded when creating a conversion imagein Unicode Conversion Services. Unicode Conversion Services does not provideany means of obtaining this information programmatically; this is why theInfoSphere CDC’s CONVERSION statements need to be provided.

The following keywords are supported:“METHOD”“SRCCCSID”“TGTCCSID” on page 73

METHOD

Specifies the technique-search-order to be used for the specified CCSIDs in theCONVERSION statement.

For more information about technique-search-order values, see the appropriate IBMdocumentation.

Default Setting—The conversion technique is not set.

SRCCCSID

Specifies a source Coded Character Set Identifier (CCSID) in a conversion pair.

Unicode Conversion Services can convert character data from this CCSID to thetarget CCSID specified in the CONVERSION statement.

This is a required keyword that cannot be omitted from the CONVERSIONstatement.


TGTCCSID

Specifies a target Coded Character Set Identifier (CCSID) in a conversion pair.

Unicode Conversion Services can convert character data to this CCSID from thesource CCSID specified in the CONVERSION statement.

This is a required keyword that cannot be omitted from the CONVERSIONstatement.

IANAMAP

The IANAMAP statement specifies a relationship between a Unicode ConversionServices Coded Character Set Identifier (CCSID) and one or more correspondingIANA code set names.

This relationship needs to be specified because Unicode Conversion Services canonly recognize CCSIDs, whereas other conversion systems may only recognizeIANA code set name text strings.

The IANAMAP statement contains two keywords. A default set of IANAMAPstatements is provided in the CHCUCSxx sample member. This member should becopied to the configuration control data set and renamed to contain a valid suffix.

You can add, modify, or delete IANAMAP statements. You can specify as manyIANAMAP statements as you want.

The following keywords are supported:“CCSID”“NAME”

CCSID

Specifies the Coded Character Set Identifier (CCSID) to be mapped to an IANAcode set name or names.

This keyword specifies the CCSID that is mapped to the code set name or names.This value must have a numeric data type. CCSIDs are the numbers used byUnicode Conversion Services to represent single-byte and double-byte code pages.For example, 1047 is the CCSID for the EBCDIC single-byte code page used onAmerican English z/OS servers.

NAME

Specifies the IANA code set names that should be associated with the CodedCharacter Set Identifier (CCSID).

This keyword specifies one or more IANA code set names that should beassociated with the CCSID specified on the CCSID keyword. If more than oneIANA name is specified, they should be separated by commas and enclosed inbrackets.


Executing InfoSphere CDCThe member named CHCPROC in the SCHCCNTL data set contains sample JCLfor executing InfoSphere CDC. This JCL is in the form of a JCL procedure. Afterappropriate modifications, it can be catalogued by storing it in a system procedurelibrary, or used as the basis for producing a job that can be submitted for executionin batch mode. If the modified JCL is catalogued in a system procedure library,then it can be called by JCL that is submitted as a batch job, or referenced by az/OS START command entered on a system console. If it is used to produce a jobfor submission to batch execution, then it can be used either as an in-streamprocedure within the job’s JCL, or stripped down to raw step execution JCL.

Whatever the manner in which the CHCPROC sample is used, the main distinctionis whether InfoSphere CDC executes as a started task or a batch job.

If InfoSphere CDC is executed as a batch job, then the JOB statement must specifythe security identifier that has been assigned to the InfoSphere CDC address space,and used to replace the <CHCUserID> substitution placeholder. This securityidentifier is coded as the value of the USER keyword on the JOB statement. Apassword (the value of the PASSWORD keyword) may also be required, if thesubmitter of the job does not have surrogate capability for the security identifier.

If InfoSphere CDC is executed as a z/OS started task, then the appropriate stepsmust be taken to associate the security identifier with the z/OS started task thatwill execute InfoSphere CDC. These steps can differ, depending on the accesscontrol software being used by the installation.

InfoSphere CDC uses storage above the bar. As distributed, the CHCPROC sampleJCL has a REGION parameter coded with a value of 0M. This causes theMEMLIMIT parameter to use the defaulted value of “NOLIMIT”. If you changethe REGION parameter to anything other than 0M, then the MEMLIMIT defaultvalue will no longer be “NOLIMIT”, and requests for storage above the bar mayfail. If the REGION parameter value is changed, be sure to add an explicitMEMLIMIT parameter to the JCL that permits sufficient storage above the bar tobe acquired.

It is of especial importance to edit the //SYSTCPD DD statement to reference thecorrect TCP/IP configuration document for your system. If this is not donecorrectly, InfoSphere CDC will appear to start normally but any attempt to start asubscription to a remote target will fail due to communications errors. This will bedue to the fact that the correct DNS (Domain Name Server) is not being referenced,so any attempt to resolve a remote host name will fail. These communicationserrors are often misinterpreted as software defects in our product or TCP/IP whenthey are, in fact, simply the result of incorrect configuration.

Note: A single placeholder is provided for both the owner of DB2 resources(tables, plans, and so on) and the security identifier of the address space thatexecutes InfoSphere CDC. It is necessary that the same name be used both as theowner of InfoSphere CDC’s DB2 resources and as the InfoSphere CDC executionsecurity identifier. Failure to do so will cause InfoSphere CDC’s initialization tofail, an error message will be issued, and InfoSphere CDC will terminateprematurely.


Estimating InfoSphere CDC’s requirements for hiperspaces andauxiliary storage

During ongoing mirroring activity, an active InfoSphere CDC subscription uses theDB2 IFI to access the DB2 Log and obtain the changes for source tables that arebeing replicated. The subscription collects the changes into commit groups basedon the DB2 Unit of Recovery in which the changes occurred. When thesubscription obtains an indication of a COMMIT or a ROLLBACK from the DB2Log, it closes the associated commit group and disposes of it. If a ROLLBACK wasdetected, then the commit group is discarded. If a COMMIT was detected, then thecommit group is transmitted to the target server for application to the mappedtables.

Before a commit group is closed, the active subscription must hold the changes ina storage area (stage them) until their method of disposal has been determined. Atany point in time, the active subscription could be staging many commit groupsconcurrently. The staging resource used is a z/OS Hiperspace. Each activesubscription acquires a z/OS Hiperspace when it starts and releases it when itends. As changes for a commit group are being gathered, the subscription writesthem into the Hiperspace. As the commit groups are closed and disposed of, thesubscription removes the changes from the Hiperspace and makes the storageavailable for reuse for other commit groups.

During ongoing mirroring across multiple subscriptions, each active subscriptionwill have a number of incomplete commit groups, each with different amounts ofchanges staged. As a subscription continues to process DB2 Log data, the volumeof staged changes across all the commit groups will increase until a COMMIT orROLLBACK indication is received from the DB2 Log and a commit group isclosed. Then the changes contained in the commit group that has been closed willbe disposed of and the volume of staged data will decrease. This produces a “sawtooth” behavior for the volume of staged data across all active subscriptions, withthe volume rising gradually as data is staged, then dropping sharply when acommit group is disposed of. An estimate of the resource requirements to stagecommit groups will need to know the highest potential value the “points” of thesaw tooth can attain. The practical highest resource requirement may be lower thanthis potential value.

In order to estimate InfoSphere CDC’s requirement for storage resources, you mustbe familiar with the contents of the DB2 Log. Specifically, you must be familiarwith the profile of DB2 units or recovery that contains changes to tables to bemirrored by InfoSphere CDC. Such tables are called “sensitive” tables, and thecontaining DB2 units of recovery are called “sensitive” units of recovery. Youshould be able to identify all sensitive units of recovery based on knowledge of theapplications that update the sensitive tables. You should also be able to estimatethe maximum concurrency of each sensitive unit of recovery, and the maximumnumber of inserts, updates and deletes against sensitive tables that are contained inthe sensitive units of recovery. Once these estimates have been obtained, you cancalculate the size of the staging resources required.

See also:“Staging resources calculations” on page 76


Related concepts

“Expanded storage, hiperspaces, and storage above the bar” on page 3

Staging resources calculationsAssuming that M sensitive units of recovery have been identified, numbered 1 toM, and that N sensitive tables have been identified, numbered 1 to N, the valuesbeing used in the calculation are as follows:v URConcurrency_m: The maximum number of concurrently logged (overlapping)

copies of sensitive unit of recovery m (ranging from 1 to M).v INSERTs_m_n: The maximum number of inserts into sensitive table n (ranging

from 1 to N) that occur in unit of recovery m. This may be 0 for certaincombinations of m and n.

v DELETEs_m_n: The maximum number of deletes from sensitive table n thatoccur in unit of recovery m. This may be 0 for certain combinations of m and n.

For each value of m, calculate:

where 128 is the control information overhead, and UPDATEs_m_n is doubled toaccount for before and after images of the updated row.

Then calculate

TotalChangeVolume is the outside maximum amount of storage contained inhiperspaces and which potentially can be required of Auxiliary Storage to managethe staging of ongoing mirroring activity. As mentioned earlier, the practicalmaximum may be lower than TotalChangeVolume. Some of the factors that canproduce lower results are:v How well distributed (versus “clumped”) the commits and rollbacks are in the

DB2 Log.v How many changes are discarded by filtering criteria in the source environment.v How variable the estimates of INSERTs_m_n, UPDATEs_m_n, and

DELETEs_m_n are (these estimates are of maximum) from the average valuesfor specific m and n.

You should consider whether it is practical to reduce the value ofTotalChangeVolume in an attempt to reach a practical value. Monitoring resourcesused by InfoSphere CDC may be useful in this regard.

BUFTHRESHOLD keyword considerationsInfoSphere CDC provides the ability to supply a threshold value on the use of theDB2 OPx buffer that is employed to monitor the extension of the DB2 Log. Thissection explains how this threshold value can be specified and its associatedimpact on server performance.

During initialization, when InfoSphere CDC for z/OS internally issues the DB2 IFICOMMAND request that activates a DB2 Monitor Trace against a selected OPx


buffer, it supplies a threshold value to DB2. This threshold value specifies theminimum number of DB2 Log data bytes that DB2 should store in the OPx bufferbefore sending notification to InfoSphere CDC. DB2 will not inform InfoSphereCDC (using a z/OS POST service request) that there is DB2 Log data in the OPxbuffer to be processed until this minimum number of bytes is available in the OPxbuffer.

See also:“Specifying BUFTHRESHOLD”“BUFTHRESHOLD value considerations”

Specifying BUFTHRESHOLDInfoSphere CDC for z/OS supports the specification of a keyword, namedBUFTHRESHOLD, in the CHCDBMxx member of the configuration control dataset. The value of this keyword (a number between 1 and 99) is interpreted as thepercentage of the OPx buffer that is to be filled with DB2 Log data before DB2notifies InfoSphere CDC that there is additional data to be processed. Conversionfrom a percentage to a byte count is handled internally by InfoSphere CDC forz/OS.Related reference

“BUFTHRESHOLD” on page 51

BUFTHRESHOLD value considerationsThe following values should be considered:

“Historical considerations”“General considerations”“Latency considerations” on page 78“CPU resources considerations” on page 78“Conclusion” on page 79

Historical considerationsThe default setting of 1 (1%) for the BUFTHRESHOLD keyword was chosen fortwo reasons:v It is consistent with the value used prior to the implementation of the

BUFTHRESHOLD keyword, and so there will be no unexpected behavior if thekeyword is not specified.

v It is the best value to eliminate replication latency during mirroring. This is anissue when InfoSphere CDC is being evaluated, where small groups of changesare being made to tables on the source server, and the target server is beingexamined for equivalent changes.

After an evaluation of InfoSphere CDC for z/OS has been completed, a permanent,more suitable value for BUFTHRESHOLD should be chosen that is higher than 1%.

General considerationsReplication latency and CPU resource consumption are the key issues to beconsidered when determining a working value for the BUFTHRESHOLD keyword.

These two issues conflict with each other. Specifically, replication latency increasesand CPU resource consumption decreases as higher values for BUFTHRESHOLDare specified. CPU resource consumption referenced in this section is through the


task that monitors the extension of the DB2 Log, and represents only a smallportion of the overall CPU resources consumed by InfoSphere CDC for z/OSduring replication.

Latency considerationsWhen a higher value is specified for BUFTHRESHOLD, that percentage of the OPxbuffer must contain DB2 Log data before DB2 notifies InfoSphere CDC for z/OSthere is data to be processed. If the default for BUFSIZE used (the optimal value is132 KB), then a BUFTHRESHOLD value of 50% means that at least 66 KB of DB2Log data must have been written to the DB2 Log before InfoSphere CDC for z/OScan start to process the new data. This 66KB of data represents the DB2 Log datalatency. If the average rate at which the DB2 Log is being extended is known, thena data latency of 66 KB can be converted to a time latency value that can becalculated using the following formulas:

TimeLatency = DataLatency × DB2LogDataRate

or

DataLatency = TimeLatency DB2LogDataRate

To obtain an acceptable time latency value, use the desired time latency value inthe second formula and calculate an appropriate value for the data latency. Thenconvert the data latency value to a percentage of the value of the BUFSIZEkeyword, and use the calculated percentage as the value of the BUFTHRESHOLDkeyword. The DB2 Database Administrator should know or be able to determinethe DB2 Log average data rate. The maximum and minimum DB2 Log data rateswithin a cyclical period (for example, a day, a week, month-end peak) may also bea consideration when determining the desired value for BUFTHRESHOLD.

A smaller time latency value may be desired when real-time, continuous mirroringof data is being performed. If real-time, continuous mirroring is not being used,then time latency has no significance for determining the value of theBUFTHRESHOLD keyword.

CPU resources considerationsWhen a lower BUFTHRESHOLD value is specified, DB2 will notify InfoSphereCDC more frequently when there is DB2 Log data to be processed in the OPxbuffer. Each notification causes the DB2 Log monitor task (the DAL task) inInfoSphere CDC for z/OS to become active and perform the following steps:1. Establish a new DB2 Log reading position where it last detected no more DB2

Log data could be read.2. Acquire DB2 Log data on a one-record-at-a-time basis (a limitation of the DB2

IFI).3. Detect that there is no more new DB2 Log data to be read.4. Reestablish that it is ready for another asynchronous notification from DB2

when there is more data to be processed in the OPx buffer.

The second step absorbs the same resources no matter what percentage is used forthe value of BUFTHRESHOLD. However, the other steps represent a fixed cost ofprocessing a notification from DB2. This cost is expressed in expended CPUprocessing cycles. The lower the value of BUFTHRESHOLD, these CPU processingcycles will be expended more frequently, and the more the overall CPU utilizationwill increase. It would seem that setting the value of BUFTHRESHOLD to its


maximum value (99%) should achieve the largest reduction in the consumption ofCPU resources by the DAL task. Unfortunately, this is not the case.

When the DAL task is activated and starts to process the notification from DB2that the OPx buffer has DB2 Log data that can be processed, it effectively enters arace with DB2. The DAL task is trying to acquire and process all the DB2 Log datarecords that have been stored in the OPx buffer, and DB2 is storing new DB2 Logdata records into the OPx buffer as they are being created. Unless the DAL tasksucceeds in its attempt to clear the OPx buffer, DB2 will store the new DB2 Logdata records in the OPx buffer, until eventually a DB2 Log data record cannot fit.Only if the DAL task is able to win this race and perform the third step can it goback to an inactive state, and DB2 can start to refill the empty OPx buffer.

If the DAL task is unable to process the OPx buffer’s data faster than DB2continues to fill it, DB2 will soon detect the exhaustion of the OPx buffer and issuethe following message:

DSNW133I + DSNWVOPX - TRACE DATA LOST, <OPx> NOT ACCESSIBLE RC=08

The <OPx> text in the message indicates the actual OPx buffer to which the DB2Monitor Trace is being written. This message indicates that the OPx buffer hasoverflowed and should not be construed as a critical condition. InfoSphere CDCfor z/OS will still be able to obtain the DB2 Log data during its normal DB2 Logdata capture processing.

The DAL task is able to detect that an OPx buffer has overflowed. After detection,the DAL task repositions to the head of the DB2 Log with specific IFI requests, andthen resumes at the fourth step. This resynchronization process can use more CPUresources than the more acceptable situation of clearing the OPx buffer, therebydefeating the purpose of setting a high value for the BUFTHRESHOLD keyword.Additionally, the DSNW133I message can be a hindrance to the Operationspersonnel, or to an Automated Operations product that is sensitive to this message.Obviously, when DB2 is processing at peak periods, the rate of production of DB2Log data is at its highest, and the likelihood of the OPx buffer being filled is at itsgreatest.

ConclusionBased on the previous sections, the following approach is suggested for setting aworkable value to the BUFTHRESHOLD keyword:1. Determine the maximum and minimum DB2 Log data rates during prime

processing times within a cyclical period.2. If real-time continuous mirroring is being used, determine a replication latency

that is acceptable for the prime processing period.3. Use the minimum DB2 Log data rate and the acceptable level of replication

latency to calculate a maximum BUFTHRESHOLD value, using the formulaepresented earlier. If real-time continuous mirroring is not being used, choose ahigh initial value for the BUFTHRESHOLD keyword (for example, 80%).

4. Set the BUFTHRESHOLD keyword to a value, and then monitor for messageDSNW133I in the JES Log during peak processing periods to determine ifBUFTHRESHOLD is set too high.

5. If an unacceptable number of DSNW133I messages are detected, reduce thevalue of the BUFTHRESHOLD keyword by equal amounts (for example, indecrements of 5%). Then repeat the fourth step.


This approach should minimize CPU resource usage by the DAL task whileachieving the desired level of replication latency (if applicable).

Installing and running multiple InfoSphere CDC instancesThis section contains important considerations about managing multipleInfoSphere CDC instances on a single image of the mainframe or against a singleDB2 subsystem or Data Sharing Group.

InfoSphere CDC for z/OS is installed in two stages. The first stage consists ofrunning SMP/E jobs and the second stage consists of running DB2 jobs andconfiguring various operating system components like TCP/IP and SAF (SecurityAccess Facility).

The first stage creates the SMP/E Target Libraries, including two partitioned datasets containing executable code and DB2 DBRMs. Once created, these TargetLibraries can be used for as many instances of InfoSphere CDC for z/OS asdesired, as long as the number of instances created is within limitations enforcedby the operating system and DB2. For this reason, you only have to run theSMP/E jobs once, during the initial install, regardless of how many instances ofInfoSphere CDC are to be executed on the server.

The second stage creates required VSAM clusters (Product Administration Log andmetadata), creates the product metadata tables (in DB2), grants required authorityto InfoSphere CDC for z/OS in DB2, and creates the DB2 Plans from thedistributed DBRMs. This stage also includes the assignment of a unique identifierto the instance of InfoSphere CDC so that it can be recognized by the SAF. Thisunique identifier is also used to identify the owner of the metadata tables that arecreated in this stage. All these actions, which are part of the second stage, must beperformed once per instance of InfoSphere CDC that is executed, with some minorallowances.

An instance of InfoSphere CDC for z/OS can be identified by its metadata. Inother words, the metadata is the instance. To execute a new instance of InfoSphereCDC, new metadata must be created. Since the metadata tables have specificnames that cannot be changed, the owner of the metadata tables is used to qualifythe table names, making them unique.

It is not possible for multiple executing instances of InfoSphere CDC for z/OS toshare the same set of metadata tables, as this could lead to the same subscriptionexecuting concurrently in two separate instances. To prohibit this from occurring,InfoSphere CDC serializes access to the metadata it is using. If another instance ofInfoSphere CDC attempts to use the same metadata tables, it will be suspendeduntil the first instance has terminated its address space. This is true even if the twocontending instances are executing in different images of the operating system andattempting to access the single metadata instance within a DB2 Data SharingGroup.

Each instance of InfoSphere CDC for z/OS uses VSAM clusters to hold messages(the Product Administration Log or PAL) and some additional metadata. Sincethese VSAM clusters are written during InfoSphere CDC execution, it is importantthat they not be shared among multiple instances of InfoSphere CDC. As a result,the SHAREOPTIONS assigned to these VSAM clusters by the installation jobs thatdefined them do not permit the clusters to be shared. Do not change theseSHAREOPTIONS and attempt to use the same VSAM clusters across multipleinstances of InfoSphere CDC.


When the distributed DBRMs are used to create DB2 Plans, the owner of themetadata tables is supplied in the control statements that specify which DBRMs areused to create the DB2 Plans. Since InfoSphere CDC for z/OS never qualifies areference to a table with an owner identifier, the identifiers supplied in the controlstatements are used to determine which instance of the metadata is used by theDB2 Plans produced from the DBRMs. Since multiple distinct sets of metadata aresupported, the DB2 plans produced must also be distinct. This is achieved byusing a suffix in the DB2 Plan name (the “plan suffix”). A plan suffix is chosen andset during the second stage of the installation process. It is supplied to the job thatcreates the DB2 Plans from the DBRMs that are made available by the first stage ofthe installation process. For each instance of the metadata, a new suffix must beassigned, and only one suffix can be assigned to each instance of the metadata.This ties the plan suffix and the metadata together in a one-to-one relationship,and indirectly ties the plan suffix to the metadata owner and execution SAFidentifier assigned to the instance of InfoSphere CDC.

Reverting to InfoSphere CDC for z/OS version 5.4This section contains instructions for reverting to InfoSphere CDC for z/OS version5.4, after having upgraded from that release of the predecessor product toInfoSphere CDC version 6.2. Under normal conditions, there should never be areason to return to using version 5.4 in preference to version 6.2. However, if foroperational reasons a decision is made to reinstate use of InfoSphere CDC forz/OS version 5.4 after having used InfoSphere CDC version 6.2, then you willneed to take action to ensure that version 5.4 will be able to start replication at thecorrect point, and function correctly. Note that any use and configuration offeatures available for the first time in version 6.2, such as specifying character setconversion for source columns, will not be preserved after downgrading to version5.4 again.

Several features of version 6.2 are not backward compatible with version 5.4.However, there is a high degree of backward compatibility, making it possible toreimplement version 5.4 to continue replication activities. For instance, themetadata stored in the version 6.2VSAM cluster is unchanged from version 5.4,and the same file may be used interchangeably between the two products.

If you choose to revert to using version 5.4 , you must at least take action todowngrade the Metadata DB2 tables. In addition, if your site makes use ofInfoSphere CDC User Exits to provide additional functionality beyond thestandard abilities of InfoSphere CDC, then you will need to take steps to provideversion 5.4 with User Exits that provide equivalent functionality.

There are also optional steps you may take, depending on your operationalpreferences. Review the following sections to assist you in planning yourdowngrade process.

Once you have determined the actions you will be taking, you will need to stopreplication using version 6.2, and perform them all before starting version 5.4. Youshould plan for sufficient time and resources to complete the required necessaryactions, because replication will be unavailable while they are being performed.

See also:“Downgrading metadata DB2 tables” on page 82“Downgrading with user exits” on page 86“Downgrading and the product administration log” on page 87


“Downgrading configuration parameters” on page 87Related concepts

“Downgrading with user exits” on page 86

Downgrading metadata DB2 tablesYou will need to take action to provide Transformation Server for z/OS withusable metadata DB2 tables that contain the updated replication configuration fromInfoSphere CDC.

The metadata DB2 tables used by InfoSphere CDC are not compatible withTransformation Server for z/OS, and vice versa. For this reason, the upgrade toInfoSphere CDC renamed the existing Transformation Server for z/OS metadataDB2 tables, then copied the required contents to the new InfoSphere CDCmetadata DB2 tables. Once InfoSphere CDC is in use, it is possible that changes toreplication configuration have been made, such as source or target table mappings.It is almost certain that bookmark and status information will have been updatedby replication activities. Failing to migrate this updated information to theTransformation Server for z/OS metadata DB2 tables would result inTransformation Server for z/OS using outdated information, which would likelyresult in a loss of data integrity.

The process of providing current information in the Transformation Server forz/OS metadata DB2 tables consists of several actions that must be performed insequence. The stages involved can be summarized as follows: Firstly, all bookmarkinformation in the metadata DB2 tables must be confirmed, or set, as being in aformat that is compatible with the prior release; Secondly, the content of somecolumns is adjusted to account for the differences between the EBCDIC encodingused by Transformation Server for z/OS, and the UTF-8 encoding in InfoSphereCDC; Third, the InfoSphere CDC metadata DB2 tables are renamed so thatTransformation Server for z/OS metadata DB2 tables can be created with the samenames; Next, the Transformation Server for z/OS metadata DB2 tables, which wererenamed during the process of installing InfoSphere CDC, are renamed back totheir original names; Finally, the (now compatible) contents of the InfoSphere CDCmetadata DB2 tables are copied into the empty Transformation Server for z/OSmetadata DB2 tables.

A sample job has been provided in the SCHCCNTL data set to assist with theabove process. The provided job accomplishes all of the above with the exceptionof reformatting the bookmark information.

In order to ensure that the InfoSphere CDC metadata DB2 tables are in a consistentstate during the downgrade, all replication activities must be stopped throughoutthe metadata downgrade process. Although InfoSphere CDC will need to be active(running) to reformat bookmarks, if such reformatting is necessary, it is stronglyrecommended that you stop InfoSphere CDC in order to take a backup copy of thetablespace) containing the InfoSphere CDC metadata DB2 tables, as well as therenamed Transformation Server for z/OS metadata DB2 tables, before proceeding.

Replication activities must not be resumed in InfoSphere CDC at any time after thedowngrade process has begun. Once the downgrade process has been successfullycompleted, replication activities will resume in Transformation Server for z/OS atthe same point where they were stopped in InfoSphere CDC.

See also:“Reformatting saved bookmarks” on page 83


“Manually resetting the bookmark version” on page 84“Running the CHCDNGRD job” on page 85

Related concepts

“Completing the installation using the distributed sample jobs” on page 9“Reformatting saved bookmarks”“Running the CHCDNGRD job” on page 85

Reformatting saved bookmarksThe bookmark information stored in the metadata DB2 tables records the status ofdata replication so that the correct position to start reading the DB2 log can belocated. This information is updated as replication proceeds, so that changes to thesource tables are neither skipped nor replicated more than once. During themaintenance cycle of Transformation Server for z/OS version 5.4, the format of thebookmark information was changed from the older ″version 0″ format to thecurrent, and incompatible, ″version 1″ format. InfoSphere CDC is capable ofreading both formats, and any version 0 bookmark encountered will be silentlyupdated to the version 1 format during replication activities.

The Transformation Server for z/OS instance that you are reverting to must be ableto interpret the bookmark format that is stored in the metadata DB2 tablesassociated with the release. This means that it must either be capable of dealingwith both version 1 and version 0 format bookmarks, or alternatively, allbookmarks that will be copied to the metadata DB2 tables must be in version 0format.

The bookmark format change, and the capability of handling both formats, wasfirst added to Transformation Server for z/OS version 5.4 by PTF CHC0009. Thecapability may or may not be available in maintenance updates to other releases ofTransformation Server for z/OS.

Note: Contact IBM support to determine if maintenance is available that will allowthe version of Transformation Server for z/OS to which you are reverting toprocess ’Version 1’ format bookmarks. If such maintenance is available, then youshould obtain and apply it to your Transformation Server for z/OS target librariesbefore beginning the downgrade process. If you are reverting to TransformationServer for z/OS version 5.4, then ensure that PTF CHC0009 is installed on yoursystem and applied to the instance that will be used after downgrading.

If you are reverting to an instance of Transformation Server for z/OS that you canconfirm is able to process version 1 format bookmark information, then you do notneed to take any action to reformat your bookmarks, and you can proceed with theother steps in the downgrade process.

If you are unable to confirm that the Transformation Server for z/OS maintenancelevel you are reverting to is capable of processing version 1 format bookmarks, youwill need to use the SETLOGPOS command in InfoSphere CDC to reformat thebookmarks to version 0 format.

Even if you are reverting to a Transformation Server that is able to process version1 format bookmarks, you can still use the SETLOGPOS command to reformat thebookmarks to version 0 format. However, doing so is not recommended unless it isrequired. Resetting the bookmark format using the command depends on manuallyentering bookmark log positions for every configured subscription. This providesnumerous opportunities for errors that could result in data integrity beingcompromised.


Note: Do not reset the bookmark manually using the SETLOGPOS commandunless it is required because the maintenance level of Transformation Server forz/OS does not support version 1 bookmarks.CAUTION:Failure to ensure that the bookmark information is in a compatible format willresult in Transformation Server for z/OS being unable to process the bookmarks.This will prevent mirroring activity from starting, and may result in a loss ofdata integrity or force you to Refresh all your replicated tables.

Related concepts

“Running the CHCDNGRD job” on page 85Related reference

“SETLOGPOS—Set log position” on page 123

Manually resetting the bookmark versionThe InfoSphere CDC SETLOGPOS command can be used to set the log positionsrecorded in the bookmark for a subscription. Additionally, it has an optionalparameter that specifies the version of the bookmark format that will contain thespecified log position information.

The SETLOGPOS command cannot be used to reformat a bookmark without alsospecifying at least one log position. This means that when you enter theSETLOGPOS command, you will be replacing the log position information storedin the current (version 1) bookmark. In order to ensure data integrity for futurereplication, it is essential that the same log position be specified for the reformattedbookmark as was stored in the existing bookmark. The only way to be determinethe log positions stored in the current bookmark is to use the bookmark viewerutility. In InfoSphere CDC for z/OS, the bookmark information is made availableby using the Metadata Print Utility program.

The log position stored in the InfoSphere CDC metadata on the sourceenvironment must be synchronized with the bookmark information stored in themetadata of the target environment. This will be the case when replication for asubscription is successfully stopped in a controlled manner, without errors. Forevery subscription configured in InfoSphere CDC, you will need to record thethree log positions stored in the current bookmark. These log positions will beused when entering the SETLOGPOS command for the subscription.

CAUTION:You must ensure that all replication has ended without error after endingreplication before running the bookmark viewer utility. If this is not possiblefor any reason, then you will need to obtain the bookmark position informationfrom the target system metadata for the source that corresponds to the affectedsubscription. Consult the appropriate Transformation Server for z/OS orInfoSphere CDC documentation for the target system platform for informationon how to use the bookmark viewer to determine the position information.

The bookmark viewer will report three positions for each subscription: The LastCommitted Position; the Earliest Open Position; and the Last Applied Position. Youshould retain this output for reference purposes, and record each of these positionsfor later use in the SETLOGPOS command that will set the log positions in thereformatted bookmark.

If, as recommended earlier in these instructions, InfoSphere CDC has been shutdown, then it must be started to allow the SETLOGPOS command to be entered.


No replication activity should be started, as this will possibly change the bookmarkposition information recorded from the bookmark viewer reports produced earlier.

For each subscription, you must issue the SETLOGPOS command to InfoSphereCDC, specifying the three positions reported by the bookmark viewer for thatsubscription, and also specifying the keyword VERSION=0. After each command isissued, examine the JESMSGLG for message(s) indicating that the SETLOGPOScommand was successfully processed.

Tip:

v You can enter all the required commands in to a command member of theconfiguration dataset, and have InfoSphere CDC issue the commands for youinternally. This may make it easier to enter and verify the entry of subscriptionnames and bookmark positions before actually issuing the commands to changethe bookmark positions and formats.

v After you have reset the bookmark for every target configured in InfoSphereCDC, you should run the bookmark viewer again, and compare the positionreported in the reformatted bookmark with that recorded from the originalbookmark.

Once the bookmark has been set for all targets in InfoSphere CDC, you shouldstop InfoSphere CDC and continue the downgrade process by running theCHCDNGRD job.Related concepts

“Bookmark viewer” on page 147Related reference

“SETLOGPOS—Set log position” on page 123“COMMAND—Process InfoSphere CDC commands” on page 116

Running the CHCDNGRD jobThe sample JCL job assumes that the original, renamed, Transformation Server forz/OS version 5.4 metadata DB2 tables still exist. Modify the CHCDNGRD job,according to the comment block in its JCL. Run the job, which will use theCHCV6MIG program to prepare the contents of the InfoSphere CDC metadata byconverting the encrypted contents of specific columns to be compatible withTransformation Server for z/OS. This downgrade must be performed on theInfoSphere CDC metadata before the contents are copied to the TransformationServer for z/OS metadata, because the utility requires access to columns that donot exist in the Transformation Server for z/OS metadata.

CAUTION:The bookmark information stored in the InfoSphere CDC metadata tables mustbe in a format compatible with the release being downgraded to before runningthis job.

The downgrade step of the CHCGNGRD job will issue messages indicating thestatus of the downgrade process, and will also set a condition code that is used tocontrol the execution of subsequent steps in the job. If the downgrade step issuccessful, as indicated by completion with a condition code of zero (0) or four (4),then the job will continue the downgrade process by using the DSNTIAD program(distributed with DB2) to rename the InfoSphere CDC metadata DB2 tables tonames that are not used by either product. It then renames the TransformationServer for z/OS metadata tables that were originally renamed during the upgradeinstall back to the names required by Transformation Server for z/OS version 5.4.


Finally, it deletes the contents of the Transformation Server for z/OS metadata DB2tables, and copies the required data into them from the newly renamed InfoSphereCDC metadata DB2 tables.

Note: If the original Transformation Server for z/OS tables no longer exist, thenyou can create empty metadata DB2 tables by using the CHCCRMTD job availablein the SCHCCNTL data set created when Transformation Server for z/OS version5.4 was installed. Doing so will require that the InfoSphere CDC metadata tablesbe renamed first, because the metadata DB2 tables in Transformation Server forz/OS and InfoSphere CDC have the same names. Refer to the TransformationServer for z/OS version 5.4 installation documentation for instructions on runningthis job.Related concepts

“Reformatting saved bookmarks” on page 83

Downgrading with user exitsIf your site makes use of InfoSphere CDC User Exits to provide additionalfunctionality beyond the standard abilities of InfoSphere CDC, then you may needto rewrite these exits to use the incompatible Transformation Server for z/OS userexit data structures. If you wrote your exits for the first time for InfoSphere CDC,then you will have to at least recompile the exits using the header files that mapthe user exit parameters that were provided for Transformation Server for z/OS.Before recompiling, you will also need to assess whether the logic in your userexits will perform correctly with the back-level interface. The most likely reasonthat your exit logic would need modification would be the fact that most characteridentifiers passed to the user exit are provided to InfoSphere CDC user exitsencoded in UTF-8, while for Transformation Server for z/OS user exits they areencoded in EBCDIC.

If, as is more likely if you are in the situation of reverting to Transformation Serverfor z/OS from InfoSphere CDC, you have user exits that were originally writtenfor Transformation Server for z/OS, and the original user exit object modules arestill available, then you will only need to link the user exits again according to therequirements of Transformation Server for z/OS. Refer to the TransformationServer for z/OS version 5.4 documentation for these requirements. If the originalobject modules are not available, then you will need to recompile the user exits,after undoing any changes to the source code that were made to make the userexits usable with the InfoSphere CDC interface.

The most likely scenario, at least in the early stages of implementing InfoSphereCDC, is that any user exits you had in place for Transformation Server for z/OSwere implemented in InfoSphere CDC using the backward compatible user exitinterface. If this is the case, then you can restore the user exits to being usable byTransformation Server for z/OS by simply link editing them again using theinstructions provided in the Transformation Server for z/OS version 5.4documentation. Both Transformation Server for z/OS and InfoSphere CDC providea module called CHCEXIT that is to be link-edited with user exits. The CHCTEXITprovided with Transformation Server for z/OS must be link edited with your userexit in order to be usable with Transformation Server for z/OS.


Related concepts

“Linking Transformation Server user exits for InfoSphere CDC” on page 23

Downgrading and the product administration logThe Product Administration Log (PAL) VSAM cluster contains historical eventsassociated with the operation of the product. The format of the PAL cluster iscompatible between InfoSphere CDC and Transformation Server for z/OS, but thecontents are not. The PAL records the information in logged messages, retrievableby source or target name. The name used to retrieve the contents is encoded inEBCDIC by Transformation Server for z/OS, and in UTF-8 by InfoSphere CDC.This means that, while both products can log messages into the same cluster, oneproduct will not be able to retrieve messages logged by the other.

When downgrading to Transformation Server for z/OS, you may either create anew PAL VSAM cluster for Transformation Server for z/OS, or reuse theInfoSphere CDC PAL VSAM cluster. In the first case, most messages logged byInfoSphere CDC will be unavailable to from the Management Console, while in thesecond case, none of the messages will be available.

You should use the same VSAM cluster for Transformation Server for z/OS as wasin use by InfoSphere CDC. If you choose to use a different VSAM cluster, use theCHCDFPAL sample JCL from the Transformation Server for z/OS SCHCCTNLdataset to create one with a different name that the cluster used by InfoSphereCDC, and edit the Transformation Server for z/OS CHCPROC JCL to refer to thenew name.

Downgrading configuration parametersYou are not required to take any action to downgrade configuration parameters.The only configuration parameter that has been changed in InfoSphere CDC is theaddition of the new IANAMAP specification in the CHCUCSxx configurationdataset member. If Transformation Server for z/OS encounters this specificationwhen it starts running, it will report each occurrence as an unrecognized parametererror. However, it will ignore the unrecognized parameter and will continue toinitialize successfully. You may choose to remove or comment out the IANAMAPspecifications from the Transformation Server for z/OS CHCUCSxx configurationmember to prevent the issuing of message CHC9676W when TransformationServer for z/OS starts.Related reference




Upgrading from DB2 version 7.1 to DB2 version 8.1

Note: Before upgrading DB2 version 7.1 to DB2 version 8.1, you must firstsuccessfully upgrade from InfoSphere CDC version 5.4 to version 6.2.

This section contains important considerations when upgrading the DB2 instancethat InfoSphere CDC is connected to from DB2 version 7.1 to DB2 version 8.1.InfoSphere CDC functions properly on both version of DB2, but there are featuresand capabilities of DB version 8.1 in full-function mode that require changes to theInfoSphere CDC metadata.

DB2 provides a staged upgrade process from version 7.1 to version 8.1. Refer tothe appropriate DB2 documentation for details, but put briefly, DB2 version 8.1 canbe run in three modes: Compatibility Mode, Enabling New Function Mode, andFull Function Mode. As long as DB2 version 8.1 is running in Compatibility Mode,or Enabling New Function Mode, you do not need to make any changes to yourInfoSphere CDC installation. However, once you have upgraded DB2 version 8.1 toFull Function Mode, InfoSphere CDC will be unable to process the longeridentifiers available in full function mode, and will not be able to process SQLidentifiers that contain Unicode characters that cannot be translated to the DB2single-byte EBCDIC code page. In order to process all valid SQL identifiers, theInfoSphere CDC metadata DB2 tables need to be modified.

One of the differences between the InfoSphere CDC metadata DB2 table definitionsfrom the DB2 version 7.1 compatible format and the DB2 version 8.1 compatibleformat is that the DB2 version 8.1 compatible metadata tables are defined in aUnicode tablespace, while the DB2 version 7.1 compatible metadata DB2 tables arecreated in an EBCDIC tablespace. Since it is not possible to alter a tablespace tochange the encoding scheme, it is necessary to recreate the metadata DB2 tables ina new tablespace. The new metadata DB2 tables will be created with columnlengths sufficient to accommodate the longest SQL identifiers supported by DB2version 8.1. Sample jobs are provided in the distribution datasets to accomplishthis task.

Your InfoSphere CDC metadata contains replication configuration information thatmay represent a significant investment of time and effort. Therefore, it should bepreserved and copied to the new Unicode metadata DB2 tables. The distributedsample jobs accomplish the upgrade process in three phases, using three jobswhich must be run in order. InfoSphere CDC must be stopped (shut down) duringthe entire metadata upgrade process. Before you begin the metadata upgradeprocess, you should ensure that you have a current and complete backup of yourmetadata DB2 tables using your standard administrative procedures.

In this section, you will learn:“Running the CHCPGRN6 job” on page 90“Running the CHCCRMTD job” on page 90“Running the CHCPGCP6 job” on page 90“Running the CHCBNDPL job” on page 90


Running the CHCPGRN6 jobJCL to rename the existing EBCDIC InfoSphere CDC metadata DB2 tables. Modifythe CHCGPRN6 job according to the comment block in its JCL and run the job.

Running the CHCCRMTD jobJCL to create DB2 tables that will contain the part of InfoSphere CDC for z/OSmetadata that resides in DB2 tables.

The last step in the CHCCRMTD job will create indexes over some of the DB2System Catalog tables. For this upgrade process, the indexes should already existbecause they will have been created during the initial install of InfoSphere CDC.Delete the BLDINDEX, step from the JCL before running the job.Related concepts

“Running the CHCCRMTD job” on page 17

Running the CHCPGCP6 jobJCL to copy the InfoSphere CDC contents from the renamed EBDIC DB2 metadatatables to the newly created Unicode InfoSphere CDC metadata DB2 tables.

Modify the CHCGPRN6 job according to the comment block in its JCL and run thejob. This job will copy the contents of the DB2 version 7.1 compatible formatmetadata tables, which were renamed when the CHCPGRN6 job was run, into thenewly created DB2 version 8.1 compatible metadata DB2 tables.

Running the CHCBNDPL jobJCL to bind the DB2 Plans that will be used by InfoSphere CDC to access the DB2Log, metadata tables, and application data tables that are to be replicated.

The InfoSphere CDC plans must be bound again to properly access the redefinedmetadata DB2 tables. Refer to the instructions for running the CHCBNDPL job foran initial install.

Once the CHCBNDPL job has been run to rebind the InfoSphere CDC DB2 plans,you may restart InfoSphere CDC and resume normal operations.

There is no sample JCL provided to reverse the changes to the metadata DB2tables, as is no reason that such an action will be needed. Once DB2 version 8.1has been converted to Full Function mode, there is no process to revert to lesscapable functionality. Similarly, once the metadata has been upgraded to supportFull Function mode, there is no need to revert to the prior metadata DB2 tabledefinitions. Doing so would only revive the limitations on character sets andlengths of SQL identifiers, to no advantage.Related concepts

“Running the CHCBNDPL job” on page 18


InfoSphere CDC commands

This section describes the operator console commands that are supported by anyinstance of InfoSphere CDC that has been installed on a z/OS system. It assumesthat you are familiar with the z/OS environment.

This section is intended for console operators and should be consulted after youhave installed InfoSphere CDC for z/OS on your z/OS system and ManagementConsole on your workstation.

Note: It is not possible to enter the full set of Unicode characters using the z/OSconsole command interface. This means that it may not be possible to completelyspecify a name that includes non-English characters in a command. In some cases,such as the SETMIRST command, you can use the predefined value of ALL, or usewildcards to cause the non-English names to be processed by the command.However, it may not always be possible to accomplish what you want usingconsole commands. When this is the case, you must use Management Console.

In this section, you will learn:“System configuration”“Communication commands” on page 92“Replication commands” on page 102“Table mapping commands” on page 110“Other Commands” on page 116

System configurationInfoSphere CDC for z/OS is installed on a z/OS source or target system. On az/OS system, commands are submitted from the operator console, and appropriatemessages are returned by InfoSphere CDC to the operator console. This sectiondescribes the commands that can be issued from the console in source and targetenvironments.

Management Console allows you to specify the tables to replicate and which targetservers will receive the replicated data. In addition, you can identify the tables onthe target server that will receive replicated data and the type of datatransformations that you want to apply to the data. You can also use ManagementConsole to monitor data replication activities. Although it is not shown in thefigure below, Management Console can be installed on multiple workstations, andeach session can interact with a z/OS system at the same time.

To initialize the replication environment on a z/OS system, the START commandmust be issued through the operator console. This initialization step can also beachieved by submitting a specific JCL batch job through the console or from a userterminal (to submit the job from a user terminal, the user that is logged on to theserver must have been granted sufficient privileges).

Based on the tables and subscriptions that you have identified in ManagementConsole, data residing on the source server can be replicated to different target


servers. Appropriate InfoSphere CDC software must be installed on each of thesetarget servers so that replicated data can be directed to target tables and datatransformations can be performed.

The figure below illustrates the connections between different systems in areplication configuration, and the flow of data from source to target environments.

Related concepts

“IBM InfoSphere Change Data Capture installation or upgrade” on page 1

Communication commandsInfoSphere CDC has several commands that control communication.

See also:“SHUTDOWN—Stop InfoSphere CDC address space”“START—Start InfoSphere CDC address space” on page 94“STOP—Stop InfoSphere CDC address space” on page 97“STRTSCOM—Initialize communications environment” on page 98“STRTSDBM—Initialize database management system” on page 99

SHUTDOWN—Stop InfoSphere CDC address space

This command stops an InfoSphere CDC address space on your z/OS system. Ifyou have created more than one address space using the START command, theidentifier you specified to create the address space must be referenced.

Tip: From the operator console, you can issue the z/OS command DISPLAYACTIVE, LIST to list identifiers associated with all active address spaces.

Syntax


Settings Description

Stopping Method (CNTRLD orIMMED)

Indicates the method that you want to use to stopthe InfoSphere CDC address space.

Depending on your working environment, you maywant to stop the address space immediately or afterInfoSphere CDC has completely refreshed thecurrent table or mirrored all updates prior to adefined point in the log.

One of the following predefined values can bespecified:

v CNTRLD—Stops the address space afterInfoSphere CDC has completely refreshed thecurrent table or mirrored all updates prior to adefined point in the log. A controlled stop doesnot force existing Management Console sessionsto terminate.

v IMMED—Stops the address space immediatelyafter the SHUTDOWN command is issued. Datarefresh and mirroring stops immediately. Thismeans that a refresh may be stopped before thecurrent table is completely refreshed, and themirroring of table changes may stop before adefined point in the log. In addition, animmediate stop disconnects all existingManagement Console sessions that are interactingwith the address space and prevents futuresessions from connecting to the address space.

Default Setting: CNTRLD

The preferred setting is CNTRLD, since it ensurescompletion of a data refresh and stops mirroring atdefined points. It also allows existing ManagementConsole sessions to continue with other work. UseIMMED if you need to stop the address space asquickly as possible.Note: The STOP command is equivalent to theSHUTDOWN command when IMMED is specified.However, any subsequent attempt to issue anothercommand (for example, the DSPACT command)referring to the same InfoSphere CDC address spacethat was stopped using the SHUTDOWN commandmay or may not be accepted.

Examples Description

MODIFY TSAS,SHUTDOWN Stops the InfoSphere CDC address spacethat was labeled by the identifier TSASwhen it was created by the STARTcommand.

Stops the InfoSphere CDC address space ina controlled manner (the default setting forthe stopping method is CNTRLD). As aresult, it ensures completion of a datarefresh and stops mirroring at definedpoints. In addition, existing ManagementConsole sessions are maintained.

InfoSphere CDC commands 93


F TSAS,SHUTDOWN=IMMED Stops the InfoSphere CDC address spacethat was labeled by the identifier TSASwhen it was created by the STARTcommand.

Stops the InfoSphere CDC address spaceimmediately. As a result, data refresh andmirroring processes may be stopped prior toreaching defined points, and all existingManagement Console sessions aredisconnected from the address space.

START—Start InfoSphere CDC address space

This command creates an InfoSphere CDC address space on your z/OS system.The command identifier is used to distinguish different address spaces that havebeen created.

The START command allows you to initialize the communication and DBMSenvironments in the InfoSphere CDC address space. If you decide not to initializethese environments using this command, you must issue the STRTSCOM andSTRTSDBM commands to initialize the communications and DBMS environmentsrespectively.

Instead of issuing the START command, you can submit a batch job (if you havesufficient authorization) to create an InfoSphere CDC address space. Sample batchjobs that can be customized to your working environment are provided withInfoSphere CDC. However, the preferred approach is to create address spaces byusing the START command.

Note: The three consecutive commas shown in the syntax diagram must beincluded in START commands issued from the operator console.

Syntax



CommunicationInitialization (NOCOMMor COMM)

Indicates whether you want to initialize the communicationsenvironment using the START command.

One of the following predefined values can be specified:

v NOCOMM—Indicates that you do not want to initializethe communications environment when the InfoSphereCDC address space is initializing.

v COMM—Indicates that you want to initialize thecommunications environment when the InfoSphere CDCaddress space is initializing.

Default Setting: NOCOMM

DBMS Initialization(NODBMS or DBMS)

Indicates whether you want to initialize the DBMSenvironment using the START command.


v NODBMS—Indicates that you do not want to initialize theDBMS environment when the InfoSphere CDC addressspace is initializing.

v DBMS—Indicates that you want to initialize the DBMSenvironment when the InfoSphere CDC address space isinitializing.

Default Setting: NODBMS



InfoSphere CDC TaskStartup (COLDSTART)

Indicates which InfoSphere CDC tasks are to perform a coldstart.

This setting can apply to the DLP task and the DLR task.

If the DLP task performs a cold start, it discards anyinformation about the DB2 instance to which InfoSphereCDC was attached in the previous invocation of theInfoSphere CDC address space. Without a cold start, theDLP task tries to rely on stored information describing theDB2 instance used by the previous InfoSphere CDC addressspace invocation.

If the DLR task performs a cold start, the DB2 Log Cache iscleared and rebuilt, starting from the current head of theDB2 Log. Without a cold start, the DLR task leaves theexisting DB2 Log Cache intact and continues to cache DB2Log records from the point in the DB2 log where it left off inthe previous InfoSphere CDC address space invocation.


v NONE—None of the eligible tasks performs a cold start.

v ALL—Cold starts are performed by all of the DLP andDLR tasks.

v DLP—Only the DLP task performs a cold start.

v DLR—Only the DLR task performs a cold start.

Default Setting: NONE

CAUTION:Cold starting may take more time to complete as comparedto not cold starting at all.Note: This setting can still be specified when NODBMS isspecified or defaulted. This setting is established andreferenced when the corresponding setting in theSTRTSDBM command is inherited.


START CHCPROC.TSAS,,,(NOCOMM,DBMS,) Creates an InfoSphere CDC addressspace that is labeled by the identifierTSAS.

Initializes the DBMS environment,but does not initialize thecommunications environment.

S CHCPROC.TSAS,,,(COMM,DBMS,COLDSTART=DLR) Creates an InfoSphere CDC addressspace that is labeled by the identifierTSAS.

Initializes both the communicationand DBMS environments.

The InfoSphere CDC DLR taskperforms a cold start.



S CHCPROC.TSAS,,,(COMM,,COLDSTART=ALL) Creates an InfoSphere CDC addressspace that is labeled by the identifierTSAS.

Initializes the communicationsenvironment, but does not initializethe DBMS environment.

Even though the InfoSphere CDCwill not perform a cold start whenprocessing this command (see noteunder Task Startup), theCOLDSTART setting of ALL isestablished and referenced when thecorresponding setting in theSTRTSDBM command is inherited.

Note: The syntactical requirements for the z/OS MODIFY command andexplanations of the <procname> and <identifier> elements can be found in theIBM console commands manual that contains information about operatorcommands.

This command can be issued on source environments and target environments.Related reference

“STOP—Stop InfoSphere CDC address space”

STOP—Stop InfoSphere CDC address space

This command stops an InfoSphere CDC address space on your z/OS system.

If you have created more than one address space using the START command, theidentifier you specified to create the address space must be referenced.

The STOP command immediately stops the InfoSphere CDC address space. It isequivalent to issuing the SHUTDOWN command and specifying IMMED as theclosing method. Any subsequent attempt to issue another command referring tothe same InfoSphere CDC address space that was stopped using the STOPcommand results in an error being reported.

Tip: From the operator console, you can issue the z/OS command DISPLAYACTIVE, LIST to list identifiers associated with all active address spaces.

Syntax


Settings: None.


STOP TSAS Stops the InfoSphere CDC address spacethat was labeled by the identifier TSASwhen it was created using the STARTcommand.

P TSAS Stops the InfoSphere CDC address spacethat was labeled by the identifier TSASwhen it was created using the STARTcommand.



“START—Start InfoSphere CDC address space” on page 94

STRTSCOM—Initialize communications environment

This command initializes the communications environment in the InfoSphere CDCaddress space.

This command must be issued before data can be replicated to target server.

If you previously issued the START command and specified COMM, thiscommand should only be used to initialize the communications environment againafter it has been stopped.

If you specified NOCOMM with the START command, this command is requiredto initialize the communications environment for the first time. If you have createdmore than one address space using the START command, the identifier youspecified to create the address space must be referenced to initialize a specificcommunications environment.

Tip: From the operator console, issue the z/OS command DISPLAY ACTIVE, LISTto list identifiers associated with all active address spaces.

Syntax


SettingDescription Header

Communications Environment (ALL orTCP/IP)

Indicates the type of communicationsenvironment that you want to initialize.

One of the following predefined values canbe specified:

v ALL—Refers to all communicationsinterfaces supported by the product.

v TCP/IP—A TCP/IP communicationsenvironment is initialized.

Default Setting: ALLNote: In this release, specifying ALL isequivalent to specifying TCP/IP.


This command can be issued on source environments and target environments.

STRTSDBM—Initialize database management system

This command initializes the DBMS environment in the InfoSphere CDC addressspace.

The DBMS environment controls access to the databases that contain the data youintend to replicate.

If you previously issued the START command and specified DBMS, you do nothave to issue this command. If you specified NODBMS with the START command,this command is required to initialize the DBMS environment.

Syntax



DBMS Environment (ALL orDB2)

Indicates the type of DBMS environment that youwant to initialize.

The type of environment is based on the database thatcontains the data you want to replicate.


v ALL—Initializes a DBMS environment to handledata replication from all types of databases that aresupported by InfoSphere CDC.

v DB2—Initializes a DBMS environment that supportsdata replication from DB2 databases.

Default Setting: ALL

In this release, specifying ALL is equivalent tospecifying DB2 (ALL refers to all database typessupported by the product).



Task Startup (COLDSTART) Indicates which InfoSphere CDC tasks are to performa cold start.

This setting can apply to the DLP task, and the DLRtask.

If the DLP task performs a cold start, it discards anyinformation about the DB2 instance to whichInfoSphere CDC was attached in the previousinvocation of the InfoSphere CDC address space.Without a cold start, the DLP task tries to rely onstored information describing the DB2 instance usedby the previous InfoSphere CDC address spaceinvocation.

If the DLR task performs a cold start, the DB2 LogCache is cleared and rebuilt, starting from the currenthead of the DB2 Log. Without a cold start, the DLRtask leaves the existing DB2 Log Cache intact andcontinues to cache DB2 Log records from the point inthe DB2 log where it left off in the previous InfoSphereCDC address space invocation.


v INHERIT—Inherits the corresponding COLDSTARTsetting specified by the START command or JCLEXEC statement.

v NONE—Existing profiles from the previousInfoSphere CDC address space invocation arereferenced. Neither the DLP nor the DLR taskperforms a cold start.

v ALL—Cold starts are performed by all tasks.

v DLP—Only the DLP task performs a cold start.

v DLR—Only the DLR task performs a cold start.

Default Setting: INHERITNote: Cold starting may take more time to completeas compared to not cold starting at all.


MODIFY TSAS,STRTSDBM Initializes a DBMS environment thatsupports data replication from DB2databases (the default setting for the DBMSenvironment is ALL).

The COLDSTART setting specified by theSTART command or JCL EXEC statementdetermines whether or not the InfoSphereCDC DLP or DLR tasks perform a cold start.

F TSAS,STRTSDBM=DB2,COLDSTART=NONE Initializes a DBMS environment thatsupports data replication from DB2databases.

The existing Log Profile and Log Data Cachefrom the previous address space invocationare used.



F TSAS,STRTSDBM=DB2,COLDSTART=DLR Initializes a DBMS environment thatsupports data replication from DB2databases.

The InfoSphere CDC DLR task performs acold start, causing the Log Data Cachecontrol information to be reset, and log datacaching to resume from the extension pointof the DB2 Log.



Replication commandsInfoSphere CDC has several commands that control replication.

See also:“STRTSMIR—Start mirroring”“ENDTSMIR—End mirroring” on page 104“STRTSRSH—Start refresh” on page 106“ENDTSRSH—End refresh” on page 108

STRTSMIR—Start mirroring

This command starts mirroring updates applied to source tables that have beenselected to replicate data to the specified subscription. Each update can bemirrored after it is applied (continuous mirroring) or accumulated updates can bemirrored at a later time (net change mirroring).

Note: Mirroring can be started and stopped from the operator console or inManagement Console. Therefore, it is important to realize that mirroring to thespecified subscriptions can be started at the operator console and then stopped inManagement Console. InfoSphere CDC handles conflicting commands that areissued from the operator console and Management Console.

Syntax



Subscription (SUBSCR) Identifies the subscriptions to receivemirrored data from selected source tables.

One or more subscriptions can be specified.In addition, you can specify the wildcardcharacter (*) to reference multiplesubscriptions having names that start withthe same set of characters. An example isprovided below to illustrate how wildcardsare used.

The following predefined value can bespecified:

v ALL—Specifies all subscriptions that aredefined in the InfoSphere CDC addressspace.

Mirroring Method (CONTINUOUS orPERIODIC)

Indicates the method that you want to useto mirror data to target environments. Oneof the following predefined values can bespecified:

v CONTINUOUS—Specifies continuousmirroring to target environments.

v PERIODIC—Specifies net changemirroring to target environments.

Default Setting: CONTINUOUS


MODIFY TSAS,STRTSMIR,SUBSCR=ALL Starts mirroring source table updates to allsubscriptions defined in the InfoSphere CDCaddress space. Since the default setting forthe mirroring method is CONTINUOUS,updates are mirrored continuously to alldefined subscriptions.

MODIFY TSAS,STRTSMIR,SUBSCR=(SUB1),PERIODIC

Starts mirroring source table updates totarget SUB1. Accumulated updates aremirrored to target SUB1 at a later time.



F TSAS,STRTSMIR,SUBSCR=(SUB1,SUB2*),CONTINUOUS

Starts mirroring source table updates tosubscription SUB1 and all subscriptionshaving a name that starts with SUB2 (forinstance, SUB2A, SUB2B, and SUB2C).Updates are mirrored continuously to thespecified subscriptions.


This command can be issued on source environments.Related reference

“ENDTSMIR—End mirroring”

ENDTSMIR—End mirroring

This command stops data mirroring from selected source tables to the specifiedsubscriptions. Mirroring can be stopped immediately or in a controlled manner.Use this command when it is necessary to stop mirroring before starting systemmaintenance work or prior to scheduled downtimes.

Note: Mirroring can be started and stopped from the operator console or inManagement Console. Therefore, it is important to realize that mirroring to thespecified subscriptions can be started in Management Console and stopped at theoperator console. InfoSphere CDC handles conflicting commands that are issuedfrom the operator console and Management Console.

Syntax



Subscription (SUBSCR) Identifies the subscriptions for whichmirroring is stopped.




Stopping Method (CNTRLD or IMMED) Indicates the method that you want to useto stop mirroring.


v CNTRLD—Stops mirroring in acontrolled manner. This means thatInfoSphere CDC completes all updatesprior to a defined point in the log andthen stops any further mirroring.

v IMMED—Stops mirroring immediately.This means that the mirroring of tableupdates may stop prior to a defined pointin the log.


The preferred method is to stop mirroring ina controlled manner (CNTRLD). Stopmirroring immediately (IMMED) if it cannotbe stopped in a controlled manner.



MODIFY TSAS,ENDTSMIR,SUBSCR=ALL Stops mirroring source table updates to allsubscriptions defined in the InfoSphere CDCaddress space.

Since the default setting for the stoppingmethod is CNTRLD, mirroring is stoppedafter all current source table updates havebeen applied.

MODIFY TSAS,ENDTSMIR,SUBSCR=(SUB1),IMMED

Stops mirroring source table updates tosubscription SUB1.

Mirroring is stopped immediately, withoutwaiting for any current work to complete.

F TSAS,ENDTSMIR,SUBSCR=(SUB1,SUB2*),CNTRLD

Stops mirroring source table updates tosubscription SUB1 and all subscriptionshaving a name that starts with SUB2 (forinstance, SUB2A, SUB2B, and SUB2C).

Mirroring is stopped after all current sourcetable updates have been applied.



“STRTSMIR—Start mirroring” on page 102

STRTSRSH—Start refresh

This command starts refreshing source tables that have been selected forreplication in a table mapping.

Use this command to copy entire source tables to target environments. Thisensures that source and target tables are synchronized before mirroring is started.

Note: A data refresh can be started and stopped from the operator console or inManagement Console. Therefore, it is important to realize that refreshing data tothe specified subscriptions can be started at the operator console and then stoppedin Management Console. InfoSphere CDC handles conflicting commands that areissued from the operator console and Management Console.

Syntax



Subscription (SUBSCR) Identifies the subscription to receive refreshed data fromselected source tables.

One or more subscriptions can be specified. In addition,you can specify the wildcard character (*) to referencemultiple subscriptions having names that start with thesame set of characters. An example is provided below toillustrate how wildcards are used.

The following predefined value can be specified:

v ALL—Specifies all subscriptions that are defined in theInfoSphere CDC address space.

Tables (TABLES) Indicates whether to refresh all selected source tables tothe specified subscriptions or only those selected sourcetables that have a refresh status of REFRESH.

Refresh statuses for source tables that are refreshed totarget environments are set by the SETRSHSTS command.


v FLAG—Only selected source tables that have a refreshstatus of REFRESH are refreshed to the specifiedtargets.

v ALL—All selected source tables are refreshed to thespecified subscriptions regardless of the refresh state ofthe source tables.

Default Setting: FLAG


MODIFYTSAS,STRTSRSH,SUBSCR=ALL

Starts refreshing selected source tables to all subscriptionsdefined in the InfoSphere CDC address space.

Since the default setting for the refresh status is FLAG,only selected source tables that have a status ofREFRESH are refreshed to all defined targets.



MODIFY TSAS,STRTSRSH,SUBSCR=(SUB4),TABLES=FLAG

Starts refreshing selected source tables to target SUB4.

Only selected source tables that have a refresh status ofREFRESH are refreshed to target SUB4.

F TSAS,STRTSRSH,SUBSCR=(SUB1,SUB2*),TABLES=ALL

Starts refreshing selected source tables to subscriptionSUB1 and all subscriptions having a name that startswith SUB2 (for instance, SUB2A, SUB2B, and SUB2C).

All selected source tables are refreshed to the specifiedsubscriptions regardless of the refresh state of the sourcetables.



“ENDTSRSH—End refresh”

ENDTSRSH—End refresh

This command stops data from being refreshed to the specified targets. A datarefresh can be stopped immediately or in a controlled manner. Since a refresh endsafter the last row has been replicated, you may want to allow a refresh operationto complete instead of stopping it by using this command. Stopping a refresh maybe required if the amount of data to be refreshed and the amount of time it wouldtake to complete the refresh are significant.

Note: A data refresh can be started and stopped from the operator console or inManagement Console. Therefore, it is important to realize that refreshing data tothe specified targets can be started in Management Console and then stopped atthe operator console. InfoSphere CDC handles conflicting commands that areissued from the operator console and Management Console.


Syntax


Subscription (SUBSCR) Identifies the targets for which data refreshis stopped.

One or more targets can be specified. Inaddition, you can specify the wildcardcharacter (*) to reference multiple targetshaving names that start with the same set ofcharacters. An example is provided below toillustrate how wildcards are used.


v ALL—Specifies all targets that are definedin the InfoSphere CDC address space.

Stopping Method (CNTRLD or IMMED) Indicates the method that you want to useto stop refreshing data.


v CNTRLD—Stops refreshing data in acontrolled manner. This means thatInfoSphere CDC completes refreshing thecurrent source table and then stops anyfurther replication.

v IMMED—Immediately stops a datarefresh. This means that InfoSphere CDCcompletes refreshing the current row inthe source table and then stops anyfurther replication.


The preferred method is to stop refreshingin a controlled manner (CNTRLD). Stop arefresh immediately (IMMED) when itcannot be stopped in a controlled manner.


MODIFY TSAS,ENDTSRSH,SUBSCR=ALL Stops refreshing source tables to all targetsdefined in the InfoSphere CDC addressspace.

Since the default setting for the stoppingmethod is CNTRLD, InfoSphere CDC stopsthe refresh after the current source table hasbeen completely refreshed.

MODIFY TSAS,ENDTSRSH,SUBSCR=(SUB4),IMMED Stops refreshing source tables to targetSUB4.

InfoSphere CDC stops the refresh after thecurrent row in a source table has beencompletely refreshed.



FTSAS,ENDTSRSH,SUBSCR=(SUB1,SUB2*),CNTRLD

Stops refreshing source tables to target SUB1and all targets having a name that startswith SUB2 (for instance, SUB2A, SUB2B, andSUB2C).

InfoSphere CDC stops the refresh after thecurrent source table has been completelyrefreshed.



“STRTSRSH—Start refresh” on page 106

Table mapping commandsInfoSphere CDC has several commands that control table mapping.

See also:“SETMIRSTS—Set mirroring status”“SETRSHSTS—Set refresh status” on page 113

SETMIRSTS—Set mirroring status

This command allows you to set the mirroring status of source tables that have areplication method of MIRROR.

Since the mirroring status applies to a source table and subscription combination,you must identify the source tables and the selected subscriptions that are affectedby this command.

The mirroring status determines which source tables are mirrored to targetenvironments when the STRTSMIR command is issued. It also dictates whethertarget tables are refreshed with source table data before mirroring starts.

Note: The command will not change the mirroring status of any source tables insubscriptions that are actively mirroring (running) when the command is issued.

Syntax



Subscription (SUBSCR) Identifies the subscriptions that are selectedby the specified source tables.




Tables (TABLES) Identifies the selected source tables that areaffected by this command.

Only source tables having a replicationmethod of MIRROR are affected by thiscommand.

One or more source tables within a databasecan be specified. In addition, you can specifythe wildcard character (*) to referencemultiple tables having names that start withthe same set of characters. An example isprovided below to illustrate how wildcardsare used.


v ALL—Specifies all source tables definedin the InfoSphere CDC address space thathas a replication method of MIRROR.



Status (STATUS) Indicates the mirroring status assigned tothe source tables identified in this command.

The mirroring status determines whichsource tables are mirrored to targetenvironments when the STRTSMIRcommand is issued and whether these targettables are initially refreshed with sourcetable data before data mirroring starts.

One of the following predefined values mustbe specified:

v IDLE—Indicates that the specified sourcetables are not mirrored to the selectedsubscription when mirroring is started.

v ACTIVE—Indicates that the specifiedsource tables are mirrored to the selectedsubscription when mirroring is started.The target tables are not initially refreshedwith source table data before mirroringstarts.

v REFRESH—Indicates that the specifiedtarget tables are initially refreshed withsource data before mirroring starts.


MODIFY TSAS,SETMIRSTS,SUBSCR=ALL,TABLES=ALL,STATUS=REFRESH

Changes the status of all source tableshaving a replication method of MIRRORthat are selected to any subscription.

The status is set to REFRESH to indicate thatthe mapped target tables are refreshed withsource table data before mirroring starts.

MODIFY TSAS,SETMIRSTS,SUBSCR=(SUB1),TABLES=(DB1.OWN1.TBL*), STATUS=IDLE

Changes the status of all source tables indatabase DB1 (owned by OWN1) that havenames starting with TBL (for instance, TBL1,TBL2, and TBL3) and selected tosubscription SUB1. Only those source tableshaving a replication method of MIRROR areaffected by this command.

The status is set to IDLE to indicate thatthese tables are not mirrored to subscriptionSUB1 when mirroring is started.

MODIFY TSAS,SETMIRSTS ,SUBSCR=(SUB2),TABLES=(DB1.OWN1.TBL1,DB1.OWN1.TBL2),STATUS=ACTIVE

Changes the status of source tables TBL1and TBL2 in database DB1 (owned byOWN1) that are selected to subscriptionSUB2 and have a source method ofMIRROR.

The status is set to ACTIVE to indicate thatthese tables are mirrored to subscriptionSUB2 when mirroring is started. The targettables mapped to the two source tables arenot initially refreshed before mirroring starts



F TSAS,SETMIRSTS,SUBSCR=(SUB1,SUB2*),TABLES=(DB1.OWN1.*),STATUS=REFRESH

Changes the status of all source tables indatabase DB1 (owned by OWN1) that areselected to subscription SUB1 and allsubscriptions having a name that starts withSUB2 (for instance, SUB2A, SUB2B, andSUB2C). Only those source tables having areplication method of MIRROR are affectedby this command.

The status is set to REFRESH to indicate thatthe mapped target tables are initiallyrefreshed with source table data beforemirroring starts.



“ENDTSRSH—End refresh” on page 108“STRTSRSH—Start refresh” on page 106

SETRSHSTS—Set refresh status

This command allows you to set the refresh status of source tables that have areplication method of REFRESH.

Since the refresh status applies to a source table and subscription combination, youmust identify the source tables and the selected subscriptions that are affected bythis command.

The refresh status determines which source tables are refreshed to a targetenvironment when the STRTSRSH command is issued.

Note: The command will not change the refresh status of any source tables insubscriptions that are actively refreshing (running) when the command is issued.

Syntax



Subscription (SUBSCR) Identifies the subscriptions that are selected bythe specified source tables.

One or more subscriptions can be specified. Inaddition, you can specify the wildcard character(*) to reference multiple subscriptions havingnames that start with the same set of characters.An example is provided below to illustrate howwildcards are used.


v ALL—Specifies all subscriptions defined in theInfoSphere CDC address space.

Tables (TABLES) Identifies the selected source tables that areaffected by this command.

Only source tables that have a replicationmethod of REFRESH are affected by thiscommand.

One or more source tables within a database canbe specified. In addition, you can specify thewildcard character (*) to reference multipletables having names that start with the same setof characters. An example is provided below toillustrate how wildcards are used.


v ALL—Specifies all source tables defined in theInfoSphere CDC address space that has areplication method of REFRESH.



Status (STATUS) Indicates the refresh status assigned to thesource tables identified in this command.

The refresh status determines which sourcetables are refreshed to target environments whenthe STRTSRSH command is issued.

One of the following predefined values must bespecified:

v IDLE—Indicates that the specified sourcetables are not refreshed to the selectedsubscriptions when a data refresh is started.

v REFRESH—Indicates that the specified sourcetables are refreshed to the selectedsubscriptions when a data refresh is started.


MODIFY TSAS,SETRSHSTS,SUBSCR=ALL,TABLES=ALL,STATUS=REFRESH

Changes the status of all source tables having areplication method of REFRESH that are selectedto any subscription.

The status is set to REFRESH to indicate thatthese source tables are refreshed to subscriptionswhen a data refresh is started.

MODIFY TSAS,SETRSHSTS,SUBSCR=(SUB1),TABLES=(DB1.OWN1.TBL*),STATUS=IDLE

Changes the status of all source tables indatabase DB1 (owned by OWN1) that havenames starting with TBL (for instance, TBL1,TBL2, and TBL3) and selected to subscriptionsSUB1. Only those source tables having areplication method of REFRESH are affected bythis command.

The status is set to IDLE to indicate that thesetables are not refreshed to subscription SUB1when a data refresh is started.

MODIFY TSAS,SETRSHSTS,SUBSCR=(SUB2),TABLES=(DB1.OWN1.TBL1,DB1.OWN1.TBL2),STATUS=IDLE

Changes the status of source tables TBL1 andTBL2 in database DB1 (owned by OWN1) thatare selected to subscription SUB2 and having areplication method of REFRESH.

The status is set to IDLE to indicate that thesetables are not refreshed to subscription SUB2when a data refresh is started.

F TSAS,SETRSHSTS,SUBSCR=(SUB1,SUB2*),TABLES=(DB1.OWN1.*),STATUS=REFRESH

Changes the status for all source tables indatabase DB1 (owned by OWN1) that areselected to subscription SUB1 and allsubscriptions having a name that starts withSUB2 (for instance, SUB2A, SUB2B, and SUB2C).Only those source tables having a replicationmethod of REFRESH are affected by thiscommand.

The status is set to REFRESH to indicate thatthese source tables are refreshed to the specifiedsubscriptions when a data refresh is started.




“ENDTSRSH—End refresh” on page 108“STRTSRSH—Start refresh” on page 106

Other CommandsInfoSphere CDC has several commands that control miscellaneous actions.

See also:“COMMAND—Process InfoSphere CDC commands”“DSPACT—Display activity” on page 117“ENDUR—End unit of recovery” on page 120“REPORT—Generate report” on page 122“SETLOGPOS—Set log position” on page 123“STGMGR—Storage Manager” on page 125“STRTSDSC—Describe source tables to subscription” on page 125“TRACE—Trace InfoSphere CDC tasks” on page 127“TRACEDEST—Set trace destination” on page 132

COMMAND—Process InfoSphere CDC commands

This command identifies the suffix(es) of the CHCCMDxx members (in theCHCCNTRL data set) containing one or more InfoSphere CDC console commandsthat are issued when this command is invoked.

Any console command (including COMMAND) can be specified in a CHCCMDxxmember. Commands specified in a member must omit the MODIFY, F,<procname> and <identifier> elements.

Note: A configuration control statement supports a keyword called COMMANDthat provides the same function after successful InfoSphere CDC address spaceinitialization. If the COMMAND keyword was specified in the statement, use ofthe COMMAND command in your environment may be redundant.

Syntax



Member Suffix (<CommSuffix>) Identifies the suffix of a CHCCMDxxmember (in the CHCCNTRL data set)containing one or more InfoSphere CDCconsole commands that are issued when thiscommand is invoked.

You can specify the suffix of a CHCCMDxxmember that had its commands invokedafter InfoSphere CDC address spaceinitialization. In this case, the same set ofcommands is invoked again whenCOMMAND is issued.

Multiple suffixes can be specified when youwant to invoke console commands in morethan one CHCCMDxx member. The order ofthe suffixes specified in this settingdetermines the order in which sets ofcommands are issued. However, one shouldnot assume that the order of the specifiedsuffixes determines the order in which setsof commands complete their execution. Inother words, command completions may notnecessarily follow the specified suffix order.


MODIFY TSAS,COMMAND=(01) Invokes the InfoSphere CDC consolecommands defined in the CHCCMD01member.Note: If you specify one suffix, theparentheses are not required. However, youcan use parentheses in each COMMANDinvocation, as they are required whenspecifying more than one suffix.

F TSAS,COMMAND=(02,03) Invokes the InfoSphere CDC consolecommands defined in the CHCCMD02 andCHCCMD03 members.

The set of commands in CHCCMD02 isissued before the set of commands inCHCCMD03.

Related concepts

“IBM InfoSphere Change Data Capture installation or upgrade” on page 1Related reference

“COMMAND” on page 31

DSPACT—Display activity

This command requests that messages conveying information about activity withinthe InfoSphere CDC address space be directed to the console operator that issuedthe DSPACT command.

The messages are placed in the system log for the console operator, and can befiltered by message type. This command should be used when you require a


snapshot of activity within the InfoSphere CDC address space. The generatedmessages reveal various statuses and statistics at the time when the command isissued.

If you require continuous monitoring of replication activity, use InfoSphere CDCManagement Console.

Syntax



Message Type (ALL , REPLIC, DBMS, orCOMM)

Indicates the types of messages that areplaced in the system log for the consoleoperator.


v ALL—Returns messages that conveyinformation about all types of activitieswithin the InfoSphere CDC address space.

v REPLIC—Returns messages that conveyinformation about ongoing replicationactivities (data refresh and mirroring) totarget environments.

v DBMS—Returns messages that conveyinformation about activities related to theDBMS environment.

v COMM—Returns messages that conveyinformation about activities related to thecommunications environment.

Default Setting: ALL

Specifying ALL is equivalent to issuing thiscommand three times (one invocation foreach message type). If you want two typesof messages to be returned to the operatorconsole, this command has to be issuedtwice.

The set of messages placed in the system logfor each predefined value is as follows:

v ALL: CHC9776I, CHC9817I, CHC9789I,CHC9733I, CHC9800I, CHC9830I,CHC9742I, CHC9751I, CHC9753I,CHC9840I, CHC9853I

v REPLIC: CHC9751I, CHC9753I,CHC9840I, CHC9853I

v DBMS: CHC9835I, CHC9742I

v COMM: CHC9776I, CHC9817I,CHC9789I, CHC9733I, CHC800I


MODIFY TSAS,DSPACT All types of messages that conveyinformation about the current state of theInfoSphere CDC address space are directedto the console operator through the systemlog (the default setting for the message typeis ALL).

Specifically, the following messages aregenerated in the system log: CHC9676I,CHC9817I, CHC9789I, CHC9733I, CHC9800I,CHC9830I, CHC9742I, CHC9751I, CHC9753I,CHC9840I, and CHC9853I.



F TSAS,DSPACT=REPLIC Messages that convey information about thecurrent state of data replication are directedto the console operator through the systemlog.

Specifically, the following messages aregenerated in the system log: CHC9751I,CHC9753I, CHC9840I, and CHC9853I.

MODIFY TSAS,DSPACT=DBMS Messages that convey information aboutactivities related to the DBMS environmentare directed to the console operator throughthe system log.

Specifically, the following messages aregenerated in the system log: CHC9830I,CHC9742I.



“STRTSDBM—Initialize database management system” on page 99“CHC9817I” on page 648“CHC9676W” on page 610“CHC9789I” on page 638“CHC9733I” on page 626“CHC9753I” on page 629“CHC9800I” on page 641“CHC9840I” on page 653“CHC9853I” on page 659“CHC9742I” on page 626“CHC9751I” on page 628“CHC9830I” on page 649

ENDUR—End unit of recovery

This command may be issued to instruct InfoSphere CDC for z/OS to dispose of aunit of recovery (transaction) by either queuing it for transmission to the target ordiscarding it.

ENDUR identifies:v the unit of recoveryv the subscription that is currently active that is to be acted onv the manner of disposition for the unit of recovery


CAUTION:Normally, units of recovery are sent to the target system and applied there in theorder in which their COMMIT actions are read from the DB2 Log. Using theENDUR command to force the disposition of a unit of recovery necessarily willinterfere with this order. Changes within a unit of recovery that are subjected tothe ENDUR,DISP=COMMIT command may be transmitted to the target side soonerthan they would have been, or later than they should have been if they havebeen delayed somehow. Changes within a unit of recovery that are subjected tothe ENDUR,DISP=ROLLBACK command will be discarded when they possibly shouldhave been sent to the target side. All of these scenarios will desynchronize thesource and target tables from which the manipulated units of recovery containedchanges. These effects must be weighed against the need to use the ENDURcommand to force changes from the subscription’s staging space.


Subscription (SUBSCR) Identifies the subscription.

Only one subscription can be specified.

If the subscription is not actively mirroring,an error message will be issued.

Unit of Recovery Identifier (URID) Identifies the 6 byte Unit of Recoveryidentifier.

This information can be obtained from thesecond data column of the staging spacereport.

Member (MBR) Specifies the member identifier.

The MBR keyword must be specified with anon-zero value if and only if the connectedDB2 subsystem is a member of a DataSharing Group.

The MBR keyword should not be specified ifthe connected DB2 subsystem is not amember of a Data Sharing Group



Disposition (DISP) Indicates the manner of disposition of theunit of recovery.

The following predefined values can bespecified:

v COMMIT—Artificially ends and queuesthe unit of recovery for transmission tothe target system.

v ROLLBACK—Artificially ends anddiscards the unit of recovery.

Example Description

F TSAS.ENDUR,SUBSCR=NCTEST02,URID=02DFD6A05A0B,DISP=ROLLBACK

Artificially ends and discards the unit ofrecovery with an ID of 02DFD6A05A0b forsubscription NCTEST02 defined in theInfoSphere CDC address space TSAS.

REPORT—Generate report

This command allows you to generate a report in the CHCREPRT data set.

Currently, only a staging space report can be generated. This report providesdetailed information about the staging space for a specified subscription or for allactive subscriptions. The report can be used to diagnose staging space problemsthat have occurred or could surface at a later time. You may want to generate sucha report when generated InfoSphere CDC messages indicate potential or actualstaging space problems. For example, the report could indicate or confirm that thestaging space has reached capacity, and as a result, replication to the associatedsubscription has been stopped.

Note: This command may be used to generate other types of reports in futureInfoSphere CDC releases.

Staging space reports can only be generated when replication to the identifiedsubscription is active.



Task (TASK) Identifies the InfoSphere CDC task that generatesthe report.

Currently, only one task (SDT) can generatereports. The only setting is SDT.

Report Type (TYPE) Identifies the type of report that is generated andplaced in the CHCREPRT data set.

Currently, only staging space reports can begenerated. The only setting is STGSP.

Subscription (SUBSCR) Identifies the subscription for which the report isgenerated.


If no subscription is identified, the report will begenerated for all active subscriptions.

Detail (DETAIL) Includes a detail line in the report for each tablethat has changes in the unit of recovery.


Example Description

MODIFYTSAS,REPORT,TASK=SDT,TYPE=STGSP,SUBSCR=SUB1

Generates a staging space report for subscriptionSUB1 defined in the InfoSphere CDC addressspace.



SETLOGPOS—Set log position

This command allows you to set the position in the log where mirroring will startscraping for a specific subscription the next time mirroring is started.

Note that this command does not change the log position for subscriptions whichare currently active.



Subscription (SUBSCR) Identifies the subscription that is to have itslog position set.

Only one subscription can be specified.

Log position (POSITION) Identifies the position in the log where thissubscription should start scraping the nexttime mirroring is started.

You can specify one, two, or three strings of1 to 16 hexadecimal digits separated bycommas and enclosed by parentheses. For adata sharing group, each string will beassumed to be a DB2 log LRSN. For anon-data sharing group, each string will beassumed to be a DB2 log RBA. If only onestring is specified, the parentheses may beomitted.

The first string is the log position of the lastcommit record processed by thesubscription. The second string is the logposition of the earliest open commit groupwhen replication was ended. The thirdstring is the log position of the last appliedchange processed by the subscription. If onlyone string is specified, it will also be used asthe log position of the earliest open commitgroup.

Bookmark Version (VERSION) Note: This is an optional keyword andshould only be used when downgradingfrom version 6.2 to a previousrelease.Identifies the version of thebookmark. If you do not specify thiskeyword, the default value of 1 will beassumed. The other valid value for thisparameter is 0.Note: Version 1 bookmark is used byversion 6.2 of the product. Version 0bookmark is used by version 5.4 and belowof the product.



SETLOGPOS,SUBSCR=TOAS400,POSITION=C0C01991D0EF0000

Sets the log position for the specifiedsubscription with a version 1 bookmark.

SETLOGPOS,SUBSCR=TOAS400,POSITION=C0C01991D0EF0000, VERSION=0


SETLOGPOS,SUBSCR=TOAS400,POSITION=(C0C01991D0EF0000,C0C01991D0EA0000)


SETLOGPOS,SUBSCR=TOAS400,POSITION=(C0C01991D0EF0000,C0C01991D0EA0000, C0C01991D0EB0000)


STGMGR—Storage Manager

This command allows you to monitor and manage the storage manager.


Status (STATUS) Requests that a report of the status of the storage manager and itsusers be displayed on the console.

Specify the name of a storage manager. If no value is given, thestatus of all users is displayed.

Storage Amount(ADDSTG)

Specifies the increase in the amount of above the bar (64–bit)storage that the Storage Manager is allowed to use.

This increase is on top of the configured amount and will be ineffect for this execution of InfoSphere CDC for z/OS only.


f dmc0038s,stgmgr,status Displays the status of the storage manager.

f dmc0038s,stgmgr,status,name=alltypes Displays the status of the storage managerfor a single user.

f dmc0038s,stgmgr,addstg=50m Increases the storage of the storage managerby 50MB.

STRTSDSC—Describe source tables to subscription

This command sends source table descriptions to the specified subscriptions.


Source table descriptions have to be sent to target environments after a change hasbeen made to one or more source table attributes or after it has been selected to asubscription. For example, if you change the replication method for a table, theappropriate source table attributes are updated to reflect these changes. Before datafrom this source table can be replicated to different subscriptions, a newdescription of the table has to be sent to each subscription.

Only descriptions of selected source tables that have undergone such changes sincethe last STRTSDSC command was issued are transferred to target environments.

Syntax


Subscription (SUBSCR) Identifies the subscriptions to receivedescriptions of selected source tables thathave been changed since the last STRTSDSCcommand was issued.





MODIFY TSAS,STRTSDSC,SUBSCR=ALL Descriptions of selected source tables thathave been changed since the last STRTSDSCcommand was issued are sent to allsubscriptions defined in the InfoSphere CDCaddress space.

MODIFY TSAS,STRTSDSC,SUBSCR=(SUB4) Descriptions of selected source tables thathave been changed since the last STRTSDSCcommand was issued are sent tosubscription SUB4.



F TSAS,STRTSDSC,SUBSCR=(SUB1,SUB2*) Descriptions of selected source tables thathave been changed since the last STRTSDSCcommand was issued are sent tosubscription SUB1.

Descriptions of selected source tables thathave been changed since the last STRTSDSCcommand was issued are also sent tosubscriptions having a name that starts withSUB2 (for instance, SUB2A, SUB2B, andSUB2C).


This command can be issued on source environments.

TRACE—Trace InfoSphere CDC tasks

This command activates or deactivates specified trace types in InfoSphere CDCtasks.

Initially, all trace types are deactivated. Activating trace types must be performedexplicitly by using this command. If trace types are activated, replicationperformance may deteriorate during the trace.

CAUTION:Tracing of InfoSphere CDC tasks should only be performed when requested byTechnical Support.

Syntax




Options (ON, OFF, LIST, or <suffix>) Indicates whether trace types are beingactivated or deactivated by the command.See Trace Types below for information abouttrace types.

Instead of activating (ON) or deactivating(OFF) trace types, an option (<suffix>) isprovided for identifying the member in theCHCCNTRL data set that contains one ormore TRACE commands to be executed insequence. Another option (LIST) issupported for just listing the active tracetypes in the specified tasks. No trace typesare activated or deactivated when LIST isspecified. You can use the list option to keeptrack of activated and deactivated traces in atask, which is especially important beforestarting replication in a productionenvironment.

One of the following values can be specified:

v ON—Specified trace types in the tasks areactivated.

v OFF—Specified trace types in the tasks aredeactivated.

v LIST—Lists the active trace types in thespecified tasks. The active trace types arelisted in InfoSphere CDC messageCHC9662I.

v <suffix>—The two-character suffixidentifying the CHCTRC<suffix> memberthat contains one or more TRACEcommands to be performed in sequence.

Default Setting: ON

Task Names (TASK) Identifies the names of the active InfoSphereCDC tasks that are affected by thiscommand.

One or more of the following task names canbe specified:

MIT, OSC, PAL, CIT, PAA, DIT, DSC, DAL,DSL, DDT, DDR, DTC, CCI, CCO, CDI,CDO, CLS, CMO, CVF, DDT, SCT, SDT, TCT

Task names are enclosed with parentheses,and separated by commas. If an activeinstance of a specified task cannot be found,the request to trace the task is not discarded.Instead, the request is placed in a wait queueuntil the next task becomes active.

This setting is required if ON, OFF, or LISTis the selected option.Note: You do not have to be aware of thesignificance of each InfoSphere CDC task.IBM Technical Support may indicate whichtask names should be specified.



Trace Types (TYPE) Identifies the trace types in the specifiedInfoSphere CDC tasks that are affected bythis command.

Trace types are numbered from 1 to 255inclusively. Multiple trace types must beenclosed within parentheses, and separatedby commas.

This setting is required if ON or OFF is theselected option.Note: You do not have to be aware of thesignificance of each trace type. IBM TechnicalSupport may indicate which trace typesshould be specified.

Subscription (SUBSCR) Identifies the subscription that is affected bythis command.

Only one subscription name can bespecified.

This setting is optional, and it only appliesto active or the next active instance of theDDT, SCT, and SDT tasks (if they arespecified - see Task Names, above) for thesubscription. If this setting is omitted, thiscommand is applied to the next instance ofthe specified tasks (across all subscriptions)that are activated.

Source Identifier (PUBLSH) Identifies the source identifier that is affectedby this command.

Only one source identifier can be specified.

This setting is optional, and it only appliesto active or the next active instance of theDDR and DTC tasks (if they are specified,see Task Names) for the source identifier. Ifthis setting is omitted, this command isapplied to the next instance of the specifiedtasks (across all source identifiers) that areactivated.

User (USER) Identifies the security identifier that isaffected by this command.

Only one security identifier can be specified.

This setting is optional, and it only appliesto the active or the next active instance ofthe PAA task (if it is specified, see TaskNames, above) for the security identifier. Ifthis setting is omitted, this command isapplied to the next instance of the specifiedtask (across all security identifiers) that isactivated.



Parameter String (PARM) Identifies the parameters that are passed tothe specified tasks.

This setting is optional. When specified, thissetting identifies a 64-character string thatcan be used to pass parameters to thespecified tasks.Note: IBM Technical Support may specifythe content of this string.

Examples Descriptions

MODIFY TSAS,TRACE=LIST,TASK=(MIT,CIT,DDT,DDR,DTC)

Lists the active trace types for fiveInfoSphere CDC tasks (MIT, CIT, DDT,DDR, and DTC).

MODIFY TSAS,TRACE=ON,TASK=(DDT,DTC),TYPE=(1,4,22),SUBSCR=SUB1,PARM="TEST1TEST2"

Activates three trace types (1, 4, and 22)in the DDT and DTC tasks.

Activation applies to the specified tracetypes in active or the next activeinstance of the DDT task forsubscription SUB1.

Activation applies to the specified tracetypes in the next instance of the DTCtask (across all source identifiers) that isactivated.

A parameter string (″TEST1TEST2″) ispassed to the DDT and DTC tasks.

F TSAS,TRACE=ON,TASK=(DDT,DDR,PAA),TYPE=(3,103),SUBSCR=SUB2 PUBLSH=PUBID2,USER=GSMITH,PARM="TEST3TEST4"

Activates two trace types (3 and 103) inthe DDT, DDR, and PAA tasks.

Activation applies to the specified tracetypes in the active or the next activeinstance of the DDT task forsubscription SUB2.

Activation applies to the specified tracetypes in the active or the next activeinstance of the DDR task for publisheridentifier PUBID2.

Activation applies to the specified tracetypes in the active or the next activeinstance of the PAA task for securityidentifier GSMITH.

A parameter string (″TEST3TEST4″) ispassed to the DDT, DDR, and PAAtasks.


Examples Descriptions

F TSAS,TRACE=ON,TASK=(MIT,OSC,DDT),TYPE=(202,54),SUBSCR=SUB3

Activates two trace types (54 and 202) inactive MIT, OSC, and DDT tasks.

Activation applies to the specified tracetypes in active or the next activeinstance of the MIT and OSC tasks.

Activation applies to the specified tracetypes in the active or the next activeinstance of the DDT task forsubscription SUB3.

F TSAS,TRACE=OFF,TASK=(MIT,OSC,PAL),TYPE=(108,209,77)

Deactivates three trace types (77, 108,and 209) in active or the next activeinstance of the MIT, OSC, and PALtasks.Note: A TRACE command overrides aprevious TRACE command if some orall task and trace type combinations arethe same. If task and trace typecombinations across separate TRACEcommands are mutually exclusive,tracing is cumulative. In this case, noneof the trace types activated ordeactivated in earlier commands areaffected by subsequent commands. Ifnecessary, use the LIST option todetermine the trace types that arecurrently active


This command can be issued on source environments and target environments.Related concepts

“IBM InfoSphere Change Data Capture installation or upgrade” on page 1Related reference


TRACEDEST—Set trace destination

When the TRACE command is used, this command identifies or sets thedestinations of InfoSphere CDC trace information.

Trace information can be directed to the IBM Generalized Trace Facility (GTF) or aSPOOL data set.

CAUTION:Tracing of InfoSphere CDC tasks should only be performed when requested byIBM Technical Support.

Syntax



Trace Destination (GTF, SYSOUT, orBOTH)

Identifies the destinations where InfoSphereCDC trace information is placed. Traceinformation can be direct to the IBMGeneralized Trace Facility (GTF) or a SPOOLdata set.

The following predefined values can bespecified:

v GTF—InfoSphere CDC trace informationis directed to the GTF.

v When InfoSphere CDC tracinginformation is directed to GTF, log recordsare stamped with a GTF user eventidentifier (EID) of 300. For GTF to acceptInfoSphere CDC tracing information, theGTF TRACE and USR parameters must beset in the following manner:

– TRACE = USRP

– USR = (300)

GTF can be configured and activatedbefore running the TRACE command. IfGTF is not active when the command isinvoked, a message is issued to indicatethat gathering of data on trace eventsbegins when GTF is started. For moreinformation about GTF, consult theappropriate IBM publication.

v SYSOUT—InfoSphere CDC traceinformation is directed to a SPOOL dataset.

v BOTH—InfoSphere CDC traceinformation is directed to GTF and aSPOOL data set.

If this setting is omitted, the currentdestinations where trace information is beingplaced is identified (GTF, SYSOUT, orBOTH).


Example Description

MODIFY TSAS,TRACEDEST Identifies the current destinations whereInfoSphere CDC trace information is beingplaced. GTF, SYSOUT, or BOTH is returnedby this command.

MODIFY TSAS,TRACEDEST=GTF Directs InfoSphere CDC trace information tothe IBM Generalized Trace Facility (GTF).

F TSAS,TRACEDEST=BOTH Directs InfoSphere CDC trace information tothe IBM Generalized Trace Facility (GTF)and a SPOOL data set.




Code page conversion services

This section provides information about configuring InfoSphere CDC for z/OS touse code page conversion service.

In this section, you will learn:“Introduction”“Unicode Conversion Services”“Language Environment Code Page Conversion tables” on page 136

IntroductionOne of InfoSphere CDC’s replication features is the translation of text data fromthe code page of the source server to the code page of the target server. You canconfigure InfoSphere CDC for z/OS to use either Unicode Conversion Services orthe Language Environment’s Code Page Conversion Services to perform text datatranslation.

Either way, InfoSphere CDC must have access to the Language Environment’s codepage conversion tables that are distributed with z/OS.

Notes:

v For better performance when converting characters between different codepages, you should configure InfoSphere CDC to use Unicode ConversionServices instead of Language Environment’s Code Page Conversion Services.

v By default, InfoSphere CDC attempts to use Unicode Conversion Services toperform translation of text data from one code page to another. If UnicodeConversion Services is not initialized or configured properly, InfoSphere CDCissues warning messages during initialization to indicate that UnicodeConversion Services is not available or conversions between specific code pagesare not available. In this case, Language Environment’s Code Page ConversionServices are used.

Related concepts

“Language Environment Code Page Conversion tables” on page 136“Unicode Conversion Services”

Unicode Conversion ServicesThe support for Unicode Conversion Services is provided by the z/OS operatingsystem. If this support is not available, InfoSphere CDC uses LanguageEnvironment’s Code Page Conversion Services instead.

Note: For better performance when converting characters between different codepages, you should configure InfoSphere CDC to use Unicode Conversion Servicesinstead of Language Environment’s Code Page Conversion Services.

During initialization, InfoSphere CDC determines if UCS support is provided byz/OS. If UCS is available, UCS configuration statements are read from theCHCUCSxx member of the configuration control data set, where xx is a suffixselected by the installer.


The suffix of the CHCUCSxx member is specified using the UCSCONFIG keywordin the CONFIG statement.

The sample UCS Configuration data set member is copied to the ConfigurationControl data set during the installation process, and should be modified for yourworking environment.Related concepts

“CONVERSION” on page 72Related reference

“UCSCONFIG” on page 43

Language Environment Code Page Conversion tablesInfoSphere CDC for z/OS can use the code page conversion services of LanguageEnvironment® to perform the text data translation. To do so, InfoSphere CDC forz/OS must have access to the Language Environment’s code page conversiontables that were distributed with z/OS.

Note: Even if you choose Unicode Conversion Services to perform code pageconversion of text data, it is important to follow the directions in this section,because problems (related to your working environment) may occur when usingUnicode Conversion Services. When such problems occur, InfoSphere CDC revertsto using Language Environment’s Code Page Conversion Services.

The default name of the data set containing the Language Environment code pageconversion tables is ’CEE.SCEEUTBL’. However, when z/OS was installed, thedefault name for this data set may not have been used. The installer has the optionof selecting a different high-level qualifier for the Language Environment data set,replacing the “CEE” with one or more prefixes of their own choice. If the decisionwas made at installation time to change the high-level qualifier of the LanguageEnvironment data set, then InfoSphere CDC for z/OS must be provided with thechosen high-level qualifier so that it can locate the Language Environment codepage conversion tables data set.

The installer must modify the CHCPROC JCL, adding an environment variablethat contains the chosen high-level qualifier. Change the PARM keyword operandon the EXEC statement in the CHCPROC to add the following parameter data:PARM=('/ENVAR(_ICONV_UCS2_PREFIX=<newprefix>)/COMM,DBMS')

where <newprefix> is the high-level qualifier that replaces CEE for the LanguageEnvironment data set.


DB2 performance considerations

This section contains information about performance considerations and techniqueswhen using InfoSphere CDC and DB2.

In this section, you will learn:“Static versus dynamic SQL”“%GETCOL and %SELECT function calls and processing efficiency” on page140“User exits and efficiency” on page 141

Static versus dynamic SQLInfoSphere CDC uses Static SQL to access and manage its metadata DB2 tables.InfoSphere CDC for z/OS uses Dynamic SQL when dealing with data in usertables. Dynamic SQL is used for user tables because it is built at execution time,when it is possible to determine how user tables were created.

When InfoSphere CDC is installed on the source system, Dynamic SQL is usedwhen obtaining data during a refresh. During mirroring, table data is obtainedfrom the DB2 Log, so no SQL, neither Dynamic nor Static, is used to obtain userdata during mirroring.

When InfoSphere CDC is installed on the target system, Dynamic SQL is used toapply changes to the user tables.

It is known that Dynamic SQL is much less efficient then Static SQL. Still, properlymanaged Dynamic SQL can be made to be almost as efficient as Static SQL. Toexplain how this improvement in Dynamic SQL efficiency is possible, considerhow Dynamic and Static SQL differ in preparation and execution.

Processing of SQL by the DBMS can be broken down into three steps:1. Syntactic and semantic analysis: verifying that the SQL is coded according to

the syntax rules, and determining what it is meant to achieve.2. Access permission and path analysis: determining if the resources accessed by

the SQL are permitted for the requester, and if they are permitted, how thataccess will be provided (determining the access path).

3. Execution and completion analysis: obtaining or changing the data accordingto the specification of the SQL and preparing returned status information aboutthe outcome of the request.

Step 1 is relatively innocuous and absorbs CPU resources only. Step 2 is veryresource intensive, as it requires the DBMS to access multiple tables to resolve thequestions of security permissions and available access paths, and then to store theresults in other tables as temporary “plan”. Step 3’s efficiency is dependent on thetype of processing specified by the SQL, what access path has been chosen, whatserver resources are available, and so on.

In the case of Static SQL, Step 1 occurs during precompilation of the source codecontaining the Static SQL. Step 2 occurs during the BIND process that occurs afterprecompilation but before execution. Step 3 occurs at execution time. This is the


reason that Static SQL is perceived to be efficient. Most of its onetime processingoccurs earlier, before the statement needs to be executed. Only Step 3 occurs eachtime that the Static SQL statement is executed.

In the case of Dynamic SQL, the three steps occur at execution time. If a DynamicSQL statement is simply built and executed, the three steps occur duringprocessing of the EXECUTE request. The next time a similar SQL statement isrequired, all three steps are performed again. This is the reason that Dynamic SQLis so much less efficient that Static SQL. In this section, this type of Dynamic SQLis identified as naive Dynamic SQL.

It is possible with Dynamic SQL, however, to provide some degree of separationbetween the three steps at execution time. The executing program can build theSQL statement and then prepare it into a buffer. The PREPARE statementencompasses Step 1 and Step 2. Subsequently, the program can execute theprepared SQL statement from the buffer. In this case, the EXECUTE statementperforms only Step 3. Furthermore, the SQL statement in the prepared buffer canbe executed as many times as it is needed, until a COMMIT is issued. TheCOMMIT will invalidate the contents of the prepared buffer. In this section, thistype of Dynamic SQL is identified as astute Dynamic SQL.

The following is a simple comparative analysis of the efficiencies of the three typesof SQL. In this analysis, CPU time was measured. I/O activity by the DBMS wasnot measured, but the elapsed time for completing the SQL requests wasmeasured. The analysis consisted of three separate test runs:1. 1000 Static SQL INSERT statements.2. 1000 naive Dynamic SQL INSERT statements (for example, 1000 EXECUTE

statements).3. 1000 astute Dynamic SQL INSERT statements (for example, 1 PREPARE and

1000 EXECUTE statements from the prepared buffer).

The results are provided in the following table:

Note: The timings presented here are examples, only for the purposes ofillustrating the relative performance of dynamic and static SQL. They should notbe considered as representative of the actual performance that InfoSphere CDC willachieve in your working environment.

Test (1000 INSERTS) CPU Time SRB Time Total CPU Time Elapsed Time

Static SQL .95 sec. .01 sec. .96 sec. .04 min.

EXECUTE only (naive) 14.49 sec. .02 sec. 14.51 sec. .30 min.

PREPARE and EXECUTE(astute)

.99 sec. .02 sec. 1.01 sec. .04 min.

The table above reveals that combining a single PREPARE statement with multipleEXECUTE statements is comparable to Static SQL. The naive Dynamic SQL usesabout 15 times more CPU and takes about 7.5 times the elapsed time of Static SQL.The astute Dynamic SQL uses only about 1.052 times more CPU than Static SQL,and has an indistinguishable elapsed time. The additional flexibility of astuteDynamic SQL is worth the slight increase (5.2%) in CPU utilization over theinflexible Static SQL.

InfoSphere CDC uses astute Dynamic SQL when it accesses user table data.Recalling that each COMMIT purges the Dynamic SQL’s prepared buffer, it can be


seen that the efficiency of the astute Dynamic SQL is directly related to the numberof times the prepared buffer can be reused before a COMMIT is issued. The rate atwhich COMMIT statements are issued is not under InfoSphere CDC’s control.

On the source system, a cursor is opened to access the table’s data during aRefresh operation, and each row is fetched individually. A COMMIT is issued (onlyto release locks) when there are no more rows to be fetched. Therefore, on thesource system, for almost any table, astute Dynamic SQL should be virtually thesame as Static SQL in its efficiency.

On the target system, when the apply process is making changes to user tables, itcommits those changes when it receives a COMMIT statement from the sourcesystem. The target system does not issue COMMIT statements by itself. The sourcesystem sends COMMIT statements to the target system when the source systemobtains them from the DBMS Log. Therefore, on the target system, astute DynamicSQL’s efficiency is based on how frequently COMMIT statements are issued by theuser’s application that originally changed the replicated tables on the sourcesystem. Large commit groups are applied on the target system almost as efficientlyas Static SQL. Small commit groups, such as those generated by onlinetransactions, can be inefficient, approaching the inefficiency of naive Dynamic SQL.The Transaction Grouping feature can be engaged by the customer to causeInfoSphere CDC to collect commit groups received at the target system, andcommit them together as a single unit of work, based on customer-providedparameters. This will have a positive effect on performance on the target system,as it will increase the efficiency of the astute Dynamic SQL being used to apply thechanges.

On the target system, InfoSphere CDC reserves 50 PREPARE buffers for retainingprepared Dynamic SQL for each subscription. For each mapped table in asubscription on the target system that is receiving changes, it is possible that anINSERT, UPDATE, or DELETE change can be applied to the table. A subscription’sPREPARE buffer is allocated to a table-and-change combination when the first suchchange for a specific table is received in the commit group. When there are morethan 16 (50 buffers per subscription and 3 change types per table) tables mappedto a subscription, the 50 PREPARE buffers could all be in use. If this shouldhappen, then InfoSphere CDC uses an LRU (Least Recently Used) algorithm todecide which PREPARE buffer is reused for astute Dynamic SQL. This means that,even when commit groups are large, when a subscription has more than 16 tablesmapped, the efficiency of the astute Dynamic SQL begins to drop.

One way to increase the efficiency of the apply process at the target system is tochange user applications so that they contain appreciable numbers of changes ineach commit group. This may be possible with batch jobs, but is impractical withcommit groups generated by online transactions. With the use of the TransactionGrouping feature, however, it is no longer necessary to modify applicationprograms to increase the efficiency of replication. Still it would increase theefficiency of the application programs themselves.

Another way to increase the efficiency of the apply process at the target system isto replace the astute Dynamic SQL that is not efficient with Static SQL coded in auser exit.

To summarize, these are the considerations for deciding if InfoSphere CDC’s astuteDynamic SQL will become inefficient.v A “profile” of the DBMS Log’s commit groups that contain data to be replicated

is required. It is the Database Administrator’s task to identify those replicated

DB2 performance considerations 139

tables that are being changed in small commit groups, and to determine howmany of these small commit groups will be created in a particular time period.Both the number of changes in commit groups and the numbers of such commitgroups need to be considered to assess the efficiency of the apply process.

v Subscriptions where there are more than 16 selected tables need to be examined.Is there a restriction on the types of changes (INSERT, UPDATE and DELETE)that are being applied to a particular table? A table may receive a highproportion of UPDATE changes, but very few INSERT and DELETE changeswithin a subscription. This would tend to require only a single PREPARE bufferfor that table in the commit group, increasing the efficiency of the subscription’sastute Dynamic SQL. When the mix of tables combined with the types ofchanges to the tables exceeds 50, the efficiency begins to decrease, and this trendworsens as the table-and-change mix gets larger.

v InfoSphere CDC’s Transaction Grouping feature can be engaged at the target toincrease the minimum size of the logical units of work being applied. This willincrease the efficiency of the astute Dynamic SQL.

Related concepts

“User exits and efficiency” on page 141Related reference

“COMMITFREQ” on page 63

%GETCOL and %SELECT function calls and processing efficiency%GETCOL or %SELECT function calls can be used in expressions and row filteringexpressions. The %GETCOL function provides a mechanism to obtain current datafrom an application table, which is then used in the evaluation of the expression.%SELECT provides a similar capability to %GETCOL, but is more powerful andnatural to use, due to its accepting an SQL SELECT statement to specify thecurrent data to be accessed.

When processing a %GETCOL function call, InfoSphere CDC prepares andexecutes SQL to obtain the data specified. Such ad hoc SQL can be very inefficient,depending on the access path that DB2 uses when the SQL is executed. To addressthis exposure, InfoSphere CDC issues a DB2 EXPLAIN against the SQL at the timethat the %GETCOL function is entered into or changed in an expression or rowfiltering expression. During installation, the CHCCRMTD sample job will havecreated a <CHCUserID>.PLAN_TABLE. DB2 stores the results of the EXPLAIN inthis PLAN_TABLE, where it is accessed and examined by InfoSphere CDC. If thead hoc SQL uses an inefficient access path, then an appropriate warning message isissued in Management Console.

%GETCOL function call access path warning messages should not be ignored. Forexample, inefficient %GETCOL function calls used in row filtering expressionscould slow data processing by the source environment to the extent thatInfoSphere CDC may be slower at obtaining data from the DB2 Log than DB2 is inwriting to it, producing ever-increasing replication latency. In addition to thefailure to perform, %GETCOL function call access path problems can causeInfoSphere CDC to absorb large amounts of CPU and I/O resources, negativelyimpacting other jobs running on the same server.

Some of the types of inefficiencies that can be indicated in the PLAN_TABLE arenon-unique key and partial key accesses, index space scans, and table space scans.Non-unique and partial key accesses may or may not be acceptable, depending onthe amount of data accessed by the partial key. Index space and table space scans


should never be permitted. Assessment of these types of access path problem typesis the normal responsibility of a Database Administrator. The DBA should be ableto determine what is required to correct the access path situation. Usually, it can becorrected by building a new index with the required keys to allow a full key accessto obtain the data. A different way to improve %GETCOL efficiency may be theuse of different key columns or the addition of more key columns to the%GETCOL function call, if this is possible, causing the access path to change. Thisapproach can avoid the building of another index, which would require DB2 bufferresources when it was being accessed.

Yet another approach would be to avoid the use of %GETCOL function callsentirely.

%SELECT is processed differently from %GETCOL. The SQL SELECT statementframework provided in a %SELECT function is not subjected to an EXPLAINrequest, and no information about the efficiency of the SQL SELECT statement ispassed back to the user. Of course, the dynamic SQL produced for the %SELECTstatement can still employ an inefficient access path. It is the responsibility of theDBA to use the tools available (for example, EXPLAIN(YES) during binding andsubsequent analysis of the PLAN_TABLE produced) to determine if the SELECTSQL statement created by the %SELECT statement executes efficiently.Related concepts

“User exits and efficiency”

User exits and efficiencyThis section discusses using user exits for the purpose of increasing the efficiencyof InfoSphere CDC. It does not present information on how to write user exits.

As noted in other parts of this section, user exits can be used to increaseInfoSphere CDC’s efficiency. This is in addition to the usual reason for using a userexit, the requirement of filtering rows or deriving data that cannot be accomplishedusing expressions or row filtering expressions. User exits can be employed toincrease efficiency by replacing multiple %GETCOL or %SELECT function calls inrow filtering expressions at the source environment, or in expressions at either thesource environment or the target environment.

To replace multiple %GETCOL and %SELECT function calls, the %USER functioncan be used instead of %GETCOL or %SELECT to invoke Static SQL This approachdoes not remove the responsibility for ensuring that the SQL coded within the%USER exit is effective and efficient. It is the responsibility of the DBA to use thetools available (for example, EXPLAIN(YES) during binding and subsequentanalysis of the PLAN_TABLE produced) to determine if the SELECT SQLstatement coded within the %USER exit executes efficiently.Related concepts

“InfoSphere CDC user exits” on page 165

DB2 performance considerations 141


Automatic restart and schema evolution

This section contains information about the support that is provided toautomatically restart subscriptions during InfoSphere CDC address space or DBMSinitialization. It also identifies the schema changes that end active InfoSphere CDCreplication.

In this section, you will learn:“Automatic restart”“Schema evolution” on page 145“Restarting replication” on page 145

Automatic restartPreviously, you had to manually restart continuous mirroring for a subscriptionafter a normal or abnormal termination. A better approach is to have subscriptionsrestart automatically so that continuous mirroring can resume without the need formanual intervention.

This section introduces the concept of persistency and how it is used toautomatically restart continuous mirroring.

See also:“Persistency”“Direct and indirect requests” on page 144“DB2 unavailability” on page 145

PersistencyPersistency is a subscription attribute that can be enabled or disabled. You mustenable this attribute for those subscriptions you want to restart after a normal orabnormal termination. To change the persistency attribute for a subscription, usethe CHCMTAUT utility.

Continuous mirroring for a persistent subscription can automatically restart inresponse to a normal or abnormal termination of the following:v InfoSphere CDC address space

For persistent subscriptions that were active or inactive when the terminationoccurred, continuous mirroring automatically restarts when the address spacereinitializes.However, persistent subscriptions that were terminated or became inactive as aresult of a direct request are not restarted automatically during address spaceinitialization.

v DBMSFor persistent subscriptions that were active when the termination occurred,continuous mirroring automatically restarts when the DBMS reinitializes.

v CommunicationsFor persistent subscriptions that were active when the termination occurred,continuous mirroring automatically restarts when communications arereestablished.


v Target serverFor persistent subscriptions that were active when the termination occurred,continuous mirroring automatically restarts when the subscription server isrestarted. In this case, automatic restart is only supported when InfoSphere CDCor Transformation Server for z/OS version 5.1.7 or higher is running on thetarget server.

When communications or the subscription server terminates, InfoSphere CDCattempts to automatically restart continuous mirroring for persistent subscriptionsat regular intervals. Attempts continue until an automatic restart is successful orthe persistent subscription or InfoSphere CDC address space is terminated. You canset how often InfoSphere CDC attempts to automatically restart continuousmirroring for all persistent subscriptions by modifying theAUTORESTARTINTERVAL configuration control statement keyword.

Persistency is only relevant to subscriptions that are used for continuous mirroring.If a persistent subscription is used for refresh or net change mirroring, thissubscription is restarted according to how the same subscription was terminatedthe last time it was used for continuous mirroring.

For nonpersistent subscriptions, you must manually restart continuous mirroring atthe correct point in the DB2 Log after normal or abnormal termination.

Note: You can now configure subscription persistency in Management Console.Existing processes should be migrated to Management Console since thiscommand will be discontinued in a future release.Related concepts

“CHCMTAUT Utility” on page 151“Direct and indirect requests”Related reference

“AUTORESTARTINTERVAL” on page 30

Direct and indirect requestsA direct request is a requested operation where subscription names are fully orpartially specified. For example, the following InfoSphere CDC console commandsare direct requests:

MODIFY <Address_Space_Name>,ENDTSMIR,SUBSCR=(PRODSUB),CNTRLD

MODIFY <Address_Space_Name>,ENDTSMIR,SUBSCR==(PR*),IMMED

In the first example, the full name of the subscription is specified. In the secondexample, the wildcard character is used to select all subscriptions that have namesstarting with the characters PR.

An indirect request is a requested operation where subscription names are not fullyor partially referenced. For example, the following InfoSphere CDC consolecommand is an indirect request:

MODIFY <Address_Space_Name>,ENDTSMIR,SUBSCR=ALL,CNTRLD

In the example, a predefined value (ALL) is used to reference all subscriptionsdefined in the InfoSphere CDC address space regardless of their names.


DB2 unavailabilityWhen access to DB2 has been lost (either through scheduled or unscheduledactivity), InfoSphere CDC sends a message to the SYSLOG and CHCPRINT SPOOLdata set to indicate that DB2 has shut down and that it is waiting for DB2 tobecome available. This message is also sent to the product administration log.When DB2 can be accessed again, another message is generated and sent to thesame destinations.

When DB2 shuts down (either through scheduled or unscheduled activity), activeInfoSphere CDC mirroring and refresh tasks are terminated. Apply tasks areterminated if they cannot be suspended after a DB2 shut down. When DB2 can beaccessed again, previously active InfoSphere CDC mirroring tasks for persistentsubscriptions are restarted automatically. You must manually restart InfoSphereCDC refresh tasks. You must also manually restart apply tasks if they were notsuspended and then resumed.

Schema evolutionIf a schema change is applied to a table during mirroring or before replication isstarted, InfoSphere CDC detects that change. Based on the type of schema change,replication is stopped or prevented from starting.

The following schema changes result in InfoSphere CDC preventing or stoppingactive replication for the affected table:v The table’s DATA CAPTURE CHANGES attribute has been disabled.v The table has been dropped from the database.v The table’s DBID, OBID or PSID has been changed.v A column in the table has been inserted, removed or renamed.

If a column is added to a table so that it is the last column in the table, activereplication continues. Active replication ends when a column is added in anyother position in the table.

v The data type of a column in the table has been changed.v The scale or length of a column in the table has been changed.

For other detected schema changes, InfoSphere CDC starts or continues datareplication from the affected table. When mirroring of a source table is stopped asa result of a schema change, active replication of other source tables under thesame subscription continues.

Restarting replicationIf a schema changes prevents replication from starting or continuing, you mustperform one or more of the following operations in Management Console beforestarting or restarting replication:v Update the source table definitions.v Remap the source table.v Perform a REORG of table space containing the source table.

If row updates and deletes are applied to the source table after the schema changeand before the definition update or REORG is performed, you must also refreshthe source table before restarting mirroring.

Automatic restart and schema evolution 145

For some schema changes, you do not have to perform all of the listed operations.If you require a specific procedure in response to a schema change, contact yourdatabase administrator or IBM representative for assistance.

For more information about updating table definitions, mapping and refreshingtables, see your Management Console documentation.

For information about table space reorganization, see the appropriate IBMpublication.


Bookmark viewer

This section contains information about submitting a batch job to displaybookmark information on a target environment.

In some situations, you may need to view precisely the progress of InfoSphereCDC’s scraping and applying activities for a subscription and retrieve exactinformation about the log position that is being processed on the targetenvironment. Also, in situations of failure, you may need to know the last commitgroup applied for the subscription so that you can set a log position on the sourceenvironment, if need be.

In the subscription environment, the last processed log position is indicated by avalue that identifies a position or entry in the source environment log. This valueis called a bookmark.

A batch program submitted on a target environment can display bookmarkinformation.

In this section, you will learn:“Submitting the CHCMDPRT batch job on a target environment”“Batch job result” on page 148“Sample bookmark viewer output” on page 148

Submitting the CHCMDPRT batch job on a target environment1. Modify the CHCMDPRT member in the SCHCCNTL data set.

This member is a JCL shell that you can use to submit the job that displaysbookmark information. If you decide to use the shell, a number of placeholdersidentified by angled brackets (< >) must be substituted with settings specific toyour environment.

2. In the member, perform the substitutions as described in the following table:

Substitution Placeholder Directions

High-level Qualifier(<CHC.HCHC540>)

Specify the high-level qualifier used for the InfoSphereCDC execution load library data set.

DB2 DSN Program LoadModule(DSNxxx.SDSNLOAD)

Specify the name of the data set containing the DB2 DSNprogram load module.

Metadata Cluster(<MetaDatacluster>)

Specify the name of the VSAM cluster containingInfoSphere CDC metadata that is not stored in DB2 tables.

This VSAM cluster is identified as a data set in theCHCMTDTA DD statement in the CHCPROC JCL forexecuting InfoSphere CDC.

DB2 Subsystem(<DB2Subsys>)

Specify the SSID (subsystem identifier) of the DB2subsystem containing the InfoSphere CDC metadata tables.


Substitution Placeholder Directions

DB2 Plan Suffix (<PlanSuffix>) Specify the two-character suffix identifying the DB2 planthat was bound to the InfoSphere CDC metadata tables inthe DB2 subsystem.

The plan suffix was specified during installation.

Source ID (<Source>) Specify the source identifier for which you want to viewbookmark information.

A source identifier lets you determine the source ofreplicated data. Bookmark information about one or moresources can be displayed.

Specify a source identifier or the following value:

v *—Display bookmark information for all sourceidentifiers defined in the InfoSphere CDC metadata.

Bookmark Only Indicator(<Y/N>)

Specify whether or not you want to display just bookmarkinformation or a comprehensive report containingbookmark information and other details about theidentified source environments.

Specify one of the following values:

v Y—Display just bookmark information for the identifiedsource environments.

v N—Display bookmark information and other detailsabout the identified source environments in acomprehensive report. For information about otherinformation in the report, see the comments provided inthe JCL shell.

Related concepts

“Customizing your InfoSphere CDC installation” on page 3

Batch job resultThe batch job returns one of the following results:v 0: The batch job completed successfully.v 4: The batch job completed, but warnings were generated.v 8 or higher: The batch job was unsuccessful. Errors were reported.

If a nonzero result is returned, examine output from the job to troubleshootproblems.

Sample bookmark viewer output

In addition to a result value, bookmark information is displayed, by default, on theoperator console. Sample output as a result of submitting the CHCMDPRT batchjob is shown below.

In addition to a result value, bookmark information is displayed to the fileallocated to the SYSPRINT Data Definition (DD) statement.Publication ATLANTA** No bookmark information available **

Publication BOSTON


Bookmarks: Bookmark timestamp 2006-01-23-14.05.39.114304Bookmark Journal Id TS53INT/DMCJRNLast Committed Position DMCJRN0005TS53INT 00000000000000000021Earliest Open Position DMCJRN0005TS53INT 00000000000000000021Last Applied Position DMCJRN0005TS53INT 00000000000000000021

Publication CHICAGOBookmarks: Bookmark timestamp 2006-02-06-14.28.05.050304

Bookmark Journal Id AD71Last Committed Position X'00000044ec5b7e0f'Earliest Open Position X'00000044ec243c89'Last Applied Position X'0000000000000000'

Publication DALLASBookmarks: Bookmark timestamp 2006-01-19-09.33.51.599747

Bookmark Journal Id AD71Last Committed Position X'0000004309cedb3d'Earliest Open Position X'0000004309ceda0d'Last Applied Position X'0000000000000000'

Publication SEATTLEBookmarks: Bookmark timestamp 2006-02-03-12.38.13.439088

Bookmark Journal Id AD71Last Committed Position X'00000044e33966dc'Earliest Open Position X'00000044e33869c3'Last Applied Position X'0000000000000000'

Total number of publications is 5.

Note: The number of bookmark positions displayed depends on your sourceenvironment database. InfoSphere CDC for Oracle (redo log edition) andInfoSphere CDC for IBM i source environments generate three bookmark positions.Other source environments may generate only one bookmark position.

The following table identifies and describes the bookmark information that can bereturned by the bookmark viewer.

Bookmark Information Description

Bookmark Timestamp The timestamp of the most recently scraped entry on the sourceenvironment.

Bookmark Journal Id The object on the source environment that contains the entries.

Last Committed Position The position of the last entry to be applied to the target tablethat has been confirmed. Confirmation means that the commitgroup containing the entry has been committed or the entryhas been processed.

Earliest Open Position The entry position marking the beginning of the oldest commitgroup that is still uncommitted or being rolled back.

Last Applied Position The position of the last entry applied to the target table.

Bookmark viewer 149


CHCMTAUT Utility

This section contains information about the utility that you can use to defineconfiguration settings outside of Management Console.

Most replication configuration activities require you to work with ManagementConsole after InfoSphere CDC software has been installed on source and targetservers. To facilitate configuration activities that are specific to InfoSphere CDC forz/OS and cannot be performed using Management Console, a utility is providedthat allows you to perform different operations through a set of commands.CHCMTAUT also allows you to interrogate current source environment and targetenvironment settings so that appropriate updates can be made through the utility.

In this section, you will learn:“Invoking the CHCMTAUT utility”“CHCMTAUT commands”

Invoking the CHCMTAUT utility

CHCMTAUT can be run in batch or as a TSO foreground application.

To invoke CHCMTAUT, adhere to the following format:

CHCMTAUT <db2_subsystem> [<plan_name>]

The first parameter (<db2_subsystem>), which is mandatory, identifies the name ofthe DB2 subsystem that contains the InfoSphere CDC metadata. The secondparameter (<plan_name>), which is optional, identifies the name of the plan to usewhen connecting to the subsystem. If the plan name is omitted, the default isCHCMTAUT.

CHCMTAUT commandsAfter invoking the CHCMTAUT utility, supported commands can be issued. Thecommand syntax may use one or more of the following notations:

Square brackets ([ ]): Identifies command parameters that do not have to bespecified. Mandatory parameters are not enclosed by square brackets.

Vertical bar ( | ): Identifies the list of command parameters or settings from whichone must be specified.

Brace brackets ({ }): Used to group one or more command parameters.

See also:“END” on page 152“HELP” on page 152“LIST” on page 152“LOADER” on page 153“PERSISTENCY” on page 155


“QUIT” on page 155“REFRESHISOLATION” on page 156“UCASE” on page 156“CLEAR” on page 157

END

Syntax END

Description Ends the CHCMTAUT utility.

After issuing this command, other CHCMTAUT commands thatare issued are not processed.

This command is the same as the QUIT command.

Settings None

HELP

Syntax HELP

Description Displays help information for the CHCMTAUT utility.

Settings None

LIST

Syntax LIST {PUBLSH(source_id) [TABLE(tbl)] | SUBSCR(sub)} [HELP]

Description Displays the current attributes for a source environment, targetenvironment, or one or more source tables.

Settings v PUBLSH( )

The name of the source environment in your replicationconfiguration for which attributes are displayed.

The identifier is used in the subscription environment todetermine the source of replicated data.

v TABLE( )

The name of the source table for which attributes are displayed.Note: This setting can only be specified when you want todisplay attributes of the source.

The owner of the source tables or the library where the tablesreside can precede the table name specification. To specifymultiple source tables, append the wildcard character (*) to thecommon part that appears at the beginning of the table names(for example, CUST* references the tables named CUST1,CUST2, and CUST3). Specify this setting multiple times if thetable names do not start with the same set of characters.

v SUBSCR( )

The name of the target environment in your replicationconfiguration for which attributes are displayed.

HELP Displays help information for the LIST command.

Examples LIST PUBLSH(HQSYS) TABLE(CUST1)

LIST SUBSCR(LA)


LOADER

Syntax LOADER PUBLSH(source_id) [TABLE(tbl)] {{USE(use) [PARMS(prm)]}| {[USE(use)] PARMS(prm)}} [HELP]

Description Defines DB2 LOAD utility settings for a source environment or one ormore tables.

Note that system-level DB2 LOAD settings are defined through theDB2LOADER configuration control statement.

These settings are overridden at the source environment and tablelevels when this command is used.

CHCMTAUT Utility 153


The name of the source environment that is affected by thiscommand.Note: If the TABLE setting is also specified, DB2 LOAD settings aredefined at the table level. The TABLE setting must be omitted if DB2LOAD settings are to be applied at the source environment level.

The source environment is identified by an identifier, which is usedin the target environment to determine the source of replicated data.

v TABLE( )

The name of the source table that is affected by this command.Note: If the TABLE setting is specified, DB2 LOAD settings are notalso applied at the source environment level. The TABLE setting hasto be omitted to apply DB2 LOAD settings at the sourceenvironment level.

The owner of the source tables or the library where the tables residecan precede the table name specification. To specify multiple sourcetables, append the wildcard character (*) to the common part thatappears at the beginning of the table names (for example, CUST*references the tables named CUST1, CUST2, and CUST3). Separateinvocations of this command are required if the table names do notstart with the same set of characters.

v USE ( )

Enables or disables use of DB2 LOAD to refresh data at the sourceenvironment or table level.


– SYSTEM—References the corresponding system or sourceenvironment level-setting that determines DB2 LOAD use. Thesource environment level setting is referenced when the TABLEsetting is specified. The system-level setting is referenced whenonly the PUBLSH setting is specified. Note that the system-levelsetting is defined through the USELOADER keyword in the DB2configuration control statement.

– YES—Enables use of DB2 LOAD at the source environment ortable level. DB2 LOAD settings identified through this commandare applied to the specified source environment or tables.

– NO—Disables use of DB2 LOAD at the source environment ortable level. The standard InfoSphere CDC refresh is used insteadof DB2 LOAD. Even though DB2 LOAD has been disabled,settings identified through this command are applied to thespecified source environment or tables.

If omitted, the system-level setting or the previous setting for thespecified source environment or table is used.

v PARMS( )

The two-character suffix of the CHCLDRxx member containing theDB2 LOAD settings that are applied to the specified sourceenvironment or tables.

Note that a suffix is specified for the CHCLDRxx member thatcontains the Configuration Control statement defining system-levelDB2 LOAD settings.

Specifying the same suffix means that the system-level DB2 LOADsettings are also used at the source environment or table level.Specifying a different suffix references a separate CHCLDRxxmember.

If omitted, the system-level setting or the previous setting for thespecified source environment or table is used.


HELP Displays help information for the LOADER command.

Examples LOADER PUBLSH(HQSYS) TABLE(CUST2*) USE(YES) PARMS(01)

LOADER PUBLSH(HQSYS) USE(SYSTEM)

Related concepts

“DB2LOADER” on page 65“Modifying DB2 LOAD configuration control statements” on page 65Related reference

“USELOADER” on page 64

PERSISTENCY

Syntax PERSISTENCY SUBSCR(target) [ON | OFF] [HELP]

Description Enables or disables persistency for the specified subscription.

A subscription can only be restarted automatically if it is enabledfor persistency.

Settings v SUBSCR( )

The name of the target environment in your replicationconfiguration for which attributes are displayed.

v ON | OFF

Indicates whether persistency is enabled or disabled for thespecified subscription.


– ON—Enables persistency for the subscription so that it can berestarted automatically during InfoSphere CDC address spaceor DBMS initialization.

– OFF—Disables persistency for the subscription. Thesubscription is not restarted automatically during InfoSphereCDC address space or DBMS initialization. This is the defaultsetting.

HELP Displays help information for the PERSISTENCY command.

Examples PERSISTENCY SUBSCR(LA) ON

Note: You can now configure subscription persistency in Management Console.Existing processes should be migrated to Management Console since thiscommand will be discontinued in a future release.Related concepts

“Persistency” on page 143

QUIT

Syntax QUIT

Description Ends the CHCMTAUT utility.

After issuing this command, other CHCMTAUT commands thatare issued are not processed. This command is the same as theEND command.

Settings None.


REFRESHISOLATION

Syntax REFRESHISOLATION PUBLSH(source_id) TABLE(tbl)ISOLATION(lvl) [HELP]

Description Defines the refresh isolation level for the specified table.

The refresh isolation level for a table determines how isolated theInfoSphere CDC data refresh process is from other applicationsthat modify the table. A high degree of isolation may be requiredto limit or prevent concurrent changes to the refreshed table byother applications.


The identifier for the source environment.

The source environment is identified by an identifier, which isused in the target environment to determine the source ofreplicated data.

v TABLE( )

The name of the source table for which the refresh isolation levelis defined.Note: You cannot specify the wildcard character (*) to identifymultiple source tables.

v ISOLATION( )

The refresh isolation level for the specified table.

The isolation levels are RR (Repeatable Read), RS (ReadStability), CS (Cursor Stability), and DEFAULT. The first threesettings are supported in DB2. For more information about thesesettings, consult the appropriate DB2 documentation thatcontains information about isolation levels.

If you specify DEFAULT, the refresh isolation level used will beas specified when the CHCDTR DB2 Plan was bound. Thecontrol statement for binding this DB2 Plan is contained in theCHCBNDPL job, and, as distributed, is set to CS (CursorStability). Changing the ISOLATION keyword in the BINDstatement in the CHCBNDPL job changes the refresh isolationlevel of all tables (subsequent invocations of theREFRESHISOLATION command overrides this change for thespecified tables).Note: While it is possible to change the value of theISOLATION keyword in the BIND statement for the CHCDTRDB2 Plan to UR (Uncommitted Read), you should not set thiskeyword in the BIND statement to UR. If this default isolationlevel is changed to UR, IBM cannot provide assistance on dataintegrity problems with the refreshed data.

HELP Displays help information for the REFRESHISOLATION command.

Example REFRESHISOLATION PUBLSH(HQSYS) TABLE(CUST3)ISOLATION(CS)

UCASE

Syntax UCASE


Description Toggles the treatment of lowercase characters that may be specifiedin other CHCMTAUT commands.

By default, CHCMTAUT treats all command input as uppercasecharacters. This can lead to problems when lowercase letters areused to specify names of source and target entities. Treating allcharacters as uppercase can be disabled with odd numbered uses(for example, first use, third use, and so on) of this command.Even numbered uses (for example, second use, fourth use, and soon) of this command reinstates the default behavior as describedabove.

Settings None.

CLEAR

Syntax CLEAR

Description Clears the screen when CHCMTAUT is running under TSO.

Settings None



Supported DB2 for z/OS data types

This section identifies the DB2 for z/OS data types that InfoSphere CDC canreplicate. It also identifies the supported mappings.

In this section, you will learn:“Supported data types”“Supported mappings”

Supported data types

The following DB2 for z/OS data types can be replicated by InfoSphere CDC:v BIGINTv CHAR (for BIT, MIXED, SBCS)v DATEv DECIMALv FLOATv GRAPHICv INTEGERv ROWIDv SMALLINTv TIMEv TIMESTAMPv VARCHAR (for BIT, MIXED, SBCS)v VARGRAPHIC

Note: InfoSphere CDC running on a source or target does not support thereplication of large object (LOB) data.

Supported mappingsInfoSphere CDC provides a variety of mappings for supported DB2 for z/OS datatypes.

See also:“Numeric types”“Character types” on page 160“Date and time types” on page 160“DBCS types” on page 160“Row Identifier types” on page 160

Numeric types

Published Data Types Supported Mappings

DECIMAL Any numeric, or binary data type

FLOAT Any numeric or binary data type



INTEGER Any numeric or binary data type

SMALLINT Any numeric or data type

Character types


CHAR (for BIT) Any character, variable character, or binarydata type

CHAR (for MIXED) Any character, variable character, or binarydata type

CHAR (for SBCS) Any character, variable character, or binarydata type

VARCHAR (for BIT) Any character, variable character, or binarydata type

VARCHAR (for MIXED) Any character, variable character, or binarydata type

VARCHAR (for SBCS) Any character, variable character, or binarydata type

Date and time types


DATE Any date, time, or timestamp data type

TIME Any date, time, or timestamp data type

TIMESTAMP Any date, time, or timestamp data type

DBCS types


GRAPHIC Any graphic, vargraphic, character or binarydata type

VARGRAPHIC Any graphic, vargraphic, character or binarydata type

Row Identifier types


ROWID Any ROWID or binary data type


Management Console tutorial tables

This section contains information about defining the sample DB2 tables that arereferenced in the Management Console tutorial.

Note: If you do not intend to work with the sample tables for the ManagementConsole tutorial, you can ignore the following information.

To help you become familiar with Management Console, a tutorial has beencreated that can be used with all supported InfoSphere CDC products. Throughthis tutorial, important concepts are introduced. In addition, instructions areprovided for performing simple replication through Management Consoleinvolving sample DB2 tables. InfoSphere CDC provides the underlying support towork with these sample tables.

To work with the sample DB2 tables through the tutorial, they must be created andloaded. The distribution medium contains a job and data to accomplish thispurpose.

Member CHCBLTTL in the SCHCCNTL data set contains a job that creates thesample DB2 tables, and load them from data contained in the SCHCTTL SMP/ETarget Library. The CHCBLTTL job has several placeholders to be resolved. Most ofthe placeholders are the same as those used to modify the jobs required forinstalling InfoSphere CDC. Two of the placeholders are unique to the CHCBLTTLjob, and do not appear in any of the other jobs found in the SCHCCNTL data set.

One of these unique placeholders is the <TTLTBLSPC> placeholder. This placeholderappears only in the CHCBLTTL job to allow the installer to build the sample tablesin a DB2 table space other than the one containing the InfoSphere CDC metadatatables. It is important that the sample tables are not created in the same DB2table space that contains the InfoSphere CDC metadata tables. If they occupy thesame DB2 table space, then DB2 application deadlocks or failure of replicationactivities could result.

The other unique placeholder is the <TTLOwner> placeholder. This placeholder isused to specify the owner of the sample tables when they are created. The installerchooses the value of this placeholder. A unique placeholder has been supplied sothat the owner of the sample tables need not be the same as the owner of theInfoSphere CDC metadata tables.

Submit the job in the CHCBLTTL member, and examine the output after the jobcompletes execution. The output should indicate that a DB2 table space and threenew tables have been created, with the necessary indices, and loaded with datafrom the distributed SCHCTTL data set.Related concepts

“Customizing your InfoSphere CDC installation” on page 3



InfoSphere CDC metadata tables

This section identifies the tables that are being used by InfoSphere CDC for z/OSto maintain metadata representing your current replication configuration on az/OS system.

InfoSphere CDC for z/OS maintains a set of tables containing metadatarepresenting your current replication configuration. For various reasons, you maywant to back up these tables. However, you should not modify the contents ofthese tables unless requested to do so by your IBM representative.

In this section, you will learn:“Source environment metadata tables”“Target environment metadata tables”“General metadata tables” on page 164

Source environment metadata tablesv DMMD_JOURNAL_STATSv DMMD_SCHEMAv DMMD_SRC_DERIV_DEFv DMMD_TABLEv DMMD_TABLE_FIELDSv DMMD_TARGET_FIELDSv DMMD_TARGET_IDv DMMD_TARGET_TABLEv DMMD_USER_LOG

Target environment metadata tablesv DMMD_CONFAUDv DMMD_DERIV_DEFv DMMD_JRNL_STAT_TGTv DMMD_SOURCE_FIELDv DMMD_SOURCE_IDv DMMD_SOURCE_SERIALv DMMD_SQL_STMTv DMMD_SRC_ROW_IDv DMMD_TGT_TBL_ATTRv DMMD_TGT_TBL_MAPv DMMD_USER_EXIT_TGTv DMMD_VAL_TRANS


General metadata tablesv DMMD_AUTH_DBv DMMD_AUTH_SUBv DMMD_AUTH_TBLv DMMD_AUTH_USERv DMMD_CATLG_TBLv DMMD_USER_GROUPv PLAN_TABLE


InfoSphere CDC user exits

This section is intended for advanced users who are planning to invoke user exitprograms to enhance the standard data transformation functionality provided inInfoSphere CDC. Sample user exit programs are provided with InfoSphere CDC.

In this section, you will learn:“About table-level user exit and row-level user exit programs”“Working with table-level and row-level user exit programs” on page 166“About expression user exits” on page 180“Working with expression user exit programs” on page 182“About conflict resolution user exits” on page 192“Working with conflict resolution user exit programs” on page 193“Conflict resolution audit table” on page 206“About notifications user exits” on page 209“Working with Notifications user exit programs” on page 210

About table-level user exit and row-level user exit programsTable-level user exit and row-level user exit programs allow you to invokeuser-written programs to customize the standard database operations that areperformed by InfoSphere CDC in the target environment. User exit programs canbe invoked before or after a clear table, insert row, delete row, or update rowoperation. In addition, you can disable these operations and replace them byidentifying the user exit programs that are to be invoked when a clear, insert,delete, or update is received from the source environment.

See also:“Predefined entry data structures for table-level user exits and row-level userexits”“Load module specification in Management Console” on page 166“Sample table-level and row-level user exit programs” on page 166“Performance considerations” on page 166

Predefined entry data structures for table-level user exits androw-level user exits

When a user exit program is invoked, predefined data structures are passed to theprogram. These structures are used to pass information associated with the specifictable-level or row-level operation that caused the user exit program to be invoked.In addition, the user exit program can return information through the same datastructures so that it can be passed in subsequent calls. Therefore, these structuresmust be defined in each user exit program so that the information can berecognized and processed. Your user exit program can then reference specific itemsof information in the data structures.

A COBOL copy member describing the predefined data structures is contained inthe CHCUEXCB member of the SCHCCOB SMP/E target library. A C header filedescribing the predefined data structures is contained in the CHCUEXC6 member


of the SCHCH SMP/E target library. An Assembly Language copy member thatdescribes these data structures as DSECTs is contained in the CHCUEXA memberof the SCHCMAC SMP/E target library. .Related concepts

“Predefined entry data structures (table-level or row-level user exits)” on page 174

Load module specification in Management ConsoleFor each target table that you can work with in Management Console, you canspecify load modules for each user exit point. For more information, see yourManagement Console documentation.

Sample table-level and row-level user exit programsSample user exit programs are provided with InfoSphere CDC. You may want touse a sample program as a base from which you develop your user exit program.

For table-level user exits and row-level user exits, three sample user exit programsare provided with InfoSphere CDC, and are contained in the membersCHCSAMRL (located in the SCHCCOB SMP/E target library), CHCSAMCX(located in the SCHCC SMP/E target library) and CHCSAMAX (located in theSCHCASM SMP/E target library). The last two programs have been written fordata refresh only. For more information about replication methods, see yourManagement Console documentation.

The CHCSAMRL member contains a COBOL program that replaces InfoSphereCDC’s standard INSERT, UPDATE and DELETE operations against the tutorialCUSTOMER table during apply processing with similar operations using StaticSQL, and provides logic to recover from duplicate key and row-not-found errors.The CHCSAMCX member contains a C program that creates a summary tablewhile a detail table is being refreshed. The CHCSAMAX member contains anassembler program that supports data refresh to a flat (QSAM) file.

You can modify these sample user exit programs for your working environment.

Note: The sample user exits can be used as starting points to construct your ownuser exits. IBM is not responsible for any issues or errors caused by the use of thesample user exits and will not modify the user exits in any way to address theseissues or errors.

Performance considerationsWhen you invoke a user-written program at a defined exit point, it is important torealize that a call is issued each time a clear, delete, insert, or update operation isapplied to the target table. Therefore, when data replication activity is high, overallperformance is affected by the kind of actions that are implemented through thecode in the user-written programs.

As a result, your programs should be written with performance in mind. Theyshould be optimized as much as possible. In certain situations, you may decidethat invoking user-written programs at specific points is not feasible if overallperformance is adversely affected.

Working with table-level and row-level user exit programsSee also:


“Defining and invoking programs at the table-level user exit and row-level userexit points”“Writing table-level user exit programs and row-level user exit programs”“Running the DB2 precompiler” on page 172“Compiling and linking table-level user exit and row-level user exit programs”on page 172“Binding the Database Request Module (DBRM)” on page 173“Predefined entry data structures (table-level or row-level user exits)” on page174

Defining and invoking programs at the table-level user exitand row-level user exit points

The process of defining programs so that they can be invoked at table-level userexit and row-level user exit points is separated into the following steps that mustbe performed in the specified order:1. Writing table-level user exit and row-level user exit programs.2. Running the DB2 Precompiler.

Note: This step only needs to be performed when table-level user exit androw-level user exit programs contain one or more SQL statements.

3. Compiling and linking table-level user exit and row-level user exit programs.4. Binding the Database Request Module (DBRM).


5. Specifying table-level user exits and row-level user exits in ManagementConsole.

Related concepts

“Writing table-level user exit programs and row-level user exit programs”“Running the DB2 precompiler” on page 172“Compiling and linking table-level user exit and row-level user exit programs” onpage 172“Binding the Database Request Module (DBRM)” on page 173

Writing table-level user exit programs and row-level user exitprograms

Even though the sample user exit programs shipped with the product are writtenin COBOL, C and Assembly Language, programs can be written in any high-levellanguage that supports reentrant coding techniques and standard OS linkage anduses the z/OS Language Environment. The user exit programs must be compiledand link-edited to use AMODE 31 (31-bit addressing).

Table-level user exit and /row-level user exit programs must contain entry points(or external functions) that have the following names, according to their intendeduse:v BEFCLR (before clear)v AFTCLR (after clear)v BEFINS (before insert)v AFTINS (after insert)

InfoSphere CDC user exits 167

v BEFDEL (before delete)v AFTDEL (after delete)v BEFUPD (before update)v AFTUPD (after update)v BEFREF (before refresh)v AFTREF (after refresh)

It is not necessary to create all of these entry points, only those that need to beused should be coded. Note that these are not the names that are specified inManagement Console. Before or after a clear, insert, delete, update, or refreshoperation is performed, if the corresponding entry point exists, then it is called,and the code that you provided for the called entry point is executed. The entrypoints you provided are also called during the times that the subscription isstarting and stopping, as described below.

Before active replication begins during the subscription’s initialization, each entrypoint that you define in a user exit program is called with the CALLTYPE field ofthe USRDATA predefined structure set to “Initialize” (value 2). This allows eachentry point to provide code to obtain resources it will require, before anyreplication activities have started. Such initialization processing could includeobtaining virtual storage resources, opening a file, obtaining onetime informationfrom DB2 tables, and so on.

After active replication is complete during the subscription’s termination, eachentry point that you define in a user exit program is called with the CALLTYPEfield of the USRDATA predefined structure set to “Terminate” (value 3). Thisallows each entry point to provide code to release resources it required, after allreplication activities have ceased. Such termination processing could releaseobtained virtual storage, close an opened file, etcetera.

For CALLTYPE values of “Initialize” and “Terminate” (values 2 and 3), no rowdata (if applicable) is passed to the user exit program in the predefined datastructures.

While active replication is ongoing, each entry point that you define in a user exitprogram is called with the CALLTYPE field of the USRDATA predefined structureset to “Process” (value 1). This indicates that the user exit program is being calledfor its processing purpose, and that row data (if applicable) is being passed to theuser exit program in the predefined data structures.

It can be seen from the paragraphs above that each entry point is called at leasttwice. For instance, if an AFTDEL entry point is defined, it is called twice even ifthere were no deletes replicated between the times that the subscription wasstarted and stopped. You must provide code in each entry point for detecting andprocessing the “Initialize” and “Terminate” values of the CALLTYPE field of theUSRDATA predefined structure, otherwise the result will be unpredictable, and theuser exit program could abnormally terminate.

When a user exit program entry point completes its processing, it must pass back areturn code to InfoSphere CDC. This return code is the value returned by aprogram/function call. In the COBOL language, the return code is stored in theRETURN-CODE special register before the GOBACK statement for the program isexecuted. In C language, the return code is provided as the value of a returnstatement. In Assembly Language, the return code is provided as the value of theRC keyword in the RETURN macro instruction. The return code will cause


InfoSphere CDC to produce the defined responses as indicated in the followingtable:

Return Code Definition/Response

Before Exits After Exits

0 InfoSphere CDC continues normalprocessing.

InfoSphere CDC ignores any errorsfrom the SQL statement thatapplied the change, and replicationcontinues without any errorhandling by InfoSphere CDC.

4 Table-level and row-level operationsare bypassed, corresponding afterentry points will still be called ifthey were provided.

This return code is not valid forafter entry points.

8 InfoSphere CDC reports a minor error, and replication activities arestopped if the ENDONERROR keyword has been set to “YES” for thespecific replication activity (Refresh, Mirror, Audit).

12 InfoSphere CDC reports a severe error, and replication activities arestopped regardless of the ENDONERROR setting.

If the SQL apply statement (INSERT, UPDATE or DELETE) for the target table hasnot been disabled using Management Console, then the SQLCODE value returnedby these apply statements are passed to the after user exit programs (AFTINS,AFTUPD and AFTDEL) in the DBRTNCDE field of the USRDATA predefinedstructure. These after user exit programs can then affect the subsequent processingof an SQL error by InfoSphere CDC when they pass back their return code toInfoSphere CDC. Specifically, a return code of 0 will suppress InfoSphere CDC’sSQL error processing, a return code of 8 will allow error processing to proceednormally, and a return code of 12 will fail the subscription unconditionally.

User exit programs can also issue DB2 SQL statements themselves. Such SQLstatements must be issued through the standard DB2 High-level LanguageInterface. Programs that contain DB2 SQL statements must be prepared using theDB2 precompiler or the corresponding language’s SQL coprocessor (if available).

User exit programs cannot issue COMMIT or ROLLBACK SQL statements unlessthey are called with the CALLTYPE field of the USRDATA predefined structure setto “Terminate” (value 3). For any other value of CALLTYPE, an SQL COMMIT orROLLBACK statement issued from a table-level user exit or row-level user exit willbe intercepted by InfoSphere CDC and suppressed, and the SQLCODE valuereceived from the SQL COMMIT or ROLLBACK statement will be 0.

Table-level user exits and row-level user exits are called from the z/OS task thatimplements the InfoSphere CDC Apply process. For this reason, any changes madeto application data tables using SQL statements issued from within table-level userexits and row-level user exits will be committed or rolled back when InfoSphereCDC issues its SQL COMMIT or ROLLBACK statement for the commit group itwas applying when it called the table-level user exits and row-level user exits. Anychanges arising from SQL statements issued from within table-level user exits androw-level user exits will be in the same logical unit of work (LUoW) at the targetside as the changes that were passed to the user exits when they issued the SQLstatements.


Under certain detected deadlock or timeout conditions, DB2 will internallyROLLBACK a unit of work and indicate this to the issuer of the last SQL statementfor the unit of work by setting the SQLCODE to -911 or -913. When SQLstatements are issued from table-level user exits and row-level user exits, such anSQLCODE is intercepted by InfoSphere CDC and not presented to the table-leveluser exits and row-level user exits. Instead, an SQLCODE of 0 is presented.InfoSphere CDC will then recover from the ROLLBACK condition by reissuing allthe SQL in the current unit of work. In doing so, InfoSphere CDC will also recallany table-level user exits and row-level user exits for the changes being(re)applied. For this reason, it is not necessary to code logic in the user exitprograms to check for SQLCODE values of -911 or -913 being returned from anySQL statements, nor to provide the attendant logic to handle such SQLCODEvalues.

The USERDATA field in the USRDATA predefined structure is meant to be used bythe user exits as a common resource field. It is defined in COBOL as a POINTER,in C as a void *, and in Assembly Language as an A-con. Initially, when thesubscription starts, this field has all bits reset, which is equivalent to the POINTERvalue NULL/NULLS in COBOL or the pointer value NULL in C. The content ofthis field is never accessed or altered by InfoSphere CDC after the subscription hasstarted. The content of this field is passed to all the table-level user exits androw-level user exits for all tables within a subscription. Each table-level user exitand row-level user exit receives the contents of this field as they were when thepreviously called table-level user exit and row-level user exit returned control toInfoSphere CDC. The first table-level user exit and row-level user exit to receivecontrol for any table within the subscription can initialize the USERDATA field. Forexample, the first table-level user exit and row-level user exit to receive control canstore a pointer to acquired storage in this field, and the acquired storage can beused to convey data and communicate status to subsequent calls of any of theprovided table-level user exits and row-level user exits for all tables in thesubscription. It is the responsibility of the table-level user exits and row-level userexits to release any resources they acquire before a subscription ends.

Because all table-level user exits and row-level user exits are driven by the singletask that implements the Apply process for a subscription within InfoSphere CDC,the table-level user exits and row-level user exits will be driven consecutively, andno two table-level user exits and row-level user exits will ever receive controlconcurrently within the same subscription. This effectively enforces a serializationon the content of the USERDATA field, and any user exit can examine and modifythe content of the USERDATA field (or whatever data structure to which it points)without concern for serializing the accesses.

Any activity within a table-level user exits and row-level user exit that involves“blocking” services (for example, issuing a DB2 SQL statement), or suspendingexecution (for example, issuing an Assembly Language WAIT macro instruction),will suspend the entire Apply process, and delay the subscription. Try to designthe table-level user exits and row-level user exits to minimize or eliminate the useof such services.

Frequently, it may be desirable for a table-level user exit and row-level user exit togenerate a message describing a detected condition before it concludes. Forexample, a set of before insert, before update and before delete row-level user exitsthat implement pre-checking for and mitigation of operational errors (“row notfound” and “duplicate key”) may want to issue a message describing the stepsthey took to eliminate an operational error. Such a message would be somethinglike:


Operational Error avoided, UPDATE for key “1234” of CUSTOMER_ACCOUNT tablewas changed to an INSERT

A message of this nature should be associated with other messages from thesubscription in the event log. To achieve this, the USRMSG field of the USRDATApredefined structure can be used. Text for the message should be stored in theUSRMSG field. This text must not exceed 512 characters, and the first charactermust not be a blank character. Only valid graphic display characters that can beentered on a keyboard should be used and the USRMSG field should beblank-padded to the full 512 characters. This text will be used to issue a CHC0335Imessage with informational severity. This message will appear in the Event Log forthe subscription, and in the CHCPRINT spooled data set. The subscription willcontinue according to the specification of the return code, as described above.

table-level user exits and row-level user exits must be coded, compiled and linkedited as reentrant programs. This is generally as simple as specifying the RENToption for the compiler and the linkage editor. If an exit is written in AssemblyLanguage, specific design and coding accommodations are required to producereentrant code. If InfoSphere CDC loads a table-level user exit and row-level userexit and detects that it is not marked as reentrant by the linkage editor, theninitialization of the associated subscription will fail and the subscription willterminate. If a table-level user exit and row-level user exit is marked reentrant bythe linkage editor but is actually not executing according to the requirements ofreentrancy, then unexpected errors can result, including the failure of thetable-level user exit and row-level user exit, or corruption of the data being passedto the table-level user exit and row-level user exit.

During development and testing, and sometimes during production execution,user-written table-level user exits and row-level user exits may experience errorconditions that result in an abnormal termination. For example, a table-level userexit and row-level user exit may attempt to store data into a virtual storage areausing a storage reference pointer, but inadvertently, the storage reference pointercontains the NULL pointer value. This will result in an ABEND S0C4 (GeneralProtection Fault). Normally, InfoSphere CDC intercepts all abnormal terminationsthat arise from within table-level user exits and row-level user exits. InfoSphereCDC then issues an explanatory message to the Event Log and CHCPRINTspooled output data set, and terminates the subscription that called the failingtable-level user exit and row-level user exit. Based on the Language Environmentoptions provided to the InfoSphere CDC address space, LE may produce adiagnostic printout of the intercepted error, or permit a dump of the address spaceat the time of the error to occur. It is also possible to specify LanguageEnvironment options that inhibit InfoSphere CDC from intercepting suchcatastrophic errors. In this case, the catastrophic error is elevated to InfoSphereCDC itself, and the entire InfoSphere CDC address space may fail. It is the yourresponsibility to locate and fix any errors in their table-level user exits androw-level user exits. Judiciously specified Language Environment options, coupledwith diagnostic tests and messages issued from within the table-level user exit androw-level user exit can be helpful in achieving this goal. The LanguageEnvironment options that disable the interception of abnormal terminations withinthe Language Environment enclave should not be used unless for a specific issueand in a controlled environment.


Related concepts

“Running the DB2 precompiler”Related reference

“USRDATA structure” on page 175“ENDONERROR” on page 35“CHC0335I” on page 302

Running the DB2 precompiler


If your table-level user exit and row-level user exit programs contain one or moreSQL statements, you have to take some measures to have the SQL statementsconverted to the language of the hosting program. In the past, DB2 provided aprogram called the DB2 Precompiler that was used for this purpose. Now DB2 alsoprovides compiler extension facilities, called SQL statement coprocessors, which areinvoked by the compiler during its execution to handle embedded SQL. SQLstatement coprocessors are available for COBOL, C, C++ and PL/I at the time ofthis writing. If you have access to the DB2 coprocessor for the language you usedto write your table-level user exits and row-level user exits and the compiler youwill use is able to work with the DB2 coprocessor, then go to the next section. Ifyou must use the DB2 precompiler, then consult the appropriate IBM manual formore information about using the DB2 precompiler.

Compiling and linking table-level user exit and row-level userexit programs

In this step, compile and link-edit the user exit programs.

User exits receive control as subordinate functions within InfoSphere CDC. Whenyou compile some languages, it is necessary to direct the compiler to produce amain program or a subprogram (subordinate function), in accordance with how theprogram will be used. For example, the IBM C compiler has a “START/NOSTART”option. “START” is specified if the C program will be called directly through JCLor from TSO, that is, as a “main”. “NOSTART: is specified if the C program will belink-edited into a load module and will only receive control when it is called bysome other program within the load module, that is, as a subordinate function.Where the language being used requires it, always direct the compiler to compileany user exits as subordinate functions, not as a main program. Failure to do socould significantly increase the cost of calling the user exit, or cause the user exit tofail when it is called.

As seen above, there are several types of table-level user exits and row-level userexits. If more than one of these user exits is required for all table mappings for asingle subscription, then, as laid out above, they can be written as separatefunctions within a single source file. Alternatively, each table-level user exit androw-level user exit can be a single function within its own source file, althoughthere may be little advantage to constructing them this way. In either case, theLink-editing step draws all the user exits for all table mappings in a singlesubscription into a single load module. The name for the load module is of yourchoosing, so long as it is unique and does not conflict with any names used byInfoSphere CDC (which all begin with “CHC”), DB2 (which all begin with “DSN”)or any z/OS system modules.


InfoSphere CDC supplies a module called CHCTEXIT (in the SCHCLOAD SMP/Etarget library). This module ties the different types of table-level user exits androw-level user exits together into a single unit. It must be link-edited with theoutput from the compiler, to produce an executable load module. In addition,CHCTEXIT must be defined as the entry point of the load module.

Note: The C compiler can be directed to produce an intermediate object textformat called XOBJ. This should be passed through the C prelinker to produceold-format OBJ text before link-editing the user exit. Alternatively, direct the Ccompiler to product Generalized Object File Format output by specifying the GOFFoption.

The following are the link-edit control statements necessary to produce a functionaltable-level user exit and row-level user exit://SYSLIN DD *CHANGE CHCCMPLV(CHCUEXL1)INCLUDE SYSLIB(CHCTEXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)/*

Replace:v <objmodule> with the name of the object module produced by the compiler. If

more than one object module is required, insert an additional INCLUDEstatement for each object module.

v <loadmodule> with the name of the load module that is produced from thelink-edit and is specified in Management Console. This name must not be thesame as any load module provided with InfoSphere CDC. To be certain of this,it is best not to use a load module name that starts with “CHC”.



When compiling and link-editing, respond to any errors or warnings that arereported. If you are working with the sample user exit programs provided withInfoSphere CDC, and you have not modified them, no errors or warnings shouldbe generated.

Note: User exit programs must be successfully compiled and link-edited beforeproceeding.

Binding the Database Request Module (DBRM)

Note: You only need to perform this step when user exit programs contain one ormore SQL statements.

In this step, bind the user exit’s DBRM that was created during precompilationwith the InfoSphere CDC CHCDTC DB2 plan (CHCDTC is a generic name). It isrecommended that any user exit DBRM’s be bound into a package using the DB2


BIND PACKAGE command. Using a package, rather than binding the user exitDBRM directly into the CHCDTC plan, allows the user exit to use its own valuesfor certain BIND parameters such as QUALIFIER and ENCODING. The packagecreated for the user exit can then be included in the BIND for plan CHCDTC usingthe PKLIST parameter. For BIND statements for all the InfoSphere CDC DB2 plans,refer to the CHCBNDPL member located in the SCHCCNTL SMP/E target library.Related concepts

“Running the DB2 precompiler” on page 172“Running the DB2 precompiler” on page 187“Running the DB2 precompiler” on page 197

Predefined entry data structures (table-level or row-level userexits)

Each user exit program must provide the necessary support to accept predefineddata structures containing information associated with the specific table-level orrow-level operation that caused the user exit program to be invoked. Since userexit programs can be written in different languages, a general description of fieldsin each structure is provided in the following sections:v USRDATA Structure (Table-level and row-level user exits)v Journal Record Header Structurev Table Structurev Column Structurev Key Structure

A COBOL copy member describing the predefined data structures is contained inthe CHCUEXCB member of the SCHCCOB SMP/E target library. A C header filedescribing the predefined data structures is contained in the CHCUEXC6 memberthat is located in the SCHCH SMP/E target library. An Assembly Language copymember that describes the predefined data structures as DSECTs is contained inthe CHCUEXA member that is located in the SCHCMAC SMP/E target library.

Where the various predefined data structures’ data fields can be preset withspecific, indicative values, the descriptive definitions for the specific languages usesymbolic definitions for these values. The CHCUEXCB COBOL copy membercontains 88-level symbols that define the indicative values. The CHCUEXC6 Cheader file contains manifest constants that define the indicative values. TheCHCUEXA Assembly Language copy member contains EQU(ate) statements thatdefine the indicative values. It is good programming practice to use these symbolicvalue representations and not the actual values in any language coding, so thatfuture changes to the assignments of the indicative values will not cause problemswith your user exits.

See also:“USRDATA structure” on page 175“Journal record header structure” on page 177“Table structure” on page 178“Column structure” on page 179“Key structure” on page 179


USRDATA structure

This structure contains different information about the table-level user exit androw-level user exit that caused the user exit program to be invoked. USRDATAcontains pointers to other predefined structures. Unless otherwise noted, allcharacter fields in this structure are in UTF-8, blank padded and NOT NULLterminated.

Field NameLength(bytes) Type Description

LABEL 8 Character An eye-catcher label for the structurecontaining the string “USRDATA6” inEBCDIC.

This field helps you to identify thisstructure in an address space dump.

SRCSYSID 8 Character The source system identifier.

EXITNAME 8 Character The name of the load module that isspecified in Management Console, inEBCDIC.

EXITTYPE 2 Integer The exit point where the user exit programwas invoked.

Possible values for a Table/Row level userexit:

1=After clear, 2=Before clear, 3=After delete,4=Before delete, 5=After insert, 6=Beforeinsert, 7=After update, 8=Before update11=Derived Expression %User exit

CALLTYPE 2 Integer The type of user exit call.

Possible values:

1=Process, 2=Initialize, 3=Terminate

USERDATA 4 Address Used to return data from the program thatcan be referenced in subsequentinvocations.

Data placed in this field is persistent acrossuser exit program invocations.

USRMSG 512 Character Used to return a message that is placed inthe Event Log.

RESERVED1 64 Character An area reserved for future expansion.

PFILE 4 Address A pointer to the structure containinginformation about the source and targettables.

IMGHDR 4 Address A pointer to the structure containinginformation about the journal record(NULL for deletes).

B4IMGSIZE 4 Integer The size of the before table record in bytes.

B4IMG 4 Address A pointer to the before table record (NULLfor inserts).

B4NULLINDSIZE 4 Integer The number of NULL fields in the beforetable record.



B4NULLIND 4 Address A pointer to an array that identifies theNULL fields in the before table record.

Possible values (in each array element):

0=Corresponding field is not NULL,1=Corresponding field is NULL

IMGSIZE 4 Integer The size of the after table record in bytes.

IMG 4 Address A pointer to the after table record (NULLfor deletes).

NULLINDSIZE 4 Integer The number of NULL fields in after tablerecord.

NULLIND 4 Address A pointer to an array that identifies theNULL fields in after table record.



TGTIMGSIZE 4 Integer The size of the target table record in bytes.

TGTIMG 4 Address A pointer to the target table record (NULLfor deletes).

TGTNULLINDSIZE 4 Integer The number of NULL fields in the targettable record.

TGTNULLIND 4 Address A pointer to an array that identifies theNULL fields in the target table record.



TGTKEYSIZE 4 Integer The size of the target table key in bytes.

TGTKEY 4 Address A pointer to the target table key (NULL forinserts).

REPLMETHOD 4 Integer Replication method in effect.

Possible values:

0=Mirroring, 1=Refresh, 2=Audit

DBRTNCDE 4 Integer For after user exit invocations, the SQLreturn code of the last row updateoperation. The content of this field isindeterminate for before user exitinvocations.

TGTKEYNULLINDSZ 4 Integer The number of NULL fields in the targettable key.

TGTKEYNULLIND 4 Address A pointer to an array that identifies theNULL fields in the target table key.






PPPARM 4 Address An area that is reserved for expression userexits.

Related reference

“Table structure” on page 178“Journal record header structure”

Journal record header structure

This structure contains information about the journal record, and is referenced bythe B4IMGHDR and IMGHDR fields in the USRDATA structure.

Field Name

Length(inbytes) Type Description

LABEL 8 Character An eye-catcher label for the structurecontaining the string “USRJRNL6” inEBCDIC.


JOCCID 8 UnsignedInteger

The relative record number of the starttransaction record in a commitment block.

JOCTRR 8 UnsignedInteger

The relative record number of the sourcetable record.

JOSEQN 8 UnsignedInteger

The sequence number of the journal record.

JOSEQN_BEF 8 UnsignedInteger

The sequence number of the before imagejournal record on an update.

JOCODE 1 Character The journal code for the record.

Possible values:

R=Record type record, U=Refresh typerecord

JOENTT 2 Character The entry type within the journal code.

Possible values:

PT=Insert, DL=Delete, UP=Update afterimage, RR=Refresh record

JOENTT_BEF 2 Character The entry type within the journal code for abefore image.

Possible values:

DL=Delete, UB=Update before image

JOJOB 30 Character The name of the job associated with thejournal record.

JONBR 10 Character The number of the job associated with thejournal record.


Field Name


JOUSER 30 Character The name of the user associated with thejournal record.

JOJRN 90 Character The name of the journal containing therecord.

JOJRNLIB 256 Character The name of the library where the journal islocated.

JOMBR 10 Character The name of the source member.

JOOBJ 256 Character The name of the source table.

JOPGM 30 Character The name of the program associated withthe journal record.

JOSYNM 30 Character The source system identifier.

JOTSTP 26 Character The timestamp associated with the journalrecord.

JOTSTP_BEF 26 Character The timestamp associated with the beforeimage journal record.

JOUSPF 30 Character The user profile associated with the journalrecord.

Table structure

This structure contains information about the source table (object) and the targettable (entity), and is referenced by the PFILE field in the USRDATA structure.

Field Name


LABEL 8 Character An eye-catcher label for the structurecontaining the string “USRFILE6” inEBCDIC.

This field helps you to identify this structurein an address space dump.

FILNME 256 Character The name of the source table.

FILLIB 256 Character The name of the library where the sourcetable is located.

TGTENTNME 128 Character The name of the target table.

TGTENTLIB 128 Character The owner of the target table.

TGTENTKEYNME 128 Character The name of the target table index.

TGTENTKEYLIB 128 Character The owner of the target table index.

PATR 4 Address A pointer to an array of structures containinginformation about each source and targetcolumn mapping.

PKEY 4 Address A pointer to an array of structures containinginformation about target key columns.

ATRCNT 2 Integer The number of columns in the target table.

KEYCNT 2 Integer The number of target table columns in thekey.


Field Name


TGTENTREPMTD 4 Integer The method of replication to the target table.

Possible values:

1=Mirror, 2=Refresh, 3=Audit

ASSIGNTYPE 4 Integer The type of the table mapping.

Possible values:

2=Standard, 3=Audit, 4=Summarization,5=One-to-One Consolidation, 6=One-to-ManyConsolidation, 7=Adaptive Apply

Related reference

“USRDATA structure” on page 175“Key structure”“Column structure”

Column structure

This structure contains information about a single column in a row image, and isreferenced by the PCOLUMN field of the Row Image structure.

Field Name


PNAME 4 Address A pointer to the name of the column

LENGTHORNULL 4 Integer An integer containing the length of the datain the column. Will contain negative 1 (-1) ifthe column value is NULL.

ALLOCATEDLEN 4 Integer An integer containing the number of bytesallocated to hold the column data. May belarger than the length of the actual data valuein the column.

PDATA 4 Address A pointer to the column data. Usually aNULL terminated character string.

Related reference

“Table structure” on page 178

Key structure

This structure contains information about key columns. The PKEY field in the tablestructure points to an array that contains one of more instances of the followingstructure.


Field Name


LABEL 8 Character An eye-catcher label for the structurecontaining the string “USRKEY6” inEBCDIC.


ATRKEYSEQ 2 Integer The sequence number of the columnin the key.

ATRNO 2 Integer The index in the column arrayidentifying the structure that containsinformation about the key column.

The column array is addressed by thePATR field in the table structure.

RESERVED1 4 Integer An area reserved for futureexpansion.

Related reference

“Table structure” on page 178“Column structure” on page 179

About expression user exitsWhen defining an expression in Management Console, the set of column functionsthat are provided by InfoSphere CDC may not be sufficient to perform certainoperations that are required in your working environment. To address this issue, acolumn function is provided that you can use to invoke a user exit program fromwithin an expression. User exit programs provide a way to define the operationsthat you want to perform through programming logic. Such programs shouldreturn a result, and can also return to InfoSphere CDC a code that indicateswhether or not the user exit invocation was successful. Based on the return code,InfoSphere CDC operations continue or end.

See also:“The %USER function”“Predefined entry data structures for expression user exits” on page 181“Sample expression user exit programs” on page 181“Performance considerations” on page 182

Related concepts

“Writing expression user exit programs” on page 183

The %USER functionThe %USER function allows you to call a user exit program from within anexpression. The name of the program you want to call and the input parametersthat you want to pass is specified in the %USER function call.

Since the %USER function is contained in expressions specified in ManagementConsole, the called user exit program should return a result to the expression. Inthe user exit program, the first position of a predefined array is reserved fordefining the result of the user exit program call that is returned to the expression.


In addition, the user exit program can return a code to determine whether or notInfoSphere CDC operations continue after the user exit program call.

For more information about the %USER function, see your Management Consoledocumentation.Related concepts

“Predefined entry data structures for expression user exits”

Predefined entry data structures for expression user exitsFor each input parameter specified in the %USER invocation, different attributes ofthe parameter are passed to the named program, along with the actual value of theparameter. In order to receive these attributes in a user exit program, a predefineddata structure has been created that identifies the specific attributes that arepassed. In the user exit program, the code that you provide must accept an arrayof up to 21 pointers. The first pointer addresses the data structure that is used toreturn a result back to the %USER function in Management Console. The other 20pointers reference the same data structure and are reserved for each inputparameter specified in the %USER invocation (a maximum of 20 input parameterscan therefore be specified in a %USER function call). When returning a value, it isimportant to note that the same attributes associated with each input parameter(data type, length, and so on) must also be specified in the user exit program forthe returned value (the first pointer in array).

A COBOL copy member describing the predefined data structures is contained inthe CHCUEXCB member of the SCHCCOB SMP/E target library. A C header filedescribing the predefined data structures is contained in the CHCUEXC6 memberof the SCHCH SMP/E target library. An Assembly Language copy member thatdescribes these data structures as DSECTs is contained in the CHCUEXA memberof the SCHCMAC SMP/E target library.Related reference

“USRDATA structure (Expression user exits)” on page 190“XVAR input result parameter structure” on page 191

Sample expression user exit programsSample user exit programs are provided with InfoSphere CDC. You may want touse a sample program as a base from which your develop your user exit program.

For expression user exits, six sample user exit programs are provided withInfoSphere CDC, and are contained in the members CHCSAMUX, CHCSAMHX,CHCSAMTT, CHCSAMTX and CHCSAMGX (located in the SCHCC SMP/E targetlibrary), and CHCSAMUB (located in the SCHCCOB SMP/E target library). Allmembers are located in the SMP/E target library SCHCC.

The CHCSAMUX member contains a C program that converts an integer to its textequivalent. For example, if a value of 453 is passed to the program, then theprogram returns ″four hundred fifty three″.

The CHCSAMHX member contains a C program that converts data of any type tohexadecimal format and returns the result as a character string. For example, if aninteger value of 65535 in a 32-bit fixed point binary field is passed to the program,the result that is returned is ″0000FFFF″. If an EBCDIC character value of ″65535″ ispassed to the program, then the program returns ″F6F5F5F3F5″.


The CHCSAMTT member contains a C program that searches a CHAR-type dataitem for the presence of one or more text strings, and returns an indication of whatit found. Where more than one text string is provided, the user exit can be directedto logically AND or OR the presence of the text strings in order to determine if theCHAR-type data passes or fails the examination.

The CHCSAMTX member contains a C program that returns the current date, time,or timestamp. Up to two optional offsets (one for days and the other for hours) canbe specified to return a date, time, or timestamp relative to the current value. Forexample, if the date format (*ISODATE) and a single offset of 7 (days) are passedto the program, the date that is returned is the current date plus seven days. If thetimestamp format (*ISOTMST) and the offsets 21 (days) and –12 (hours) are passedto the program, then the program returns the current timestamp plus 21 days, andminus 12 hours.

The CHCSAMGX member contains a C program that returns the name of a bankbranch from the tutorial tables. This sample program illustrates the use of SQLstatements in a user exit program. In this case, SQL statements retrieve the namefrom a table through the use of a foreign key.

The CHCSAMUB member contains a COBOL program that accepts a packeddecimal key value and uses it to index an existing table in order to return thecorresponding value in an integer column.

You can modify these sample user exit programs for your working environment.

Note: The sample user exits can be used as starting points to construct your ownuser exits. IBM is not responsible for any issues or errors caused by the use of thesample user exits and will not modify the user exits in any way to address theseissues or errors.

Performance considerationsA user exit program can be invoked from within an expression or row filteringexpression. If %USER is included in an expression, the user exit program specifiedin the %USER invocation is called a number of times during refresh and mirroringoperations. Therefore, when data replication activity is high, overall performance isaffected by the kind of actions that are implemented through the code in the userexit programs.

As a result, your programs should be written with performance in mind. Theyshould be optimized as much as possible. In certain situations, you may decidethat invoking user exit programs at specific points is not feasible if overallperformance is adversely affected.

Working with expression user exit programsSee also:

“Defining and invoking user exit programs within an expression” on page 183“Writing expression user exit programs” on page 183“Running the DB2 precompiler” on page 187“Compiling and linking expression user exit programs” on page 187“Binding the Database Request Module (DBRM)” on page 173“Predefined entry data structures” on page 189


Defining and invoking user exit programs within anexpression

The process of defining programs so that they can be invoked from within anexpression in Management Console is separated into the following steps that mustbe performed in the specified order:1. Writing Expression User Exit Programs.2. Running the DB2 Precompiler.

Note: This step only needs to be performed when expression user exitprograms contain one or more SQL statements.

3. Compiling and Linking Expression User Exit Programs.4. Binding the Database Request Module (DBRM).

Note: This step only needs to be performed when expression user exitprograms contain one or more SQL statements.

5. Specifying %USER in Management Console.Related concepts

“Writing expression user exit programs”“Running the DB2 precompiler” on page 187“Binding the Database Request Module (DBRM)” on page 173Related reference

“Compiling and linking expression user exit programs” on page 187

Writing expression user exit programsUser exit programs must be IBM Language Environment compliant, and usereentrant coding techniques and standard OS linkage. The expression user exitsmust be compiled and link-edited to use AMODE 31 (31-bit addressing).

Before active replication begins during the subscription’s initialization, eachexpression user exit program is called with the CALLTYPE field of the USRDATApredefined structure set to “Initialize” (value 2). This allows each entry point toprovide code to obtain resources it will require, before any replication activitieshave started. Such initialization processing could include obtaining virtual storageresources, opening a file, obtaining onetime information from DB2 tables, and soon.

After active replication is complete during the subscription’s termination, eachexpression user exit program is called with the CALLTYPE field of the USRDATApredefined structure set to “Terminate” (value 3). This allows each entry point toprovide code to release resources it required, after all replication activities haveceased. Such termination processing could release obtained virtual storage, close anopened file, etcetera.

For CALLTYPE values of “Initialize” and “Terminate” (values 2 and 3), no userparameters (if applicable) are passed to the user exit program in the XVARpredefined data structures.

While active replication is ongoing, each entry point that you define in anexpression user exit program is called with the CALLTYPE field of the USRDATApredefined structure set to “Process” (value 1). This indicates that the expression


user exit program is being called for its processing purpose, and that userparameters (if applicable) are being passed to the user exit program in the XVARpredefined data structures.

It can be seen from the paragraphs above that each entry point is called at leasttwice. For instance, if an expression user exit is specified in a %USER function ofan expression, it is called twice even if there were no changes replicated betweenthe times that the subscription was started and stopped. You must provide code inan expression user exit for detecting and processing the “Initialize” and“Terminate” values of the CALLTYPE field of the USRDATA predefined structure,otherwise the result will be unpredictable, and the expression user exit programcould abnormally terminate.

When an expression user exit completes its processing, in addition to the returnvalue that is returned through the first pointer, the user exit program that youwrite must pass back a return code to InfoSphere CDC. This return code is thevalue returned by a program/function call. In the COBOL language, the returncode is stored in the RETURN-CODE special register before the GOBACKstatement for the program is executed. In C language, the return code is providedas the value of a return statement. In Assembly Language, the return code isprovided as the value of the RC keyword in the RETURN macro instruction.InfoSphere CDC recognizes the following return codes and responds as indicatedin the following table:

User Exit ProgramCall Type (CALLTYPEValue) Return Code Definition/Response

Process (1) 0 The user exit program processing call wassuccessful. InfoSphere CDC continues normalprocessing.

8 InfoSphere CDC reports a minor error.

If the expression containing the %USER functionis processed in the target environment, replicationactivities are stopped if the ENDONERRORparameter has been set to “YES” for the specificreplication activity (Refresh, Mirror, Audit).

If the expression containing the %USER functionis processed in the source environment,replication activities are stopped unconditionally.

12 InfoSphere CDC reports a severe error, andreplication activities are stopped.

Initialize (2) 0 The user exit program initialization call wassuccessful. InfoSphere CDC continues normalprocessing.

Nonzero value An error was encountered during the user exitinitialization call. InfoSphere CDC reports theerror, and replication activities are not started.

Terminate (3) 0 The user exit program termination call wassuccessful. InfoSphere CDC continues normalprocessing.

Nonzero value An error was encountered during the user exittermination call. InfoSphere CDC reports theerror, but due to the type of call, normalprocessing continues.


User exit programs can also issue DB2 SQL statements. Such SQL statements mustbe issued through the standard DB2 High-level Language Interface. Programs thatcontain DB2 SQL statements must be prepared using the DB2 precompiler or thecorresponding language’s SQL coprocessor (if available).

User exit programs cannot issue COMMIT or ROLLBACK SQL statements unlessthey are called with the CALLTYPE field of the USRDATA predefined structure setto “Terminate” (value 3). For any other value of CALLTYPE, an SQL COMMIT orROLLBACK statement issued from a expression user exit will be intercepted byInfoSphere CDC and suppressed, and the SQLCODE value received from the SQLCOMMIT or ROLLBACK statement will be 0.

Expression user exits that are coded within row filtering expressions or withinsource expressions are called from the z/OS task that implements the InfoSphereCDC Logical Scrape process. Since no changes are made to application tables at thesource side, there can be no expectation of a COMMIT or ROLLBACK being issuedby InfoSphere CDC at the source side, and any SQL statements issued from withinexpression user exits called on the source side may never be committed. It isimproper to code any SQL statements that actually change application data tablesin expression user exits called on the source side of a subscription. SQL statementsthat query application data can be coded.

Expression user exits that are coded within an expression on the target side arecalled from the z/OS task that implements the InfoSphere CDC Apply process. Forthis reason, any changes made to application data tables using SQL statementsissued from within expression user exits will be committed or rolled back whenInfoSphere CDC issues its SQL COMMIT or ROLLBACK statement for the commitgroup it was applying when it called the table-level user exits and row-level userexits. Any changes arising from SQL statements issued from within table-level userexits and row-level user exits will be in the same logical unit of work (LUoW) atthe target side as the changes that were passed to the user exits when they issuedthe SQL statements.

Under certain detected deadlock or timeout conditions, DB2 will internallyROLLBACK a unit of work and indicate this to the issuer of the last SQL statementfor the unit of work by setting the SQLCODE to -911 or -913. When SQLstatements are issued from expression user exits, such an SQLCODE is interceptedby InfoSphere CDC and not presented to the expression user exits. Instead, anSQLCODE of 0 is presented. InfoSphere CDC will then recover from theROLLBACK condition by reissuing all the SQL in the current unit of work. Indoing so, InfoSphere CDC will also recall any expression user exits for the changesbeing (re)applied. For this reason, it is not necessary to code logic in the user exitprograms to check for SQLCODE values of -911 or -913 being returned from anySQL statements, nor to provide the attendant logic to handle such SQLCODEvalues.

The USERDATA field in the USRDATA predefined structure is meant to be used bythe user exits as a common resource field. It is defined in COBOL as a POINTER,in C as a void *, and in Assembly Language as an A-con. Initially, when thesubscription starts, this field has all bits reset, which is equivalent to the POINTERvalue NULL/NULLS in COBOL or the pointer value NULL in C. The content ofthis field is never accessed or altered by InfoSphere CDC after the subscription hasstarted. The content of this field is passed to all the user exits for all tables within asubscription. Each user exit receives the contents of this field as they were when


the previously called user exit returned control to InfoSphere CDC. The first userexit to receive control for any table within the subscription can initialize theUSERDATA field. For example, the first user exit to receive control can store apointer to acquired storage in this field, and the acquired storage can be used toconvey data and communicate status to subsequent calls of any of the providedexpression user exits for all tables in the subscription. It is the responsibility of theuser exits to release any resources they acquire before a subscription ends.

Because all expression user exits are driven by the single task that implements theScrape or Apply process for a subscription within InfoSphere CDC, the expressionuser exits will be driven consecutively, and no two expression user exits will everreceive control concurrently within the same subscription. This effectively enforcesa serialization on the content of the USERDATA field, and any user exit canexamine and modify the content of the USERDATA field (or whatever datastructure to which it points) without concern for serializing the accesses.

Any activity within an expression user exit that involves “blocking” services (forexample, issuing a DB2 SQL statement), or suspending execution (for example,issuing an Assembly Language WAIT macro instruction), will suspend the entireScrape or Apply process, and delay the subscription. Try to design the expressionuser exits to minimize or eliminate the use of such services.

Frequently, it may be desirable for a table-level user exit and row-level user exit togenerate a message describing a detected condition before it concludes. Forexample, a set of before insert, before update and before delete row-level user exitsthat implement prechecking for and mitigation of operational errors (“row notfound” and “duplicate key”) may want to issue a message describing the stepsthey took to eliminate an operational error. Such a message would be somethinglike:

Operational Error avoided, UPDATE for key “1234” of CUSTOMER_ACCOUNT tablewas changed to an INSERT

A message of this nature should be associated with other messages from thesubscription in the event log. To achieve this, the USRMSG field of the USRDATApredefined structure can be used. Text for the message should be stored in theUSRMSG field. This text must not exceed 512 characters, and the first charactermust not be a blank character. Only valid graphic display characters that can beentered on a keyboard should be used and the USRMSG field should beblank-padded to the full 512 characters. This text will be used to issue a CHC0335Imessage. This message will appear in the Event Log for the subscription, and inthe CHCPRINT spooled data set. The subscription will continue according to thespecification of the return code, as described above.

Expression user exits must be coded, compiled and link-edited as reentrantprograms. This is generally as simple as specifying the RENT option for thecompiler and the linkage editor. If an exit is written in Assembly Language,specific design and coding accommodations are required to produce reentrantcode. If InfoSphere CDC loads a expression user exit and detects that it is notmarked as reentrant by the linkage editor, then initialization of the associatedsubscription will fail and the subscription will terminate. If a expression user exitis marked reentrant by the linkage editor but is actually not executing according tothe requirements of reentrancy, then unexpected errors can result, including thefailure of the expression user exit, or corruption of the data being passed to theexpression user exit.


During development and testing, and sometimes during production execution,user-written expression user exits may experience error conditions that result in anabnormal termination. For example, an expression user exit may attempt to storedata into a virtual storage area using a storage reference pointer, but inadvertently,the storage reference pointer contains the NULL pointer value. This will result inan ABEND S0C4 (General Protection Fault). Normally, InfoSphere CDC interceptsall abnormal terminations that arise from within expression user exits. InfoSphereCDC then issues an explanatory message to the Event Log and CHCPRINTspooled output data set, and terminates the subscription that called the failingexpression user exit. Based on the Language Environment options provided to theInfoSphere CDC address space, LE may produce a diagnostic printout of theintercepted error, or permit a dump of the address space at the time of the error tooccur. It is also possible to specify Language Environment options that inhibitInfoSphere CDC from intercepting such catastrophic errors. In this case, thecatastrophic error is elevated to InfoSphere CDC itself, and the entire InfoSphereCDC address space may fail. It is the your responsibility to locate and fix anyerrors in their expression user exits. Judiciously specified Language Environmentoptions, coupled with diagnostic tests and messages issued from within theexpression user exit can be helpful in achieving this goal. The LanguageEnvironment options that disable the interception of abnormal terminations withinthe Language Environment enclave should not be used unless for a specific issueand in a controlled environment.Related concepts

“About expression user exits” on page 180“Running the DB2 precompiler”Related reference

“USRDATA structure (Expression user exits)” on page 190“CHC0335I” on page 302


Note: This step only needs to be performed when expression user exit programscontain one or more SQL statements.

If your expression user exit programs contain one or more SQL statements, youhave to take some measures to have the SQL statements converted to the languageof the hosting program. In the past, DB2 provided a program called the DB2precompiler that was used for this purpose. Now DB2 also provides compilerextension facilities, called SQL statement coprocessors, which are invoked by thecompiler during its execution to handle embedded SQL. SQL statementcoprocessors are available for COBOL, C, C++ and PL/I at the time of this writing.If you have access to the DB2 coprocessor for the language you used to write yourexpression exit and the compiler you will use is able to work with the DB2coprocessor, then go to the next section. If you must use the DB2 precompiler, thenconsult the appropriate IBM manual for more information about using the DB2precompiler.

Compiling and linking expression user exit programs


User exits receive control as subordinate functions within InfoSphere CDC. Whenyou compile some languages, it is necessary to direct the compiler to produce amain program or a subprogram (subordinate function), in accordance with how the


program will be used. For example, the IBM C compiler has a “START/NOSTART”option. “START” is specified if the C program will be called directly through JCLor from TSO ( in other words, as a “main”). “NOSTART: is specified if the Cprogram will be link-edited into a load module and will only receive control whenit is called by some other program within the load module (in other words, as asubordinate function). Where the language being used requires it, always direct thecompiler to compile any user exits as subordinate functions, not as a mainprogram. Failure to do so could significantly increase the cost of calling the userexit, or cause the user exit to fail when it is called.

The name for the load module is of your choosing, so long as it is unique and doesnot conflict with any names used by InfoSphere CDC (which all begin with“CHC”), DB2 (which all begin with “DSN”) or any z/OS system modules.

InfoSphere CDC supplies a module called CHCTEXIT (in the SCHCLOAD SMP/Etarget library). This module ties the different types of expression exit together intoa single unit. It must be link-edited with the output from the compiler, to producean executable load module. In addition, CHCTEXIT must be defined as the entrypoint of the load module.


The following are the link-edit control statements necessary to produce a functionalexpression user exit://SYSLIN DD *CHANGE CHCCMPLV(CHCUEXL1)INCLUDE SYSLIB(CHCTEXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)/*

Replace:v <objmodule> with the name of the object module produced by the compiler. If


v <loadmodule> with the name of the load module that is produced from thelink-edit and is specified in the %USER function call. This name must not be thesame as any load module provided with InfoSphere CDC. To be certain of this,it is best not to use a load module name that starts with “CHC:.








In this step, bind the user exit’s DBRM that was created during precompilationwith the InfoSphere CDC CHCDTC DB2 plan (CHCDTC is a generic name). It isrecommended that any user exit DBRM’s be bound into a package using the DB2BIND PACKAGE command. Using a package, rather than binding the user exitDBRM directly into the CHCDTC plan, allows the user exit to use its own valuesfor certain BIND parameters such as QUALIFIER and ENCODING. The packagecreated for the user exit can then be included in the BIND for plan CHCDTC usingthe PKLIST parameter. For BIND statements for all the InfoSphere CDC DB2 plans,refer to the CHCBNDPL member located in the SCHCCNTL SMP/E target library.Related concepts


Predefined entry data structuresEach user exit program must provide the necessary support to accept predefineddata structures containing information about the %USER function call that causedthe user exit program to be invoked. Since user exit programs can be written indifferent languages, a general description of the fields in each structure is providedin the following sections:v USRDATA Structure (Expression User Exits)v XVAR Input/Result Parameter Structure




“USRDATA structure (Expression user exits)”“XVAR input result parameter structure” on page 191

USRDATA structure (Expression user exits)

This structure contains different information about the expression user exit thatcaused the user exit program to be invoked. USRDATA contains a pointer toanother predefined structure that is described in the following section. Unlessotherwise noted, all character fields in this structure are in UTF-8, blank paddedand NOT NULL terminated.

Note: The same structure is used for table-level user exits and row-level user exits.For expression user exits, only a subset of the fields in the structure is used. Onlythe fields that are used are identified and described in the following table. Allother fields must also be defined in your programs, but they are initialized tozeroes (integer type fields), blank characters (character type fields) and NULL(address fields).

Field Name


LABEL 8 Character An eye-catcher label for the structurecontaining the string “USRDATA6”, inEBCDIC.




For expression user exits, this field contains11. Values from 1 to 8 inclusively are used todistinguish the different types of table-leveluser exits and row-level user exits.


Possible values:


USERDATA 4 Address Used to return data from the program thatcan be referenced in subsequent invocations.


USRMSG 512 Character Used to return a message that is placed inEvent Log.

PPARM 4 Address A pointer to an array of structures, whereeach structure contains information about a%USER input or result parameter.


Related concepts

“Writing expression user exit programs” on page 183“About expression user exits” on page 180Related reference

“USRDATA structure” on page 175“XVAR input result parameter structure”

XVAR input result parameter structure

This structure contains the attributes (data type, length, and so on) of an inputparameter that is passed to the user exit program identified through the %USERfunction. The same structure is used to define the attributes of the result returnedfrom the user exit program.

This section introduces and describes each field in the structure.

Field Name


DATATYP 2 Integer The type of data passed to or returned fromthe user exit program.

Possible values:

1=Character, 2=Date, 3=Double Float, 4=LongInteger, 5=Packed Decimal, 6=Time, 7=ZonedDecimal

DATALEN 2 Integer The length of the data passed through theparameter (in bytes).

DATADGT 2 Integer The number of digits in numerical datapassed through the parameter.

DATADEC 2 Integer The number of decimal places in numericaldata passed through the parameter.

NULLVAL 2 Integer Indicates whether the data passed though theparameter is NULL.

Possible values:

0=Data is not NULL, 1=Data is NULL.

DTMFMT 4 Character The format of date or time data passedthrough the parameter.

Possible values for times:

*USA=HH:MM AM/PM, *HMS=HH MM SS,*ISO=HH.MM.SS, *EUR=HH.MM.SS,*JIS=HH:MM:SS

Possible values for dates:

*ISO=CCYY/MM/DD, *JIS=CCYY/MM/DD,*USA=MM/DD/CCYY, *EUR=DD/MM/CCYY, *YMD=YY/MM/DD,*MDY=MM/DD/YY, *DMY=DD/MM/YY,*JUL=YY.DDD


Field Name


DATAVAL 2048 Character The data value passed as an input parameteror returned as a result of the user exitprogram invocation.

All input data is converted to character data,and the result of the user exit programinvocation is returned as character data,always in UTF-8 encoding.

About conflict resolution user exitsWhen a conflict is detected, you can resolve the conflict by invoking a customizeduser exit program. This program allows you to define a conflict resolution strategythat is not covered by one of the standard resolution methods (source wins, targetwins, largest value wins, or smallest value wins). The user exit program canresolve the conflict by returning a row that will be applied to the target table.

See also:“Predefined entry data structures for conflict resolution user exits”“Load module specification in Management Console” on page 166“Performance considerations for conflict resolution user exits”

Predefined entry data structures for conflict resolution userexits

When a user exit program is invoked, predefined data structures are passed to theprogram. These structures are used to pass information associated with the specificoperation conflict that caused the user exit program to be invoked. In addition, theuser exit program can return information through the same data structures so thatit can be passed in subsequent calls. Therefore, these structures must be defined ineach user exit program so that the information can be recognized and processed.Your user exit program can then reference specific items of information in the datastructures.

A COBOL copy member describing the predefined data structures is contained inthe CHCUEXCB member of the SCHCCOB SMP/E target library. C header filesdescribing the predefined data structures are contained in the CHCUEXC6 memberof the SCHCH SMP/E target library. An Assembly Language copy member thatdescribes these data structures as DSECTs is contained in the CHCUEXA memberof the SCHCMAC SMP/E target library.

Load module specification in Management ConsoleFor each target table that you can work with in Management Console, you canspecify load modules for each user exit point. For more information, see yourManagement Console documentation.

Performance considerations for conflict resolution user exitsWhen you invoke a user-written program at a defined exit point, it is important torealize that a call is issued each time a conflict is detected for the target table.


Therefore, when conflicts occur at a high rate, overall performance is affected bythe kind of actions that are implemented through the code in the user-writtenprograms.

As a result, your programs should be written with performance in mind. Theyshould be optimized as much as possible. In certain situations, you may decidethat invoking user-written programs is not feasible if overall performance isadversely affected.

Working with conflict resolution user exit programsSee also:

“Defining and invoking programs at the conflict resolution user exit points”“Writing conflict resolution user exit programs”“Running the DB2 precompiler” on page 197“Compiling and linking conflict resolution user exit programs” on page 197“Binding the Database Request Module (DBRM)” on page 173“Predefined entry data structures” on page 199

Defining and invoking programs at the conflict resolution userexit points

The process of defining programs so that they can be invoked at conflict resolutionuser exit points is separated into the following steps that must be performed in thespecified order:1. Writing conflict resolution user exit programs.2. Running the DB2 precompiler.

Note: This step only needs to be performed when conflict resolution user exitprograms contain one or more SQL statements.

3. Compiling and linking conflict resolution user exit programs.4. Binding the Database Request Module (DBRM).

Note: This step only needs to be performed when user exit programs containone or more SQL statements.

5. Specifying conflict resolution user exits in Management Console.Related concepts

“Writing conflict resolution user exit programs”“Running the DB2 precompiler” on page 197“Binding the Database Request Module (DBRM)” on page 173Related reference

“Compiling and linking conflict resolution user exit programs” on page 197

Writing conflict resolution user exit programsEven though the sample user exit programs shipped with the product are writtenin COBOL, C and Assembly Language, programs can be written in any high-levellanguage that supports reentrant coding techniques and standard OS linkage anduses the z/OS Language Environment. The user exit programs must be compiledand link-edited to use AMODE 31 (31-bit addressing).


Conflict Resolution user exit programs must contain an entry point (or externalfunction) that has the following name (Note that this is not the name that isspecified in Management Console):v CDRXIT

The entry point you provided is also called during the times that the subscriptionis starting and stopping, as described below.

Before active replication begins during the subscription’s initialization, the entrypoint that you define in a user exit program is called with the CALLTYPE field ofthe CDRDATA predefined structure set to ″Initialize″ (value 2). This allows eachentry point to provide code to obtain resources it will require, before anyreplication activities have started. Such initialization processing could includeobtaining virtual storage resources, opening a file, obtaining one-time informationfrom DB2 tables, and so on.

After active replication is complete during the subscription’s termination, the entrypoint that you define in a user exit program is called with the CALLTYPE field ofthe CDRDATA predefined structure set to ″Terminate″ (value 3). This allows eachentry point to provide code to release resources it required, after all replicationactivities have ceased. Such termination processing could release obtained virtualstorage, close an opened file, etcetera..

For CALLTYPE values of ″Initialize″ and ″Terminate″ (values 2 and 3), no conflictdata is passed to the user exit program in the predefined data structures.

While active replication is ongoing, the entry point that you define in your userexit program is called with the CALLTYPE field of the CDRDATA predefinedstructure set to ″Process″ (value 1). This indicates that the user exit program isbeing called for its processing purpose, and that conflict data is being passed to theuser exit program in the predefined data structures.

It can be seen from the paragraphs above that each entry point is called at leasttwice even if there are no conflicts detected between the times that the subscriptionis started and stopped. You must provide code for detecting and processing the″Initialize″ and ″Terminate″ values of the CALLTYPE field of the CDRDATApredefined structure, otherwise the result will be unpredictable, and the user exitprogram could abnormally terminate.

When a user exit program entry point completes its processing, it must pass back areturn code to InfoSphere CDC. This return code is the value returned by aprogram/function call. In the COBOL language, the return code is stored in theRETURN-CODE special register before the GOBACK statement for the program isexecuted. In C language, the return code is provided as the value of a returnstatement. In Assembly Language, the return code is provided as the value of theRC keyword in the RETURN macro instruction. The return code will causeInfoSphere CDC to produce the defined responses as indicated in the followingtable:

Return Code Definition/Response

0 InfoSphere CDC continues normal processing.

0 InfoSphere CDC reports a severe error, and replicationactivities are stopped regardless of the ENDONERRORsetting.


User exit programs can also issue DB2 SQL statements themselves. Such SQLstatements must be issued through the standard DB2 High-level LanguageInterface. Programs that contain DB2 SQL statements must be prepared using theDB2 precompiler or the corresponding language’s SQL coprocessor (if available).

User exit programs cannot issue COMMIT or ROLLBACK SQL statements unlessthey are called with the CALLTYPE field of the CDRDATA predefined structure setto ″Terminate″ (value 3). For any other value of CALLTYPE, an SQL COMMIT orROLLBACK statement issued from a conflict resolution user exit will beintercepted by InfoSphere CDC and suppressed, and the SQLCODE value receivedfrom the SQL COMMIT or ROLLBACK statement will be 0.

Conflict resolution user exits are called from the z/OS task that implements theInfoSphere CDC Apply process. For this reason, any changes made to applicationdata tables using SQL statements issued from within conflict resolution user exitswill be committed or rolled back when InfoSphere CDC issues its SQL COMMIT orROLLBACK statement for the commit group it was applying when it called theuser exit. Any changes arising from SQL statements issued from within conflictresolution user exits will be in the same logical unit of work (LUoW) at the targetside as the changes that were passed to the user exits when they issued the SQLstatements.

Under certain detected deadlock or timeout conditions, DB2 will internallyROLLBACK a unit of work and indicate this to the issuer of the last SQL statementfor the unit of work by setting the SQLCODE to -911 or -913. When SQLstatements are issued from conflict resolution user exits, such an SQLCODE isintercepted by InfoSphere CDC and not presented to the user exit. Instead, anSQLCODE of 0 is presented. InfoSphere CDC will then recover from theROLLBACK condition by reissuing all the SQL in the current unit of work. Indoing so, InfoSphere CDC will also recall any conflict resolution user exits for thechanges being (re)applied. For this reason, it is not necessary to code logic in theuser exit programs to check for SQLCODE values of -911 or -913 being returnedfrom any SQL statements, nor to provide the attendant logic to handle suchSQLCODE values.

The USERDATA field in the CDRDATA predefined structure is meant to be usedby the user exits as a common resource field. It is defined in COBOL as aPOINTER, in C as a void *, and in Assembly Language as an A-con. Initially, whenthe subscription starts, this field has all bits reset, which is equivalent to thePOINTER value NULL/NULLS in COBOL or the pointer value NULL in C. Thecontent of this field is never accessed or altered by InfoSphere CDC after thesubscription has started. The content of this field is passed to all the conflictresolution user exits for all tables within a subscription. Each conflict resolutionuser exit receives the contents of this field as they were when the previously calledconflict resolution user exit returned control to InfoSphere CDC. The first conflictresolution user exit to receive control for any table within the subscription caninitialize the USERDATA field. For example, the first conflict resolution user exit toreceive control can store a pointer to acquired storage in this field, and theacquired storage can be used to convey data and communicate status tosubsequent calls of any of the provided conflict resolution user exits for all tablesin the subscription. It is the responsibility of the conflict resolution user exits torelease any resources they acquire before a subscription ends.

Because all conflict resolution user exits are driven by the single task thatimplements the Apply process for a subscription within InfoSphere CDC, theconflict resolution user exits will be driven consecutively, and no two conflict


resolution user exits will ever receive control concurrently within the samesubscription. This effectively enforces a serialization on the content of theUSERDATA field, and any user exit can examine and modify the content of theUSERDATA field (or whatever data structure to which it points) without concernfor serializing the accesses.

Any activity within a conflict resolution user exit that involves ″blocking″ services(for example, issuing a DB2 SQL statement), or suspending execution (for example,issuing an Assembly Language WAIT macro instruction), will suspend the entireApply process, and delay the subscription. Try to design the conflict resolutionuser exits to minimize or eliminate the use of such services.

Frequently, it may be desirable for a conflict resolution user exit to generate amessage describing a detected condition before it concludes. For example, to issuea message describing the steps they taken to resolve the conflict. Such a messagemight be something like:Operational Error avoided, UPDATE for key "1234" of CUSTOMER_ACCOUNT table waschanged to an INSERT

A message of this nature should be associated with other messages from thesubscription in the event log. To achieve this, the USRMSG field of the CDRDATApredefined structure can be used. Text for the message should be stored in theUSRMSG field. This text must not exceed 512 characters, and the first charactermust not be a blank character. Only valid graphic display characters that can beentered on a keyboard should be used and the USRMSG field should beblank-padded to the full 512 characters. This text will be used to issue a CHC0335Imessage with informational severity. This message will appear in the Event Log forthe subscription, and in the CHCPRINT spooled data set. The subscription willcontinue or terminate according to the specification of the return code, as describedabove.

Conflict resolution user exits must be coded, compiled and link edited as reentrantprograms. This is generally as simple as specifying the RENT option for thecompiler and the linkage editor. If an exit is written in Assembly Language,specific design and coding accommodations are required to produce reentrantcode. If InfoSphere CDC loads a conflict resolution user exit and detects that it isnot marked as reentrant by the linkage editor, then initialization of the associatedsubscription will fail and the subscription will terminate. If a conflict resolutionuser exit is marked reentrant by the linkage editor but is actually not executingaccording to the requirements of reentrancy, then unexpected errors can result,including the failure of the conflict resolution user exit, or corruption of the databeing passed to the conflict resolution user exit.

During development and testing, and sometimes during production execution,user-written conflict resolution user exits may experience error conditions thatresult in an abnormal termination. For example, a conflict resolution user exit mayattempt to store data into a virtual storage area using a storage reference pointer,but inadvertently, the storage reference pointer contains the NULL pointer value.This will result in an ABEND S0C4 (General Protection Fault). Normally,InfoSphere CDC intercepts all abnormal terminations that arise from within conflictresolution user exits. InfoSphere CDC then issues an explanatory message to theEvent Log and CHCPRINT spooled output data set, and terminates thesubscription that called the failing conflict resolution user exit. Based on theLanguage Environment options provided to the InfoSphere CDC address space, LEmay produce a diagnostic printout of the intercepted error, or permit a dump ofthe InfoSphere CDC address space at the time of the error to occur. It is also


possible to specify Language Environment options that inhibit InfoSphere CDCfrom intercepting such catastrophic errors. In this case, the catastrophic error iselevated to InfoSphere CDC itself, and the entire InfoSphere CDC address spacemay fail. It is then your responsibility to locate and fix any errors in their conflictresolution user exits. Judiciously specified Language Environment options, coupledwith diagnostic tests and messages issued from within the conflict resolution userexit can be helpful in achieving this goal. The Language Environment options thatdisable the interception of abnormal terminations within the LanguageEnvironment enclave should not be used unless for a specific issue and in acontrolled environment.Related reference

“CDRDATA structure” on page 200“CHC0335I” on page 302


Note: This step only needs to be performed when conflict resolution user exitprograms contain one or more SQL statements.

If your conflict resolution user exit programs contain one or more SQL statements,you have to take some measures to have the SQL statements converted to thelanguage of the hosting program. In the past, DB2 provided a program called theDB2 precompiler that was used for this purpose. Now DB2 also provides compilerextension facilities, called SQL statement coprocessors, which are invoked by thecompiler during its execution to handle embedded SQL. SQL statementcoprocessors are available for COBOL, C, C++ and PL/I at the time of this writing.If you have access to the DB2 coprocessor for the language you used to write yourconflict resolution exit and the compiler you will use is able to work with the DB2coprocessor, then go to the next section. If you must use the DB2 precompiler, thenconsult the appropriate IBM manual for more information about using the DB2precompiler.

Compiling and linking conflict resolution user exit programs


User exits receive control as subordinate functions within InfoSphere CDC. Whenyou compile some languages, it is necessary to direct the compiler to produce amain program or a sub-program (subordinate function), in accordance with howthe program will be used. For example, the IBM C compiler has a″START/NOSTART″ option. ″START″ is specified if the C program will be calleddirectly through JCL or from TSO, that is, as a ″main″. ″NOSTART: is specified ifthe C program will be link-edited into a load module and will only receive controlwhen it is called by some other program within the load module, that is, as asubordinate function. Where the language being used requires it, always direct thecompiler to compile any user exits as subordinate functions, not as a mainprogram. Failure to do so could significantly increase the cost of calling the userexit, or cause the user exit to fail when it is called.

The name for the load module is of your choosing, so long as it is unique and doesnot conflict with any names used by InfoSphere CDC (which all begin with″CHC″), DB2 (which all begin with ″DSN″) or any z/OS system modules.

InfoSphere CDC supplies a module called CHCTEXIT (in the SCHCLOAD SMP/Etarget library). This module ties the different types of user exits together into a


single unit. It must be link-edited with the output from the compiler to produce anexecutable load module. In addition, CHCTEXIT must be defined as the entrypoint of the load module.


The following are the link-edit control statements necessary to produce a functionalexpression user exit://SYSLIN DD *CHANGE CHCCMPLV(CHCUEXL1)INCLUDE SYSLIB(CHCTEXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)/*

Replacev <objmodule> with the name of the object module produced by the compiler. If


v <loadmodule> with the name of the load module that is produced from thelink-edit and is specified in Management Console. This name must not be thesame as any load module provided with InfoSphere CDC. To be certain of this,it is best not to use a load module name that starts with ″CHC″.







In this step, bind the user exit’s DBRM that was created during precompilationwith the InfoSphere CDC CHCDTC DB2 plan (CHCDTC is a generic name). It isrecommended that any user exit DBRM’s be bound into a package using the DB2BIND PACKAGE command. Using a package, rather than binding the user exitDBRM directly into the CHCDTC plan, allows the user exit to use its own values


for certain BIND parameters such as QUALIFIER and ENCODING. The packagecreated for the user exit can then be included in the BIND for plan CHCDTC usingthe PKLIST parameter. For BIND statements for all the InfoSphere CDC DB2 plans,refer to the CHCBNDPL member located in the SCHCCNTL SMP/E target library.Related concepts


Predefined entry data structuresEach user exit program must provide the necessary support to accept predefineddata structures containing information associated with the specific conflictresolution operation that caused the user exit program to be invoked. Since userexit programs can be written in different languages, a general description of fieldsin each structure is provided in the following sections:v CDRDATA Structurev Conflict Detection Resolution (CDR) Control Structurev Row Image Structurev Column Structure



“CDRDATA structure” on page 200“Conflict Detection Resolution (CDR) control structure” on page 201“Row Image structure” on page 203“Column structure” on page 203


Related concepts

“Predefined entry data structures for conflict resolution user exits” on page 192Related reference

“CDRDATA structure”“Conflict Detection Resolution (CDR) control structure” on page 201“Row Image structure” on page 203“Column structure” on page 203

CDRDATA structure

This structure contains different information about the conflict resolution user exitthat caused the user exit program to be invoked. CDRDATA contains pointers toother predefined structures. Unless otherwise noted, all character fields in thisstructure are in UTF-8, blank padded and NOT NULL terminated.

Field Name


LABEL 8 Character An eye-catcher label for the structurecontaining the string “CDRDATA6” inEBCDIC.


SRCSYSID 8 Character The source system identifier.



Possible values for a Conflict Resolution UserExit:

16=Conflict Resolution exit


Possible values:


USERDATA 4 Address Used to return data from the program thatcan be referenced in subsequent invocations.



USRMSG 512 Character Used to return a message that is placed inthe Event Log.

PCONTROL 4 Address A pointer to the structure containinginformation about the conflict to be resolved.

PBEFOREIMG 4 Address A pointer to the structure containinginformation describing the Before image ofthe row with a detected conflict.


Field Name


PAFTERIMG 4 Address A pointer to the structure containinginformation describing the After image of therow with a detected conflict.

PTARGETIMG 4 Address A pointer to the structure containinginformation describing the Before image ofthe row with a detected conflict.

PDESIREDIMG 4 Address A pointer to the structure containinginformation describing the Desired image ofthe row with a detected conflict.


Related concepts

“Writing conflict resolution user exit programs” on page 193Related reference

“Row Image structure” on page 203

Conflict Detection Resolution (CDR) control structure

This structure contains information about the conflict detected in applying data tothe target table. It is referenced by the PCONTROL field in the CDRDATAstructure.

Field Name


REVISION 4 Integer An integer giving the version of the CDRuser exit interface.

Possible values:

1=Revision 1

PSRCSCHEMA 4 Address A pointer to the source schema name.

PSRCTABLE 4 Address A pointer to the source table name.

PSRCMEMBER 4 Address A pointer to the source member name.

PSRCTIMESTMP 4 Address A pointer to the timestamp from the sourcesystem

The referenced timestamp is a characterstring in the format ″CCYY-MM-DDhh:mm:ss.ffffff″

PSUBSCRIPTION 4 Address A pointer to the subscription name.

PTGTSCHEMA 4 Address A pointer to the target table schema name.

PTGTTABLE 4 Address A pointer to the target table name.

PTGTMEMBER 4 Address A pointer to the target member name(expected to be NULL on z/OS).

NUMCOLS 4 Integer The number of columns in the row imagestructures.


Field Name


OPERATION 1 Integer A code indicating the operation on the targettable that resulted in the conflict.

Possible values:

1=Insert, 2=Update, 3=Delete

CONFLICT 1 Integer A code indicating the conflict type that wasdetected.

Possible values:

1=Row exists, 2=Row missing, 3=Beforeimage different

HASBEFORE 1 Integer A code indicating whether the before imagewas provided to the user exit

Possible values:

1=Image exists, 0=Image not available

HASAFTER 1 Integer A code indicating whether the after imagewas provided to the user exit

Possible values:


HASTARGET 1 Integer A code indicating whether the target imagewas provided to the user exit

Possible values:


HASDESIRED 1 Integer A code indicating whether the desired imagewas provided to the user exit

Possible values:


HASBEFORE 1 Integer A code indicating whether the before imagewas provided to the user exit

Possible values:


RETCODE 1 Integer An integer to be updated by the user exit toindicate processing success or failure.

Possible values:

0=Processing continues, >0=An erroroccurred. replication activities are stoppedregardless of the ENDONERROR setting.


Field Name


DORESOLVE 1 Integer An integer to be updated by the user exit toindicate whether or not the desired imageshould be applied to the target table.

Possible values:

1=Use desired image, 0=Conflict notresolved. A permanent error will be logged.Replication will continue or stop, accordingto the ENDONERROR setting.

Related concepts

“Predefined entry data structures” on page 199Related reference

“Row Image structure”

Row Image structure

This structure contains information about a row image for the conflict. Each of thePBEFOREMG, PAFTERIMG, PTARGETIMG and PDESIREDIMG fields in the CDRControl structure points to an array that contains one of more instances of thefollowing structure.

Field Name


PCOLUMN 4 Address A pointer to a column structure.

Related reference

“Conflict Detection Resolution (CDR) control structure” on page 201“Column structure”

Column structure

This structure contains information about source columns (fields) and targetcolumns (attributes). The PATR field in the table structure points to an array thatcontains one of more instances of the following structure.

Field Name


LABEL 8 Character An eye-catcher label for the structure containingthe string “USRATR6” in EBCDIC.

This field helps you to identify this structure inan address space dump.

ATRNME 30 Character The name of the target table column.

ATRDFTOTH 30 Character The value mapped to the target table column ifATRDFTYP is set to O.

ATRCODEPAGE 20 Character Column code page name in EBCDIC.

ATRLEN 4 Integer The length (in bytes) of the target table column.


Field Name


ATRCCSID 4 Integer The column CCSID (Coded Character SetIdentifier)

ATRTYP 2 Integer The data type of the target table column.

Possible values:

2=Character, 4=Date, 6=Packed Decimal, 7=Float,8=Graphic, 9=Long (4 byte) integer, 10=Rowid,11=Small (2 byte) integer, 12=Time,13=Timestamp, 14=Varchar, 15=Graphic, 16=LongLong (8 byte) Integer, 17=Binary, 18=Decfloat,19=Varbin (variable length binary)

ATRSUBTYPE 2 Integer The subtype of the character target table column.

Possible values:

0=No subtype, 1=Char for bit, 2=Char for mixeddata, 3=Char for SBCS data

ATRSRC 2 Integer The type of mapping for the target table column.

Possible values:

1=Constant, 2=Derived expression, 3=Publicationtable column mapping, 4=Journal control field

ATRDFTYP 2 Integer The defined value mapped to the target tablecolumn.

Possible values:

0=No constant, 1=Blank, 2=Current date, time, ortimestamp, 3=NULL, 4=Other value, 5=Zero.

ATRALWNUL 2 Integer An indicator of whether the target table columnis NULL-capable.

Possible values:

1=NULL-capable, 0=Not NULL-capable

ATRDGT 2 Integer The number of digits in a numeric target tablecolumn.

ATRDEC 2 Integer The number of decimal places in a numeric targettable column.

ATRSEQ 2 Integer The sequence number of the target table column.

ATRKEYSEQ 2 Integer The sequence number of the target table columnin the key.

ATRVALTRN 2 Integer An indicator of whether data translations havebeen defined for the target table column.

Possible values:

0=Data translations have not been defined,1=Data translations have been defined


Field Name


ATRSUMTYPE 2 Integer An indicator of the type of summarization to beperformed on the target column

Possible values:

0=No summarization, 1=Accumulation,2=Deduction

ATRSUMKEY 2 Integer The sequence number of the summarization keyfor the target column.

ATRCDRSEL 2 Integer An indicator of whether Conflict Detection andResolution has been selected for the targetcolumn.

Possible values:

1=Conflict detection is to be performed, 0=Noconflict detection will be performed

ATRGENALWAYS 2 Integer An indicator of whether or not the target columnis defined as GENERATE ALWAYS

Possible values:

1=Column is GENERATE ALWAYS, 0=Column isnot GENERATE ALWAYS

ATRIDENTITY 2 Integer An indicator of whether or not the target columnis defined as an identity column

Possible values:

1=Column is an identity, 0=Column is not anidentity column


FLDNME 30 Character The name of the source table column.

FLDORIGTYPE 30 Character The name of the source table column type.

FLDCODEPAGE 20 Character Source table column code page name in EBCDIC

FLDDTMSEP 1 Character The character that separates elements in datesand times for the source table column.


FLDCCSID 4 Integer If applicable, the coded character set identifier forthe source table column.

FLDPOS 4 Integer The offset of the source table column in thejournal record.

FLDLEN 4 Integer The length (in bytes) of the source table column.


Field Name


FLDTYP 2 Integer The data type of the source table column.

Possible values:

2=Character, 4=Date, 6=Packed Decimal, 7=Float,8=Graphic, 9=Long (4 byte) integer, 10=Rowid,11=Small (2 byte) integer, 12=Time,13=Timestamp, 14=Varchar, 15=Graphic, 16=LongLong (8 byte) Integer, 17=Binary, 18=Decfloat,,19=Varbin (variable length binary)

FLDALWNUL 2 Integer An indicator of whether the source table columnis NULL-capable.

Possible values:

1=NULL-capable, 0=Not NULL-capable

FLDSEQNO 2 Integer The sequence number of the target table column.

FLDDGT 2 Integer The number of digits in a numeric source tablecolumn.

FLDDEC 2 Integer The number of decimal places in a numericsource table column.


Conflict resolution audit table

When InfoSphere CDC resolves a conflict between the source and target tables, itrecords information about the resolution in the DMMD_DMCONFAUD table.InfoSphere CDC creates this table in the target metadata location that is specifiedduring the configuration of InfoSphere CDC.

You can use the DMMD_DMCONFAUD table to track how conflict resolutionaffects your target table. For example, you can query the AFTERIMG column tosee when a change was made to the target table. Then you can review the contentsof the BEFOREIMG and AFTERIMG columns to see the change on the sourcetable that resulted in the data on the target table. This can help in identifyingissues in your conflict resolution strategy.

Conflict detection and resolution is configured in Management Console. For moreinformation, see your Management Console documentation.

The structure of the DMMD_DMCONFAUD table is as follows:

Column Description

CNFTIME The date and time on the target when the conflict wasdetected.

SRCTIME The time the conflicting data was applied to the sourcetable.

SRCSYSID The source ID of the subscription.

SRCSCHEMA The schema or library name for the source table.

SRCNAME The name of the source table.


Column Description

SRCMEMBER This field is blank.

TGTSCHEMA The schema or library for the target table.

TGTNAME The name of the target table.

TGTMEMBER This column is only used for the IBM i platform.

OPTYPE The row-level operation on the source that caused theconflict. The value is one of:

v 1—arrow was inserted into the source table.

v 2—arrow was updated on the source table.

v 3—arrow was deleted from the source table.

CNFTYPE The type of conflict that was detected. The value is oneof:

v 1—arrow was inserted into the source table. The keyfor that row already exists in the target table.

v 2—arrow was updated or deleted on the source table.The key for that row does not exist in the target table.

v 3—arrow was updated or deleted on the source table.The images of the source and target tables do notmatch.

v 4—an unexpected conflict was detected.

RESMTD The conflict resolution method that was used. The valueis one of:

v 1—source wins

v 2—target wins

v 3—largest value wins

v 4—smallest value wins

v 5—user exit

If the resolution method was None, then a row will notbe entered into this table. See your InfoSphere CDCdocumentation for more information on these methods.

CNFRES Indicates if the conflict was resolved. The value is oneof:

v Y—the conflict was resolved.

v N—the conflict was not resolved.

BEFORETRNC Indicates if the before image stored in BEFOREIMG wastruncated. The value is one of:

v Y—the value was truncated.

v N—the value was not truncated.

BEFOREIMG A representation of the row in the source table after itwas changed. See Row Image Format for moreinformation on the format of this column.

AFTERTRNC Indicates if the after image stored in AFTERIMG wastruncated. The value is one of:



AFTERIMG A representation of the row in the source table after itwas changed. See Row Image Format for moreinformation on the format of this column.


Column Description

TGTIMG A representation of the row in the target table beforereplication occurred. See Row Image Format for moreinformation on the format of this column.

TGTTRNC Indicates if the after image stored in TGTIMG wastruncated. The value is one of:



WINIMG A representation of the final row in the target table afterconflict resolution has occurred. See Row Image Formatfor more information on the format of this column.

WINTRNC Indicates if the image stored in WINIMG was truncated.The value is one of:



See also:“Row image format”“Truncated images”

Related concepts

“InfoSphere CDC metadata tables” on page 163Related reference

“Row image format”

Row image format

The BEFOREIMG, AFTERIMG, TGTIMG, and WINIMG columns in the audittable show representations of a row in either the source or target table.

The images in these columns are limited by the maximum length of VARCHARdata on your target metadata database. The images contain all of the values in therow, except for data in raw, binary, or LOB columns. The data from each column ispresented in the following format:(length:value)

In the format above, value is the data in the column and length is the number ofcharacters used to represent the data. The images display numeric data ascharacter strings and NULL values as (null).

The row images match the column order in the source table and the conflictresolution audit table. These images may be truncated if the image is longer thanthe maximum length of VARCHAR data in the target metadata database. If atable’s key column is not the first column in the table, then it may be truncated.

Truncated images

If a row image is longer than the maximum length of a VARCHAR column, thenthey will be truncated. There is a column in the audit table that indicates if eachimage column has been truncated. For example, if WINTRNC is Y, then the valueof WINIMG was truncated. The format of the truncated column is:(-length:value)


In the format above, value is the truncated value and length is the number ofcharacters in the truncated string.

About notifications user exitsIn Management Console, you can identify specific InfoSphere CDC events thatgenerate notifications allowing you to respond quickly to certain situations. Afternotifying one or more message categories, you can specify how you want to benotified. InfoSphere CDC currently supports three different notification methods.One of them is to call a user exit program when a notification is triggered. If thismethod is selected, information contained in this section is relevant.

See also:“Notifications”“Predefined entry data structures for notifications user exits”“Sample notifications user exit program”“Performance considerations”

NotificationsFor more information about this feature, see your Management Consoledocumentation.

Predefined entry data structures for notifications user exitsWhen a user exit program is invoked, predefined data structures are passed to theprogram. These structures are used to pass information about the triggerednotification that caused the user exit program to be invoked. In addition, the userexit program can return information through the same data structures so that it canbe accessed in subsequent calls. Therefore, these structures must be defined in eachuser exit program so that the information can be recognized and processed. Youruser exit program can then reference specific items of information in the datastructures.Related reference

“Predefined entry data structures” on page 214

Sample notifications user exit programSample user exit programs are provided with InfoSphere CDC. You may want touse a sample program as a base from which your user exit program is developed.

For Notifications exits, a single sample user exit program is provided with theproduct, and is contained in the CHCSAMLX member (located in the SCHCCSMP/E target library). This program provides a skeleton for alert handling basedon the attributes of the notification specified through Management Console. It alsoprovides stubs where code can be added for user exit initialization and terminationtasks.

Performance considerationsNotifications are triggered each time an InfoSphere CDC message belonging to aspecific functional zone and severity level is generated. If you notify a number ofzone and severity level combinations, and select user exit programs as thenotification handler in each case, performance is an important consideration inenvironments that generate a large volume of messages.


As a result, your programs should be written with performance in mind. Theyshould be optimized as much as possible. In certain situations, you may decide toonly invoke user exit programs in critical situations (for instance, only when fatalmessages are generated) to minimize the performance impact.

Working with Notifications user exit programsSee also:

“Defining and invoking Notifications user exit programs”“Writing notifications user exit programs”“Compiling and linking notifications user exit programs” on page 213“Predefined entry data structures” on page 214

Defining and invoking Notifications user exit programs

The process of defining programs so that they can be invoked in response totriggered notifications is separated into the following steps that must be performedin the specified order:1. Writing notifications user exit programs.2. Compiling and linking notifications user exit programs.3. Specifying notifications user exits in Management Console.Related reference

“Writing notifications user exit programs”“Compiling and linking notifications user exit programs” on page 213

Writing notifications user exit programs

Specifying Notifications user exits in Management Console.

Notifications user exit programs must contain the following entry point (orexternal functions) name:v ALRMXIT

Before active replication begins during the subscription’s initialization, eachNotifications user exit program is called with the CALLTYPE field of theUSRALARM predefined structure set to “Initialize” (value 2). This allows eachentry point to provide code to obtain resources it will require, before anyreplication activities have started. Such initialization processing could includeobtaining virtual storage resources, opening a file, obtaining one-time informationfrom DB2 tables, and so on.

After active replication is complete during the subscription’s termination, eachNotifications user exit program is called with the CALLTYPE field of theUSRALARM predefined structure set to “Terminate” (value 3). This allows eachentry point to provide code to release resources it required, after all replicationactivities have ceased. Such termination processing could release obtained virtualstorage, close an opened file, and so on.

For CALLTYPE values of “Initialize” and “Terminate” (values 2 and 3), no specificmessage was issued or passed to the user exit program in the USRALARM andMessage predefined data structures.


While active replication is ongoing, each Notifications user exit program is calledwith the CALLTYPE field of the USRALARM predefined structure set to “Process”(value 1). This indicates that the Notifications user exit program is being called forits processing purpose, and that a message will be issued and is being passed tothe user exit program in the USRALARM and Message predefined data structures.

It can be seen from the paragraphs above that each exit is called at least twice. Forinstance, if an Notifications user exit is specified, it is called twice even if therewere no messages generated in the alarmed category between the times that thesubscription was started and stopped. You must provide code in an Notificationsuser exit for detecting and processing the “Initialize” and “Terminate” values ofthe CALLTYPE field of the USRALARM predefined structure, otherwise the resultwill be unpredictable, and the Notifications user exit program could abnormallyterminate.

When an Notifications user exit completes its processing, in addition to any actiontaken during processing, the user exit program that you write must pass back areturn code to InfoSphere CDC. This return code is the value returned by aprogram/function call. In the COBOL language, the return code is stored in theRETURN-CODE special register before the GOBACK statement for the program isexecuted. In C language, the return code is provided as the value of a returnstatement. In Assembly Language, the return code is provided as the value of theRC keyword in the RETURN macro instruction. InfoSphere CDC recognizes thefollowing return codes and responds as indicated in the following table:

Return Code Definition and Response

0 The user exit program invocation wassuccessful. InfoSphere CDC continuesnormal processing.

8 An error was encountered during executionof the user exit program. InfoSphere CDCreports a standard processing error, andreplication activities are stopped.Note: For this return code, InfoSphere CDCreplication activities always terminate. Thecurrent setting of the ENDONERRORconfiguration control statement keyword isnot examined to determine whetherreplication activities should continue or end.

Notifications user exit programs cannot issue any SQL statements. Any attempt todo so will result in the abnormal termination of the user exit program.

The USERDATA field in the USRDATA predefined structure (see USRALARMStructure) is meant to be used by the user exits as a common resource field. It isdefined in COBOL as a POINTER, in C as a void *, and in Assembly Language asan A-con. Initially, when the subscription starts, this field has all bits reset, whichis equivalent to the POINTER value NULL/NULLS in COBOL or the pointer valueNULL in C. The content of this field is never accessed or altered by InfoSphereCDC after the subscription has started. The content of this field is passed to all theNotifications user exits within a subscription. Each user exit receives the contentsof this field as they were when the previously called user exit returned control toInfoSphere CDC. The first user exit to receive control within the subscription caninitialize the USERDATA field. For example, the first user exit to receive controlcan store a pointer to acquired storage in this field, and the acquired storage canbe used to convey data and communicate status to subsequent calls of any of the


provided Notifications user exits in the subscription. It is the responsibility of theuser exits to release any resources they acquire before a subscription ends.

Because all Notifications user exits are driven by the single task that implementsthe Product Administration Log process for a subscription within InfoSphere CDC,the Notifications user exits will be driven consecutively, and no two Notificationsuser exits will ever receive control concurrently within the same subscription. Thiseffectively enforces a serialization on the content of the USERDATA field, and anyuser exit can examine and modify the content of the USERDATA field (or whateverdata structure to which it points) without concern for serializing the accesses.

Any activity within a notifications user exit that involves “blocking” services orsuspending execution (for example, issuing an Assembly Language WAIT macroinstruction), will suspend the entire Product Administration Log process, and delaythe InfoSphere CDC address space, including all the subscriptions. Try to designthe Notifications user exits to minimize or eliminate the use of such services.

Notifications user exits must be coded, compiled and link-edited as reentrantprograms. This is generally as simple as specifying the RENT option for thecompiler and the linkage editor. If an exit is written in Assembly Language,specific design and coding accommodations are required to produce reentrantcode. If InfoSphere CDC loads a Notifications user exit and detects that it is notmarked as reentrant by the linkage editor, then initialization of the associatedsubscription will fail and the subscription will terminate. If a Notifications user exitis marked reentrant by the linkage editor but is actually not executing according tothe requirements of reentrancy, then unexpected errors can result, including thefailure of the Notifications user exit, or corruption of the data being passed to theNotifications user exit.

During development and testing, and sometimes during production execution,user-written notifications user exits may experience error conditions that result inan abnormal termination. For example, a Notifications user exit may attempt tostore data into a virtual storage area using a storage reference pointer, butinadvertently, the storage reference pointer contains the NULL pointer value. Thiswill result in an ABEND S0C4 (General Protection Fault). Normally, InfoSphereCDC intercepts all abnormal terminations that arise from within Notifications userexits. InfoSphere CDC then issues an explanatory message to the Event Log andCHCPRINT spooled output data set, and terminates the subscription that calledthe failing Notifications user exit. Based on the Language Environment optionsprovided to the InfoSphere CDC address space, LE may produce a diagnosticprintout of the intercepted error, or permit a dump of the address space at the timeof the error to occur. It is also possible to specify Language Environment optionsthat inhibit InfoSphere CDC from intercepting such catastrophic errors. In this case,the catastrophic error is elevated to InfoSphere CDC itself, and the entireInfoSphere CDC address space may fail. It is your responsibility to locate and fixany errors in their Notifications user exits. Judiciously specified LanguageEnvironment options, coupled with diagnostic tests and messages issued fromwithin the Notifications user exit can be helpful in achieving this goal. TheLanguage Environment options that disable the interception of abnormalterminations within the Language Environment enclave should not be used unlessfor a specific issue and in a controlled environment.


Related reference

“USRALARM structure” on page 214“ENDONERROR” on page 35

Compiling and linking notifications user exit programs


User exits receive control as subordinate functions within InfoSphere CDC. Whenyou compile some languages, it is necessary to direct the compiler to produce amain program or a subprogram (subordinate function), in accordance with how theprogram will be used. For example, the IBM C compiler has a “START/NOSTART”option. “START” is specified if the C program will be called directly through JCLor from TSO, that is as a “main”. “NOSTART: is specified if the C program will belink-edited into a load module and will only receive control when it is called bysome other program within the load module, that is, as a subordinate function.Where the language being used requires it, always direct the compiler to compileany user exits as subordinate functions, not as a main program. Failure to do socould significantly increase the cost of calling the user exit, or cause the user exit tofail when it is called.

The name for the load module is of your choosing, so long as it is unique and doesnot conflict with any names used by InfoSphere CDC (which all begin with“CHC”), DB2 (which all begin with “DSN”) or any z/OS system modules.

InfoSphere CDC supplies a module called CHCTEXIT (in the SCHCLOAD SMP/Etarget library). This module must be link-edited with the output from the compiler,to produce an executable load module. In addition, CHCTEXIT must be defined asthe entry point of the load module.


The following are the link-edit statements necessary to produce a functionnotifications user exit://SYSIN DD *CHANGE CHCCMPLV(CHCUEXL1)INCLUDE SYSLIB(CHCTEXIT)INCLUDE SYSLIB(<objmodule>)ENTRY CHCTEXITNAME <loadmodule>(R)/*

Replace:v <objmodule> with the name of the object module produced from by the compiler.

If more than one object module is required, insert an additional INCLUDEstatement for each object module.

v <loadmodule> with the name of the load module that is produced from thelink-edit and is specified in the user exit alert handler. This name must not bethe same as any load module provided with InfoSphere CDC. To be certain ofthis, it is best not to use a load module name that starts with “CHC″.




When compiling and link-editing, respond to any errors or warnings that arereported. If you are working with the sample user exit program provided withInfoSphere CDC, and you have not modified this program, no errors or warningsshould be generated.


Predefined entry data structures

Each user exit program must provide the necessary support to accept predefineddata structures containing information associated with the triggered notificationthat caused the user exit program to be invoked. Since user exit programs can bewritten in different languages, a general description of fields in each structure isprovided in the following sections:v USRALARM Structure (Notifications user exits)v Message Structure

A COBOL copy member describing the predefined data structures is contained inthe CHCUEXCB member of the SCHCCOB SMP/E target library. A C header filedescribing the predefined data structures is contained in the CHCUEXC memberthat is located in the SCHCH SMP/E target library. An Assembly Language copymember that describes the predefined data structures as DSECTs is contained inthe CHCUEXA member that is located in the SCHCMAC SMP/E target library.

Where the various predefined data structures’ data fields can be preset withspecific, indicative values, the descriptive definitions for the specific languages usesymbolic definitions for these values. The CHCUEXCB COBOL copy membercontains 88-level symbols that define the indicative values. The CHCUEXC Cheader file contains manifest constants that define the indicative values. TheCHCUEXA Assembly Language copy member contains EQU(ate) statements thatdefine the indicative values. It is good programming practice to use these symbolicvalue representations and not the actual values in any language coding, so thatfuture changes to the assignments of the indicative values will not cause problemswith your user exits.

See also:“USRALARM structure”“Message structure” on page 217

USRALARM structure

This structure contains the attributes of the triggered notification that caused theuser exit program to be invoked through the alert handler. It also contains pointersto a structure that provides information about the InfoSphere CDC messageresponsible for triggering the notification.


Field Name


LABEL 8 Character An eye-catcher label for the structure containingthe string “USRALARM6” in EBCDIC.

This field helps you to identify this structure in anaddress space dump.

LENGTH 2 Integer The total number of bytes consumed by thisstructure.


Possible values:


ENTTYPE 2 Integer The type of server that generated the InfoSphereCDC message triggering the notification.

Possible values:

0=Publisher (Source), 1=Subscriber (Target),2=Generic

ENTNAME 10 Character The source or target system identifier.

This field is blank if ENTTYPE is set to 2.

ZONE 2 Integer The functional zone of the InfoSphere CDCmessage that triggered the notification.

Possible values:

1=Describe transmitter, 2=Describe receiver,3=Refresh, 4=Scrape, 5=Apply,6=Communications, 7=Environment

For more information about functional zones, seeyour Management Console documentation.

CATG 2 Integer The severity level of the InfoSphere CDC messagethat triggered the notification.

Possible values:

1=Fatal, 2=Error, 3=Informational, 4=Status,5=Operational

For more information about message severitylevels, see your Management Consoledocumentation.

AREA 2 Integer The internal functional area that generated theInfoSphere CDC message triggering thenotification.

You may be asked to provide this number to IBMin a product support call.


PMSG 4 Address A pointer to the structure containing the text inthe InfoSphere CDC message that triggered thenotification.


Field Name


PSRCLIB 4 Address A pointer to the structure identifying the sourcetable library or owner associated with theInfoSphere CDC message that triggered thenotification.

The pointer is NULL if no source library or owneris associated with the message.

PSRCTBL 4 Address A pointer to the structure identifying the sourcetable associated with the InfoSphere CDC messagethat triggered the notification.

The pointer is NULL if no source table isassociated with the message.

PSRCCOL 4 Address A pointer to the structure identifying the sourcetable column associated with the InfoSphere CDCmessage that triggered the notification.

The pointer is NULL if no source table column isassociated with the message.

PTGTLIB 4 Address A pointer to the structure identifying the targettable library or owner associated with theInfoSphere CDC message that triggered thenotification.

The pointer is NULL if no target library or owneris associated with the message.

PTGTTBL 4 Address A pointer to the structure identifying the targettable associated with the InfoSphere CDC messagethat triggered the notification.

The pointer is NULL if no target table isassociated with the message.

PTGTCOL 4 Address A pointer to the structure identifying the targettable column associated with the InfoSphere CDCmessage that triggered the notification.

The pointer is NULL if no target table column isassociated with the message.

USERDATA 4 Address Used to return data from the program that can bereferenced in target invocations.

Data placed in this field is persistent across userexit program invocations.

JOBNAME 8 Character The name of the InfoSphere CDC address space inEBCDIC.

TSVERSION 12 Character The version of InfoSphere CDC (expressed in theformat VxRxMx) installed on the source or targetserver in EBCDIC.



Related reference

“Message structure”

Message structure

This structure contains information about the InfoSphere CDC message thattriggered a notification. It is referenced by a number of fields in the USRALARMstructure.

Field Name


LENGTH 2 Integer The total number of bytes consumed by thisstructure.

DATA 512 Character Information related to the InfoSphere CDCmessage that triggered the notification.

Related reference

“USRALARM structure” on page 214



SMF Record Layout

In this section, you will learn:“SMF record header”“Actual SMF performance records written by InfoSphere CDC” on page 229

SMF record header

Offset Name Length Format Description

00(00) SMFLEN 2 binary Record length (maximum size of 32,756). Thisfield and the next field (total of four bytes) formthe record descriptor word (RDW). The first twobytes (this field) must contain the logical recordlength including the RDW. The second two bytes(the following field) are used for variable blockspanned records. If the record is not spanned, setthese two bytes to hexadecimal zeroes. Thesefields must be filled in before writing the recordto the SMF data set.

02(02) SMFSEG 2 binary Segment descriptor.

04(04) SMFFLG 1 binary Bit Meaning When Set

v 0-2 Reserved

v 3 MVS/SP™ version 4 and above. Bits 3, 4, 5,and 6 are on.*

v 4 MVS/SP version 3. Bits 4, 5, and 6 are on

v 5 MVS/SP version 2. Bits 5 and 6 are on.

v 6 VS2. Bit 6 is on.

v 7 Reserved.

*Do not use information located elsewhere in thisrecord to determine the MVS™ product level.

05(05) SMFRTY 1 binary Record type (hexadecimal values are 00 - FF).Specified by the SMFTYPE keyword.

06(06) SMFTME 4 binary Time since midnight, in hundredths of a second,record was moved into the SMF buffer.

10(0A) SMFDTE 4 packed Date when the record was moved into the SMFbuffer, in the form 0cyydddF (where c is 0 for19xx and 1 for 20xx, yy is the current yea (0-99),ddd is the current day (1-366), and F is the sign).

14(0E) SMFSID 4 EBCDIC System identification (from the SMFSIDkeyword).

See also:“InfoSphere CDC SMF record header” on page 220“InfoSphere CDC SMF performance segment header” on page 220“InfoSphere CDC SMF performance segments” on page 222


InfoSphere CDC SMF record header


00(00) TSRECLEN 2 binary Length of the entire record, including thisheader, but not including the standard SMFheader.

02(02) TSHDRLEN 2 binary Length of this header.

04(04) TSEYECTR 8 EBCDIC Eye catcher. ’TSSMFREC’

12(0C) TSVERSN 4 binary Version of this SMF record. May differ fromthe versions of the individual segments.

16(10) TSJOBNM 8 EBCDIC Job name of the InfoSphere CDC addressspace.

24(18) TSASID 2 binary Address space ID of the InfoSphere CDCaddress space.

26(1A) TSSSID 4 EBCDIC Subsystem ID of the DB2 instance to whichInfoSphere CDC is attached.

30(1E) TSCATG 2 binary Category of the InfoSphere CDC SMF record:

0—Status record (not yet used).

1—Performance record.

32(20) TSENTYP 2 binary Type of the entity that created this SMFrecord:

0—Non specific.

1—Source subscription.

2—Target subscription.

3—DB2 Log Cache (single scrape).

34(22) TSENTNM 12 EBCDIC Name of the entity that created this SMFrecord. ’SYSTEM’ for nonspecific entity.Subscription name for source subscriptionand target subscription. ’LOG CACHE’ forDB2 Log Cache.

46(2E) TSINTVL 4 binary The interval, in seconds, spanned by thisSMF record.

50(32) TSSEGS 2 binary The number of segments following thisheader.

52(34) TSRESVD 26 notapplicable

Reserved for future expansion.

InfoSphere CDC SMF performance segment header


00(00) TSSSEGLN 2 binary Length of the entire segment, includingthis header.

02(02) TSSHDRLN 2 binary Length of this header.

04(04) TSSVERSN 4 binary Version of this segment. May differfrom the version of the overall SMFrecord and the versions of othersegments.



08(08) TSSENTYP 4 binary Type of the entity that created thissegment:

1—MIT task.

2—OSC task.

3—PAL task.

4—CIT task.

5—PAA tasks.

6—DIT task.

7—DSC task.

8—Reserved value. This value waspreviously used for the DAA task ofTransformation Server for z/OS.InfoSphere CDC does not use thisvalue.

9—DAL task.

10—DSL task.

11—DDT task.

12—DDR task.

15—DTC task.

16—DLP task.

18—CMO task.

19—CLS task.

20—CCI tasks.

21—CCO tasks.

22—CDI task.

23—CDO task.

24—SCT task.

25—TCT task.

26—SDT task.

27—CVF tasks.

28—DLR task.

29—DCW task.

30—MAA task.

12(0C) TSSENTNM 12 EBCDIC Name of the entity that created thissegment.

SMF Record Layout 221


24(18) TSSSTS 4 binary Status of the entity that created thissegment:

0—Undetermined.

1—Inactive.

2—Starting.

3—Active.

4—Ending.

28(1C) TSSSTSMD 4 binary Sub-status of the entity that created thissegment:

X’00’—Undetermined.

X’01’—Normal.

X’02’—Error.

X’04’—Describe.

X’08’—Refresh.

X’10’—Refresh before mirror.

X’20’—Mirror continuous.

X’40’—Mirror next change.

32(20) TSSRESVD 32 notapplicable

Reserved for future expansion.

InfoSphere CDC SMF performance segmentsAll non-instantaneous values (for example, cumulative counts) in SMFPerformance Segments are counts for the interval spanned by the SMF record only.

See also:“InfoSphere CDC SMF performance segment for OSC task” on page 223“InfoSphere CDC SMF performance segment for CIT task” on page 223“InfoSphere CDC SMF performance segment for PAL task” on page 223“InfoSphere CDC SMF performance segment for MAA task” on page 223“InfoSphere CDC SMF performance segment for CMO task” on page 223“InfoSphere CDC SMF performance segment for CLS task” on page 223“InfoSphere CDC SMF performance segment for CVF task” on page 223“InfoSphere CDC SMF performance segment for DSC task” on page 223“InfoSphere CDC SMF performance segment for DLP task” on page 224“InfoSphere CDC SMF performance segment for DAL task” on page 224“InfoSphere CDC SMF performance segment for PAA task” on page 224“InfoSphere CDC SMF performance segment for CCI task” on page 224“InfoSphere CDC SMF performance segment for CCO task” on page 224“InfoSphere CDC SMF performance segment for DLR task” on page 224“InfoSphere CDC SMF performance segment for DCW task” on page 225


“InfoSphere CDC SMF performance segment for SCT task” on page 225“InfoSphere CDC SMF performance segment for SDT mirror task” on page 225“InfoSphere CDC SMF performance segment for DSL mirror task” on page 225“InfoSphere CDC SMF performance segment for TCT mirror task” on page 226“InfoSphere CDC SMF performance segment for DTC mirror task” on page 226“InfoSphere CDC SMF performance segment for CDI task” on page 229“InfoSphere CDC SMF performance segment for CDO task” on page 229

InfoSphere CDC SMF performance segment for OSC task


00(00) OSCCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for CIT task


00(00) CITCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for PAL task


00(00) PALCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for MAA task


00(00) MAACPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for CMO task


00(00) CMOCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for CLS task


00(00) CLSCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for CVF task


00(00) CVFCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for DSC task


00(00) DSCCPU 8 binary Microseconds of CPU consumed by task.


InfoSphere CDC SMF performance segment for DLP task


00(00) DLPCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for DAL task


00(00) DALCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for PAA task


00(00) PAACPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for CCI task


00(00) CCICPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for CCO task


00(00) CCOCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for DLR task


00(00) DLRCPU 8 binary Microseconds of CPU consumed by task.

08(08) DLRHOL 8 binary Head of DB2 log. Instantaneous value.

16(10) DLRLIC 8 binary Lowest DB2 log position in the DB2 LogCache. Instantaneous value.

24(18) DLRHIC 8 binary Highest DB2 log position in the DB2 LogCache. Instantaneous value.

32(20) DLRWRT 4 binary Requests to write to DB2 Log Cache.

36(24) DLRRD 4 binary Requests to read from DB2 Log Cache.

40(28) DLRRDOK 4 binary Requests to read from DB2 Log Cache thatwere fulfilled from the cache.

44(2C) DLRRDNOK 4 binary Requests to read from DB2 Log Cache thatwere not fulfilled from the cache.

48(30) DLRBLWT1 4 binary New blocks written to the Level 1 DB2 LogCache.

52(34) DLRBLUP1 4 binary Blocks updated in the Level 1 DB2 LogCache.

56(38) DLRBLRD1 4 binary Blocks read from the Level 1 DB2 LogCache.

60(3C) DLRBLRD2 4 binary Blocks read from the Level 2 DB2 LogCache.


InfoSphere CDC SMF performance segment for DCW task


00(00) DCWCPU 8 binary Microseconds of CPU consumed by task.

08(08) DCWBLWT2 4 binary Blocks written to the Level 2 DB2 LogCache.

InfoSphere CDC SMF performance segment for SCT task


00(00) CCOCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for SDT mirror task


00(00) SDTCPU 8 binary Microseconds of CPU consumed by task.

08(08) SDTLPLW 8 binary Last DB2 log position read from the logwindow. Instantaneous value.

16(10) SDTLPSND 8 binary Last DB2 log position sent to the target.Instantaneous value.

24(18) SDTSNDS 4 binary Number of TCP sends to the target.

28(1C) SDTSNDBT 8 binary Number of bytes sent to the target.

36(24) SDTINS 4 binary Insert operations sent to the target.

40(28) SDTUPD 4 binary Update operations sent to the target.

44(2C) SDTDEL 4 binary Delete operations sent to the target.

48(30) SDTCMT 4 binary Commits sent to the target.

52(34) SDTLRRLW 4 binary Log records read from the log window.

56(38) SDTLRISS 4 binary Log records inserted into the Staging Space.

60(3C) SDTLRRSS 4 binary Log records removed from the Staging Space.

64(40) SDTLRSS 4 binary Log records currently in the Staging Space.Instantaneous value.

68(44) SDTSZSS 8 binary Number of bytes currently in the StagingSpace. Instantaneous value.

76(4C) SDTCMTSS 4 binary Number of completed commit groups in theStaging Space. Instantaneous value.

80(50) SDTCRCMT 4 binary Size of commit group currently being sent tothe target. Instantaneous value.

84(54) SDTMXCMT 4 binary Size of largest commit group sent to date.Instantaneous value.

88(58) SDTMNCMT 4 binary Size of smallest commit group sent to date.Instantaneous value.

InfoSphere CDC SMF performance segment for DSL mirror task


00(00) DSLCPU 8 binary Microseconds of CPU consumed by task.

08(08) DSLHOL 8 binary Current head of DB2 log. Instantaneousvalue.



16(10) DSLSCRP 8 binary Current DB2 log position being read.Instantaneous value.

24(18) DSLNUMFL 4 binary Number of InfoSphere CDC log recordsfiltered out.

28(1C) DSLBYTFL 8 binary Bytes in InfoSphere CDC log records filteredout.

36(24) DSLNUMIF 4 binary Number of IFI 0306 calls issued.

44(2C) DSLCPUIF 8 binary CPU microseconds consumed by IFI 0306calls.

InfoSphere CDC SMF performance segment for TCT mirror task


00(00) TCTCPU 8 binary Microseconds of CPU consumed by task.

InfoSphere CDC SMF performance segment for DTC mirror task


00(00) DTCCPU 8 binary Microseconds of CPU consumed by task.

08(08) DTCJRNLS 4 binary Last DB2 log position read from the logwindow. Instantaneous value.

12(0C) DTCJ0RCV 4 binary Number of TCP receives accepted from thesource for journal 0.

16(10) DTCJ0RBT 8 binary Number of bytes received from the source forjournal 0.

24(18) DTCJ0INS 4 binary Number of insert operations received fromthe source for journal 0.

28(1C) DTCJ0UPD 4 binary Number of update operations received fromthe source for journal 0

32(20) DTCJ0DEL 4 binary Number of delete operations received fromthe source for journal 0.

36(24) DTCJ0CMT 4 binary Number of commits received from the sourcefor journal 0.

40(28) DTCJ1RCV 4 binary Number of TCP receives accepted from thesource for journal 1.

44(2C) DTCJ1RBT 8 binary Number of bytes received from the source forjournal 1.


56(38) DTCJ1UPD 4 binary Number of update operations received fromthe source for journal 1.

60(3C) DTCJ1DEL 4 binary Number of delete operations received fromthe source for journal 1.









92(5C) DTCJ2CMT 4 binary Number of commits received from the sourcefor journal 2.



108(6C) DTCJ3INS 4 binary Number of insert operations received fromthe source for journal 3.




124(7C) DTCJ4RCV 4 binary Number of TCP receives accepted from thesource for journal 4.



140(8C) DTCJ4UPD 4 binary Number of update operations received fromthe source for journal 4.





164(A4) DTCJ5INS 4 binary Number of insert operations received fromthe source for journal 5.

168(A8) DTCJ5UPD 4 binary Number of update operations received fromthe source for journal 5.

172(AC) DTCJ5DEL 4 binary Number of delete operations received fromthe source for journal 5.

176(B0) DTCJ5CMT 4 binary Number of commits received from the sourcefor journal 5.

180(B4) DTCJ6RCV 4 binary Number of TCP receives accepted from thesource for journal 6.



184(B8) DTCJ6RBT 8 binary Number of bytes received from the source forjournal 6.

192(C0) DTCJ6INS 4 binary Number of insert operations received fromthe source for journal 6.

196(C4) DTCJ6UPD 4 binary Number of update operations received fromthe source for journal 6.

200(C8) DTCJ6DEL 4 binary Number of delete operations received fromthe source for journal 6.

204(CC) DTCJ6CMT 4 binary Number of commits received from the sourcefor journal 6.

208(D0) DTCJ7RCV 4 binary Number of TCP receives accepted from thesource for journal 7.

212(D4) DTCJ7RBT 8 binary Number of bytes received from the source forjournal 7.

220(DC) DTCJ7INS 4 binary Number of insert operations received fromthe source for journal 7.

224(E0) DTCJ7UPD 4 binary Number of update operations received fromthe source for journal 7.

228(E4) DTCJ7DEL 4 binary Number of delete operations received fromthe source for journal 7.

232(E8) DTCJ7CMT 4 binary Number of commits received from the sourcefor journal 7.

236(EC) DTCJ8RCV 4 binary Number of TCP receives accepted from thesource for journal 8.

240(F0) DTCJ8RBT 8 binary Number of bytes received from the source forjournal 8.

248(F8) DTCJ8INS 4 binary Number of insert operations received fromthe source for journal 8.

252(FC) DTCJ8UPD 4 binary Number of update operations received fromthe source for journal 8.







284(11C) DTCJ9DEL 4 binary Number of delete operations received fromthe source for journal 9.



InfoSphere CDC SMF performance segment for CDI task


00(00) CDICPU 8 binary Microseconds of CPU consumed by task.

08(08) CDISND 4 binary TCP sends performed.

12(0C) CDIRCV 4 binary TCP receives performed.

16(10) CDISNDBT 8 binary Bytes sent.

24(1C) CDIRCVBT 8 binary Bytes received.

InfoSphere CDC SMF performance segment for CDO task


00(00) CDOCPU 8 binary Microseconds of CPU consumed by task.

08(08) CDOSND 4 binary TCP sends performed.

12(0C) CDORCV 4 binary TCP receives performed.

16(10) CDOSNDBT 8 binary Bytes sent.

24(1C) CDORCVBT 8 binary Bytes received.

Actual SMF performance records written by InfoSphere CDCSee also:

“The system SMF performance record”“The log cache performance record” on page 230“The source subscription mirror performance record” on page 231“The target subscription mirror performance record” on page 231

The system SMF performance record


00(00) SYSSHDR 18 mixed Standard SMF Record Header.

18(12) SYSTHDR 78 mixed InfoSphere CDC SMF Record Header.

96(60) SYSOSCH 64 mixed InfoSphere CDC Performance SegmentHeader.

160(A0) SYSOSC 8 mixed InfoSphere CDC Performance Segmentfor OSC task.

168(A8) SYSCITH 64 mixed InfoSphere CDC Performance SegmentHeader.

232(E8) SYSCIT 8 mixed InfoSphere CDC Performance Segmentfor CIT task.

240(F0) SYSPALH 64 mixed InfoSphere CDC Performance SegmentHeader.

304(130) SYSPAL 8 mixed InfoSphere CDC Performance Segmentfor PAL task.

312(138) SYSMAAH 64 mixed InfoSphere CDC Performance SegmentHeader.

376(178) SYSMAA 8 mixed InfoSphere CDC Performance Segmentfor MAA task.



384(180) SYSCMOH 64 mixed InfoSphere CDC Performance SegmentHeader.

448(1C0) SYSCMO 8 mixed InfoSphere CDC Performance Segmentfor CMO task.

456(1C8) SYSCLSH 64 mixed InfoSphere CDC Performance SegmentHeader.

520(208) SYSCLS 8 mixed InfoSphere CDC Performance Segmentfor CLS task.

528(210) SYSCVFH 64 mixed InfoSphere CDC Performance SegmentHeader.

592(250) SYSCVF 8 mixed InfoSphere CDC Performance Segmentfor CVF task.

600(258) SYSDSCH 64 mixed InfoSphere CDC Performance SegmentHeader.

664(298) SYSDSC 8 mixed InfoSphere CDC Performance Segmentfor DSC task.

672(2A0) SYSDLPH 64 mixed InfoSphere CDC Performance SegmentHeader.

736(2E0) SYSDLP 8 mixed InfoSphere CDC Performance Segmentfor DLP task.

744(2E8) SYSDALH 64 mixed InfoSphere CDC Performance SegmentHeader.

808(328) SYSDAL 8 mixed InfoSphere CDC Performance Segmentfor DAL task.

816(330) SYSPAAH 64 mixed InfoSphere CDC Performance SegmentHeader.

880(370) SYSPAA 8 mixed InfoSphere CDC Performance Segmentfor PAA tasks.

898(378) SYSCCIH 64 mixed InfoSphere CDC Performance SegmentHeader.

952(3B8) SYSCCI 8 mixed InfoSphere CDC Performance Segmentfor CCI tasks

960(3C0) SYSCCOH 64 mixed InfoSphere CDC Performance SegmentHeader.

1024(400) SYSCCO 8 mixed InfoSphere CDC Performance Segmentfor CCO tasks

The log cache performance record


00(00) LCHDR 18 mixed Standard SMF Record Header.

18(12) LCTHDR 78 mixed InfoSphere CDC SMF Record Header.

96(60) LCDLRH 64 mixed InfoSphere CDC Performance SegmentHeader.

160(A0) LCDLR 64 mixed InfoSphere CDC Performance Segmentfor DLR task.



224(E0) LChange DataCaptureWH

64 mixed InfoSphere CDC Performance SegmentHeader.

288(120) LChange DataCaptureW

12 mixed InfoSphere CDC Performance Segmentfor DCW task.

The source subscription mirror performance record


00(00) SRCHDR 18 mixed Standard SMF Record Header.

18(12) SRCTHDR 78 mixed InfoSphere CDC SMF Record Header.

96(60) SRCSCTH 64 mixed InfoSphere CDC Performance SegmentHeader.

160(A0) SRCSCT 8 mixed InfoSphere CDC Performance Segmentfor SCT task.

168(A8) SRCSDTH 64 mixed InfoSphere CDC Performance SegmentHeader.

232(E8) SRCSDT 92 mixed InfoSphere CDC Performance Segmentfor SDT mirror task.

324(144) SRCDSLH 64 mixed InfoSphere CDC Performance SegmentHeader.

388(184) SRCDSL48 48 mixed InfoSphere CDC Performance Segmentfor DSL mirror task.

436(1B4) SRCCDIH 64 mixed InfoSphere CDC Performance SegmentHeader.

500(1F4) SRCCDI 32 mixed InfoSphere CDC Performance Segmentfor CDI task.

532(214) SRCCDOH 64 mixed InfoSphere CDC Performance SegmentHeader.

596(254) SRCCDO 32 mixed InfoSphere CDC Performance Segmentfor CDO task.

The target subscription mirror performance record


00(00) TGTHDR 18 mixed Standard SMF Record Header.

18(12) TGTTHDR 78 mixed InfoSphere CDC SMF Record Header.

96(60) TGTTCTH 64 mixed InfoSphere CDC Performance SegmentHeader.

160(A0) TGTTCT 8 mixed InfoSphere CDC Performance Segmentfor TCT task.

168(A8) TGTDTCH 64 mixed InfoSphere CDC Performance SegmentHeader.

232(E8) TGTDTC 292 mixed InfoSphere CDC Performance Segmentfor DTC mirror task.

524(20C) TGTCDIH 64 mixed InfoSphere CDC Performance SegmentHeader.



588(24C) TGTCDI 32 mixed InfoSphere CDC Performance Segmentfor CDI mirror task.

620(26C) TGTCDOH 64 mixed InfoSphere CDC Performance SegmentHeader.

684(2AC) TGTCDO 32 mixed InfoSphere CDC Performance Segmentfor CDO task.


Event messages reference

This section describes the messages that are generated by InfoSphere CDC. Itassumes that you are familiar with the z/OS environment.

This document is intended primarily for console operators and clientadministrators. It should be consulted after you have installed InfoSphere CDC onyour z/OS system and Management Console on your Windows® or UNIX®

workstations.“Introduction to event messages”“Event message identifier changes” on page 235“CHC00 messages” on page 238“CHC01 messages” on page 257“CHC02 messages” on page 268“CHC03 messages” on page 289“CHC04 messages” on page 326“CHC05 messages” on page 337“CHC06 messages” on page 366“CHC07 messages” on page 374“CHC08 messages” on page 399“CHC10 messages” on page 410“CHC11 messages” on page 410“CHC12 messages” on page 419“CHC14 messages” on page 421“CHC15 messages” on page 435“CHC16 messages” on page 449“CHC18 messages” on page 464“CHC19 messages” on page 465“CHC20 messages” on page 471“CHC30 messages” on page 473“CHC50 messages” on page 492“CHC60 messages” on page 502“CHC70 messages” on page 555“CHC90 messages” on page 571

Introduction to event messagesIn this section, you will learn:

“Message identifier format”“Message descriptions” on page 234

Message identifier formatEach message that is generated by InfoSphere CDC has a unique identifier. Allmessage identifiers for InfoSphere CDC are at least eight characters in length andadhere to the following format:


CHC<message number><severity indicator>(<address space id>)

For all messages, the first three characters in the message identifier are CHC. Thisallows you to identify messages that are generated by InfoSphere CDC.

The message number (<message number>) component is four characters in length.It is used to uniquely identify each message that is generated by InfoSphere CDC.

The severity indicator (<severity indicator>) is a single letter that conveys theseverity level of the messages. Table 1 identifies the severity indicators that areused. They are presented in increasing order of severity.

“Severity indicators”

Severity indicators

Severity Indicators Description

L (Logged Information) This type of message conveys information that is not required atthe time this message was generated, but is being producedbecause it may be required at some time in the future,depending on the outcome of InfoSphere CDC’s runtimeactivity.

T (Trace) This type of message indicates that a trace point has beenreached during InfoSphere CDC processing. Messages of thistype would not normally be generated in your workingenvironment.

I (Informational) This type of message conveys information about InfoSphereCDC activity that usually does not require any action. Messagesof this type are sometimes generated in response to an operatorconsole command.

W (Warning) This type of message identifies an exception or unexpectedsituation that does not currently limit the execution ofInfoSphere CDC but may lead to undesirable repercussions asexecution continues.

E (Error) This type of message declares the existence or occurrence of acondition that caused a task within InfoSphere CDC to fail.

A (Abnormal End) This type of message is issued to provide information about thereason for the abnormal termination of the InfoSphere CDCaddress space or a task running within the address space.

Since multiple InfoSphere CDC address spaces can be active at one time, anaddress space identifier (<address space id>) enclosed in parentheses is sometimesappended to the message identifier. This identifier indicates the InfoSphere CDCaddress space from where the message was generated, and is the same identifierthat was used when the address space was created.

Message descriptionsFor each message that is described in this section, the following items ofinformation are described:

Note: When a message variable is to be replaced with text, such as the name of acolumn in a DB2 table that is not in U.S. English, it may not always be possible todisplay the variable text. This is likely the case when messages are routed to thesystem console or a spool dataset, such as CHCPRINT or CHCAUDIT, whichgenerally can only display single-byte EBCDIC characters. In these cases, the


variable text will be translated to EBCDIC for display. If the variable text containsuntranslatable characters, then the untranslatable characters will be replaced with aplaceholder (’*’) in the message as it appears on the console or in the sysprintdataset. For logged messages, the full untranslated text is recorded in the ProductAdministration Log, and can normally be viewed with Management Console.v Message Identifier and Text—The first item of information that is provided is

the actual message identifier and text that appears in the system or productadministration logs. In some messages, brace brackets in the text identify a finiteset of terms (terms are separated by vertical bars). Only one of the terms that arelisted actually appears in the message text. If the list of possible terms is long,the message text contains a numeric reference to a list of the terms presentedbelow the message text.

v Explanation—Explains the message in more detail and describes the possiblecauses that led to the message being generated.

v Message Variable—Identifies and describes each variable that is part of themessage text. Variables are presented in italic text in the message. They are usedto focus attention on specific items (for example, a specific table or subscriptionthat needs to be identified). As a result, a variable can have an unlimitednumber of values (names, numbers, and so on). Note that some messages do notcontain variables.

v Message Destination—Identifies where the message is logged. Most messagesare routed to either the system or product administration log.– System log— A z/OS log that InfoSphere CDC uses to convey information

about product operations to the console operator. Note that system logmessages may or may not be directed to the operator console.

– Product administration log— An InfoSphere CDC log (in the CHCPRINTspool data set) containing messages that you can read in ManagementConsole.

Some messages may only be displayed interactively, in a message box, inManagement Console and not placed in the product administration log.InfoSphere CDC also maintains a log (in the CHCAUDIT spool data set) that isintended for diagnostic purposes. Some messages are just placed in this log. Thedestination for these messages is identified as the audit log.

v System Action—If applicable, the action that is performed or not performed bythe system in situations that led to the message being generated.

v Operator Response—If applicable, the actions that should be taken by theconsole operator in response to the message. When the console operator isrequired to act, it is usually in response to a message that is placed in thesystem log.

v Client Administrator Response—If applicable, the actions that should be takenby the client administrator in response to the message. In this section, the clientadministrator refers to the person responsible for configuring replication inManagement Console. When the client administrator is required to act, it isusually in response to a message that is placed in the product administrationlog.

Event message identifier changesAs of version 6.2 PTF xxxxx, changes in message identifier numbering have beeneffected for the following event messages:

Previous Number New Number

CHC0041 CHC0082, CHC0083

Event messages reference 235


CHC0045 CHC0120, CHC0121, CHC0122, CHC0123

CHC0048 CHC0129, CHC0130

CHC0049 CHC0136, CHC0137

CHC0074 CHC0143, CHC0144

CHC0111 CHC1122, CHC1123, CHC1124, CHC1125, CHC1126, CHC1127,CHC1128, CHC1129, CHC1130, CHC1131, CHC1132, CHC1133,CHC1134, CHC1135, CHC1136, CHC1137, CHC1138, CHC1139,CHC1140, CHC1141, CHC1142, CHC1143, CHC1144, CHC1145,CHC1147, CHC1148, CHC1149, CHC1150, CHC1151, CHC1152,CHC1153, CHC1154, CHC1155, CHC1156, CHC1157, CHC1158,CHC1159, CHC1160, CHC1161, CHC1162, CHC1163, CHC1164,CHC1165, CHC1166, CHC1167, CHC1168, CHC1169, CHC1170,CHC1171, CHC1172, CHC1173, CHC1174, CHC1175, CHC1176,CHC1177, CHC1178, CHC1179, CHC1180, CHC1181, CHC1182,CHC1183, CHC1184, CHC1185, CHC1186, CHC1187, CHC1188,CHC1189, CHC1190, CHC1191, CHC1192, CHC1193, CHC1194,CHC1195, CHC1196, CHC1197, CHC1198, CHC1199, CHC1200,CHC1201, CHC1202, CHC1203, CHC1204, CHC1205, CHC1206,CHC1207, CHC1208, CHC1209, CHC1210, CHC1211, CHC1212,CHC1213, CHC1214, CHC1215, CHC1216, CHC1217, CHC1218,CHC1219, CHC1220, CHC1221, CHC1222, CHC1224, CHC1225,CHC1226, CHC1227, CHC1228, CHC1229, CHC1230, CHC1231

CHC0229 CHC0247, CHC0248




CHC0241 CHC0281, CHC0282, CHC0283

CHC0242 CHC0289, CHC0290, CHC0291

CHC0245 CHC0379, CHC0380, CHC0381, CHC0382, CHC0383, CHC0384


CHC0304 CHC0411, CHC0412

CHC0323 CHC0418, CHC0419, CHC0420, CHC0421, CHC0422


CHC0338 CHC0495, CHC0496

CHC0349 CHC0502, CHC0503

CHC0345 CHC0511, CHC0512, CHC0513, CHC0514, CHC0515, CHC0516,CHC0517, CHC0518, CHC0519

CHC0362 CHC0583, CHC0584

CHC0363 CHC0662, CHC0663

CHC0370 CHC0669, CHC0670

CHC0400 CHC0676, CHC0677

CHC0510 CHC0683, CHC0684, CHC0685, CHC0686, CHC0687, CHC0688,CHC0689, CHC0690


CHC0563 CHC0764, CHC0765

CHC0597 CHC0792, CHC0793



CHC0601 CHC0799, CHC0800, CHC0801, CHC0802, CHC0803, CHC0804,CHC0805



CHC0902 CHC0917, CHC0918

CHC1105 CHC1251, CHC1252

CHC1112 CHC1258, CHC1259


CHC1409 CHC1432, CHC1433

CHC1512 CHC1543, CHC1544, CHC1545

CHC1519 CHC1551, CHC1552, CHC1553

CHC1530 CHC1559, CHC1560


CHC1901 CHC1914, CHC1915



CHC5001 CHC5002, CHC5003

CHC5100 CHC5110, CHC5111, CHC5112


CHC5105 CHC5127, CHC5128, CHC5129

CHC5106 CHC5135, CHC5136, CHC5137

CHC5107 CHC5143, CHC5144

CHC9202 CHC9220, CHC9221, CHC9222



CHC9648 CHC9676, CHC9677



CHC9701 CHC9756, CHC9757, CHC9758



CHC9731 CHC9817, CHC9818, CHC9819







CHC00 messagesSee also:

“CHC0012W” on page 239“CHC0015I” on page 239“CHC0023W” on page 239“CHC0024W” on page 240“CHC0025W” on page 240“CHC0026W” on page 241“CHC0027W” on page 241“CHC0029E” on page 241“CHC0030E” on page 242“CHC0031E” on page 242“CHC0040I” on page 243“CHC0044I” on page 243“CHC0046I” on page 243“CHC0047I” on page 244“CHC0050E” on page 244“CHC0051W” on page 245“CHC0052W” on page 246“CHC0055I” on page 246“CHC0056I” on page 247“CHC0057I” on page 248“CHC0058E” on page 248“CHC0059E” on page 249“CHC0060I” on page 249“CHC0061E” on page 250“CHC0068E” on page 250“CHC0069E” on page 251“CHC0071E” on page 251“CHC0072W” on page 252“CHC0073W” on page 252“CHC0075E” on page 253“CHC0077E” on page 253“CHC0078E” on page 254“CHC0079E” on page 254“CHC0080E” on page 254“CHC0081E” on page 255“CHC0082I” on page 255“CHC0083I” on page 256“CHC0095E” on page 256“CHC0099I” on page 256


CHC0012WCHC0012W Replication functions are already running for subscription name.The request has been rejected.

Explanation—A request to start replication was issued to a subscription that wasalready active. The subscription was active as a result of activity initiated from theoperator console or from Management Console. The request is rejected.

Message Variables:

name—The subscription name.

Message Destination—Product administration log

System Action—None

Operator Response—Issue the DSPACT command to determine if the subscriptionis active. If the subscription is inactive, issue the same request again.

Client Administrator Response—Determine the status of the subscription inManagement Console. Issue the same request again in the event that thesubscription is now inactive.

CHC0015ICHC0015I Event log cleanup is complete. read records were read, deleted recordswere deleted.

Explanation—An event log cleanup cycle has completed. The event log cleanup isrun either at product start up, or a preset time each day, depending on the systemparameters. All messages older than the configured number of days will bedeleted.

Message Variables:

read—The number of event messages read.

deleted—The number of event messages deleted.

Message Destination—System log


Operator Response—None

Client Administrator Response—This is a product issue. For more information,contact IBM Technical Support.

CHC0023WCHC0023W There are no tables to mirror or refresh to subscription. The subscriptionis ending.

Explanation—An attempt to start data refresh or mirroring to a subscription hasbeen made even though no tables are selected for replication to the subscription orno tables can be found that satisfy the replication criteria.


Message Variables—None


System Action—Replication to subscription environments is not started.

Operator Response—Contact the client administrator.

Client Administrator Response—For each table that is selected to replicate data tothe specified subscriptions, verify the status of the table to ensure that it can berefreshed or mirrored. If no tables are selected for replication to the subscription,select one or more tables before starting replication.

CHC0024WCHC0024W The .User ID does not have sufficient DB2 authority to view subscriptions.

Explanation—The security identifier specified to access InfoSphere CDC metadatafor a datastore does not have sufficient DB2 authority to view existingsubscriptions. The security identifier is specified in Access Manager for a specificdatastore.



System Action—In Management Console, no existing subscriptions under thedatastore are displayed.


Client Administrator Response—If you need to work with existing subscriptions,specify a security identifier that has sufficient DB2 authority to work with existingsubscriptions, or change the DB2 authority granted to the current security identifierto a level that allows existing subscriptions to be displayed. If you only need tocreate new subscriptions under the datastore, this message can be ignored.

CHC0025WCHC0025W The User ID and Password combination is not valid.

Explanation—The security identifier and password combination specified to accessInfoSphere CDC metadata for a datastore is not valid. The security identifier andpassword combination is specified in Access Manager for a specific datastore.



System Action—Through Management Console, a connection to the datastore isdenied.


Client Administrator Response—Specify a valid security identifier and passwordcombination. After making the necessary changes, attempt to connect to thedatastore in Management Console.


CHC0026WCHC0026W The associated password for the User ID has expired.

Explanation—The password associated with the security identifier specified toaccess InfoSphere CDC metadata for a datastore has expired. The security identifierand password combination is specified in Access Manager for a specific datastore.



System Action—The attempt to connect to the datastore was not prevented as aresult of the expired password. An incorrect password (see CHC0025W) wouldhave prevented a connection to the datastore.


Client Administrator Response—Change the current password associated with thesecurity identifier.Related reference


CHC0027WCHC0027W The definition of source table owner.table has not been altered. Anupdate of the definition is not required.

Explanation—The re-add function was applied to a table that has not had itsdefinition changed. The re-add function is issued internally in ManagementConsole, and is required when the definition of a table has changed.

Message Variables:

owner—The owner of the table.

table—The name of the table.




Client Administrator Response—Re-adding a table that has not been changed hasno negative impact. However, check that the selected table is the one that youwant to re-add. If the wrong table was selected in Management Console, apply there-add function to the desired table.

CHC0029ECHC0029E Unable to retrieve security group information for Authorization ID id.

Explanation—No RACF user group lists were returned to InfoSphere CDC for thespecified security identifier. The security identifier is being used to access anInfoSphere CDC datastore. This message is generated when a connection to anInfoSphere CDC replication agent is attempted in Management Console.


Message Variables:

id—The security identifier that is being used to access an agent in ManagementConsole.


System Action—The attempt to establish a connection will be denied.


Client Administrator Response—Contact your RACF administrator to indicatethat there is a problem associated with the specified security identifier. Note themessage number and contact your InfoSphere CDC administrator if you requirefurther assistance.

CHC0030ECHC0030E There was an error accessing the event log. The PAL task returned errorcode=code (text), reason code= number (reason).

Explanation—A request to retrieve event log messages has failed.

Message Variables:

code—The numeric error code returned by the Product Administration Log task.

text—Text describing the error encountered.

number—The numeric reason code returned by the Product Administration Logtask.

reason—Text describing the reason for the error.

Message Destination—Message box in Management Console

System Action—The request for event log messages is denied.

Operator Response—Examine the system log to identify any messages that arerelated to this problem.

Client Administrator Response—Record the message number. Contact yourInfoSphere CDC administrator or IBM representative for assistance.

CHC0031ECHC0031I An invalid message ID was entered. Message IDs must be numeric, and inthe range of low to high.

Explanation—You have entered an invalid message identifier in the FilterMessages dialog box in Management Console. The message may be invalidbecause it contains non-numeric characters, or because the number is either toolow or too high.

Message Variables:

low—The lowest message ID supported for filtering.


high—The highest message ID supported for filtering.


System Action—The request to filter messages is denied.

Operator Response—Correct the message identifiers to be all numeric, within theallowed range. Each message identifier must be entered on a separate line in thedialog box.


CHC0040ICHC0040I Persistent subscription name will be started.

Explanation—InfoSphere CDC issues this message during its initialization. Thepersistent subscription identified in the message will start because it was active thelast time InfoSphere CDC was shut down.

Message Variables:



System Action—The named subscription will be started.


Client Administrator Response—None

CHC0044ICHC0044I Mirroring has been initiated for subscription name.

Explanation—InfoSphere CDC has started mirroring data for the specifiedsubscription.

Message Variables:



System Action—As indicated in the message text.



CHC0046ICHC0046I Scraping begins with data written at time (Log Position position).


Explanation—Identifies the timestamp and position in the DB2 Log of the changerecord that was scraped first after activation of data mirroring to a specificsubscription in Management Console. The message does not infer that the changerecord causing this message to be generated has been sent to the target server.

Message Variables:

time—The timestamp of the change record that indicates when it was written tothe DB2 Log. The timestamp is based on the system clock.

position—The LRSN or RBA value that indicates the position of the change recordin the DB2 Log.





CHC0047ICHC0047I The first change sent with data was written at time (Log Positionposition).

Explanation—Identifies the timestamp and position in the DB2 Log of the changerecord that was sent first after activation of data mirroring to a specificsubscription in Management Console. Due to commitment control and staging, thechange record identified in the message text is not necessarily the first one scrapedfrom the DB2 Log. It is the first change record in the first commit group that hasmet the requirements for transmission to the target server.

Message Variables:







CHC0050ECHC0050E Data with an invalid length was received for variable length columnname in table table. The received length is received, the maximum length for thecolumn is maximum. Transaction URID is id, record RBA/LRSN is rba.

Explanation—An invalid length was received for a variable length column. TheDB2 Log data length is greater than the maximum length defined for the column.


Message Variables:

name—The name of the source column that contains invalid data.

table—The name of the table that contains column name.

received—The length of the data in the DB2 Log.

maximum—The maximum length allowed for the column.

id—The DB2 Log Unit of Recovery (Commit Group) ID. This value can be used tolocate the commit group in the DB2 Log that contains the invalid data.

rba—The DB2 RBA or LRSN of the log record in error. This value can be used tolocate the log record in the DB2 Log that contains the invalid data.


System Action—An SVC dump will be generated and data mirroring to thesubscription environment will end.


Client Administrator Response—This message frequently occurs after running theREORG utility on a compressed table space while mirroring is not active. In thiscase, DB2 is unable to decompress old log data created prior to the REORGexecution. The corrective action to be taken is to refresh the table.

Otherwise, if this message occurs in the absence of a REORG being performed, orwhen the table space is not compressed, run the DB2 DSN1LOGP utility to retrievethe commit group. Note the information contained in the message and contactyour InfoSphere CDC administrator if you require further assistance.

CHC0051WCHC0051W The oldest open commit group in the staging space for subscriptionname opened at time has exceeded the open commit group warning ageof maximum minutes by exceeds minutes.

Explanation—The oldest open commit group in the staging space for thesubscription identified in the message has an age that is older than the warningperiod that is set through the OPENCOMMITWARNAGE configuration controlstatement keyword. This message is generated each time a check is made of theoldest open commit group, and the age of this commit group exceeds the specifiedwarning period. InfoSphere CDC conducts a check of each staging space every 15minutes.

Message Variables:

name—The name of the subscription defined in Management Console associatedwith the staging space.

time—The date and time (in ISO format) when the commit group was opened.

maximum—The maximum age of the oldest open commit group that can exist in astaging space without a warning message being generated, as defined by theOPENCOMMITWARNAGE configuration control statement keyword.


exceeds—The number of minutes that the oldest open commit group exceeds themaximum age identified in maximum.




Client Administrator Response—Open commit groups may indicate potentialproblems that could surface at a later time. If the oldest open commit group isrelatively large, or there are a number of other open commit groups in the stagingspace, the contents of the staging space may reach capacity at a later time. As aresult, replication will be interrupted. Investigate the reasons for the open commitgroups, and take appropriate actions. Use the InfoSphere CDC REPORT commandto generate a staging space report that may provide more information aboutpotential problems.

CHC0052WCHC0052W The staging space for subscription name received a record out ofsequence: URID = id, PrevRecRBA = position. The record was discarded.

Explanation— A record in a commit group that has a DB2 Log position less thanor equal to the log position of the last commit group record in the staging spacehas been encountered.

Message Variables:

name—The name of the subscription defined in Management Console associatedwith the staging space.

id—The DB2 Log unit of recovery (commit group) identifier. This item ofinformation can be used to identify the commit group in the staging space that hasreceived the out-of-sequence record.

position—The position (either RBA (relative byte address) or LRSN (log recordsequence number)) in the DB2 Log of the last record for the commit group in thestaging space. The record that resulted in this message being generated has a logposition less than or equal to position.


System Action—The out-of-sequence record is discarded, as it is assumed thatInfoSphere CDC has already processed this record. Active replication continues.

Operator Response—Although replication activity continues, you may want togenerate a staging space report that may indicate problems that could surface at alater time. Use the InfoSphere CDC REPORT command to generate a staging spacereport.


CHC0055ICHC0055I Subscription subscription has been queued for restart.


Explanation—InfoSphere CDC is able to automatically restart continuous mirroringfor a persistent subscription at a later time. Continuous mirroring for the persistentsubscription stopped in response to a normal or abnormal termination of server,network, or database components in your replication configuration. InfoSphereCDC is able to automatically restart continuous mirroring for this subscription. .

Message Variables:

subscription—The name of the persistent subscription for which continuousmirroring can be automatically restarted.


System Action—Continuous mirroring for the persistent subscription willautomatically restart when server, network, and database components in yourreplication configuration are operational.


Client Administrator Response—CHC0056I is generated when continuousmirroring for the persistent subscription will automatically restart. If necessary,contact your system, network, and database administrators to inquire as to whenall components in your replication configuration will be operational.Related reference

“CHC0056I”

CHC0056ICHC0056I System host is now available. Subscription name will berestarted.

Explanation—Server, network, and database components in your replicationconfiguration are operational and continuous mirroring will automatically restartfor the identified persistent subscription.

Continuous mirroring for the persistent subscription stopped in response to anormal or abnormal termination of server, network, or database components inyour replication configuration. However, these components are now operationaland since a connection to the identified target server has been established,continuous mirroring will automatically restart.

Message Variables:

host—The host name of the target server to which a connection has beenestablished.

name—The name of the persistent subscription for which continuous mirroring willbe automatically restarted.


System Action—Continuous mirroring for the persistent subscription willautomatically restart.




CHC0057ICHC0057I System host is unavailable. A restart of subscription name willbe retried in number minutes.

Explanation—An attempt to automatically restart continuous mirroring for apersistent subscription was unsuccessful. The next attempt will be made after thespecified number of minutes. Continuous mirroring for the persistent subscriptionstopped in response to a normal or abnormal termination of communications orservers in your replication configuration. While continuous mirroring for thissubscription can be automatically restarted, the last attempt to restart wasunsuccessful as a connection could not be reestablished with the target server. Youcan set how often InfoSphere CDC attempts to automatically restart continuousmirroring for all persistent subscriptions by modifying theAUTORESTARTINTERVAL configuration control statement keyword.

Message Variables:

host—The host name of the target server to which a connection cannot bereestablished.

name—The name of the persistent subscription for which continuous mirroring canbe automatically restarted.

number—The amount of time, in minutes, before the next attempt is made toautomatically restart continuous mirroring for the persistent subscription. Thenumber of minutes identified in the message text is the current setting for theAUTORESTARTINTERVAL keyword.


System Action—Another attempt will be made to automatically restart continuousmirroring after the specified number of minutes.


Client Administrator Response—CHC0056I is generated when continuousmirroring for the persistent subscription will automatically restart. If necessary,contact your system, network, and database administrators to inquire as to whenall components in your replication configuration will be operational.Related reference


CHC0058ECHC0058E Column name in table table has an unknown data type: type.

Explanation—An invalid or unsupported data type was encountered for thespecified column.

Message Variables:

name—The name of the column that has an invalid data type.

table—The name of the table that contains column name.


type—The data type of the column.


System Action—Data mirroring to the subscription environment will end.


Client Administrator Response—InfoSphere CDC cannot replicate the columndata. An upgraded or enhanced version of InfoSphere CDC might be availablewhich can handle the column data type.

CHC0059ECHC0059E Unable to map source column srccol of type srctype to destinationcolumn tgtcol of type tgttype.

Explanation—A Management Console session attempted to map a source tablecolumn to an incompatible target table column.

Message Variables:

srccol—The name of the source column.

srctype—The numeric network type of the source column.

tgtcol—The name of the target column.

tgttype—The DB2 type of the target column.

Message Destination—Product administration log and message box inManagement Console

System Action—The mapping was not performed.


Client Administrator Response—In Management Console, map the source columnto a target column of compatible type. Alternatively, set the source column to beunmapped.

CHC0060ICHC0060I The bookmark pos1, pos2, pos3 for subscription name has beenconverted from version original to version converted.

Explanation—The bookmark for the named subscription has been converted fromits previous format to a different, probably newer, format. This is normally done tosupport new functionality in the latest version of DB2.

Message Variables:

pos1, pos2, pos3—Hexadecimal data representing the three log positions thatcomprise the bookmark. Each position is either an RBA or LRSN value from theDB2 log.

name—The name of the subscription for which the bookmark was converted.


original—The numeric version of the original bookmark.

converted—The numeric version of the newly converted bookmark.


System Action—Normal processing continues.



CHC0061ECHC0061E An invalid or unsupported bookmark version number has been encounteredfor subscription name.

Explanation—When starting a subscription, it was determined that the version ofthe subscription’s bookmark is higher than the current version of the product canaccept.

Message Variables:

number—The numeric version of the subscription’s bookmark.



System Action—The subscription fails to start.


Client Administrator Response—It is likely that the product has previously beenupgraded to a newer version and then reverted back to the current version. Recordthe message number and contact technical support to obtain assistance in revertingthe subscription’s bookmark to the previous version.

CHC0068ECHC0068E Table table schema schema has been changed since it was selected forreplication.

Explanation—The specified table was physically changed (for example, a columnwas added to or deleted from the table) in the database between the time it wasselected for replication and when replication was started.

Message Variables:

table—The name of the table that was physically changed in the database.

schema—The database where the table is located. The database is expressed in theform <database>.<user> (the <user> component identifies who created the table).



System Action—Data mirroring to the subscription environment is not started.


Client Administrator Response—In Management Console, update the source tabledefinition for the subscription. Verify table mappings in the subscriptionenvironment. Start replication again.

CHC0069ECHC0069E Table schema.table does not exist.

Explanation—The specified table was physically deleted in the database betweenthe time the list of tables was presented in Management Console and when thespecified table was selected for replication to a defined subscription. InfoSphereCDC was unable to locate the physical table when it was being selected forreplication in Management Console.

Message Variables:


table—The name of the table that was physically deleted in the database.




Client Administrator Response—In Management Console, refresh the list of tablesthat can be selected for replication. If necessary, select a different table forreplication.

Tip: In Management Console, refresh the list of tables by using the Refreshfunction. It may be necessary to disconnect and reconnect to the datastore to seethe current list of tables.

CHC0071ECHC0071E Unable to map the Journal Control Field name of type type to destinationcolumn column of type target. Journal Control Fields can only be mapped to columnswith compatible types.

Explanation—InfoSphere CDC could not map the specified journal control field tothe column in the target table. The data type of the column is not compatible withthe data type of the journal control field.

Message Variables:

name—The journal control field that could not be mapped to the column.

type— The data type of the journal control field.

column—The column in the target table that could not be mapped to the journalcontrol field.


target—The data type of the column in the target table.




Client Administrator Response—Modify the mapping so that the data type of thecolumn is compatible with the data type of the journal control field.

Tip: In an expression, you can apply one of the conversion column functions to ajournal control field to produce a value that is compatible with the data type of thesubscription table column.

CHC0072WCHC0072W number error messages have been suppressed during replication.

Explanation—Identifies the number of error messages that have been suppressedduring a replication operation (mirroring or refresh). This message is generatedonly when more than 25 error messages have been generated, and the operationhas been configured to continue after encountering nonrecoverable errors.

Message Variables:

number—The number of error messages that were suppressed after the initial 25messages were generated.





CHC0073WCHC0073W The value in keyword key is incorrect. The default value will be used.

Explanation—A value assigned to the specified keyword defined in a configurationcontrol statement is incorrect. The default value will be used.

Message Variables:

key—The name of the keyword in a configuration control statement that has beenassigned an incorrect value.

Message Destination—Product administration log and system log

System Action—The default value for the keyword is used.

Operator Response—Make the necessary correction to the statement in theconfiguration control data set that references the specified keyword and restart theInfoSphere CDC address space. If the default value identified in IBM InfoSphereCDC Installation/Upgrade on page 31 is desired, you can ignore this message.



CHC0075ECHC0075E User id does not possess sufficient authority to create tables in databasedb.

Explanation—The specified security identifier used to access an InfoSphere CDCreplication agent does not possess sufficient authority to create tables in a database.In Management Console, you can create a target table to receive replicated datafrom an mapped source table. Sufficient authority is required to complete this stepin the process of configuring replication.

Message Variables:


db—The database where tables cannot be created.




Client Administrator Response—Contact your database administrator to grant thez/OS user the authority to create tables in the specified database. Alternatively,select a different database that allows tables to be created by the specified z/OSuser.

CHC0077ECHC0077E Index owner.name on table owner.table does not exist.

Explanation—The named index for a target table could not be found.

Message Variables:

owner—The owner of the target table index.

name—The name of the target table index.

owner—The owner of the target table.

table—The name of the target table.


System Action—Mirroring ends for the subscription containing the table.


Client Administrator Response—In Management Console, refresh the list of tablesthat can be selected for replication.


Tip: In Management Console, refresh the list of table by using the Refreshfunction. It may be necessary to disconnect and reconnect to the datastore to seethe current list of tables.

CHC0078ECHC0078E Invalid value of value was received for the assignment type.

Explanation—InfoSphere CDC has received an invalid value for the assignmenttype selected in Management Console. This error may result because the version ofInfoSphere CDC is not supported by Management Console.

Message Variables:

value—The internal value that InfoSphere CDC has received for the assignmenttype.


System Action—The table mapping could not be created.

Operator Response—Report the error to your system administrator.

Client Administrator Response—Verify in your documentation that the versions ofInfoSphere CDC and Management Console that you have installed are compatible.If you have installed compatible versions and are still receiving the error, contactIBM Technical Support for assistance.

CHC0079ECHC0079E Invalid value of value was received for the multiple source flag.

Explanation—InfoSphere CDC has received an invalid value for the multiplesource flag. This flag indicates if you want to replicate multiple source tables totarget tables. This error may result because the version of InfoSphere CDC is notsupported by Management Console.

Message Variables:

value—The internal value that InfoSphere CDC has received for the multiplesource flag.





CHC0080ECHC0080E Invalid value of value was received for the number of the summarization orconsolidation key column in the target table.


Explanation—InfoSphere CDC has received an invalid value for the number of thesummarization or consolidation key column in the target table. This error mayresult because the version of InfoSphere CDC is not supported by ManagementConsole.

Message Variables:

value—The internal value that InfoSphere CDC has received for thesummarization/consolidation key column.





CHC0081ECHC0081E Summarization or consolidation column name is nullable. Nullable columnsare not supported as summarization or consolidation keys.

Explanation—InfoSphere CDC has received a request to designate a nullablecolumn as a summarization/consolidation key. Summarization/consolidation keycolumns cannot be nullable.

Message Variables:

name—The column name specified as summarization/consolidation key.



Operator Response—In Management Console, select a summarization/consolidation column that is not nullable.


CHC0082ICHC0082I Persistent subscription name will not be started because it ismarked inactive.

Explanation—InfoSphere CDC issues this message during its initialization. Thepersistent subscription identified in the message will not start because it was eithernot active the last time InfoSphere CDC was shut down or it failed.

Message Variables:







CHC0083ICHC0083I Persistent subscription name will not be started because it ismarked failed.

Explanation—InfoSphere CDC issues this message during its initialization. Thepersistent subscription identified in the message will not start because it was eithernot active the last time InfoSphere CDC was shut down or it failed.

Message Variables:






CHC0095ECHC0095E Logoff failed with return code code.

Explanation—While attempting to terminate a Management Console session, thelogoff of the user from the access control facility failed.

Message Variables:

code—The return code from the access control facility being used.


System Action—InfoSphere CDC terminates the Management Console session, butthe user may remain signed on to the access control facility.


Client Administrator Response—Look up the return code in the access controlfacility documentation and take the necessary corrective action.

CHC0099ICHC0099I SQL Information: text.

Explanation—An informational SQL code was received. The text field contains themessage text associated with the code.

Message Variables:


text—The text interpretation of the code.






“CHC0100W”“CHC0101I” on page 258“CHC0102E” on page 258“CHC0104E” on page 258“CHC0105E” on page 259“CHC0107I” on page 259“CHC0108E” on page 260“CHC0109E” on page 260“CHC0110E” on page 260“CHC0112E” on page 261“CHC0113E” on page 261“CHC0115W” on page 261“CHC0116E” on page 262“CHC0117W” on page 262“CHC0118E” on page 263“CHC0119E” on page 263“CHC0120I” on page 264“CHC0121I” on page 264“CHC0122I” on page 264“CHC0123I” on page 264“CHC0129I” on page 265“CHC0130I” on page 265“CHC0136I” on page 266“CHC0137I” on page 267“CHC0143E” on page 267“CHC0144E” on page 268

CHC0100WCHC0100W SQL warning: text.

Explanation—A warning SQL code was received. The text field contains themessage text associated with the code.

Message Variables:

text—The text interpretation of the SQL code.






CHC0101ICHC0101I Failing SQL: text.

Explanation—This message identifies a failing statement in a user-specified SQLstatement for after clear or after refresh processing.

Message Variables:

text—The user-specified SQL statement.


System Action—Replication continues or ends based on the ENDONERRORkeyword setting.


Client Administrator Response—Check for previous messages that identify thereason for the error.

CHC0102ECHC0102E SQL error: message.

Explanation—Identifies a generated SQL error message that is relayed to theproduct administration log.

Message Variables:

message— A generated SQL error message.


System Action—The component (Management Console, instance, and so on) thatcaused the SQL error message to be generated will stop.


Client Administrator Response—Note the SQL message text and contact yourdatabase administrator for further assistance.

CHC0104ECHC0104E The DB2 plan for task name requires a re-bind.

Explanation—The DB2 plan for the identified InfoSphere CDC task is notup-to-date.


Message Variables:

name—The InfoSphere CDC task whose plan is not up-to-date.


System Action—The identified InfoSphere CDC task stops running.

Operator Response—Rebind the plan for the identified InfoSphere CDC task. Thename of the plan to rebind is determined from the name of the task. For example,if the name of the task is DSC, the plan that needs rebinding is named CHCDSCxx,where xx is the plan suffix specified in the PLANSUFFIX configuration controlstatement keyword.


CHC0105ECHC0105E The DB2 plan plan for task task does not exist or access was not granted.

Explanation—The DB2 plan for the identified InfoSphere CDC task does not exist,or the security identifier assigned to InfoSphere CDC does not have execute accesson the plan.

Message Variables:

plan—The name of the DB2 plan associated with the identified task.

task—The name of the InfoSphere CDC task.



Operator Response—Determine whether or not the plan exists on the server. If itdoes not exist, bind the plan server. If it does exist, grant execute access on theplan to the security identifier assigned to InfoSphere CDC.


CHC0107ICHC0107I Executing on DB2 V8 with V7 metadata.

Explanation—InfoSphere CDC is running on a server where DB2 version 8.1 hasbeen installed, but the InfoSphere CDC metadata is still at the version 7.1 level.This message is generated when the InfoSphere CDC address space is started.Specific DB2 version 8.1 features and functions supported by InfoSphere CDC arenot available when the InfoSphere CDC metadata is at the DB2 version 7.1 level.For example, support for long names in DB2 version 8.1 is not available.



System Action—The InfoSphere CDC address space is started normally.



Client Administrator Response—To use the DB2 version 8.1 features and functionsthat are supported by InfoSphere CDC, shut down the InfoSphere CDC addressspace and upgrade the InfoSphere CDC DB2 metadata tables to be compatible withDB2 version 8.1 or above.

CHC0108ECHC0108E Invalid value of value received for the Conflict Resolution method.

Explanation—The agent received an invalid Conflict Resolution method value.

Message Variables:

value—The invalid value received.

Message Destination—Product administration log and Management Console

System Action—Conflict Detection configuration is halted.



CHC0109ECHC0109E Invalid value of value received for the Conflict Detection column selectionflag.

Explanation—The agent received an invalid Conflict Detection column selectionflag.

Message Variables:






CHC0110ECHC0110E Invalid value of value received for the Conflict Resolution user exit type.

Explanation—The agent received an invalid Conflict Resolution user exit typevalue.

Message Variables:







CHC0112ECHC0112E An internal error occurred while processing request value.

Explanation—The agent encountered an error while it was processing a request.

Message Variables:

value—The request value from the message.


System Action—The current action being performed by the agent is halted.



CHC0113ECHC0113E Request value was not expected in a group request.

Explanation—The agent was processing a group request message and itencountered an unexpected request.

Message Variables:

value—The request value from the message.


System Action—The current action being performed by the agent is halted.



CHC0115WCHC0115W Attribute name in table owner.table has an illegal summarization typetype in the metadata.

Explanation—The InfoSphere CDC detected an illegal summarization type in themetadata.

Message Variables:


name—The name of the table attribute that has an illegal mapping.



type—The illegal summarization type that was detected in the metadata.





CHC0116ECHC0116E Error accessing the metadata. The PAL task returned reason code=code.

Explanation—A request to retrieve or set Notifications has failed.

Message Variables:

code—The numeric reason code returned by the Product Administration Log task.


System Action—The request to manipulate Notifications is denied.

Operator Response—Examine the system log to identify any messages that arerelated to this problem.

Client Administrator Response—Further investigation is required. Record themessage number and text, and then contact IBM Technical Support.

CHC0117WCHC0117W The metadata contains an undefined value of value for the describerequired attribute of table table in subscription name.

Explanation—The metadata contains an unexpected value for the flag thatindicates whether a describe is required for a given table in a given subscription.

Message Variables:

value—The unexpected numeric value of the describe required flag. Expectedvalues are 1 (describe required) and 2 (describe not required).





System Action—The unexpected value is treated as a value of 2 (describe notrequired) and normal processing continues.


Client Administrator Response—Further investigation is required to determinehow the metadata was corrupted. Contact IBM Technical Support.

CHC0118ECHC0118E Target column name of type type cannot be mapped to the constant name.

Explanation—A Management Console session has attempted to map a target tablecolumn to a constant of incompatible type. Most likely, an attempt has been madeto map a numeric column to a non-numeric constant.

Message Variables:

name—The name of the column.

type—The DB2 type of the column.

name—The constant.




Client Administrator Response—In Management Console, map the column to aconstant of compatible type.

CHC0119ECHC0119E A request was received out of sequence.

Explanation—A Management Console session has sent an unexpected request tothe InfoSphere CDC agent.



System Action—The request is disallowed.




CHC0120ICHC0120I Mirroring has been ended normally for subscription name.

Explanation—All mirroring activity for the specified subscription has ended.

Message Variables:






CHC0121ICHC0121I Mirroring has been ended abnormally for subscription name.


Message Variables:






CHC0122ICHC0045I Mirroring has been ended by the operator for subscription name.


Message Variables:






CHC0123ICHC0123I Mirroring has been ended immediately by the operator for subscriptionname.



Message Variables:






CHC0129ICHC0129I The latest scraped data was written at time. number changes were sent.The current Log Position is position.

Explanation—Identifies the timestamp of the most recent change record scrapedfrom the DB2 Log at the time this message was generated. The message alsoindicates the number of change records that have been sent to the target serversince activation of data mirroring to a specific subscription in ManagementConsole, and the current position in the DB2 Log. If the DB2 Log positionidentified in the message text is the head of the DB2 Log, the first message thatreports this condition contains an indicator. How frequently this message isgenerated is determined by the REPSTATSINTERVAL configuration keyword. If thetimestamp referenced in the message text is constant across a number of generatedmessages, this could mean that there is no more change records to process.

Message Variables:


number—The number of change records that have been sent to the target serversince the activation of data mirroring to a specific subscription in ManagementConsole.






CHC0130ICHC0130I The latest scraped data was written at time. number changes were sent.The current Log Position is position *Head of Log*.

Explanation—Identifies the timestamp of the most recent change record scrapedfrom the DB2 Log at the time this message was generated. The message also


indicates the number of change records that have been sent to the target serversince activation of data mirroring to a specific subscription in ManagementConsole, and the current position in the DB2 Log. If the DB2 Log positionidentified in the message text is the head of the DB2 Log, the first message thatreports this condition contains an indicator. How frequently this message isgenerated is determined by the REPSTATSINTERVAL configuration keyword. If thetimestamp referenced in the message text is constant across a number of generatedmessages, this could mean that there is no more change records to process.

Message Variables:


number—The number of change records that have been sent to the target serversince the activation of data mirroring to a specific subscription in ManagementConsole.






CHC0136ICHC0136I Scraping ends with data written at time. number changes were sent.The current Log Position is position.

Explanation—Identifies the timestamp of the change record in the DB2 Log thatwas scraped last before data mirroring to a specific subscription in ManagementConsole was stopped. The message also indicates the number of change recordsthat have been sent to the target server between the starting and stopping of datamirroring to a specific subscription in Management Console, and the currentposition in the DB2 Log. If the DB2 Log position identified in the message text isthe head of the DB2 Log, the message indicates this condition.

Message Variables:


number—The number of change records that have been sent to the subscriptionserver between the starting and stopping of data mirroring to a specificsubscription in Management Console.







CHC0137ICHC0137I Scraping ends with data written at time. number changes were sent.The current Log Position is position *Head of Log*.

Explanation—Identifies the timestamp of the change record in the DB2 Log thatwas scraped last before data mirroring to a specific subscription in ManagementConsole was stopped. The message also indicates the number of change recordsthat have been sent to the target server between the starting and stopping of datamirroring to a specific subscription in Management Console, and the currentposition in the DB2 Log. If the DB2 Log position identified in the message text isthe head of the DB2 Log, the message indicates this condition.

Message Variables:


number—The number of change records that have been sent to the target serverbetween the starting and stopping of data mirroring to a specific subscription inManagement Console.






CHC0143ECHC0143E User id is not authorized to add table owner.table.

Explanation—The specified security identifier used to access an InfoSphere CDCdatastore does not possess sufficient authority to perform an operation on a table.

Message Variables:








Client Administrator Response—Contact your database administrator to grant thez/OS user access to the specified table (SELECT authority for source table access,and INSERT, DELETE, and UPDATE authority for target table access).

CHC0144ECHC0144E User id is not authorized to assign table owner.table.

Explanation—The specified security identifier used to access an InfoSphere CDCdatastore does not possess sufficient authority to perform an operation on a table.

Message Variables:







Client Administrator Response—Contact your database administrator to grant thez/OS user access to the specified table (SELECT authority for source table access,and INSERT, DELETE, and UPDATE authority for target table access).


“CHC0211E” on page 269“CHC0212E” on page 270“CHC0213E” on page 270“CHC0220I” on page 270“CHC0221I” on page 271“CHC0222I” on page 271“CHC0223I” on page 272“CHC0224W” on page 272“CHC0225E” on page 272“CHC0226I” on page 273“CHC0227I” on page 273“CHC0228E” on page 274“CHC0231I” on page 274“CHC0232E” on page 275“CHC0233E” on page 276“CHC0235W” on page 276“CHC0236E” on page 276


“CHC0237W” on page 277“CHC0238E” on page 277“CHC0240E” on page 278“CHC0244I” on page 278“CHC0246I” on page 279“CHC0247E” on page 279“CHC0248E” on page 280“CHC0254I” on page 281“CHC0255I” on page 281“CHC0256I” on page 282“CHC0257I” on page 282“CHC0263I” on page 282“CHC0264I” on page 283“CHC0265I” on page 283“CHC0266I” on page 284“CHC0272I” on page 284“CHC0273I” on page 285“CHC0274I” on page 285“CHC0275I” on page 285“CHC0281I” on page 286“CHC0282I” on page 286“CHC0283I” on page 287“CHC0289I” on page 287“CHC0290I” on page 287“CHC0291I” on page 288

CHC0211ECHC0211E Table table, has no columns selected for replication. Table will notbe described.

Explanation—None of the columns in the named table has been selected forreplication in Management Console. At least one column in the table must beselected before performing the describe operation.

Message Variables:

table—The name of the table that has no column selected for replication.


System Action—The describe operation continues, but the specified table is notdescribed successfully.


Client Administrator Response—In Management Console, select one or morecolumns for replication in the named table. After selecting at least one column,perform the describe operation again.


CHC0212ECHC0212E The describe for table table was not successful. Check the target formore details.

Explanation—The identified source table could not be described successfully as aresult of a problem in the target environment.

Message Variables:

table—The name of the source table that could not be described successfully.


System Action—The describe operation continues for other source tables selectedfor replication to the same subscription, but the describe for the identified table isnot successful. This table can only be replicated after it has been describedsuccessfully.


Client Administrator Response—Examine messages generated in the targetenvironment to determine the cause of the problem. Perform the necessarycorrective actions, and redescribe the identified table in Management Console.

CHC0213ECHC0213E A request was received for describe of table table. The table was notfound.

Explanation—A request was received from the subscription environment todescribe the identified source table. However, the table is not currently selected forreplication.

Message Variables:

table—The name of the source table that is not currently selected for replication.


System Action—The describe operation continues for other source tables selectedfor replication to the same subscription, but the describe for the identified table isnot successful.

Operator Response—Note the message number and issue the DSPACT=ALLcommand to obtain information about current InfoSphere CDC activity. Aftercollecting the information, contact your InfoSphere CDC administrator for furtherassistance.


CHC0220ICHC0220I The control task for subscription name is starting.

Explanation—The InfoSphere CDC control task for the identified subscriptionidentifier is starting. The control task on a server manages activity on acommunications link that is used to coordinate data replication for a specific


subscription identifier. The task is starting in order to perform the initialcommunications handshake with another server.

Message Variables:

name—The name of the subscription identifier, as defined in Management Console.





CHC0221ICHC0221I The control task for subscription name is terminating.

Explanation—The InfoSphere CDC control task for the identified subscriptionidentifier is ending normally. The control task on a server manages activity on acommunications link that is used to coordinate data replication for a specificsubscription identifier. The task is ending normally, which means that transfersconducted on the communications link are ending as well.

Message Variables:






CHC0222ICHC0222I The data task for subscription name is starting.

Explanation—The InfoSphere CDC data task for the identified subscriptionidentifier is starting. The data task on a server manages activity on acommunications link that is used to transmit replicated data for a specificsubscription identifier. This task is starting to prepare for data replication after asuccessful communications handshake with another server.

Message Variables:







CHC0223ICHC0223I The data task for subscription name is terminating.

Explanation—The InfoSphere CDC data task for the identified subscription isending. The data task on a server manages activity on a communications link thatis used to transmit replicated data for a specific subscription identifier. The task isending normally, which means that data replication conducted on thecommunications link is ending as well.

Message Variables:






CHC0224WCHC0224W Table database.owner.table could not be refreshed to subscription name.The total selected length is too long.

Explanation—The specified table contains records that exceed a certain length. Asa result, the table cannot be refreshed to the specified subscription.

Message Variables:

database—The database where the table is located.

owner—The DB2 owner of the table.

table—The name of the table containing records that cannot be refreshed to thespecified subscription.

name—The name of the subscription that cannot receive the specified table due tothe length of its records.


System Action—The specified table is not refreshed to the named subscription.


Client Administrator Response—Note the message number and contact yourdatabase administrator for further assistance. The length of specific records in thetable has to be reduced before the table can be refreshed by InfoSphere CDC.

CHC0225ECHC0225E No response was received from the remote system.


Explanation—The InfoSphere CDC control task on the local server was unable toestablish a conversation with a remote server within the timeout period.

The control task manages activity on a communications link that is used tocoordinate data replication for a specific subscription.



System Action—The control task on the local server ends.


Client Administrator Response—If the problem persists, contact the systemadministrator for the remote server to determine if there are problems that arepreventing the conversation from being established. After taking necessarycorrective actions, repeat the operation performed in Management Console.

CHC0226ICHC0226I Refresh was started to subscription name for table schema.table.

Explanation—A data refresh of the specified table has been started to the namedsubscription.

Message Variables:

name—The name of the subscription, as defined in Management Console.


table—The name of the table that will be refreshed to the specified subscription.





CHC0227ICHC0227I Refresh was completed to subscription name for table schema.table.Target environment reports received rows were received, applied rows wereapplied, number rows not applied.

Explanation—A data refresh of the specified table has been completed to thenamed subscription. The number of rows received and applied in the subscriptionenvironment as well as the number of errors encountered are identified in themessage text.

Message Variables:




table—The name of the table that was refreshed to the specified subscription.

received—The number of rows received by the target.

applied—The number of rows applied to the target table.

number—The number of errors encountered by the target.





CHC0228ECHC0228E Refresh to subscription name for table schema.table ended abnormally.

Explanation—The refresh task on the source server has ended abnormally.

Message Variables:



table—The name of the source table that was refreshed to the specifiedsubscription.


System Action—Refresh task on the source server will stop sending replicateddata.


Client Administrator Response—Consult the product administration log for otherrelated messages and perform the necessary corrective actions to resolve theproblem. You have to restart the refresh to ensure source and target tables aresynchronized.

CHC0231ICHC0231I read records were read and sent records were sent to subscription namefor table schema.table.

Explanation—A refresh of the identified source table has completed. The numberof rows read from the source table and sent to the subscription environment areidentified. This message does not indicate whether or not the refresh completedsuccessfully. It is possible that the refresh completed successfully even though thenumber of rows sent to the subscription environment is less than the number of


rows read from the source table. For example, if a row filtering expression hasbeen defined for the source table, and this expression has prevented at least onerow from being refreshed, the refresh operation may have been successful eventhough the number of records read and sent in the message text are not the same.

Message Variables:

read—The number of rows read from the identified source table in the refreshoperation.

sent—The number of rows sent to the target environment in the refresh operation.

name—The name of the subscription for which the refresh was performed.


table—The name of the table that was refreshed to the specified subscription.




Client Administrator Response—Consult the product administration log for otherrelated messages that provide an indication as to whether or not the refresh wassuccessful. If the refresh was unsuccessful, perform necessary corrective actionsbased on the other messages that were generated. To properly synchronize sourceand target tables, a refresh has to be restarted after taking any necessary correctiveactions.

CHC0232ECHC0232E Invalid table ID id was received from target environment.

Explanation—Another message received from the target environment referencedan invalid internal table identifier.

Message Variables:

id—The invalid internal table identifier.


System Action—Replication ends.


Client Administrator Response—Further investigation is required. Record themessage number and internal table identifier referenced in the message text, andthen contact your InfoSphere CDC administrator or IBM representative forassistance.


CHC0233ECHC0233E The control task for subscription name has terminated unexpectedly. Thedata task is terminating.

Explanation—The InfoSphere CDC control task for the identified subscriptionidentifier has ended unexpectedly. As a result, the InfoSphere CDC data task forthe same subscription identifier is stopped. The control task on a server managesactivity on a communications link that is used to coordinate data replication for aspecific subscription identifier. The data task on a server manages activity onanother communications link that is used to transmit replicated data for a specificsubscription identifier.

Message Variables:



System Action—Replication for the subscription identifier ends.


Client Administrator Response—Consult the product administration log for othermessages that provide more details as to why the control task ended unexpectedly.Using the other messages in the log, perform necessary corrective actions.

CHC0235WCHC0235W An error occurred in the row filtering statement for table schema.table.

Explanation—An error has been detected in the row filtering expression that hasbeen defined for the specified table. This message is generated when aninconsistency has been detected in an expression that is syntactically correct. Forinstance, a column name in the expression may not exist in the source table.

Message Variables:


table—The name of the table associated with the row filtering expression.


System Action—The row filtering expression is not evaluated. Replicationcontinues, but row filtering based on the expression may produce undesirableresults. In other words, rows that should be replicated are not sent, or rows thatshould not be replicated are sent.

Operator Response—Other relevant messages in the log provide furtherclarification. Use these messages to correct the row filtering expression.


CHC0236ECHC0236E The data task for subscription name has aborted.


Explanation—The InfoSphere CDC data task for the identified subscription (by itsname or the corresponding source ID) has unexpectedly ended. As a result, theInfoSphere CDC data task for that subscription stops. The data task on a servermanages activity on a communications link that is used to transmit replicated datafor a specific subscription. The control task on a server manages activity onanother communications link that is used to coordinate data replication for aspecific subscription.

Message Variables:

name—The name of subscription or the source ID, as defined in ManagementConsole.


System Action—Replication for the affected subscription ends.


Client Administrator Response—Further investigation is required. Record themessage number and text, and then contact your InfoSphere CDC administrator orIBM representative for assistance.

CHC0237WCHC0237W The refresh of table owner.table to subscription name was endedimmediately. The refresh did not complete.

Explanation—During data refresh, InfoSphere CDC received an immediateshutdown request, either from an operator, or from the remote system. The refreshdid not complete.

Message Variables:







Client Administrator Response—If an operator was not responsible for ending therefresh, check for errors on the target. You must restart the refresh to completereplication.

CHC0238ECHC0238E parent task terminated unexpectedly. child task is terminating.

Explanation—The identified InfoSphere CDC parent task has unexpectedly ended.As a result, its child task is ending as well.


Message Variables:

parent—The three-letter name of the InfoSphere CDC parent task thatunexpectedly ended.

child—The three-letter name of the InfoSphere CDC child task that is ending as aresult of the parent task unexpectedly ending.


System Action—Depending on the tasks referenced in the message text, InfoSphereCDC operations may continue or end.



CHC0240ECHC0240E child task has aborted. parent task is terminating.

Explanation—The identified InfoSphere CDC child task has unexpectedly ended.As a result, its parent task is ending as well.

Message Variables:

child—The three-letter name of the InfoSphere CDC child task that unexpectedlyended.

parent—The three-letter name of the InfoSphere CDC parent task that is ending asa result of the child task unexpectedly ending.


System Action—Depending on the tasks referenced in the message text, InfoSphereCDC operations may continue or end.



CHC0244ICHC0244I Cache initialization failed for subscription name; subscription willcontinue without caching.

Explanation—The DB2 Log caches (Level 1 and Level 2) could not be initializedfor the identified subscription. To improve performance when using multiplesubscriptions to replicate multiple streams of data at the same time, DB2 Logrecords can be retrieved from caches that are managed by InfoSphere CDC.

Message Variables:




System Action—Active mirroring for the subscription continues. Instead ofretrieving records from the caches, records are read from the DB2 Log.



CHC0246ICHC0246I The Level 2 DB2 Log Cache dataset, name, is size MB. The minimum requiredsize is minimum MB.

Explanation—The DB2 Log Cache is being initialized. The size of the Level 2 LogCache dataset is reported. The minimum required size of the dataset, based on theInfoSphere CDC configuration, is also reported. If the dataset is smaller than theminimum required size, the DB2 Log Cache will become inactive. To improveperformance when using multiple subscriptions to replicate multiple streams ofdata at the same time, DB2 Log records can be retrieved from caches that aremanaged by InfoSphere CDC.

Message Variables:

name—The dataset name of the Level 2 DB2 Log Cache dataset.

size—The size, in megabytes, of the Level 2 DB2 Log Cache dataset.

minimum—The minimum required size, in megabytes, of the Level 2 DB2 Log Cachedataset.

Message Destination—Product administration log and InfoSphere CDC audit log

System Action—If the Level 2 DB2 Log Cache dataset is not smaller than theminimum required size, normal processing continues. If the Level 2 DB2 LogCache dataset is smaller than the minimum required size, the DB2 Log Cache willbecome inactive.


Client Administrator Response—If the Level 2 DB2 Log Cache dataset is smallerthan the minimum required size, the problem may be corrected in two ways:

Firstly, the Level 2 DB2 Log Cache dataset may be resized so that it meets orexceeds the minimum required size.

Secondly, the size of the DB2 Log Cache may be reduced by decreasing the settingfor the CACHELEVEL1SIZE configuration control statement keyword. Since theminimum required size of the Level 2 DB2 Log Cache dataset is related to thesetting for the CACHELEVEL1SIZE keyword, this will reduce the minimumrequired size of the Level 2 DB2 Log Cache dataset.

CHC0247ECHC0247E The data type type of column name is not supported for replication.


Explanation—InfoSphere CDC detected a column in a table that has anunsupported data type. The column cannot be referenced in an expression or rowexpression, and it cannot be selected for replication. If this message was generatedas a result of a refresh, the name of the table containing the column is identified inCHC0228.

Message Variables:

type—The data type of the column that is not supported by InfoSphere CDC.

name—The name of the column in a table that has an unsupported data type.




Client Administrator Response—If the identified column is referenced in anexpression or row filtering expression, change the expression so that it does notrefer to the column. If the column is in a table selected for replication, deselect thecolumn so data in that column is not replicated. Restart replication. For expressionsand row filtering expressions, you may be able to use conversion column functionsto convert data to compatible values. If you are not running the latest version ofInfoSphere CDC, contact your InfoSphere CDC administrator or IBM representativeto determine if a more recent version supports the identified data type.Related reference

“CHC0228E” on page 274

CHC0248ECHC0248E The data type type of column name is not supported in expressions.

Explanation—InfoSphere CDC detected a column in a table that has anunsupported data type. The column cannot be referenced in an expression or rowexpression, and it cannot be selected for replication. If this message was generatedas a result of a refresh, the name of the table containing the column is identified inCHC0228.

Message Variables:






Client Administrator Response—If the identified column is referenced in anexpression or row filtering expression, change the expression so that it does notrefer to the column. If the column is in a table selected for replication, deselect thecolumn so data in that column is not replicated. Restart replication. For expressionand row filtering expressions, you may be able to use conversion column functions


to convert data to compatible values. If you are not running the latest version ofInfoSphere CDC, contact your InfoSphere CDC administrator or IBM representativeto determine if a more recent version supports the identified data type.Related reference


CHC0254ICHC0254I Subscription name has received a controlled shutdown request.

Explanation—InfoSphere CDC has received a request to shut down refresh ormirroring for the identified subscription (by its name or the corresponding sourceID) immediately or in a controlled manner. This request was initiated explicitly bya user.

Message Variables:



System Action—InfoSphere CDC shuts down refresh or mirroring for thesubscription immediately or in a controlled manner. If a controlled shutdown wasrequested, all data in the current commit group is processed before the shutdownoccurs. If an immediate shutdown was requested, no further data is processed.



CHC0255ICHC0255I Subscription name has received a quick shutdown request.


Message Variables:







CHC0256ICHC0256I Subscription name has received an immediate shutdown request.


Message Variables:






CHC0257ICHC0257I Subscription name has received an abnormal shutdown request.


Message Variables:






CHC0263ICHC0263I The remote partner has requested a controlled shutdown.

Explanation—Indicates that a message was received from the source or targetenvironment to shut down refresh or mirroring immediately or in a controlledmanner.






Client Administrator Response—Consult messages generated in the source ortarget environment that provide more details as to why a request to shut downrefresh or mirroring was generated. Using these messages, perform necessarycorrective actions.

CHC0264ICHC0264I The remote partner has requested a quick shutdown.







CHC0265ICHC0234I The remote partner has requested an immediate shutdown.








CHC0266ICHC0266I The remote partner has requested an abnormal shutdown.







CHC0272ICHC0272I name task has received a controlled shutdown request.

Explanation—The identified InfoSphere CDC task has received a request fromanother task to end immediately or in a controlled manner. This message istypically generated after a normal shutdown of the InfoSphere CDC address spacehas been requested.


Message Variables:

name—The three-letter name of the InfoSphere CDC task that received a requestfrom another task to end immediately or in a controlled manner.


System Action—After the task has terminated, other related tasks or theInfoSphere CDC address space may end as well.




CHC0273ICHC0273I name task has received a quick shutdown request.


Message Variables:






CHC0274ICHC0274I name task has received an immediate shutdown request.


Message Variables:






CHC0275ICHC0275I name task has received an abnormal shutdown request.



Message Variables:






CHC0281ICHC0281I The DB2 Log Cache is active.

Explanation—The current status of the DB2 Log caches (Level 1 and Level 2) haschanged. The caches are active, inactive, or their contents have been cleared. Toimprove performance when using multiple subscriptions to replicate multiplestreams of data at the same time, DB2 Log records can be retrieved from cachesthat are managed by InfoSphere CDC. Active caches are being used to cache DB2Log records for retrieval. Inactive caches are not being used to cache records forretrieval. When the caches are inactive, records must be read from the DB2 Log byeach subscription.






CHC0282ICHC0282I The DB2 Log Cache is inactive.








CHC0283ICHC0283I The DB2 Log Cache has been cleared.







CHC0289ICHC0242I The DB2 Log Cache is starting with a range of first through last.

Explanation—The DB2 Log caches (Level 1 and Level 2) are reporting theircontents. A range of LRSNs (log record sequence numbers) or RBAs (relative byteaddresses) identify the DB2 Log records in the caches at the time of the reportwhich can be when the log caches are started, when the log caches are ended, orduring normal operations. To improve performance when using multiplesubscriptions to replicate multiple streams of data at the same time, DB2 Logrecords can be retrieved from caches that are managed by InfoSphere CDC.

Message Variables:

first—The LRSN or RBA value identifying the first DB2 Log record in the cachesat the time of activation.

last—The LRSN or RBA value identifying the last DB2 Log record in the caches atthe time of activation.





CHC0290ICHC0290I The DB2 Log Cache is processing with a range of first through last.



Message Variables:







CHC0291ICHC0291I The DB2 Log Cache is ending with a range of first through last.


Message Variables:









“CHC0300I” on page 290“CHC0305E” on page 291“CHC0309E” on page 291“CHC0310E” on page 292“CHC0311E” on page 292“CHC0312E” on page 292“CHC0313E” on page 293“CHC0314I” on page 293“CHC0315I” on page 294“CHC0316I” on page 294“CHC0317I” on page 294“CHC0318I” on page 295“CHC0319E” on page 295“CHC0320W” on page 296“CHC0321W” on page 296“CHC0322W” on page 297“CHC0324E” on page 297“CHC0325E” on page 298“CHC0326E” on page 298“CHC0327E” on page 298“CHC0328I” on page 299“CHC0330E” on page 299“CHC0331E” on page 300“CHC0332E” on page 300“CHC0333W” on page 301“CHC0334W” on page 301“CHC0335I” on page 302“CHC0336E” on page 302“CHC0337W” on page 303“CHC0339I” on page 304“CHC0340E” on page 304“CHC0341E” on page 304“CHC0342E” on page 305“CHC0344W” on page 305“CHC0346I” on page 306“CHC0347E” on page 306“CHC0348E” on page 307“CHC0350E” on page 307“CHC0351I” on page 308“CHC0352I” on page 308“CHC0353I” on page 308“CHC0354I” on page 309


“CHC0355E” on page 309“CHC0356E” on page 310“CHC0357E” on page 310“CHC0358E” on page 311“CHC0359E” on page 311“CHC0360W” on page 312“CHC0361E” on page 312“CHC0364E” on page 313“CHC0365W” on page 313“CHC0366E” on page 314“CHC0367E” on page 314“CHC0368I” on page 315“CHC0369I” on page 315“CHC0371W” on page 315“CHC0374E” on page 316“CHC0375E” on page 316“CHC0376W” on page 317“CHC0377W” on page 317“CHC0378W” on page 317“CHC0379W” on page 318“CHC0380W” on page 318“CHC0381W” on page 319“CHC0382W” on page 320“CHC0383W” on page 320“CHC0384W” on page 321“CHC0385I” on page 321“CHC0386E” on page 322“CHC0387I” on page 322“CHC0388E” on page 323“CHC0389E” on page 323“CHC0390I” on page 323“CHC0391I” on page 324“CHC0392I” on page 324“CHC0393I” on page 324“CHC0394I” on page 325“CHC0395E” on page 325“CHC0396I” on page 325

CHC0300ICHC0300I The replication update process has started.

Explanation—Data replication to the subscription environment is in progress.







CHC0305ECHC0305E Table owner.table has no columns.

Explanation—InfoSphere CDC could not locate any columns in the named targettable.

Message Variables:

owner—The owner of the target table that has no columns.

table—The name of the target table that has no columns.


System Action—The update task on the subscription server will stop running.


Client Administrator Response—Verify that the source table has been mapped toa target table.

CHC0309ECHC0309E Column name of table owner.table is mapped to a column which does notexist.

Explanation—The source table column that is mapped to the named target tablecolumn does not exist in the InfoSphere CDC metadata.

Message Variables:

name—The name of the target table column.




System Action—Update task on the target will stop running.


Client Administrator Response—In this case, repeat the task of describing thesource table. Typically, this will define the named column in the InfoSphere CDCmetadata in the target environment. If this approach is unsuccessful, contact yourInfoSphere CDC administrator for further assistance.


CHC0310ECHC0310E Column name of table owner.table is not mapped.

Explanation—The named target table column has not been mapped.

Message Variables:

name—The name of the unmapped target table column.






Client Administrator Response—Remove the column from the target table or mapthe column.

CHC0311ECHC0311E An error occurred while editing the expression for column name in tableowner.table.

Explanation—The expression for the named target column has been incorrectlyformed.

Message Variables:

name—The name of the target column that is associated with the expression.

owner—The owner of the target table containing the column.

table—The name of the target table containing the column.




Client Administrator Response—Previous messages in the product administrationlog identify the part of the expression that is incorrect. Based on the informationthat is contained in these messages, perform the necessary modifications.

CHC0312ECHC0312E User exit module name is not marked reentrant.

Explanation—The specified user exit module is not reentrant. In order to use userexit modules in InfoSphere CDC, they must be written and link-edited to bereentrant.

Message Variables:


name—The name of the user exit module that is not marked as being reentrant.


System Action—Replication activities are automatically stopped.


Client Administrator Response—Verify that the user exit module specified inManagement Console is reentrant. Either write and link-edit the module so that itis reentrant or reference a different user exit module that is reentrant.

CHC0313ECHC0313E User exit module name failed in preinitialization. rc=code.

Explanation—The named user exit program has not been properly link-edited, andis not usable.

Message Variables:

name—The name of the user exit program that returned the error indicator.

code—The numeric error code returned by the user exit preinitialization validation.


System Action—Initialization, processing, or termination activities will stop.


Client Administrator Response—Ensure that the user exit has provided a validentry point name, and recompile and rebind (link edit) the user exit program.

CHC0314ICHC0314I Table owner.table is receiving changes that occurred during the refresh.

Explanation—Updates to the source table during a refresh are being received inthe target environment prior to the start of mirroring.

Message Variables:








CHC0315ICHC0315I Table owner.table has received all changes.

Explanation—All updates to the source table during a refresh have been receivedin the target environment prior to the start of mirroring.

Message Variables:







CHC0316ICHC0316I Refresh was started for table owner.table.

Explanation—A data refresh to the named target table has been started. Thismessage is generated when the first record in the refresh operation is received inthe target environment.

Message Variables:







CHC0317ICHC0317I Refresh has ended for table owner.table.

Explanation—A data refresh to the named target table has been completed.

Message Variables:








CHC0318ICHC0318I number rows were inserted and value rows were not inserted into tableowner.table.

Explanation—Identifies the number of rows that were inserted and not inserted inthe named target table. This message is generated at the end of a data refresh.

Message Variables:

number—The number of rows inserted into the target table.

value—The number of rows not inserted into the target table. Additional messagesin the product administration log identify the reasons why certain rows were notinserted.






Client Administrator Response—If rows could not be inserted into the targettable, view the product administration log to identify problems.

CHC0319ECHC0319E An error occurred during refresh of owner.table. The program isterminating.

Explanation—An error has been encountered during a data refresh to the namedtarget table.

Message Variables:




System Action—The update task on the target server will stop running.



Client Administrator Response—Previous messages in the product administrationlog identify the cause of the error. Based on the information that is contained inthese messages, perform the necessary modifications.

CHC0320WCHC0320W Column name of table owner.table is not NULL capable.

Explanation—NULL was replicated to the named subscription column that is notcapable of accepting NULL. NULL was either received from the source table orproduced through a data transformation.

Message Variables:

name—The name of the subscription column that is not capable of accepting NULL.




System Action—The field in the named subscription column is not set to NULL.


Client Administrator Response—Change the subscription column to accept NULLor modify data transformations so that NULL cannot be generated and placed in afield in the column.

CHC0321WCHC0321W An error occurred while processing the expression for column name in tableowner.table.

Explanation—An error was encountered during the processing or calculation of anexpression for the named target column.

Message Variables:

name—The name of the subscription column associated with the expression.








CHC0322WCHC0322W An invalid data type conversion from type1 to type2 was attempted forcolumn name of table owner.table.

Explanation—A source table column has been mapped to a target table columnthat has an incompatible data type.

Message Variables:

name—The name of the target column that is mapped to an incompatible sourcecolumn.



type1—The internal data type representation used in the attempted conversion.This data type may be requested by your IBM representative during diagnosticanalysis.

type2—The DB2 data type to which the conversion was attempted.


System Action—Fields in the target column assume the default value for the datatype (for example, blank, zero, and so on).


Client Administrator Response—Change one of the columns so that the datatypes are compatible or map the subscription column to a compatible sourcecolumn or defined value.

CHC0324ECHC0324E The maximum length of an SQL command was exceeded for table owner.table.

Explanation—The SQL command created to insert, update, or delete rows exceedsthe maximum length of an SQL command.

Message Variables:






Client Administrator Response—The length of an SQL command depends on thenumber of columns in the table and the length of the column names. To addressthis error, you may have to shorten the column names or reduce the number of


columns in the table. In this case, you may want to contact your IBMrepresentative to discuss possible strategies.

CHC0325ECHC0325E Unable to update the journal status entry for id.

Explanation—An error has occurred while updating the journal status metadataentry.

Message Variables:

id—The identifier of the subscription that is associated with the journal statusentry.


System Action—The update task for the subscription stops running.



CHC0326ECHC0326E Source id has no source tables defined.

Explanation—During initialization of the update task on the target, no source tabledefinitions were found in the metadata for the indicated source ID. Either tabledescriptions have not been sent or no tables were actually included in the describeoperation to the target.

Message Variables:

id—The source ID that is the target of replicated data.





CHC0327ECHC0327E Table owner.table has no qualifying index defined.

Explanation—A qualifying index could not be found for the specified target table.A unique index is required on the target table for mirroring data.

Message Variables:


owner—The owner of the target table that does not have a unique index.

table—The name of the target table that does not have a unique index.




Client Administrator Response—Define a unique index for the table so that datacan be mirrored to the target table.

CHC0328ICHC0328I number rows were deleted from owner.table.

Explanation—Prior to a data refresh, a certain number of rows were deleted fromthe named target table.

Message Variables:

number—The number of rows deleted from the target table prior to the data refresh.If all rows are removed from the target table and the number of removed rowscannot be determined, this variable is set to ″All″.







CHC0330ECHC0330E An internal error was detected in task name, module module, level level,line number, SEQ(sequence).

Explanation—InfoSphere CDC detected an error associated with an internal task.

Message Variables:

name—The name of the internal InfoSphere CDC task that failed.

module—The name of the source module in which the internal task error wasdetected.

level—The PTF/APAR level of the source module in which the internal task errorwas detected.

number—The line number in the source module containing the logic that triggeredthe internal task error.


sequence—The sequence number of the diagnostic SDUMP. The sequence numberdecreases by one for each successive SDUMP. When the sequence number reacheszero, additional SDUMPs are not produced.


System Action—The task referenced in the message text stops running.


Client Administrator Response—If a diagnostic SDUMP is generated, obtain it,note the message number, and contact your InfoSphere CDC administrator forfurther assistance.

CHC0331ECHC0331E User exit program name was not found.

Explanation—The specified user exit program could not be located in an accessibleload library.

Message Variables:

name—The name of the user exit program that cannot be found.


System Action—The task that refreshes or mirrors data stops.


Client Administrator Response—Verify that the load module for the user exitprogram has been stored in an accessible load library, and that the name specifiedin Management Console is correctly specified.

CHC0332ECHC0332E Source id has no target tables assigned.

Explanation—After starting replication, InfoSphere CDC determined that no sourcetables were mapped to target tables.

Message Variables:

id—The identifier of the source server.




Client Administrator Response—For the selected subscription, map the sourcetables to target tables. Restart replication after completing the mappings.


CHC0333WCHC0333W An error occurred in user exit name of type type during phase code.

Explanation—A row-level user exit program has returned an error indicator(return code 8) to InfoSphere CDC.

Message Variables:

name—The name of the user exit program that returned the error indicator toInfoSphere CDC.

type—The type of the user exit that experienced the error. The type describeswhere in the processing the user exit is called.

code—A numeric code which dictates why the user exit was called.v 1—User exit called for normal processing.v 2—Called to initialize the user exit.v 3—Called to terminate the user exit.




Client Administrator Response—An explanation of the error can be returnedthrough the user exit program. If such an explanation is provided, it appears in theproduct administration log in message CHC0335I. An examination of this messageand associated procedures (if any) should provide the necessary directions as tohow to proceed.Related reference


CHC0334WCHC0334W Task will terminate due to a severe error number in user exit name oftype type during phase code.

Explanation—A row-level user exit has returned a severe error indicator (returncode 12) to InfoSphere CDC.

Message Variables:

number—The numeric error code returned by the user exit.

name—The name of the user exit that experienced the error.

type—The type of the user exit that experienced the error. The type describeswhere in the processing the user exit is called.

code—A numeric code which dictates why the user exit was called.v 1—User exit called for normal processing.v 2—Called to initialize the user exit.v 3—Called to terminate the user exit.





Client Administrator Response—An explanation of the error can be returnedthrough the user exit program. If such an explanation is provided, it appears in theproduct administration log in message CHC0335I. An examination of this messageand associated procedures (if any) should provide the necessary directions as tohow to proceed.Related reference

“CHC0335I”

CHC0335ICHC0335I text.

Explanation—A full explanation of the error code that is returned by a row-leveluser exit program, and identified in message CHC0333WI or CHC0334E.Theseverity of this message is always I (Informational) even though the message textmay indicate a more severe condition.

Message Variables:

text—The message text returned by the user exit program. The text is defined inthe user exit program.




Client Administrator Response—This message is associated with messageCHC0333WI or CHC0334E. Therefore, one of these messages will also be in theproduct administration log. The text that you return through the user exit programshould adequately describe the error so that the appropriate actions can be taken.Related reference

“CHC0333W” on page 301“CHC0334W” on page 301

CHC0336ECHC0336E Signal type was intercepted from user exit name.

Explanation—The specified user exit program (%USER or row-level) caused ahardware program check or software requested failure that was intercepted byInfoSphere CDC.

Message Variables:

type—The type of hardware program check or software requested failure that wasintercepted by InfoSphere CDC. One of the following strings is inserted in themessage text at this point:


v SIGINTv SIGABRTv SIGILLv SIGFPEv SIGSEGVv SIGTERMv SIGUSR1v SIGUSR2v SIGABNDv SIGIOERR

For more information about these signals, see the appropriate IBM C/C++publications.

name—The name of the user exit program that caused the intercepted hardwareprogram check or software requested failure.




Client Administrator Response—Review the user exit program to identify theconditions that caused the failure to occur. Modify the user exit program toaddress the problem.

CHC0337WCHC0337W An attempt by user exit name to issue a COMMIT or ROLLBACK was suppressed.

Explanation—The specified row-level user exit program attempted to issue aCOMMIT or ROLLBACK statement. Except for termination calls, such a statementcannot be specified in a user exit program.

Message Variables:

name—The name of the module containing the user exit program that issued aCOMMIT or ROLLBACK statement.


System Action—The COMMIT or ROLLBACK statement in the named user exitprogram is not performed.


Client Administrator Response—Inform the person that wrote the user exitprogram that this message was generated. The program has to be modified so thatCOMMIT or ROLLBACK statements are not issued unless the type of call is foruser exit termination.


CHC0339ICHC0339I All rows were deleted from owner.table.

Explanation—Prior to a data refresh, all rows were deleted from the target table.

Message Variables:







CHC0340ECHC0340E Stored procedure name has returned error code number.

Explanation—A stored procedure invoked by the %STPROC column functionreturned an error code.

Message Variables:

name—The name of the stored procedure.

number—The numeric error code returned by the stored procedure.


System Action—Replication terminates abnormally.


Client Administrator Response—Correct the problem in the stored procedure andrestart replication.

CHC0341ECHC0341E LiveAudit, Standard Replication, Adaptive Apply, Summarization, andConsolidation cannot be mixed for the same table within the same subscription.

Explanation—In Management Console, you have attempted to map the sametarget table using two different mapping types (LiveAudit and Standard, orLiveAudit and Summarization, and so on). This is not allowed for the same targettable within the same subscription.






Client Administrator Response—Decide which mapping type (LiveAudit,Standard, Summarization, and so on) you want to use for the target table.

If you want to audit source table changes and summarize data, for example, youcan create two subscriptions and select the same set of tables for each subscription.For one subscription, you can map the source tables to the target tables usingLiveAudit. For the other subscription, you can map a different set of target tablesusing Summarization.

CHC0342ECHC0342E Table owner.table has no keys.

Explanation—Mirroring activities involve a target table that has no key columns.Mirroring requires that at least one key column exists in the mapped target tables.

Message Variables:

owner—The owner of the target table that does not contain a key column.

table—The name of the target table that does not contain a key column.


System Action—Mirroring ends.


Client Administrator Response—In DB2, define at least one key column in thespecified target table. Alternatively, select another target table for mirroring inManagement Console.

CHC0344WCHC0344W Deadlock or timeout retry cache is full. Replication will be temporarilyunavailable.

Explanation—The retry cache reached the maximum size specified and no morerecords can be cached. If a deadlock or timeout occurs, a retry will not beattempted for this commit group.



System Action—Replication continues without deadlock/timeout retry.


Client Administrator Response—If this occurs frequently, you might need toincrease the size specified on the STG64LIMIT or RETRYCACHE keywords.


Related reference

“STG64LIMIT” on page 41“RETRYCACHESIZE” on page 61

CHC0346ICHC0346I passed rows were passed, failed rows were not passed to the load utilityfor table owner.table

Explanation—Message generated at the end of the transmit phase when DB2LOAD is used to refresh data to target tables. The message text identifies thenumber of records passed and not passed to DB2 LOAD for the named table.

Message Variables:

passed—The number of records in the named table that were passed to DB2LOAD.

failed—The number of records in the named table that were not passed to DB2LOAD.

owner—The owner of the table containing the rows passed to DB2 LOAD.

table—The name of the table containing the rows passed to DB2 LOAD.




Client Administrator Response—If the number of rows not passed to DB2 LOADis unexpected, verify the replication configuration to ensure that row filtering iscorrectly defined.

CHC0347ECHC0347E The DB2 load utility ended abnormally. Abend code: code

Explanation—An abend occurred while DB2 LOAD was loading a target table inorder to perform a refresh.

Message Variables:

code—The abend code returned by DB2 LOAD.


System Action—DB2 LOAD does not refresh the target table it was attempting toload when the abend occurred.


Client Administrator Response—Examine the output produced by DB2 LOAD todetermine the cause behind the abend. Output is placed in the SPOOL data set.


CHC0348ECHC0348E Dynamic allocation error. rc=return error code=error. Information code=information.

Explanation—A requested dynamic allocation function failed.

Message Variables:

return—The dynamic allocation service return code.

error—The dynamic allocation error return code.

information—The dynamic allocation information return code.


System Action—The operation that initiated the request is not completedsuccessfully.


Client Administrator Response—Use the return code to identify the cause of theerror. Consult the MVS Authorized Assembler Services Guide or the appropriateIBM publication.

CHC0350ECHC0350E The utility is already active for UTILID id, phase phase, status status.

Explanation—DB2 LOAD cannot be started as InfoSphere CDC has detected anactive invocation having the same utility identifier. Each active DB2 LOADinvocation must have a unique utility identifier. This issue is likely caused by apreviously unsuccessful attempt to use DB2 LOAD to refresh the same target table.

Message Variables:

id—The DB2 LOAD utility identifier that is active.

phase—The current DB2 LOAD phase when the same utility identifier wasdetected.

status—The current DB2 LOAD status when the same utility identifier wasdetected.


System Action—DB2 LOAD does not refresh any target table.


Client Administrator Response—Try to restart DB2 LOAD independently fromInfoSphere CDC. If this approach is unsuccessful, use the DB2 TERM UTILcommand to end the active DB2 LOAD invocation before attempting to refresh thetarget table again.


CHC0351ICHC0351I The DB2 load utility return code was not zero. The work datasets will notbe deleted.

Explanation—DB2 LOAD abended or ended with a nonzero return code. Anonzero return code indicates that a warning or error has been raised. The workdata sets have not been deleted so that you can determine the problem or take thenecessary steps to restart DB2 LOAD independently from InfoSphere CDC.



System Action—The work data sets are maintained for the purpose of problemdetermination.


Client Administrator Response—Use the data sets to investigate the nonzeroreturn code. If the entire table was loaded into DB2 LOAD before a failureoccurred, it may be possible to restart DB2 LOAD independently from InfoSphereCDC using the data sets created by InfoSphere CDC.

CHC0352ICHC0352I The DB2 load utility name dataset was allocated to dataset.

Explanation—Indicates that the DB2 LOAD data set has been allocated to theidentified DD name or data set.

Message Variables:

name—The default DB2 LOAD DD name of the data set.

dataset—The DD or data set name assigned to the data set.




Client Administrator Response—Use the DB2 LOAD data sets for problemdetermination and to restart DB2 LOAD in the event of an error.

CHC0353ICHC0353I Processing is being suspended for subscription source .

Explanation—Message indicating the suspension of processing as a result of DB2unavailability. As a result, the specified source system is placed in a suspendedstate until DB2 shuts down or becomes available again.

Message Variables:

source—The identifier of the source system that has been placed in a suspendedstate.



System Action—The source system enters a suspended state.



CHC0354ICHC0354I Attempting to resume processing for subscription source.

Explanation—The specified source system is attempting to connect to DB2 in orderto resume processing.

Message Variables:

source—The identifier of the source system that is attempting to migrate from asuspended state.





CHC0355ECHC0355E The %USER exit program name type call returned error code code.

Explanation—An error occurred during the initialization (EXITINIT) or termination(EXITTERM) call of a user exit program invoked through the %USER columnfunction. The message text identifies the name of the user exit program and thereturned error code. The type of call to the user exit program is identified byEXITINIT or EXITTERM. If EXITINIT is referenced in the message text, the erroroccurred in the initialization call of the user exit program. If EXITTERM isreferenced in the message text, the error occurred in the termination call of theuser exit program. The initialization call occurs before the first call that processesdata, and the termination call occurs after the last call that processes data.

Message Variables:

name—The name of the user exit program where an initialization or terminationerror occurred.

type—The type of call, either initialization (EXITINIT) or termination (EXITTERM).

code—The error code returned to InfoSphere CDC by the user exit program. Anonzero return code indicates an error.


System Action—If EXITINIT appears in the message text, the user exit programinvocation is disabled for the subscription, and further user exit activity (data


processing and termination) is halted. If EXITTERM appears in the message text,the user exit program invocation is disabled for the subscription.

Operator Response—Contact the programmer that developed the user exitprogram in your environment, and provide the information contained in themessage text. Knowledge of the program logic along with the error code shouldguide the programmer to a solution.


CHC0356ECHC0356E Table ID id was received for unknown source table owner.table.

Explanation—During replication, a target received an internal message from asource system that referenced a table identifier for an unknown source table.

Message Variables:

id—The table identifier of the unknown source table.

owner—The owner of the unknown source table.

table—The name of the unknown source table.




Client Administrator Response—Describe or redescribe the subscriptioncontaining the named source table and make sure the table has been successfullydescribed to the target. Check Event Log to determine if the describe operationwas successful. After a successful describe, restart replication for the subscription.

CHC0357ECHC0357E Table ID id was received for source table owner.table, which has not beenassigned to a target table.

Explanation—During replication, a target has received data from a source tablethat has not been mapped to a target table. In this case, the source table status hasbeen set to enable the replication of data to a target. However, a target table hasnot been mapped to receive the replicated data. In the product administration log,this message is preceded by CHC0360W, which provided a warning whenreplication was started that the source table was not mapped.

Message Variables:

id—The table identifier of the source table that is not mapped to a target table.

owner—The owner of the source table that is not mapped to a target table.

table—The name of the source table that is not mapped to a target table.





Client Administrator Response—Map the source table to a target table or set thesource table status to Idle to prevent the replication of data from the table whenreplication for the subscription is started. Restart replication. .Related reference


CHC0358ECHC0358E An unsupported column flag value flags was received on message type.

Explanation—During replication, a target received an internal message from asource system containing column flags that are invalid or not supported in thesubscription environment. A column flag is an internal mechanism that is used toindicate the presence of before and/or after image data sent to a target. In thiscase, a set of flags received by a target is invalid.

Message Variables:

flags—The invalid column flags received by the target.

type—The type of message containing the invalid column flags. One of thefollowing strings is inserted in the message text at this point:v TSM_INSERTv TSM_UPDATEv TSM_DELETE





CHC0359ECHC0359E Column name in source table owner.table has an unsupported data typetype.

Explanation—During replication, a target detected a source table column that hasan unsupported data type. Only source table columns containing data supportedby InfoSphere CDC can be replicated.

Message Variables:

name—The name of the column in the source table containing data that is notsupported by InfoSphere CDC.

owner—The owner of the source table containing the column with an unsupporteddata type.


table—The name of the source table containing the column with an unsupporteddata type.

type—The data type of the column in the source table that is not supported byInfoSphere CDC.




Client Administrator Response—In Management Console, deselect the column sothat data from this column is not replicated or define an expression in the sourcetable to convert the data into a supported type before replicating the data to atarget. Restart replication for the affected subscription.

CHC0360WCHC0360W Source table owner.table has no target table assigned.

Explanation—When replication was started, a target detected a source table that isnot mapped to a target table. In this case, the source table status has been set toenable the replication of data to a target. However, a target table has not beenmapped to receive any replicated data. In the product administration log, thismessage may be followed by CHC0357E if data from the source table is sent to thetarget at a later time.

Message Variables:

owner—The owner of the source table that is not mapped to a target table.

table—The name of the source table that is not mapped to a target table.


System Action—Replication for the affected subscription continues.


Client Administrator Response—If data from the source table will be sent to thetarget at a later time, stop replication. Map the source table to a target table or setthe source table status to Idle to prevent the replication of data from the tablewhen replication for the subscription is started. Restart replication. These steps willprevent CHC0357E from being generated and having to perform the same steps ata later time.

CHC0361ECHC0361E Invalid journal control field name was specified.

Explanation—A journal control field specified in Management Console could notbe recognized. Journal control fields can be referenced in expressions and rowexpressions. They can also be mapped to target table columns.

Message Variables:


name—The journal control field that could not be recognized.




Client Administrator Response—Review the journal control field references inManagement Console and make any necessary corrections. All journal controlfields have names that begin with an ampersand (&). In addition, some journalcontrol fields are not supported by InfoSphere CDC.

CHC0364ECHC0364E The table table cannot be processed because its type code of (type) isnot supported.

Explanation—In Management Console, a table could not be added to the tablesavailable for replication because the table has an unsupported type code.

Message Variables:

table—The name of the table that could not be added to the tables available forreplication.

type—The type code of the table.


System Action—The table is not added to the tables available for replication inManagement Console.


Client Administrator Response—Add tables that can be replicated by InfoSphereCDC to the tables available for replication.

CHC0365WCHC0365W Bookmark decoding failed for subscription name. source database is type.

Explanation—InfoSphere CDC has encountered an error while attempting todecode a source bookmark value.

Message Variables:


type—The type of the source database from which the bookmark originated.Examples would be SQLServer, Oracle, DB2 z/OS, etc.


System Action—Replication continues.



Client Administrator Response—This is likely an attempt to decode anunsupported bookmark type. To see if an update to the bookmark decoding logicis available, contact IBM Technical Support.

CHC0366ECHC0366E Table owner.table has no SELECT statement prepared.

Explanation—InfoSphere CDC has encountered an error while attempting toretrieve the current row for a table.

Message Variables:






Client Administrator Response—To resolve the problem, contact IBM TechnicalSupport.

CHC0367ECHC0367E The retrieval of type column name from source table owner.table failed.The return code is code.

Explanation—InfoSphere CDC has encountered an error while attempting toretrieve the indicated source column.

Message Variables:

type—The data type of the source column that could not be retrieved.

name—The name of the source column that could not be retrieved.

owner—The owner of the source table for which the column could not be retrieved.

table—The name of the source table for which the column could not be retrieved.

code—The returned code received by InfoSphere CDC when the error occurred.






CHC0368ICHC0368I The replication update process has applied bookmark bmk in log log fromsource.

Explanation—While mirroring data for a subscription, the InfoSphere CDC applytask has applied all data up to the indicated bookmark successfully.

Message Variables:

bmk—The source bookmark value.

log—The source log or journal name.

source—The source ID for the subscription, as defined in Management Console.





CHC0369ICHC0369I The replication update process has received bookmark received in log logfrom source. The last data applied was applied

Explanation—During mirroring, the InfoSphere CDC apply task has received theindicated bookmark successfully. The last data was applied at the bookmarkidentified in the message.

Message Variables:

received—The source bookmark value received.

log—The source log or journal name.

source—The source ID for the subscription, as defined in Management Console.

applied—The last bookmark value at which data was applied.





CHC0371WCHC0371W An unexpected event message id was received.

Explanation—InfoSphere CDC received an event notification with which it was notable to cope.


Message Variables:

id—The ID of the event received.


System Action—Processing continues.



CHC0374ECHC0374E Source table table is already assigned to a target table in subscriptionname.

Explanation—A Management Console session has attempted to map a target tableto a source table which already has a target table mapped to it.

Message Variables:

table—The name of the source table.



System Action—The table mapping was not performed.



CHC0375ECHC0375E Column name does not exist in table table.

Explanation—A Management Console session has attempted to map a source tablecolumn to a target table column, but the source table column does not exist.

Message Variables:

name—The name of the non-existent column.







CHC0376WCHC0376W An error occurred while converting a user exit parameter to a level 0compatible format for exit name.

Explanation—The named user exit module has been link-edited as a level 0(backward compatible) user exit, but the user exit parameter list cannot besuccessfully converted to the older format. This message will be accompanied byother messages giving details of the error.

Message Variables:

name—The name of the back-level user exit load module.


System Action—Processing continues, however, results may not be as expected.


Client Administrator Response—Do not use product features that wereunavailable in version 5, or else rewrite the user exit to use the current interface.

CHC0377WCHC0377W The character data chars is too long for Level-0 User exits and willbe truncated to number bytes.

Explanation—A level zero (backward compatible) user exit is in use, but acharacter field to be passed to the exit is too long to fit in the older formatparameter list. The data is truncated to fit.

Message Variables:

chars—The character data passed to the user exit interface.

number—The number of these characters that will be copied to the level 0 user exitparameter list.




Client Administrator Response—This is likely an attempt to use an older user exitin a subscription with long identifiers. Rewrite the user exit to user the currentinterface.

CHC0378WCHC0378W Future messages will be suppressed for exit name.

Explanation—This message is issued following other messages reporting errors inconverting a user exit parameter list to the older, level 0, format. The message


indicates that future conversion error messages will be internally suppressed inorder to prevent flooding the product administration log.

Message Variables:

name—The name of the backward-compatible user exit program that will haveconversion error messages suppressed.




Client Administrator Response—Refer to the prior messages to determine theerrors in user exit parameter conversion, and take the action appropriate to thoseerrors.

CHC0379WCHC0379W The Open operation failed for DB2 Log Cache dataset name. The DDstatement may be missing or incorrect.

Explanation—The identified operation could not be applied to the DB2 Log cachedata set. To improve performance when using multiple subscriptions to replicatemultiple streams of data at the same time, DB2 Log records can be retrieved fromcaches that are managed by InfoSphere CDC. CHCCACHE is the name of theLevel 2 DB2 Log cache data set. CHCCHCTL is the name of the DB2 Log cachecontrol data set. The DD statement for one of these data sets in the CHCPROC JCLis incorrect or missing.

Message Variables:

name—The name of the dataset.


System Action—If this message was generated during InfoSphere CDCinitialization, DB2 Log caching is disabled and the caches are placed in an inactivestate. If an attempt to read a record from the cache is unsuccessful, the record willbe read from the DB2 Log instead. If an attempt to write a record to the cache wasunsuccessful, the record is not placed in the cache and it will have to be retrievedfrom the DB2 Log instead.


Client Administrator Response—Verify the DD statement in the CHCPROC JCL toensure it exists and is correct.

CHC0380WCHC0380W The Read operation failed for DB2 Log Cache dataset name. The DDstatement may be missing or incorrect.

Explanation—The identified operation could not be applied to the DB2 Log cachedata set. To improve performance when using multiple subscriptions to replicatemultiple streams of data at the same time, DB2 Log records can be retrieved from


caches that are managed by InfoSphere CDC. CHCCACHE is the name of theLevel 2 DB2 Log cache data set. CHCCHCTL is the name of the DB2 Log cachecontrol data set. The DD statement for one of these data sets in the CHCPROC JCLis incorrect or missing.

Message Variables:





Client Administrator Response—Verify the DD statement in the CHCPROC JCL toensure it exists and is correct.

CHC0381WCHC0381W The Write operation failed for DB2 Log Cache dataset name. The DDstatement may be missing or incorrect.


Message Variables:





Client Administrator Response—The size of the CHCCACHE data set may not belarge enough to accommodate the Level 2 DB2 Log cache. Submit the CHCCRCCHjob to allocate a larger data set.


CHC0382WCHC0382W The Seek operation failed for DB2 Log Cache dataset name. The DDstatement may be missing or incorrect.


Message Variables:






CHC0383WCHC0383W The Locate operation failed for DB2 Log Cache dataset name. The DDstatement may be missing or incorrect.


Message Variables:







CHC0384WCHC0384W The Update operation failed for DB2 Log Cache dataset name. The DDstatement may be missing or incorrect.


Message Variables:






CHC0385ICHC0385I received records received from source system. read records read from tableowner.table. Differences found on target: missing missing records, extra extrarecords, changed changed records.

Explanation—This message reports the results of a differential refresh.

Message Variables:

received—The number of records received from the source system.

read—The number of records read from the target table.




missing—The number of records received from the source that did not exist on thetarget.

extra—The number of records read on the target that were not received from thesource.

changed—The number of records received from the source that existed on thetarget, but were different.





CHC0386ECHC0386E Differential refresh is only allowed for standard assignment.

Explanation—A differential refresh was started by the source, but the targetdetermined that the mapping type was incompatible with differential refresh.





Client Administrator Response—Differential refresh is only supported forstandard assignment. Select standard refresh to refresh this table.

CHC0387ICHC0387I Log table owner.name created.

Explanation—A differential refresh with the log option was started and the targethas created a log table where the discrepancies found during the refresh will belogged.

Message Variables:

owner—The owner name of the log table. This will be equal to the metadata owner.

name—The name of the log table. This will be built from the subscription name, thetarget table name and the date and time.






CHC0388ECHC0388E Key column column in table owner.name must be mapped directly to a sourcecolumn.

Explanation—A differential refresh was started and the specified key column is notmapped directly to a source column. The Differential refresh cannot proceed.

Message Variables:

column—The name of the key column.

owner—The owner name of the log table. This will be equal to the metadata owner.

name—The name of the log table. This will be built from the subscription name, thetarget table name and the date and time.




Client Administrator Response—A differential refresh cannot be done on thistable. Choose standard refresh to refresh this table.

CHC0389ECHC0389E The target system for subscription name does not support differentialrefresh.

Explanation—A differential refresh was started, but the target system has indicatedit does not support differential refresh.

Message Variables:





Client Administrator Response—A differential refresh cannot be done to thissystem. Choose standard refresh to refresh this table.

CHC0390ICHC0390I The replication update process ended normally.

Explanation—Data replication to the target environment has ended.




System Action—The update task on the target server will stop applying replicateddata.


Client Administrator Response—If the update process stopped abnormally,consult the product administration log for other related messages and perform thenecessary corrective actions to resolve the problem.

CHC0391ICHC0391I The replication update process ended abnormally.







CHC0392ICHC0392I The replication update process was ended by the operator.







CHC0393ICHC0393I The replication update process was ended immediately by the operator.








CHC0394ICHC0394I A deadlock or timeout has occurred on table owner.name, attemptingto recover.

Explanation—The database has returned a deadlock or timeout error to theapplication. Recovery and retry of the operation will be attempted.

Message Variables:

owner—The owner name of the table on which the error occurred.

name—The name of the table on which the error occurred.


System Action—The operation will be retried.



CHC0395ECHC0395E An error occurred while processing message number.

Explanation—An unexpected error occurred while the product was processing thespecified message. This is likely a product issue.

Message Variables:

number—The number of the message being processed.




Client Administrator Response—Contact technical support.

CHC0396ICHC0396I A recoverable database error has occurred, a retry will be attempted.

Explanation—The database has returned a recoverable error to the application. Theoperation will be retried.




System Action—The operation will be retried.




“CHC0401W”“CHC0402I” on page 327“CHC0403W” on page 327“CHC0404E” on page 328“CHC0405W” on page 328“CHC0407E” on page 329“CHC0408E” on page 329“CHC0409E” on page 330“CHC0410W” on page 330“CHC0411E” on page 331“CHC0412E” on page 331“CHC0418W” on page 331“CHC0419W” on page 332“CHC0420W” on page 332“CHC0421W” on page 333“CHC0422W” on page 333“CHC0428E” on page 334“CHC0429E” on page 334“CHC0430E” on page 335“CHC0431E” on page 335“CHC0432E” on page 336“CHC0495E” on page 336“CHC0496E” on page 336

CHC0401WCHC0401W A VSAM request failed for cluster name, return code=return, reason code=reason, RBA=rba, operation=operation (text).

Explanation—A VSAM (Virtual Storage Access Method) request failed in responseto a Management Console request, a hardware or software error, or some othererror.

Message Variables:

name—The name of the cluster.

return—The return code. Consult the appropriate IBM publication for anexplanation of this code.


reason—The reason code. Consult the appropriate IBM publication for anexplanation of this code.

rba—The RBA (relative byte address) of the record that lead to the message beinggenerated.

operation—The code that identifies the operation that was being attempted whenthe VSAM request failed.

text—Text associated with the code returned through operation


System Action—InfoSphere CDC operations will continue if it is able to recoveryfrom the request failure.


Client Administrator Response—Examine preceding messages in the system logthat addresses this problem. Use the information contained in these messages toperform necessary corrective actions.

CHC0402ICHC0402I Task name has ended abnormally.

Explanation—An internal InfoSphere CDC task has stopped running and iscurrently in the specified state.

Message Variables:

name—The name of the InfoSphere CDC task that has ended.


Depending on which task has ended, this message is sent to the system log or theproduct administration log.


Operator Response—If the task ended abnormally, examine preceding messages inthe log that addresses this problem. Use the information contained in thesemessages to perform corrective actions. Note the message number and contactyour InfoSphere CDC administrator if you require further assistance.

Client Administrator Response—See Operator Response for instructions.

CHC0403WCHC0403W The maximum message size was exceeded for message number number.

Explanation—The identified message could not be added to the productadministration log. The message that could not be added exceeds the maximumsize of 512 bytes. Messages that exceed the maximum size are placed in the defaultCHCPRINT spool file that is provided with InfoSphere CDC for z/OS.

Message Variables:


number—The identification number of the message that exceeds the maximum sizestipulated for the product administration log.


The message placed in the product administration log is CHC0403W (not themessage identified in the message text).



Client Administrator Response—To review the identified message, inspect theCHCPRINT spool file. Note the message number and contact your InfoSphereCDC administrator if you require further assistance.

CHC0404ECHC0404E Dataset name has an invalid file type.

Explanation—InfoSphere CDC cannot work with a data set created duringinstallation.

Message Variables:

name—The name of the data set that InfoSphere CDC cannot access.


System Action—InfoSphere CDC initialization is stopped.


Client Administrator Response—Consult InfoSphere CDC Installation or Upgradeto review the instructions concerning this data set, and make any necessarymodifications. Contact your InfoSphere CDC administrator if you require furtherassistance.Related concepts

“IBM InfoSphere Change Data Capture installation or upgrade” on page 1

CHC0405WCHC0405W Channel (type), zone (zone), category (name) has reported an error.The Notifications channel has been disabled.

Explanation—An error has been encountered with the named alerts and alarmschannel. A channel refers to a supported method of triggering an alert when amessage belonging to the named zone and category is generated. For moreinformation about alerts and alarms, see your Management Consoledocumentation.

Message Variables:

type—The type of channel where an error was reported. For InfoSphere CDC, oneof the following strings is inserted into the message text at this point:v user exit


v spool filev system log

zone—The alarmed functional zone that is attached to the named channel.Functional zones identify the possible replication activities that can produceInfoSphere CDC messages.

name—The alarmed category that is attached to the named channel. Categoriesidentify the different severity levels associated with InfoSphere CDC messages.


System Action—InfoSphere CDC continues to run, but the named channel isdisabled for all subsequent alarms that activate this kind of channel.

Operator Response—For the user exit handler, review the user exit programs inyour environment to identify any problems in the source code. For the spool fileand system log channels, note the message number and contact your InfoSphereCDC administrator if you require further assistance.


CHC0407ECHC0407E User exit name has reported an error. The associated alert handler willbe disabled.

Explanation—A severe error occurred in a user exit program that was invokedthrough an alert handler. The alert handler that invoked the user exit program isdisabled for all subsequent notifications that activate this handler.

Message Variables:

name—The name of the user exit program where the severe error occurred.



Operator Response—Contact the person that developed the user exit program todetermine the cause of the problem. If necessary, consult InfoSphere CDC UserExits for information about user exit programs invoked by alert handlers.

Client Administrator Response—NoneRelated concepts

“InfoSphere CDC user exits” on page 165

CHC0408ECHC0408E Invalid data was passed on request. number items were processed.

Explanation—InfoSphere CDC could not process an update to an alert definitionreceived from Management Console. The message text identifies the number ofupdates that were successfully processed before the error was reported.

Message Variables:


number—The number of alert definition updates that were successfully processedby InfoSphere CDC before the error was encountered.


System Action—The update is not processed, but InfoSphere CDC operationscontinue.


Client Administrator Response—Note the message number and contact yourInfoSphere CDC administrator if you require further assistance.

CHC0409ECHC0409E Dataset name has an invalid key or record length.

Explanation—InfoSphere CDC has detected an invalid key or record lengthassociated with a data set created during installation.

Message Variables:

name—The name of the data set having attributes that InfoSphere CDC does notexpect.


System Action—InfoSphere CDC initialization is stopped.


Client Administrator Response—Consult “IBM InfoSphere Change Data Captureinstallation or upgrade” on page 1 to review the instructions concerning this dataset, and make any necessary modifications. Contact your InfoSphere CDCadministrator if you require further assistance.

CHC0410WCHC0410W The maximum error count was exceeded. File ddn was closed.

Explanation—The maximum number of errors associated with the identified filehas been exceeded. As a result, the file has been closed.

Message Variables:

ddn—The name or DD name of the file that was closed.


System Action—The identified file is closed.

Operator Response—Other messages in the system log provide information as towhy the maximum number of errors was exceeded. Use these messages to identifythe cause. InfoSphere CDC has to be restarted before additional data and messagescan be written to the file.



CHC0411ECHC0411E A message was received for undefined table ID id.

Explanation—During replication, a target received an internal message from asource system that referenced an unrecognized table identifier or journal number.

Message Variables:

id—The table identifier that was not recognized by the target.





CHC0412ECHC0412E A message was received for undefined journal number number.

Explanation—During replication, a target received an internal message from asource system that referenced an unrecognized table identifier or journal number.

Message Variables:

number—The journal number that was not recognized by the target.





CHC0418WCHC0418W Invalid decimal data was found for column name of table owner.table.

Explanation—Data received from a source table is invalid and cannot be acceptedby the named target column.

Message Variables:

name—The name of the target column that received the invalid data.







Client Administrator Response—Identify the source of the invalid data. Ifnecessary, use the data transformation capabilities of InfoSphere CDC to convertinvalid data received from the source.

CHC0419WCHC0419W Invalid floating point was found for column name of table owner.table.


Message Variables:








CHC0420WCHC0420W Invalid integer data was found for column name of table owner.table.


Message Variables:









CHC0421WCHC0421W Invalid zoned numeric data was found for column name of tableowner.table.


Message Variables:








CHC0422WCHC0422W Invalid data was found for column name of table owner.table.


Message Variables:









CHC0428ECHC0428E An INSERT operation failed. Table name: owner.table, key: col1 = txt1,col2 =txt2, ..., coln =txtn.

Explanation—A row-level operation applied to the named target table wasunsuccessful.

Message Variables:



col1, ..., coln—The names of the key columns in the target table.

txt1, ..., txtn—The corresponding values of the key columns in the target tablepertinent to the row-level operation that failed.





CHC0429ECHC0429E An UPDATE operation failed. Table name: owner.table, key: col1 = txt1,col2 =txt2, ..., coln =txtn.


Message Variables:










CHC0430ECHC0430E A DELETE operation failed. Table name: owner.table, key: col1 = txt1,col2 =txt2, ..., coln =txtn


Message Variables:









CHC0431ECHC0431E A SELECT operation failed. Table name: owner.table, key: col1 = txt1,col2 =txt2, ..., coln =txtn.


Message Variables:










CHC0432ECHC0432E A format operation failed. Table name: owner.table, key: col1 = txt1,col2 =txt2, ..., coln =txtn.


Message Variables:









CHC0495ECHC0495E An invalid table ID id was received.

Explanation—During replication, a target received an internal message from asource system that referenced a table identifier or journal number that is not withinthe acceptable range of values.

Message Variables:

id—The table identifier that is not within the acceptable range of values.





CHC0496ECHC0495E An invalid journal number number was received.


Explanation—During replication, a target received an internal message from asource system that referenced a table identifier or journal number that is not withinthe acceptable range of values.

Message Variables:

number—The journal number that is not within the acceptable range of values.






“CHC0502E” on page 338“CHC0503E” on page 339“CHC0511I” on page 339“CHC0512I” on page 339“CHC0513I” on page 340“CHC0514I” on page 340“CHC0515I” on page 341“CHC0516I” on page 341“CHC0517I” on page 341“CHC0518I” on page 342“CHC0519I” on page 342“CHC0529E” on page 343“CHC0530E” on page 343“CHC0531E” on page 344“CHC0532E” on page 344“CHC0533E” on page 344“CHC0535E” on page 345“CHC0536E” on page 345“CHC0537E” on page 346“CHC0538E” on page 346“CHC0539E” on page 347“CHC0540E” on page 347“CHC0541E” on page 348“CHC0543E” on page 348“CHC0545E” on page 348“CHC0546E” on page 349“CHC0547E” on page 349“CHC0548E” on page 349


“CHC0549E” on page 350“CHC0550E” on page 350“CHC0551E” on page 351“CHC0552E” on page 351“CHC0553E” on page 351“CHC0554E” on page 352“CHC0555E” on page 352“CHC0556I” on page 353“CHC0557E” on page 353“CHC0558E” on page 354“CHC0560E” on page 354“CHC0561E” on page 354“CHC0562E” on page 355“CHC0564E” on page 355“CHC0565E” on page 356“CHC0566E” on page 356“CHC0567W” on page 356“CHC0568W” on page 357“CHC0569W” on page 357“CHC0570E” on page 358“CHC0571W” on page 358“CHC0572E” on page 359“CHC0573E” on page 359“CHC0574E” on page 360“CHC0575E” on page 360“CHC0576E” on page 361“CHC0577W” on page 361“CHC0579E” on page 362“CHC0580E” on page 362“CHC0581W” on page 363“CHC0582E” on page 363“CHC0583E” on page 363“CHC0584E” on page 364“CHC0595I” on page 364“CHC0596I” on page 365“CHC0598W” on page 365“CHC0599W” on page 366

CHC0502ECHC0502E An error occurred while allocating file name.

Explanation—A request to allocate the identified file was unsuccessful.

Message Variables:

name—The data set or DD name that caused an allocation error.





Client Administrator Response—Identify the cause of the error by examiningother related messages placed in the product administration log.

CHC0503ECHC0503E An error occurred while deallocating file name.

Explanation—A request to deallocate the identified file was unsuccessful.

Message Variables:

name—The data set or DD name that caused an allocation error.




Client Administrator Response—Identify the cause of the error by examiningother related messages placed in the product administration log.

CHC0511ICHC0511I The DB2 load utility was not used. The table is cascaded by the sourcesystem.

Explanation—DB2 LOAD cannot be used to refresh target tables. The message textcontains information as to why DB2 LOAD could not be used. There arelimitations on the use of DB2 LOAD.



System Action—A refresh of the target table by DB2 LOAD is not performed.Instead of DB2 LOAD, the standard InfoSphere CDC refresh will be used to refreshthe target table.


Client Administrator Response—Based on the reason, you may want to modifythe replication configuration for one or more tables in Management Console toallow DB2 LOAD to be used. If the replication configuration cannot be modified,use the standard InfoSphere CDC refresh.

CHC0512ICHC0512I The DB2 load utility was not used. The table is not the only one in thetablespace.








CHC0513ICHC0513I The DB2 load utility was not used. Live Audit is selected for the table.







CHC0514ICHC0514I The DB2 load utility was not used. A row ID is specified for the table.




System Action—A refresh of the subscription table by DB2 LOAD is notperformed. Instead of DB2 LOAD, the standard InfoSphere CDC refresh will beused to refresh the target table.




CHC0515ICHC0515I The DB2 load utility was not used. Standard clear is set to no.







CHC0516ICHC0516I The DB2 load utility was not used. The table record length is too long.







CHC0517ICHC0517I The DB2 load utility was not used. The assignment type is RowConsolidation.








CHC0518ICHC0518I The DB2 load utility was not used. The assignment type is Summarization.







CHC0519ICHC0519I The DB2 load utility was not used. Conflict Detection is selected for thetable.








CHC0529ECHC0529 Table table does not exist in the metadata.

Explanation—A Management Console session has requested that an operation beperformed upon a source table, but the table is not in the InfoSphere CDCmetadata.

Message Variables:



System Action—The requested operation is rejected.



CHC0530ECHC0530E Table owner.table has already been added to the metadata.

Explanation—An attempt has been made in Management Console to add thespecified DB2 table to metadata that already contains the table.

Message Variables:




System Action—The specified table is not added to the metadata. The metadatawill contain the same set of tables before the operation was attempted.


Client Administrator Response—To add the table to the metadata, remove theexisting table and then proceed to add the same table. Alternatively, maintain theexisting table in the metadata, and do not attempt to add the table.


CHC0531ECHC0531E Subscription name has already been defined.

Explanation—An attempt has been made to define a subscription that alreadyexists. For each agent, each subscription must be assigned a unique name.

Message Variables:

name—The name of the subscription, as defined in Management Console, whichcould not be defined.


System Action—The specified subscription is not defined.


Client Administrator Response—Choose a unique name for the subscription thathas to be defined.

CHC0532ECHC0532E Unable to load information for table owner.table.

Explanation—A SQL error occurred during the process of retrieving internalinformation pertaining to the specified table. More information about the SQL erroris contained in the product administration log.

Message Variables:

owner—The owner of the table for which information cannot be retrieved.

table—The name of the table for which information cannot be retrieved.




Client Administrator Response—Use Management Console to open the productadministration log and examine the SQL error that has been logged. Note themessage number and contact your InfoSphere CDC administrator if you requirefurther assistance.

CHC0533ECHC0533E Unable to remove table owner.table. It is still selected to subscriptions.

Explanation—An attempt has been made in Management Console to remove thespecified table from the metadata that is currently selected for replication to one ormore subscriptions. Before a table can be removed from the metadata, it be mustfirst be deselected from each subscription under a specific datastore.

Message Variables:





System Action—The table is not removed from the metadata.


Client Administrator Response—Unmap the table from each subscription, andthen remove the table from the metadata.

CHC0535ECHC0535E Table owner.table is already selected to the subscription.

Explanation—An attempt has been made to select the specified source table forreplication to a subscription that has the table already selected. The same sourcetable cannot be selected for replication to a subscription more than once.

Message Variables:

owner—The owner of the source table that is already selected to a subscription.

table—The name of the source table that is already selected to a subscription.




Client Administrator Response—To select the specified source table to thesubscription, deselect the existing table from the subscription and then proceed toselect the same table. Alternatively, maintain the existing table under thesubscription and do not select the source table to the subscription.

CHC0536ECHC0536E Table owner.table is not selected to the subscription.

Explanation—The specified table selected to a subscription could not be found inan InfoSphere CDC metadata table. Metadata tables are internally maintained byInfoSphere CDC, and are updated to reflect replication configuration changes.

Message Variables:

owner—The owner of the table that cannot be found in a metadata table.

table—The name of the table that cannot be found in a metadata table.





Client Administrator Response—Inspect the InfoSphere CDC metadata tableDMMD_TARGET_TABLE to verify that the table specified in the message text isnot referenced.

CAUTION:You should not directly modify InfoSphere CDC metadata tables, as incorrectchanges can corrupt your replication configuration. You may want to note themessage number and contact your InfoSphere CDC administrator for furtherassistance.

CHC0537ECHC0537E Column name already exists in table owner.table.

Explanation—An attempt was made to add the specified derived column to a tablethat already contains the derived column. The name of the derived column addedto a table must be unique.

Message Variables:

name—The name of the derived column that cannot be added to the specified table.

owner—The owner of the table to which the specified derived column cannot beadded.

table—The name of the table to which the specified derived column cannot beadded.


System Action—The derived column is not added to the table.


Client Administrator Response—Assign a unique name to the derived columnthat you want to add. Alternatively, remove the derived column that has the samename from the table, and then add the derived column to the table using the samename.

CHC0538ECHC0538E Unable to update the alias for column name.

Explanation—A SQL error occurred during an attempt to change the aliasassociated with the specified column.

Message Variables:

name—The name of the column associated with the alias that could not be updateddue to a SQL error.


System Action—The column alias is not changed.



Client Administrator Response—Use Management Console to open the productadministration log and examine the SQL error that has been logged. Note themessage number and contact your InfoSphere CDC administrator if you requirefurther assistance.

CHC0539ECHC0539E Subscription name does not exist.

Explanation—The specified subscription could not be found in an InfoSphere CDCmetadata table. Metadata tables are internally maintained by InfoSphere CDC, andare updated to reflect configuration changes.

Message Variables:





Client Administrator Response—Inspect the InfoSphere CDC metadata tableDMMD_TARGET_TABLE to verify that the table specified in the message text isnot referenced.

CAUTION:You should not directly modify InfoSphere CDC metadata tables, as incorrectchanges can corrupt your replication configuration. You may want to note themessage number and contact your InfoSphere CDC administrator for furtherassistance.

CHC0540ECHC0540E Replication is active to subscription name. The selected function isunavailable.

Explanation—An attempt has been made to start replication or modify theconfiguration of the specified active subscription. If replication to the specifiedsubscription is in progress, initiating replication to the subscription or modifyingits configuration cannot be performed.

Message Variables:

name—The name of the active subscription, as defined in Management Console, towhich the selected function could not be applied.




Client Administrator Response—Before applying the selected function, either stopreplication activities to the subscription or wait for replication activities (refresh ornet change mirroring) to conclude.


CHC0541ECHC0541E Connection to database is not yet established.

Explanation—An attempt has been made to issue a Management Consolecommand through an InfoSphere CDC datastore that is not connected to the userdatabase, and the command must manipulate tables in the user database. Tosuccessfully issue the given command from a client workstation runningManagement Console, a connection to the datastore database must first beestablished.




Operator Response—Examine the JESMSGLOG log to verify that the InfoSphereCDC instance and datastore processes have been started. If the JESMSGLOG logcontains any message referring to the instance or datastore process, note themessage number and contact your InfoSphere CDC administrator if you requirefurther assistance.


CHC0543ECHC0543E Column name is not nullable.

Explanation—A null-to-value or value-to-null translation was defined for a columnthat is not nullable.

Message Variables:

name—The name of the column that does not support translations to or fromNULL.


System Action—The translation is not saved.


Client Administrator Response—Remove all translations to or from NULL thathave been defined for the specified column.

CHC0545ECHC0545E Decimal fractions are not supported in Value Translations.

Explanation—A translation involving numerical data with a decimal point wasdefined for a column. This kind of translation is not supported even though thecolumn supports decimal, floating point, or a similar numerical representation.




System Action—The translation is not performed.


Client Administrator Response—Remove all translations involving numerical datathat contains a decimal point.

CHC0546ECHC0546E CHARACTER translations cannot be set into a numeric field.

Explanation—A translation that produces character data has been defined for anumeric column. For numeric columns, all translations must produce numericresults.



System Action—The translation is not saved.


Client Administrator Response—Remove all translations for a numeric columnthat produces character results.

CHC0547ECHC0547E An invalid Length for a Derived Column has been entered for column name.The permitted column lengths are: CHAR 1-255, VARCHAR 1-2048, FLOAT 4 or 8, andDECIMAL 1-31.

Explanation—The length specified for a derived column is not valid for the datatype. Derived columns are defined in Management Console.

Message Variables:



System Action—The derived column will not be defined.


Client Administrator Response—In Management Console, you must set the lengthof the derived column to a valid value. The message text identifies the supportedlengths for common data types that are supported by InfoSphere CDC.

CHC0548ECHC0548E Tablespace name does not exist in Database db.

Explanation—The table space specified in Management Console when creating atarget table does not currently exist in the named database.

Message Variables:


name—The name of the table space specified in Management Console.

db—The database specified in Management Console that does not currently containthe table space identified in the message text.


System Action—The target table is not created.


Client Administrator Response—In Management Console, you must specify thename of an existing table space in the database. If a table space does not exist inthe database, create a new table space before creating the target table or select adifferent database that has a table space.

CHC0549ECHC0549E The INTEGER Value is outside the supported ranges. The range for 4 byteINTEGERS is -2147483648 to 2147483647 the range for 2 byte INTEGERs is -32768 to32767.

Explanation—A translation for an integer column references a number that is notwithin the upper and lower limits for a signed long or short integer. In this case,the closest limit is assumed in the translation.



System Action—The translation is used, but integer values not within the limitsautomatically default to the closest limit.


Client Administrator Response—You can modify the translation in ManagementConsole so that the limits are not exceeded.

CHC0550ECHC0550E User id has connected to the InfoSphere Change Data Capture datastore.

Explanation—Provides confirmation of a connection operation for an InfoSphereCDC for z/OS datastore. The operation was performed using the specified securityidentifier.

Message Variables:

id—The security identifier that is being used to access a datastore in ManagementConsole.

Message Destination—Audit log





CHC0551ECHC0551E User id has disconnected from the InfoSphere Change Data Capture datastore.

Explanation—Provides confirmation of a disconnection operation for an InfoSphereCDC for z/OS datastore. The operation was performed using the specified securityidentifier.

Message Variables:

id—The security identifier that is being used to access a datastore in ManagementConsole.





CHC0552ECHC0552E A maximum of one ROWID column is allowed per table.

Explanation—An attempt to create a target table with more than one ROWIDcolumn was unsuccessful. In DB2 for z/OS, a maximum of one ROWID columncan be defined in a single table.



System Action—The target table was not created.


Client Administrator Response—In Management Console, remove one or moreROWID columns from the target table so that a maximum of one ROWID columnremains in the table. After removing ROWID columns, complete the table creationprocess.

CHC0553ECHC0553E Column name of type ROWID cannot be mapped to blanks, constant values,expressions or journal control fields.

Explanation—In Management Console, an attempt was made to map a ROWIDcolumn to a defined value. ROWID columns can only be mapped to other ROWIDcolumns.

Message Variables:

name—The name of the ROWID column in the target table that could not bemapped to a defined value.





Client Administrator Response—In Management Console, map the identifiedROWID column in the target table to a ROWID column in the source table.Alternatively, set the ROWID column in the target table to be unmapped.

CHC0554ECHC0554E ROWIDs are not supported in Value Translations.

Explanation—In Management Console, an attempt was made to define valuetranslations for a ROWID column in a target table. The attributes of a ROWIDcolumn prevent value translations from being defined for the column.



System Action—The value translations were not defined for the ROWID column.


Client Administrator Response—If required, define value translations for othercolumns in the target table.

CHC0555ECHC0555E Unable to add table table_1 to the metadata due to table table_2having duplicate DBID, PSID, OBID combination.

Explanation—An attempt to add a table to the metadata in Management Consolewas unsuccessful. The table has the same DBID, PSID, and OBID settings asanother table already in the metadata. Each physical DB2 table has a unique DBID,PSID, and OBID combination. This message may be generated when a table thathas been physically deleted from the database has not been removed from themetadata, and an attempt is subsequently made to add a different table with thesame combination to the metadata. In this case, the definition of the physicallydeleted table remains in the InfoSphere CDC metadata, and therefore prevents anyother table with the same combination from being added.

Message Variables:

table_1—The name of the table that cannot be added to the metadata inManagement Console.

table_2—The name of the table that is preventing the table from being added tothe metadata.


System Action—The table is not added to the metadata.



Client Administrator Response—In Management Console, deselect the table(table_2) that is preventing the addition to the metadata from all subscriptions.Remove the same table (table_2) from the metadata, and then add the other table(table_1) again.

CHC0556ICHC0556I User name is being disconnected by the inactivity time.

Explanation—A connection to an InfoSphere CDC datastore established by aManagement Console user will be automatically disconnected as a result ofcontinuous inactivity for a specified period of time. The timeout period is definedby setting the ADMININACTTIMEOUT configuration control statement keyword.A controlled shutdown of the address space cannot be performed if at least oneManagement Console user is connected to a datastore running in the addressspace. Establishing a timeout period may be required in your environment so thatan inactive connection does not prevent an InfoSphere CDC address space frombeing shut down in a controlled manner.

Message Variables:

name—The Management Console user that has been automatically disconnectedfrom the datastore.


System Action—The connection to the datastore established by the ManagementConsole user is automatically disconnected.

Operator Response—The current setting for the ADMININACTTIMEOUTkeyword may be too low. If necessary, increase this setting so that activeManagement Console users are not disconnected from their datastores too quickly.

Client Administrator Response—If the connection to the datastore must bereestablished, the user must reconnect to the datastore in Management Console.

CHC0557ECHC0557E Connection to metadata is not yet established.

Explanation—An attempt has been made to issue a Management Consolecommand through an InfoSphere CDC datastore that is not connected to themetadata, and the command must manipulate the metadata. To successfully issuethe given command from a client workstation running Management Console, aconnection to the metadata must first be established.



System Action—The command fails.

Operator Response—Examine the JESMSGLOG log to verify that the InfoSphereCDC instance and datastore processes have been started. If the JESMSGLOG logcontains any message referring to the instance or datastore process, note themessage number and contact your InfoSphere CDC administrator if you requirefurther assistance.



CHC0558ECHC0558E Subscription name is not active.

Explanation—An attempt has been made to issue a Management Consolecommand through an InfoSphere CDC datastore, and the command requires that aparticular subscription be running, but that subscription is not running. Tosuccessfully issue the given command from a client workstation runningManagement Console, the specified replication must first be started.

Message Variables:

name—The name of the subscription that must be running.



Operator Response—This is likely to be a logic error in Management Console.Contact your InfoSphere CDC administrator if you require further assistance.


CHC0560ECHC0560E The row filtering expression for table schema.name is invalid.

Explanation—An attempt has been made to issue a Management Consolecommand through an InfoSphere CDC datastore to set the row filtering expressionfor a table, but the specified row filtering expression is not valid. This is almostcertainly a user error. Common errors are specifying a column that is not in thetable (misspelling the column name), comparing a column to an invalid data type(comparing a character column to a numeric value), specifying nonexistent journalcontrol fields or column functions (misspelling the name of the journal control fieldor column function).

Message Variables:

schema.name—The schema and name of the table.





CHC0561ECHC0561E The translation metadata for column name in table table is corrupt.

Explanation—A Management Console session has requested the translations forone or more target table columns, and the translation for at least one of thosecolumns has been corrupted.


Message Variables:




System Action—A null translation for the column is returned to the ManagementConsole session and an error message is also sent to the Management Consolesession.


Client Administrator Response—Further investigation is required to determinehow the metadata was corrupted. Contact IBM Technical Support.

CHC0562ECHC0562E The maximum number of columns allowed in a CREATE TABLE SQL statementis number.

Explanation—A Management Console session has requested that a target table becreated with more than the allowable number of columns.

Message Variables:

number—The maximum number of columns allowed in a table by DB2.


System Action—The requested target table is not created.


Client Administrator Response—In Management Console, try creating a targettable with fewer columns.

CHC0564ECHC0564E The latency alert threshold values can be from 0 to 32767.

Explanation—A Management Console session has requested that a latency alertthreshold for a subscription be set to an illegal value. Latency alert thresholds maybe set to any integral value from 0 to 32767 minutes.



System Action—The requested latency alert thresholds are not set.



Client Administrator Response—In Management Console, enter legal values forthe latency alert thresholds.

CHC0565ECHC0565E Derived column identifier id in agent request number was not found fortable in subscription name.

Explanation—A Management Console session has requested that a derived columnof a source table be returned or deleted, and the derived column does not exist.

Message Variables:

id—The numeric identifier of the derived column.

number—The request number received from the Management Console session.




System Action—The request is rejected.



CHC0566ECHC0566E Source Row Identifier expression name is not valid.

Explanation—A Management Console session has requested that Row Identifierexpression for a source table be validated or set and the Row Identifier expressionis not valid.

Message Variables:

name—The offending Row Identifier expression. In order to be valid, a RowIdentifier expression must be a legal SQL WHERE clause for the table.


System Action—The Row Identifier expression is not set for the source table.


Client Administrator Response—Specify a valid Row Identifier expression for thesource table.

CHC0567WCHC0567W Deleting translation from fromval to toval, configured for column name,which does not exist in table table.


Explanation—A Management Console session has requested that a target table beremapped. Since it was originally mapped, the target table has changed such that acolumn no longer exists and that column had a translation configured.

Message Variables:

fromval—The ″from″ value for the translation.

toval—The ″to″ value for the translation.

name—The name of the column which no longer exists.

table—The name of the target table being remapped.


System Action—The translation is deleted and the target table is remapped.



CHC0568WCHC0568W Deleting expression [name] configured for column column, which does notexist in table table.

Explanation—A Management Console session has requested that a target table beremapped. Since it was originally mapped, the target table has changed such that acolumn no longer exists and that column was mapped to an expression.

Message Variables:

name—The name of the expression.

column—The name of the column which no longer exists.



System Action—The defined expression is deleted and the target table isremapped.



CHC0569WCHC0569W Deleting invalid expression [name] configured for column column, in tabletable.


Explanation—A Management Console session has requested that a target table beremapped. Since it was originally mapped, the target table has changed such that acolumn which was mapped to a expression is no longer compatible with the typeof the expression.

Message Variables:

name—The name of the expression.

column—The name of the column which has changed.



System Action—The defined expression is deleted and the target table isremapped.



CHC0570ECHC0570E Summarization or Consolidation key column name cannot be found in targettable table.

Explanation—A Management Console session has requested that a target table beremapped. Since it was originally mapped, the target table has changed such that aSummarization or Consolidation key column no longer exists.

Message Variables:

name—The name of the column which no longer exists.



System Action—The target table is not remapped.


Client Administrator Response—In Management Console, unmap then remap thetable.

CHC0571WCHC0571W Invalid translation is being deleted from fromval to toval, configuredfor column name, in table table

Explanation—A Management Console session has requested that a target table beremapped. Since it was originally mapped, the target table has changed such that acolumn which had a translation configured is no longer compatible with the typeof that translation.


Message Variables:

fromval—The ″from″ value for the translation.

toval—The ″to″ value for the translation.

name—The name of the column which has changed.



System Action—The translation is deleted and the target table is remapped.



CHC0572ECHC0572E Address space is shutting down. The request has been rejected.

Explanation—A Management Console session has requested that a subscriptionstart a refresh or mirror operation, but the InfoSphere CDC address space hasinitiated a shutdown.



System Action—The subscription is not started.


Client Administrator Response—Close the Management Console session andallow the InfoSphere CDC address space to terminate. After the InfoSphere CDCaddress space is restarted, initiate a new Management Console session and retrythe operation.

CHC0573ECHC0573E A resource shortage was encountered. The request has been rejected.

Explanation—A Management Console session has requested that a subscriptionstart a refresh or mirror operation. When attempting to start the operation,InfoSphere CDC address space was unable to obtain a required resource, such asmemory.



System Action—The subscription is not started.


Operator Response—Examine the system log for messages which indicate whatresource could not be obtained.

Client Administrator Response—Terminate the Transformation Address serveraddress space and make the changes required to make more of the requiredresource available to InfoSphere CDC. Restart the InfoSphere CDC address spaceand retry the operation. Alternatively, shut down one or more existingsubscriptions and retry the operation.

CHC0574ECHC0574E Column column in table owner.table in subscription name is not of a DB2type eligible for MBCS translation.

Explanation—The specified column is not eligible for MBCS translation.

Message Variables:

column—The column name.





System Action—MBCS translation is not set for the column.



CHC0575ECHC0575E Network type network and DB2 type type for column column in tableowner.table in subscription name are inconsistent.

Explanation—An inconsistency in the metadata for the specified column wasdetected.

Message Variables:

network—The network type of the column.

type—The DB2 type of the column.








Client Administrator Response—Update the definition of the table and retry theoperation. If this does not eliminate the error message, contact support.

CHC0576ECHC0576E Metadata for column column in table owner.table in subscription namecould not be found. Please ensure that the column exists and update the tabledefinition.

Explanation—Metadata for the specified column could not be found.

Message Variables:







Client Administrator Response—Update the definition of the table and retry theoperation. If this does not eliminate the error message, contact support.

CHC0577WCHC0577W The specified translation for column column in table owner.table insubscription name might fail.

Explanation—The translation as specified might fail. For example, if the sourcecode page is a multi byte code page and the target code page is single byte codepage, some characters will not be convertible.

Message Variables:






System Action—The MBCS translation is set.




CHC0579ECHC0579E The specified translation for column column in table owner.table insubscription name is invalid.

Explanation—The translation as specified is not valid. For example, if the sourcecolumn is binary and only a target code page is specified, the translation cannot beperformed, since the source code page is unknown.

Message Variables:






System Action—The MBCS translation is not set.



CHC0580ECHC0580E The byte byte at position position is a malformed UTF-8character.

Explanation—A character value in an expression contains an invalid UTF-8character. Expressions, and all character values passed to or generated byexpressions, are encoded in UTF-8, which uses a variable-length representation forcharacters. One of the characters in the expression or value does not have a validlength indication in the first byte of the representation. This message should onlyappear if a column that contains non-character data is passed as input to a stringfunction, or if the expression itself contains an invalid value specified as decimalintegers (using double angle bracket syntax).

Message Variables:

byte—The hexadecimal value of the byte with the invalid length indication.

position—The byte position of the start of the invalid representation.


System Action—The expression evaluation fails. Replication continues or endsbased on the ENDONERROR keyword setting.



Client Administrator Response—Correct the expression to specify valid UTF-8characters, or to not pass the column data to any string manipulation functions.

CHC0581WCHC0581W The MBCS settings to default for column column in table owner.table insubscription name is being reset.

Explanation—The MBCS translation settings for the specified column were reset todefaults. For example, if a column’s data type changed from CHARACTER toINTEGER, the MBCS translation settings would not longer be valid. When aRe-add is performed, the MBCS translation settings would be reset to defaults.

Message Variables:









CHC0582ECHC0582E Source derived columns of type type may not be created.

Explanation—A user attempted through Management Console to create a sourcederived column of an unsupported type, such as ROWID.

Message Variables:

type—The unsupported column type.


System Action—The derived column is not created.

Operator Response—Choose a supported column type for the derived column.


CHC0583ECHC0583E The View name is not valid as a target table.


Explanation—In Management Console, an attempt was made to assign to theidentified Materialized Query Table (MQT) on the target. This assignment is notallowed. You cannot perform an assignment that lets you replicate data to an MQTon a target. You can only assign an MQT on a source system to a conventionaltable on a target.

Message Variables:

name—The name of the View on the target that could not be assigned.


System Action—The assignment is unsuccessful. Active replication continues forother assignments.


Client Administrator Response—If you want to include an MQT in yourreplication configuration, assign an MQT on a source to a conventional table on atarget. This is the only supported assignment for an MQT.

CHC0584ECHC0584E The Materialized Query Table name is not valid as a target table.

Explanation—In Management Console, an attempt was made to assign to theidentified Materialized Query Table (MQT) on the target. This assignment is notallowed. You cannot perform an assignment that lets you replicate data to an MQTon a target. You can only assign an MQT on a source system to a conventionaltable on a target.

Message Variables:

name—The name of the MQT on the target that could not be assigned.


System Action—The assignment is unsuccessful. Active replication continues forother assignments.


Client Administrator Response—If you want to include an MQT in yourreplication configuration, assign an MQT on a source to a conventional table on atarget. This is the only supported assignment for an MQT.

CHC0595ICHC0595I Updates are being sent that occurred during the active refresh of tableschema.table.

Explanation—A refresh has finished and updates applied to the specified tableduring the refresh are currently being replicated to the subscription. InfoSphereCDC allows you to refresh a source table to a target environment while updatesare being applied to the source table.

Message Variables:



table—The name of the table that the updates were applied to during a refresh.





CHC0596ICHC0596I Updates that occurred during refresh have finished being sent to table

schema.table .

Explanation—A refresh has finished and all updates applied to the specifiedsource table during the refresh have been replicated to the target table. InfoSphereCDC allows you to refresh a source table to a target environment while updatesare being applied to the source table.

Message Variables:


table— The name of the table that the updates were applied to during a refresh.





CHC0598WCHC0598W SYSIBM.SYSTABLES does not have DATA CAPTURE CHANGES enabled. On-line schemaevolution detection will not be available.

Explanation—InfoSphere CDC has determined that SYSIBM.SYSTABLES does nothave DATA CAPTURE CHANGES enabled. The online schema evolution detectionfeature, which relies on DATA CAPTURE CHANGES being enabled, will not beavailable.






Client Administrator Response—On-line schema evolution detection can increaseup-time for subscriptions and provide early warning for changes to a source table,which impacts InfoSphere CDC operations. If you want to use this feature, alterthe DB2 catalog table SYSIBM.SYSTABLES to enable DATA CAPTURE CHANGES.

CHC0599WCHC0599W Table table has been dropped on date at time. The table will be markedidle.

Explanation—The identified source table was dropped from DB2 while it wasbeing mirrored by InfoSphere CDC. Mirroring immediately ends for the table thatis dropped from DB2. The replication status of the source table is automatically setto Idle. Replication continues for all other source tables being replicated for thesame subscription.

Message Variables:

table—The name of the source table dropped from DB2 while mirroring wasactive.

date—The date when the source table was dropped from DB2.

time—The time when the source table was dropped from DB2.


System Action—Mirroring ends for the dropped table. Replication continues for allother source tables being replicated for the same subscription.


Client Administrator Response—You may want to investigate the reason why thesource table was dropped from DB2. Dropping the table while mirroring wasactive may indicate that the table was accidentally dropped from DB2. Undernormal circumstances, mirroring of a table is stopped in Management Consolebefore the table is dropped. If you need to recreate the source table and restartmirroring, update the table definition in Management Console after recreating thetable. Restart mirroring after successfully updating the table definition.


“CHC0600I” on page 367“CHC0602W” on page 367“CHC0604W” on page 368“CHC0605E” on page 368“CHC0662E” on page 369“CHC0663E” on page 369“CHC0669W” on page 369“CHC0670W” on page 370“CHC0676I” on page 371“CHC0677I” on page 371“CHC0683I” on page 371


“CHC0684I” on page 372“CHC0685I” on page 372“CHC0686I” on page 372“CHC0687I” on page 373“CHC0688I” on page 373“CHC0689I” on page 374“CHC0690I” on page 374

CHC0600ICHC0600I No material changes to table name were detected. Replication continues.

Explanation—Replication of the identified source table starts or continues eventhough the table was altered in DB2. The nature of the alteration applied to thesource table in DB2 did not prevent replication of that table from starting orcontinuing.

Message Variables:

name—The name of the source table altered in DB2 during or prior to the start ofreplication.


System Action—Replication continues for all active source tables under thesubscription.



CHC0602WCHC0602W Table name has been altered on date at time.

Explanation—InfoSphere CDC is in the process of determining whether mirroringof the identified source table can continue in response to the table being altered inDB2.

Message Variables:

name—The name of the source table that has been altered in DB2 while mirroringwas active.

date—The date when the source table was altered.

time—The time when the source table was altered.


System Action—After the required analysis has been completed, CHC0600I isgenerated if mirroring continues. Otherwise, a message in the range ofCHC0832W-CHC0838W is generated if mirroring ends.



Client Administrator Response—Inspect the product administration log todetermine which message has been subsequently generated. If mirroring ends, seethe Client Administrator Response to CHC0832W-CHC0838W (as applicable).Related reference


CHC0604WCHC0604W A column has been added to table table which is in reordered row format.A reorg of the table space and refresh of the table is required.

Explanation—While mirroring, InfoSphere CDC detected that a column has beenadded to a table which is in DB2 version 9.1 Reordered Row Format. InfoSphereCDC cannot continue to mirror this table.

Message Variables:





Client Administrator Response—A REORG of the table spaces which contain thetable, followed by a refresh of the table, is required.

CHC0605ECHC0605E Table name has been dropped on date at time. Mirroring will end

Explanation—The identified source table was dropped from DB2 while it wasbeing mirrored by InfoSphere CDC. Mirroring immediately ends in error for thesubscription.

Message Variables:

name—The name of the source table dropped from DB2 while mirroring was active.

date—The date when the source table was dropped from DB2.

time—The time when the source table was dropped from DB2.


System Action—Mirroring ends in error.


Client Administrator Response—You may want to investigate the reason why thesource table was dropped from DB2. Dropping the table while mirroring wasactive may indicate that the table was accidentally dropped from DB2. Undernormal circumstances, mirroring of a table is stopped in Management Consolebefore the table is dropped. If you need to recreate the source table and restartmirroring, re-add the table in Management Console after recreating the table.


Restart mirroring after successfully re-adding the table. For information aboutre-adding tables and starting mirroring, see your ManagementConsoledocumentation.

CHC0662ECHC0662E Mirror cannot be set as a replication method for schema.name because it isa View, which is only supported for Refresh.

Explanation—In Management Console, an attempt was made to set the replicationmethod of the identified Materialized Query Table (MQT) on a source system toMirror. This is not allowed, as data in MQTs can only be refreshed.

Message Variables:

schema.name—The schema and name of the MQT on the source system that couldnot have its replication method set to Mirror.


System Action—The replication method is not set to Mirror.


Client Administrator Response—In Management Console, set the replicationmethod of the identified MQT to Refresh. For MQTs on a source system, this is theonly option for the replication method.

CHC0663ECHC0663E Mirror cannot be set as a replication method for schema.name because itis a Materialized Query Table, which is only supported for Refresh.

Explanation—In Management Console, an attempt was made to set the replicationmethod of the identified Materialized Query Table (MQT) on a source system toMirror. This is not allowed, as data in MQTs can only be refreshed.

Message Variables:

schema.name—The schema and name of the MQT on the source system that couldnot have its replication method set to Mirror.


System Action—The replication method is not set to Mirror.


Client Administrator Response—In Management Console, set the replicationmethod of the identified MQT to Refresh. For MQTs on a source system, this is theonly option for the replication method.

CHC0669WCHC0669W The replication update process failed to format the BEFORE image foroperation operation. The bookmark for the entry is bmk from source system source.The target table is owner.table.


Explanation—InfoSphere CDC was unable to format the record image.

Message Variables:

operation—The name of the operation.


source—The name of the source system.




System Action—Replication will either continue or shut down based on theseverity of the error and the end on error setting.


Client Administrator Response—This message should be preceded by othermessages which detail the exact nature of the error. Investigate these messages todetermine the problem.

CHC0670WCHC0670W Replication update process failed to format the AFTER image for operationoperation. The bookmark for the entry is bmk from source system source.The target table is owner.table.

Explanation—InfoSphere CDC was unable to format the record image.

Message Variables:

operation—The name of the operation.






System Action—Replication will either continue or shut down based on theseverity of the error and the end on error setting.


Client Administrator Response—This message should be preceded by othermessages which detail the exact nature of the error. Investigate these messages todetermine the problem.


CHC0676ICHC0676I CHCPRINT Channel was opened.

Explanation—The named file was successfully opened in an InfoSphere CDCoperation. This message is generated when the CHCPRINT spool data set isopened. The CHCPRINT spool data set, provided with InfoSphere CDC, maintainsa copy of all messages in the product administration log. InfoSphere CDC storesthese messages in the CHCPRINT spool data set for the duration of the currentInfoSphere CDC session, and it clears them from CHCPRINT when restarting.CHCPRINT is also an Notifications channel, so it is possible to disable events frombeing copied to CHCPRINT. It is not recommended that this be done, as thecontents of CHCPRINT are crucial information for diagnosing customer issues.


Message Destination—CHCPRINT spool data set.




CHC0677ICHC0677I The Audit Log was opened.

Explanation—The named file was successfully opened in an InfoSphere CDCoperation. This message is generated when the InfoSphere CDC audit log isopened. The audit log traces certain operations initiated in Management Console orfrom the operator console, as well as configuration parameters and maintenancelevels of the code.


Message Destination—The InfoSphere CDC audit log




CHC0683ICHC0683I User id has started mirroring to subscription name.

Explanation—Replication activity to the named subscription has been started orstopped by a security identifier.

Message Variables:

id—The security identifier that started replication activity.







CHC0684ICHC0684I User id has started refresh to subscription name.


Message Variables:







CHC0685ICHC0685I User id has started describe to subscription name.


Message Variables:







CHC0686ICHC0686I User id has started replication to subscription name.



Message Variables:







CHC0687ICHC0687I User id has stopped mirroring to subscription name.


Message Variables:

id—The security identifier that stopped replication activity.






CHC0688ICHC068I User id has stopped refresh to subscription name.


Message Variables:








CHC0689ICHC0689I User id has stopped describe to subscription name.


Message Variables:







CHC0690ICHC0690I User id has stopped replication to subscription name.


Message Variables:








“CHC0701I” on page 376“CHC0702I” on page 376“CHC0703I” on page 376“CHC0704I” on page 377“CHC0705I” on page 377“CHC0706I” on page 378“CHC0707I” on page 378“CHC0708I” on page 378“CHC0709I” on page 379


“CHC0711I” on page 379“CHC0712I” on page 380“CHC0713I” on page 380“CHC0714I” on page 380“CHC0715I” on page 381“CHC0716I” on page 381“CHC0717I” on page 382“CHC0718I” on page 382“CHC0719I” on page 382“CHC0721I” on page 383“CHC0722I” on page 383“CHC0723I” on page 384“CHC0724I” on page 384“CHC0725I” on page 385“CHC0726I” on page 385“CHC0727I” on page 385“CHC0728I” on page 386“CHC0729E” on page 386“CHC0731I” on page 387“CHC0732I” on page 387“CHC0733I” on page 388“CHC0734I” on page 388“CHC0735I” on page 388“CHC0736E” on page 389“CHC0741I” on page 389“CHC0742I” on page 389“CHC0743I” on page 390“CHC0744I” on page 390“CHC0745I” on page 391“CHC0746I” on page 391“CHC0747I” on page 392“CHC0751I” on page 392“CHC0752I” on page 393“CHC0753I” on page 393“CHC0755I” on page 393“CHC0761I” on page 394“CHC0762I” on page 394“CHC0763I” on page 394“CHC0764E” on page 395“CHC0765E” on page 395“CHC0772I” on page 395“CHC0779W” on page 396“CHC0782I” on page 396“CHC0783I” on page 396“CHC0788W” on page 397


“CHC0791I” on page 397“CHC0792I” on page 398“CHC0793I” on page 398“CHC0799W” on page 399

CHC0701ICHC0701I Unbalanced parentheses exist in an expression.

Explanation— An expression defined in Management Console contains left andright parentheses that do not match. For example, the first parenthesis in theexpression may be a right parenthesis. In this case, there is a missing leftparenthesis.



System Action—The expression is not evaluated.


Client Administrator Response—Correct the expression defined in ManagementConsole so that left and right parentheses match.

CHC0702ICHC0702I The expression is not a valid conditional statement.

Explanation—An expression defined in Management Console cannot be evaluateddue to an incorrectly formed conditional statement.





Client Administrator Response—Define a valid conditional statement in theexpression.

CHC0703ICHC0703I An unrecognized token token was found in position position.

Explanation—An expression defined in Management Console contains a token(field name, operator, and so on) that is unrecognized or does not appear in theexpected position.

Message Variables:

token—The token that is not recognized by the InfoSphere CDC parser.

position—The character position in the expression where the unrecognized tokenis located.





Client Administrator Response—Correct the expression by placing a recognizedtoken in the specified position.

CHC0704ICHC0704I An invalid comparison operator operator was found in location location.

Explanation—An expression defined in Management Console contains acomparison operator that is not recognized by InfoSphere CDC.

Message Variables:

operator—The comparison operator that is not recognized by the InfoSphere CDCparser.

location—The character position in the expression where the unrecognizedcomparison operator is located.




Client Administrator Response—Correct the expression by placing a recognizedoperator in the specified position.

CHC0705ICHC0705I An improperly terminated literal operator was found in location position.

Explanation—An expression defined in Management Console contains a literal thathas not been properly delimited. In most cases, this message indicates that acharacter string is missing surrounding double quotes.

Message Variables:

operator—The comparison operator that is not recognized by the InfoSphere CDCparser.

position—The character position in the expression where the incorrect literal islocated.




Client Administrator Response—Correct the expression by placing a terminatedliteral in the specified position.


CHC0706ICHC0706I An invalid function name name was found in location position.

Explanation—An expression defined in Management Console contains a columnfunction name that is not recognized by InfoSphere CDC.

Message Variables:

name—The column function name that is not recognized by the InfoSphere CDCparser.

position—The character position in the expression where the unrecognizedcolumn function name is located.




Client Administrator Response—For information about using valid functionnames in expressions, see your Management Console documentation. Alldocumented functions are not supported by InfoSphere CDC for z/OS.

CHC0707ICHC0707I Operator operator is not valid in a conditional statement.

Explanation—An expression defined in Management Console contains an operatorthat cannot be used in a conditional statement.

Message Variables:

operator—The operator found in the expression that cannot be used in aconditional statement.




Client Administrator Response—Correct the expression by replacing the existingoperator with a recognized operator. If necessary, see your Management Consoledocumentation for information about constructing valid expressions.

CHC0708ICHC0708I Operator operator is not valid in an expression.

Explanation—An expression defined in Management Console contains an operatorthat cannot be used.

Message Variables:

operator—The operator found in the expression that cannot be used.





Client Administrator Response—The notation for representing a specific operatormay differ based on the type of database. For example, the notation for not equalcould be <> for certain databases, and != for other databases. Consult theappropriate publication from the database vendor for information about the set ofsupported operators.

CHC0709ICHC0709I Token token in position position is not valid; an operator was expected.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operand, and so on) when it anticipated anoperator in the specified position.

Message Variables:

token—The token that was found in the expression when an operator wasexpected.

position—The character position in the expression where the unexpected token islocated.




Client Administrator Response—Correct the expression by placing an operator inthe specified position. If necessary, see your Management Console documentationfor information about constructing valid expressions.

CHC0711ICHC0711I Token token in position position is not valid; an operand was expected.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated anoperand in the specified position.

Message Variables:

token—The token that was found in the expression when an operand wasexpected.






Client Administrator Response—Correct the expression by placing an operand inthe specified position.

CHC0712ICHC0712I A conditional statement is not valid within an expression.

Explanation—An expression defined in Management Console contains aconditional statement. In InfoSphere CDC, an expression cannot contain aconditional statement.





Client Administrator Response—Correct the expression so it produces a value thatcan be assigned to the derived column.

CHC0713ICHC0713I Unbalanced parentheses were found in an expression; an erroroccurred at token token.

Explanation—An expression defined in Management Console contains left andright parentheses that do not match. For example, the first parenthesis in theexpression may be a right parenthesis. In this case, there is a missing leftparenthesis.

Message Variables:

token—The token in the expression that was being parsed when the error wasencountered.




Client Administrator Response—Correct the expression defined in ManagementConsole so that left and right parentheses match.

CHC0714ICHC0714I The expression starting at token contains non-numeric fields.

Explanation—An expression defined in Management Console contains a referenceto a non-numeric field when a numeric field was expected.

Message Variables:


token—The token in the expression that identifies the position of the nonnumericfield.




Client Administrator Response—Correct the expression by replacing thenon-numeric field with a numeric field.

CHC0715ICHC0715I An invalid compare occurred starting at token token; the datatypesare incompatible.

Explanation—An expression defined in Management Console contains acomparison operation between incompatible data types.

Message Variables:

token—The token in the expression that identifies the comparison operationbetween incompatible data types.




Client Administrator Response—Correct the expression so that the comparisonoperation is between compatible data types.

CHC0716ICHC0716I Token token in position position is not valid; an AND or OR operator wasexpected.

Explanation—An expression defined in Management Console contains a token(field name, operator, and so on) when an AND or OR operator was anticipated inthe specified position.

Message Variables:

token—The token in the expression that was being parsed when an AND or ORoperator was expected.






Client Administrator Response—Correct the expression by placing an AND or ORoperator in the specified position.

CHC0717ICHC0717I Unexpected end of expression

Explanation—An expression defined in Management Console is incomplete (forexample, the last token in the expression may be an arithmetic operator).InfoSphere CDC expected additional tokens after parsing the entire expression.





Client Administrator Response—Correct the expression by adding the necessarytokens to define a complete expression.

CHC0718ICHC0718I Token token in position position has the wrong datatype.

Explanation—An expression defined in Management Console contains a token(field name, literal, and so on) that has an incompatible data type.

Message Variables:

token—The token in the expression that has an incompatible data type.

position—The character position in the expression where the incompatible token islocated.




Client Administrator Response—Correct the expression by replacing the offendingtoken with one that has the correct data type.

CHC0719ICHC0719I Token token in position position is not valid. An operand was expected.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated anoperand in the specified position.

Message Variables:

token—The token that was found in the expression when an operand wasexpected.






Client Administrator Response—Correct the expression by placing an operand inthe specified position.

CHC0721ICHC0721I Token token in position position is not valid; an "(" is required.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated a leftparenthesis in the specified position. This usually indicates that a right parenthesiswas found in the expression before a matching left parenthesis.

Message Variables:

token—The token that was found in the expression when a left parenthesis wasexpected.





Client Administrator Response—Correct the expression by placing a leftparenthesis in the specified position.

CHC0722ICHC0722I Token token in position position is not valid; a ")" is required.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated a rightparenthesis in the specified position. This usually indicates that another leftparenthesis was found in the expression before a matching right parenthesis.

Message Variables:

token—The token that was found in the expression when a right parenthesis wasexpected.






Client Administrator Response—Correct the expression by placing a rightparenthesis in the specified position.

CHC0723ICHC0723I Token token in position position is not valid; a "," is required.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated a commain the specified position. Commas in expressions are typically used in columnfunctions to separate adjacent parameters.

Message Variables:

token—The token that was found in the expression when a comma was expected.





Client Administrator Response—Correct the expression by placing a comma inthe specified position.

CHC0724ICHC0724I Token token in position position is not valid; a literal is required.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated a literalin the specified position.

Message Variables:

token—The token that was found in the expression when a literal was expected.





Client Administrator Response—Correct the expression by placing a valid literalin the specified position.


CHC0725ICHC0725I Token token in position position is not valide; an option is required.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated anoption in the specified position. Options are used in certain column functions toallow the user to specify the kind of actions that are performed by the function.

Message Variables:

token—The token that was found in the expression when an option was expected.





Client Administrator Response—Correct the expression by placing a recognizedoption in the specified position.

CHC0726ICHC0726I Token token in position position is not valide; a field name is required.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (literal, operator, and so on) when it anticipated a field namein the specified position.

Message Variables:

token—The token that was found in the expression when a field name wasexpected.





Client Administrator Response—Correct the expression by placing a valid fieldname in the specified position.

CHC0727ICHC0727I Token token in position position was found in a function call. Thefunction expects a variable name in that position.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated a


variable name in the specified position. Variables are used to support conditionalbranching in a column function (%IF). They are also referenced in the %VARfunction.

Message Variables:

token—The token that was found in the expression when a variable name wasexpected.





Client Administrator Response—Correct the expression by placing a variablename in the specified position.

CHC0728ICHC0728I An error occurred at token token in position position. A requiredconditional statement was not found in the parameter list where it is expected.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token (field name, operator, and so on) when it anticipated aconditional statement in the specified position. The first parameter in the %IFcolumn function requires a conditional statement

Message Variables:

token—The token that was found in the expression when a conditional statementwas expected.





Client Administrator Response—Correct the expression by placing a validconditional statement in the specified position.

CHC0729ECHC0729E Column name contains datatype ROWID, which is not supported in derivedcolumns.

Explanation—A derived column has been defined in Management Console with adata type that is not supported by InfoSphere CDC. Alternatively, a derivedcolumn expression defined in Management Console references a column of thistype.


Message Variables:

name—The name of the column that has a data type of GRAPHIC, VARG,LONGVARG, or ROWID.


System Action—The derived column is not replicated.


Client Administrator Response—In Management Console, either deselect thederived column so that it is not replicated, or modify the expression to remove thereference to the column with a data type of GRAPHIC, VARG, LONGVARG, orROWID.

CHC0731ICHC0731I A conditional statement is not valid within a function call.

Explanation—An expression defined in Management Console contains a columnfunction call with one of the parameters being a conditional statement. Aconditional statement cannot be passed to the specified function.





Client Administrator Response—Correct the expression by specifying a parametervalue that is accepted by the function.

CHC0732ICHC0732I Invalid option name in parameter 2 of %REPLACE function.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered an incorrectly specified parameter in the %REPLACE columnfunction. This parameter, which is the second function parameter, identifies whichcharacters are replaced.

Message Variables:

name—The option in the %REPLACE function that was incorrectly specified.




Client Administrator Response—Correct the expression by specifying a recognizedoption.


CHC0733ICHC0733I Invalid option name in parameter 2 of %TODATE function.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered an incorrectly specified parameter in the %TODATE column function.This parameter, which is the second function parameter, identifies the format inwhich the date is expressed (for example, YYMMDD, MMDDYY, and so on).

Message Variables:

name—The option in the %TODATE function that was incorrectly specified.




Client Administrator Response—Correct the expression by specifying a recognizeddate format option.

CHC0734ICHC0734I Division by zero is undefined.

Explanation—An expression defined in Management Console produced a divisionby zero operation.





Client Administrator Response—Define another expression that avoids thepossibility of a division by zero operation. Alternatively, determine whether invaliddata is causing the problem.

CHC0735ICHC0735I Column function has too many parameters.

Explanation—An expression defined in Management Console contains a columnfunction with too many parameters.






Client Administrator Response—Correct the expression by removing one or moreparameters from the function call.

CHC0736ECHC0736E Expression name failed in validation.

Explanation—A Management Console session has requested an operation thatrequired validation of an expression. The expression failed in validation.

Message Variables:

name—The name of the failing expression.


System Action—The requested operation fails.


Client Administrator Response—In Management Console, enter a valid expressionand retry the operation.

CHC0741ICHC0741I Invalid token token found in position position.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered an unexpected or incorrectly formed token (field name, operator, andso on) in the specified position.

Message Variables:

token—The offending token that was found in the expression.

position—The character position in the expression where the offending token islocated.




Client Administrator Response—Correct the expression by placing a valid tokenin the specified position.

CHC0742ICHC0742I Table schema.name in subscription name has been set to status IDLE byuser.

Explanation—The specified table in the specified subscription has been set to thespecified status.

Message Variables:




user—The entity that set the new status for the table. There are three possibilities.If an actual user name is specified, then that user has set the new status of thetable using Management Console. If the string ″MODIFY command″ appears, thenthe table status was set in response to a MODIFY command directed from theconsole to InfoSphere CDC. If the string ″SYSTEM″ appears, then InfoSphere CDChas set the table status after successfully refreshing the table as part of normalprocessing.





CHC0743ICHC0743I Table schema.name in subscription subscription has been set to statusACTIVE by user.


Message Variables:








CHC0744ICHC0744I Table schema.name in subscription subscription has been set to statusREFRESH by user.



Message Variables:








CHC0745ICHC0745I Table owner.table in subscription name has been set to statusIDLE by a MODIFY command.


Message Variables:








CHC0746ICHC0746I Table owner.table in subscription name has been set to statusACTIVE by a MODIFY command.


Message Variables:









CHC0747ICHC0747I Table owner.table in subscription name has been set to statusREFRESH by a MODIFY command.


Message Variables:








CHC0751ICHC0751I Parameter 1 for %REPLACE function has the wrong datatype.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified through the first parameter in the%REPLACE column function. Only character data can be passed through the firstparameter, which identifies the data affected by the function.





Client Administrator Response—Correct the expression by specifying characterdata for the first parameter.


CHC0752ICHC0752I Parameter 3 for %REPLACE function has an invalid datatype or length.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered unacceptable data specified through the third parameter in the%REPLACE column function. Only character data less than a certain length can bepassed through the third parameter, which identifies the replaced characters.





Client Administrator Response—Correct the expression by specifying characterdata of the correct length for the third parameter.

CHC0753ICHC0753I Parameter 4 for %REPLACE function has an invalid datatype or length.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered unacceptable data specified through the fourth parameter in the%REPLACE column function. Only character data less than a certain length can bepassed through the fourth parameter, which identifies the replacement characters.





Client Administrator Response—Correct the expression by specifying characterdata of the correct length for the fourth parameter.

CHC0755ICHC0755I Parameter 2 for %REPLACE function is an invalid option.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered an incorrectly specified parameter in the %REPLACE columnfunction. This parameter, which is the second function parameter, identifies howcharacter replacement will be performed.






Client Administrator Response—Correct the expression by specifying a recognizedparameter.

CHC0761ICHC0761I Parameter 1 for %SUBSTRING function has the wrong datatype.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified through the first parameter in the%SUBSTRING column function. Only character data can be passed through thefirst parameter, which identifies the data affected by the function.





Client Administrator Response—Correct the expression by specifying characterdata for the first parameter.

CHC0762ICHC0762I Parameter 2 for %SUBSTRING must be an INTEGER value that is greaterthan 0.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified in the second parameter in the%SUBSTRING column function. Only integer data can be passed through thesecond parameter, which identifies the position of the first character extracted bythe function.





Client Administrator Response—Correct the expression by specifying integer datafor the second parameter.

CHC0763ICHC0763I Parameter 3 for %SUBSTRING function has the wrong datatype.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified through the third parameter in the%SUBSTRING column function. Only integer data can be passed through the thirdparameter, which identifies the length of the substring extracted by the function.






Client Administrator Response—Correct the expression by specifying integer datafor the third parameter.

CHC0764ECHC0764E User Exit entry point type in the agent request is invalid.

Explanation—A Management Console session has requested that a user exit be setfor a type of user exit that is not known to InfoSphere CDC.

Message Variables:

type—The numeric type of the user exit in the request.


System Action—The requested user exit is not set.



CHC0765ECHC0765E User Exit entry point type in the agent request is unsupported.

Explanation—A Management Console session has requested that a user exit be setfor a type of user exit that is known, but is not supported by InfoSphere CDC forz/OS.

Message Variables:

type—The numeric type of the user exit in the request.


System Action—The requested user exit is not set.



CHC0772ICHC0772I Parameter 2 for %TOCHAR function has the wrong datatype.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified through the second parameter in the


%TOCHAR column function. Only integer data can be passed through the secondparameter, which identifies the number of characters returned by the function.





Client Administrator Response—Correct the expression by specifying integer datafor the second parameter.

CHC0779WCHC0779W Parameter 2 for %CENTURY function is an invalid option.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered an incorrectly specified date parameter in the %CENTURY columnfunction. This parameter, which is the second function parameter, indicates theformat of the date (for example, YYMMDD, MMDDYY, and so on).





Client Administrator Response—Correct the expression by specifying a recognizeddate format parameter.

CHC0782ICHC0782I Parameter 2 for %TODATE function has the wrong datatype.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified through the second parameter in the%TODATE column function. Only character data that specifies a valid date formatcan be passed in the second parameter.





Client Administrator Response—Correct the expression by specifying validcharacter data for the second parameter.

CHC0783ICHC0783I Parameter 2 of %TODATE function is an invalid option.


Explanation—In an expression defined in Management Console, InfoSphere CDCencountered an incorrectly specified date option in the %TODATE columnfunction. This option, which is the second function parameter, indicates the formatin which the date is expressed (for example, YYMMDD, MMDDYY, and so on).





Client Administrator Response—Correct the expression by specifying a recognizeddate format option.

CHC0788WCHC0788W Parameter 1 for %CENTURY function has the wrong datatype.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified through the first parameter in the%CENTURY column function. Only numeric or character data can be passedthrough this parameter, which identifies the date to be converted to the desiredformat.





Client Administrator Response—Correct the expression by specifying validnumeric or character data for the first parameter.

CHC0791ICHC0791I Parameter 1 for %TONUMBER function has the wrong datatype.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data specified through the only parameter in the%TONUMBER column function. Only character data can be passed through thisparameter, which identifies the data to be converted to numeric data.





Client Administrator Response—Correct the expression by specifying validcharacter data for this parameter.


CHC0792ICHC0792I The Row Filtering Expression for table name will be used as a SQL WHEREclause during the Table Refresh.

Explanation—The row filtering expression defined for the identified source tablewill be treated as a SQL WHERE clause in the SELECT statement that implementsa refresh. If a correctly formed InfoSphere CDC row selection expression is treatedas a SQL WHERE clause, refresh performance improves significantly when a smallpercentage of the rows in a large table are selected for refresh. To realize thepossible improvements in refresh performance, the row filtering expression mustbe a correctly formed standard InfoSphere CDC row filtering expression and also asyntactically correct search-condition operand of the ″WHERE″ keyword in an SQLWHERE clause. In addition, the SQLWHEREROWSEL keyword in the DB2configuration control statement must be set to YES.

Message Variables:

name—The name of the source table for which a row filtering expression has beendefined.




Client Administrator Response—If the row filtering expression cannot be treatedas a SQL WHERE clause, make sure that the expression is correctly formed, andthe SQLWHEREROWSEL keyword is set to YES.

CHC0793ICHC0793I The Row Filtering Expression for table name cannot be used as a SQL WHEREclause during the Table Refresh.

Explanation—The row filtering expression defined for the identified source tablecannot be treated as a SQL WHERE clause in the SELECT statement thatimplements a refresh. If a correctly formed InfoSphere CDC row filteringexpression is treated as a SQL WHERE clause, refresh performance improvessignificantly when a small percentage of the rows in a large table are selected forrefresh. To realize the possible improvements in refresh performance, the rowfiltering expression must be a correctly formed standard InfoSphere CDC rowfiltering expression and also a syntactically correct search-condition operand of the″WHERE″ keyword in an SQL WHERE clause. In addition, theSQLWHEREROWSEL keyword in the DB2 configuration control statement must beset to YES.

Message Variables:






Client Administrator Response—If the row filtering expression cannot be treatedas a SQL WHERE clause, make sure that the expression is correctly formed, andthe SQLWHEREROWSEL keyword is set to YES.

CHC0799WCHC0799W Replication ends due to alteration of table name. Reason: DATA CAPTURECHANGES has been turned off.

Explanation—The identified source table has been altered in DB2 and as a result,replication of that table cannot be started. The schema change that preventsreplication from being started is identified in the message text. This message isgenerated when refresh or mirroring is started for a subscription.

Message Variables:



System Action—Replication of all tables (including those tables that are notaffected by the alteration) under the subscription is not started.


Client Administrator Response—Before you can start to replicate data from thesource table, you must perform one or more of the following operations inManagement Console:v Update the definition of the source tablev Remap the source tablev REORG of table space containing the source table

If row updates and deletes are applied to the source table after the schema changeand before the table definition update or REORG is performed, you must alsorefresh the source table before starting mirroring. For some schema changes, youdo not have to perform all of the listed operations. If you require a specificprocedure in response to a schema change, contact your database administrator orIBM representative for assistance.


“CHC0800W” on page 400“CHC0801W” on page 400“CHC0802W” on page 401“CHC0803W” on page 402“CHC0804W” on page 402“CHC0805W” on page 403“CHC0811E” on page 403“CHC0821E” on page 404“CHC0824E” on page 404


“CHC0825E” on page 405“CHC0826E” on page 405“CHC0831E” on page 406“CHC0839W” on page 406“CHC0844I” on page 407“CHC0845I” on page 407“CHC0846I” on page 408“CHC0847I” on page 408“CHC0848I” on page 409“CHC0859E” on page 409

CHC0800WCHC0800I Replication ends due to alteration of table name. Reason: table DBID,OBID or PSID has changed.


Message Variables:







CHC0801WCHC0801W Replication ends due to alteration of table name. Reason: one or morecolumns have been removed.

Explanation—The identified source table has been altered in DB2 and as a result,replication of that table cannot be started. The schema change that prevents


replication from being started is identified in the message text. This message isgenerated when refresh or mirroring is started for a subscription.

Message Variables:

name—The name of the source table for which replication cannot be started.






CHC0802WCHC0802W Replication ends due to alteration of table name. Reason: columns havebeen renamed, inserted or removed.


Message Variables:








CHC0803WCHC0803W Replication ends due to alteration of table name. Reason: the data typeof a column has changed.


Message Variables:







CHC0804WCHC0804W Replication ends due to alteration of table name. Reason: the length orscale of a column has changed.


Message Variables:








CHC0805WCHC0805W Replication ends due to alteration of table name. Reason: a column wasadded to a table whose rows are in RRF.


Message Variables:







CHC0811ECHC0811E Parameter parameter of the name function has the wrong data type.


Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data for a parameter in a column function call. Theparameter and function name are identified in the message text. In this case,InfoSphere CDC does not support automatic data type conversions.

Message Variables:

parameter—The parameter in the column function call that has receivedincompatible data. Parameters are identified by numbers, where 1 is the firstparameter in the function call.

name—The name of the column function in the expression that has receivedincompatible data through one of its parameters.




Client Administrator Response—Specify a parameter value of the correct type.Alternatively, modify the expression by including a column function that performsthe appropriate data type conversion on the parameter. For example, use%TOCHAR or %TONUMBER to convert the parameter to character or numericdata before passing the value to the function specified in the message text.

CHC0821ECHC0821E Parameter for %TOTIME function has the wrong data type.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered incompatible data for the %TOTIME function parameter. In this case,InfoSphere CDC does not support automatic data type conversions.





Client Administrator Response—Specify a parameter value of the correct type.Alternatively, modify the expression by including a column function that performsthe appropriate data type conversion on the parameter. For example, use%TOCHAR or %TONUMBER to convert the parameter to character or numericdata before passing the value to the %TOTIME function.

CHC0824ECHC0824E Numeric Overflow occurred during expression evaluation.

Explanation—A numeric overflow occurred during the evaluation of anexpression. Numeric overflow may occur during the evaluation of expressions androw filtering expressions.




System Action—The numeric expression will return the default value of zero.


Client Administrator Response—Although replication may continue after thismessage has been generated, the result produced by the expression may beincorrect after the default value has been applied. If possible, use a different datatype that can accommodate all large, positive numeric values that can be producedby the expression, or rewrite the expression so that numeric overflow never occurs.

CHC0825ECHC0825E Numeric Underflow occurred during expression evaluation.

Explanation—A numeric underflow occurred during the evaluation of anexpression. Numeric underflow may occur during the evaluation of expressionsand row filtering expressions.



System Action—The numeric expression will return the default value of zero.


Client Administrator Response—Although replication may continue after thismessage has been generated, the result produced by the expression may beincorrect after the default value has been applied. If possible, use a different datatype that can accommodate all large, negative numeric values that can be producedby the expression, or rewrite the expression so that numeric underflow neveroccurs.

CHC0826ECHC0826E Invalid Numeric data found during expression evaluation.

Explanation—A row filtering expression or expression contains a sequence ofcharacters that cannot be interpreted as numeric data. Valid numeric data wasexpected instead of the sequence of characters in the expression.



System Action—An appropriate default value is used instead of the sequence ofcharacters that could not be interpreted.


Client Administrator Response—Although replication may continue after thismessage has been generated, the result produced by an expression may beincorrect after the default value has been applied. Review expressions defined inManagement Console, and make any necessary corrections to ensure proper resultsare returned.


CHC0831ECHC0831E Variable name was not found. A second parameter is required in order tocreate it.

Explanation—An attempt was made to reference the value assigned to the namedexpression variable which had not been defined. Expression variables are definedby the %VAR column function. This function supports two different formats. Thefirst format, which requires two input parameters to be specified, defines a variableand assigns a value to it. The second format, which requires one input parameterto be specified, retrieves the current value assigned to the variable. Duringreplication, the first format must be evaluated for a specific variable before thesecond format can be evaluated. This message indicates that the order wasreversed - the second format was encountered first.

Message Variables:

name—The name of the undefined variable referenced in a %VAR functioninvocation.


System Action—The expression containing the %VAR function invocation is notevaluated. Replication to the subscription containing the table with the definedexpression may end.


Client Administrator Response—Examine all the expressions defined for a tablethat reference the variable in a %VAR column function. Make sure that %VARfunction in the first defined expression contains two valid input parameters. Thefirst expression is the one defined for the column with the lowest ordinal positionin the table.

CHC0839WCHC0839W Table name will be marked idle and mirroring of the table cannot continue.Reason: reason

Explanation—The identified source table has been altered in DB2 and as a result,mirroring of that table cannot continue. The replication status of the source table isautomatically set to Idle. The schema change that prevents mirroring fromcontinuing is identified in the message text. Replication continues for all othersource tables being replicated under the same subscription. This message isgenerated while the table is being mirrored.

Message Variables:

name—The name of the source table for which mirroring cannot continue.

reason—The schema change that prevents mirroring of the source table fromcontinuing. One of the following strings is inserted in the message text at thispoint:v DATA CAPTURE CHANGES has been turned offv table DBID, OBID or PSID has changedv one or more columns have been removed


v columns have been renamed, inserted or removedv the data type of a column has changedv the length or scale of a column has changedv a column was added to a table in DB2 version 9.1 Reordered Row Format


System Action—Mirroring ends for the altered table. Replication continues for allother source tables being replicated under the same subscription.


Client Administrator Response—Before you can restart mirroring data from thesource table, you must perform one or more of the following operations inManagement Console:v Re-add the source tablev Re-describe the source tablev Reassign the source table.v REORG of table space containing the source table

If row updates and deletes are applied to the source table after the schema changeand before the re-add or REORG is performed, you must also refresh the sourcetable before restarting mirroring.

For some schema changes, you do not have to perform all of the listed operations.If you require a specific procedure in response to a schema change, contact yourdatabase administrator or IBM representative for assistance. For information aboutre-adding, describing, assigning, and refreshing tables, see your ManagementConsole documentation. For information about table space REORGs, see theappropriate IBM publication.

CHC0844ICHC0844I Compare token in position position has an invalid length.

Explanation—In an expression defined in Management Console, InfoSphere CDCencountered a token that has an invalid length.

Message Variables:

position—The position in the expression string that identifies the start of theinvalid token. The first position in the expression string is 1, and the last positionis equal to the length of the expression string.




Client Administrator Response—Correct the expression by modifying the token sothat it is the proper length.

CHC0845ICHC0845I Constant token in position position has an invalid length.



Message Variables:






CHC0846ICHC0846I FieldName token in position position has an invalid length.


Message Variables:






CHC0847ICHC0847I Literal token in position position


Message Variables:







CHC0848ICHC0848I Function token in position position has an invalid length.


Message Variables:






CHC0859ECHC0859E Table name has changed and mirroring will end. Reason: reason

Explanation—The identified source table has been altered in DB2 and as a result,mirroring of that table cannot continue. Mirroring of the subscription will end. Theschema change that prevents mirroring from continuing is identified in themessage text. This message is generated while the table is being mirrored.

Message Variables:

name—The name of the source table for which mirroring cannot continue.

reason—The schema change that prevents mirroring of the source table fromcontinuing. One of the following strings is inserted in the message text at thispoint:v DATA CAPTURE CHANGES has been turned offv table DBID, OBID or PSID has changedv one or more columns have been removedv columns have been renamed, inserted or removedv the data type of a column has changedv the length or scale of a column has changedv a column was added to a table in DB2 version 9.1 Reordered Row Format


System Action—Mirroring ends in error.



Client Administrator Response—Before you can restart mirroring data from thesource table, you must perform one or more of the following operations inManagement Console:v Re-add the source tablev Re-describe the source tablev Reassign the source table.v REORG of table space containing the source table

If row updates and deletes are applied to the source table after the schema changeand before the re-add or REORG is performed, you must also refresh the sourcetable before restarting mirroring.

For some schema changes, you do not have to perform all of the listed operations.If you require a specific procedure in response to a schema change, contact yourdatabase administrator or IBM representative for assistance. For information aboutre-adding, describing, assigning, and refreshing tables, see your ManagementConsole documentation. For information about table space REORGs, see theappropriate IBM publication.


“CHC1019E”

CHC1019ECHC1019E Communications with the remote system have been lost.

Explanation—The local server has lost communications with a remote server. Thismessage can be logged on either a source or target server.



System Action—The internal InfoSphere CDC task that issued this message isstopped.


Client Administrator Response—On either the source or target server, othermessages in the product administration log may identify the cause of the problem.Use these messages to take corrective action.


“CHC1100E” on page 411“CHC1101E” on page 411“CHC1102W” on page 412“CHC1103E” on page 412“CHC1104E” on page 413


“CHC1106I” on page 413“CHC1107I” on page 413“CHC1108I” on page 414“CHC1109E” on page 414“CHC1110E” on page 414“CHC1111E” on page 415“CHC1113I” on page 415“CHC1114I” on page 415“CHC1115I” on page 416“CHC1116E” on page 417“CHC1117E” on page 417“CHC1118W” on page 417“CHC1119I” on page 418“CHC1120I” on page 418“CHC1121E” on page 419

CHC1100ECHC1100E The outbound communication queue is full. No more messages can be sent.

Explanation—A internal message could not be accepted as a result of a queuebeing full.






CHC1101ECHC1101E A heartbeat timeout has occurred. Replication will shut down.

Explanation—The InfoSphere CDC control task on the local server has not receivedany messages from the corresponding task on the remote server during theheartbeat timeout period. A heartbeat failure is declared. The control task managesactivity on a communications link that is used to coordinate data replication for aspecific subscription.






Client Administrator Response—A communications or remote server problem hasoccurred. Consult the other messages in the product administration log for moreinformation about the cause of the problem. Using these messages, performnecessary corrective actions and restart replication in Management Console. Basedon communications and server considerations in your working environment, youmay want to adjust the heartbeat timeout period. Increasing the timeout periodallows more time for communications between local and remote servers tocomplete.

CHC1102WCHC1102W an unexpected message id received. The message will be ignored.

Explanation—An InfoSphere CDC control or data task running on a serverreceived an unrecognized internal message from another server running InfoSphereCDC. The data task on a server manages activity on a communications link that isused to transmit replicated data. The control task on a server manages activity onanother communications link that is used to coordinate data replication.

Message Variables:

id—The identifier of the internal message that was not recognized.


System Action—The unrecognized internal message is ignored. Replicationcontinues.


Client Administrator Response—No immediate response is required, asInfoSphere CDC discards messages it cannot recognize. However, you may want toinspect other messages in the log to ensure no other errors have occurred close tothe time when this message was generated.

CHC1103ECHC1103E The target's bookmark length of maximum is insufficient. A length ofnumber is required.

Explanation—During the initial communications handshake between a sourcesystem and target, the source system has discovered that the defined maximumlength of a bookmark in the target environment is smaller than bookmark lengthsin the source environment. In this message, number > maximum.

Message Variables:

maximum—The defined maximum length of a bookmark in the target environment.

number—The length of bookmarks in the source environment.


System Action—Replication is not started.




CHC1104ECHC1104E Invalid commit control level level was received from the remote partner.

Explanation—During the initial communications handshake, it has been discoveredthat the commitment control level communicated from a source system or target isnot supported in the other environment. Commitment control settings defined onthe source system and target must be compatible.

Message Variables:

level—The commitment control level communicated from the source system ortarget.




Client Administrator Response—Record the message number and contact yourInfoSphere CDC administrator or IBM representative for assistance.

CHC1106ICHC1106I The Heartbeat feature is enabled. The timeout has been set to numberseconds.

Explanation—Heartbeat is enabled, and the heartbeat timeout period is set to theidentified number of seconds. This message reports the current heartbeat setting,and is generated during InfoSphere CDC initialization. A configuration controlstatement keyword called HEARTBEATTIMEOUT is provided to enable Heartbeatand to set the timeout period.

Message Variables:

number—The duration, in seconds, of the heartbeat timeout.





CHC1107ICHC1107I The Heartbeat feature is disabled.

Explanation—Heartbeat is disabled. This message is generated during InfoSphereCDC initialization. A configuration control statement keyword calledHEARTBEATTIMEOUT is provided to enable Heartbeat.







CHC1108ICHC1108I Commitment control is disabled.

Explanation—Commitment control is not supported in the subscriptionenvironment. As a result, InfoSphere CDC will not send commit records.






CHC1109ECHC1109E The remote system has reported a handshake failure.

Explanation—A problem occurred during communications handshake with aremote server.



System Action—The attempt to establish communications with the remote serverends. No data is replicated by InfoSphere CDC.


Client Administrator Response—Consult the product administration log on theremote server for other messages that provide more information as to why thecommunications handshake could not be completed. Based on these messages,perform necessary corrective actions.

CHC1110ECHC1110E Code page translation negotiation has failed.

Explanation—Code page translation could not be performed between the codepages on the local and remote servers.






Client Administrator Response—Determine whether or not code page translationcan be performed given the code pages on the local and remote servers. Iftranslation can be performed, install the correct server code page translation tables,and restart replication.

CHC1111ECHC1111E The remote system has reported a signon failure.

Explanation—An attempt to access a database on a remote server wasunsuccessful.





Client Administrator Response—Consult the product administration log on thelocal and remote servers for other messages that provide more information as towhy database access on a remote server could not be achieved. Based on thesemessages, perform necessary corrective actions.

CHC1113ICHC1113I Source original will have its name changed by the source system torenamed.

Explanation—A target has been requested to rename a publisher identifier inresponse to it being renamed in Management Console. This message is generatedwhen replication is started for the associated subscription.

Message Variables:

original—The original source identifier.

renamed—The source identifier after it has been renamed.


System Action—The source identifier will be renamed unless another sourceidentifier already exists that is named id2. If a source identifier with the new namealready exists, InfoSphere CDC generates CHC9701E.



CHC1114ICHC1114I Source original has been renamed by the source system to renamed.


Explanation—A target has renamed a source identifier in response to it beingrenamed in Management Console. This message is generated after CHC1113I,which indicates that an attempt will be made to rename the source identifier.

Message Variables:

original—The original source identifier.

renamed—The renamed source identifier.




Client Administrator Response—NoneRelated reference


CHC1115ICHC1115I Describe has completed. num1 tables were skipped, num2 tableswere described successfully, num3 tables were described unsuccessfully,num4 tables were deleted.

Explanation—A describe operation has completed, and specific information aboutthe operation is presented. The information is received from a target.

Message Variables:

num1—The number of source tables not described. On the target, the metadata forthese tables was already up-to-date, and so the describe operation was not applied.

num2—The number of source tables successfully described.

num3—The number of source tables unsuccessfully described. If at least one tablecould not be described successfully, see the Client Administrator Response below.

num4—The number of source tables for which existing metadata was deleted on thetarget. Existing target metadata for source tables that were not described in theoperation are deleted automatically.




Client Administrator Response—If one or more sources could not be successfullydescribed, examine the product administration log for other messages that providemore information about the describe operation. In particular, CHC1116E identifiesthe name of a source table that could not be described successfully. Based on thesemessages, perform necessary corrective actions.


Related reference

“CHC1116E”

CHC1116ECHC1116E The describe for table name was not successful.

Explanation—A source table could not be successfully described. On a target, thismessage identifies the name of the source table as reported by the source system.

Message Variables:

name—The name of the source table that could not be successfully described.


System Action—The describe operation for the identified source table isincomplete.


Client Administrator Response—Record the message number. Contact yourInfoSphere CDC administrator or IBM representative for assistance.Related reference


CHC1117ECHC1117E The remote partner's bookmark length of number is too long. A maximumlength of maximum is permitted.

Explanation—During the initial communications handshake between a sourcesystem and target, the target has discovered that the bookmark lengths in thesource environment are larger than the defined maximum length of a bookmark inthe target environment. In this message, number > maximum.

Message Variables:

number—The length of bookmarks in the source environment.

maximum—The defined maximum length of a bookmark in the target environment.





CHC1118WCHC1118W The control task for subscription name has lost connection withthe Monitor Agent.


Explanation—When the subscription identified in the message (by its name or thecorresponding source ID) attempted to send a status message to the MonitorAgent, InfoSphere CDC determined that the connection to the Monitor Agent hadbeen lost, most likely because the Monitor Agent task was terminated.

Message Variables:



System Action—Replication continues normally. Monitoring the subscription inManagement Console will not be possible. When the Monitor Agent restarts,replication will automatically reconnect and monitoring replication usingManagement Console will become possible again.



CHC1119ICHC1119I Sign-on accepted from type system name. Source database type isdatabase. Installation ID is idtext.

Explanation—InfoSphere CDC has accepted a connection request from the sourcenamed sysname.

Message Variables:

type—The operating system on the source.

name—The host name of the source, to which a connection has been established.

database—The type of the database installed on the source.

idtext—A unique name for the InfoSphere CDC installation on the source.





CHC1120ICHC1120I Replication has more journals than the Monitor Agent supports. Themaximum number is number.

Explanation—A subscription was reporting its performance metrics and latency tothe Monitor Agent, and doing so, it was determined that the subscription hadmore journals to report than the Monitor Agent supports.

Message Variables:


number—The maximum number of journals per replication that the Monitor Agentcan support.


System Action—Replication continues normally. The subscription will reportperformance metrics and latency only for the maximum number of journalssupported by the Monitor Agent. Any additional journals will not be reported, andthey will not generate latency messages.



CHC1121ECHC1121E The code page of the capability exchange could not be determined.Conversation code page is conversation, data code page is data.

Explanation—During a control conversation, a capability exchange message couldnot be processed because the code page of the message could not be determined.

Message Variables:

conversation—The negotiated conversation code page.

data—The negotiated data code page.


System Action—Replication fails to start.


Client Administrator Response—This is most likely an issue with the remoteinstance. Gather any diagnostic information and contact product support.


“CHC1232E”“CHC1251I” on page 420“CHC1252I” on page 420“CHC1258I” on page 420“CHC1259I” on page 421

CHC1232ECHC1232E Poorly formatted input was received for request number, detail.

Explanation—While processing the specified request, the product encounteredinvalid or unexpected information in the request.

Message Variables:

number—The request number being processed.


detail—The specific item in error.


System Action—The operation will be terminated.




CHC1251ICHC1251I Communications to host server was started on the control channel.

Explanation—Communications with the identified remote server has been startedon the control channel. The control channel is used for message transfers thatcoordinate the replication of data between servers.

Message Variables:

server—The host name of the remote server.





CHC1252ICHC1252I Communications to host server was started on the data channel.

Explanation—Communications with the identified remote server has been startedon the data channel. The data channel is used for the transmission of replicateddata.

Message Variables:






CHC1258ICHC1258I Communications for subscription name was started on the control channel.


Explanation—Communications on the control channel for a subscription identifierhave been successfully established with another server. The channel is ready totransmit data. The control channel is used for message transfers that coordinate thereplication of data between servers.

Message Variables:






CHC1259ICHC1259I Communications for subscription name was started on the data channel.

Explanation—Communications on the data channel for a subscription identifierhave been successfully established with another server. The channel is ready totransmit data. The data channel is used for the transmission of replicated data.

Message Variables:







“CHC1400E” on page 422“CHC1401E” on page 422“CHC1402E” on page 423“CHC1403E” on page 423“CHC1404E” on page 424“CHC1405E” on page 424“CHC1406E” on page 425“CHC1408E” on page 425“CHC1410W” on page 425“CHC1411W” on page 426“CHC1412E” on page 427


“CHC1413E” on page 427“CHC1414E” on page 428“CHC1415E” on page 428“CHC1416E” on page 428“CHC1417E” on page 429“CHC1418E” on page 429“CHC1419E” on page 430“CHC1420E” on page 430“CHC1421E” on page 431“CHC1422E” on page 431“CHC1423E” on page 432“CHC1424E” on page 432“CHC1425E” on page 433“CHC1426E” on page 433“CHC1432W” on page 434“CHC1433W” on page 434

CHC1400ECHC1400E Memory allocation has failed.

Explanation—An attempt to acquire main storage while processing an expressionwas unsuccessful.





Client Administrator Response—Check that there is sufficient main storage in thez/OS address space being used by InfoSphere CDC to support the on-goingprocessing of expressions. If possible, increase the storage in this address space toaccommodate expression processing.

CHC1401ECHC1401E Table name referenced in an expression does not exist

Explanation—The named table that is referenced in an expression does not exist inthe database.

Message Variables:

name—The name of the table that cannot be found.





Client Administrator Response—In Management Console, modify the table namein the expression to reference an existing table, or else change the expression toremove the table reference.

CHC1402ECHC1402E Column name referenced in an expression does not exist in table table.

Explanation—A column name referenced in an expression does not exist in thenamed table. Note that the table is also referenced in the expression. InManagement Console, expressions are automatically validated after they aredefined. However, if you modify a column name in the database after defining theexpression, this message is generated if the previous column name is stillreferenced in the expression.

Message Variables:

name—The name of the column referenced in the expression that does not exist inthe named table.

table—The name of the table referenced in the expression that does not containthe named column.




Client Administrator Response—In Management Console, perform the necessaryupdates to ensure that the expression refers to an existing column name in thetable. Restart replication activities that were stopped by this error.

CHC1403ECHC1403E An invalid data conversion from type1 to type2was attempted for columnname of table table.

Explanation—InfoSphere CDC could not perform a data type conversion betweenthe two named types. InfoSphere CDC does not support the data type conversion.For instance, this message is generated if a conversion from numeric data intocharacter data is attempted.

Message Variables:

name—The name of the column where the data type conversion cannot beperformed.

table—The name of the table containing the column where the data typeconversion cannot be performed.

type1—The data type that could not be converted.

type2—The data type into which the data could not converted.






Client Administrator Response—Review the data type conversion involving thecolumn in the named table. In Management Console, an explicit data typeconversion using a column function may have to be added to properly convert thedata type. After resolving the data type incompatibility, restart replication activitiesthat were stopped by this error.

CHC1404ECHC1404E The source data type for column name in table table is invalid.

Explanation—InfoSphere CDC does not support the data type of the column in thenamed source table.

Message Variables:

name—The name of the column in the source table that has an unsupported datatype.

table—The name of the source table containing the column that has anunsupported data type.




Client Administrator Response—Contact your system administrator to ensure thatthe latest version of InfoSphere CDC is installed on the source server. Afterupgrading InfoSphere CDC, restart replication activities that were stopped by thiserror.

CHC1405ECHC1405E Column name has an unsupported data type type.

Explanation—InfoSphere CDC does not support the data type of the namedcolumn.

Message Variables:







Client Administrator Response—Contact your system administrator to ensure thatthe latest version of InfoSphere CDC is installed on the source server. Afterupgrading InfoSphere CDC, restart replication activities that were stopped by thiserror.

CHC1406ECHC1406E SQL generation failed for table table.

Explanation—An error occurred while processing a %GETCOL function call. Therequired SQL statements could not be generated from the %GETCOL function callto retrieve a column from a secondary table.

Message Variables:

table—The name of the table that contains the expression with the %GETCOLfunction.




Client Administrator Response—Examine preceding messages in the productadministration log (accessible through Management Console) that addresses thisproblem. Use the information contained in these messages to perform correctiveactions, and then restart replication activities that were stopped by this error. Notethe message number and contact your InfoSphere CDC administrator if yourequire further assistance.

CHC1408ECHC1408E Please fix the following SQL error in your additional SQL: error.

Explanation—A Management Console session has requested to set the After Clearand/or After Refresh SQL statement for a table. The supplied SQL statement haserrors.

Message Variables:

error—An SQL error report.


System Action—The SQL statement is not set for the table.


Client Administrator Response—In Management Console, refer to the SQL errorreport, fix the errors in the SQL statement, and retry the request.

CHC1410WCHC1410W %GETCOL statement for table table requires a table space scan. This willseverely affect performance.


Explanation—A %GETCOL function call in an expression defined in ManagementConsole requires a DB2 scan of a table space. A table space scan will likelydeteriorate overall performance, and the impact is significant for most tables.

Message Variables:

table—The name of the table containing the column that invokes the %GETCOLfunction using an expression.




Client Administrator Response—If performance is unacceptable, use different oradditional key columns (if they exist in the primary table) to retrieve a secondarytable column with the %GETCOL function call. Using different or additional keycolumns may cause the %GETCOL function to generate SQL statements thatcircumvent the need for a DB2 table space scan.

CHC1411WCHC1411W An error occurred while assessing the performance impact of the%GETCOL statement for table name. The impact not assessed

Explanation—An error occurred while InfoSphere CDC was determining theperformance impact of a %GETCOL function call in an expression defined inManagement Console.

Message Variables:

name—The name of the table containing the column that invokes the %GETCOLfunction through an expression.


System Action—Although processing continues, no assessment is made of theperformance impact related to the %GETCOL function call. Notifications of adeterioration of performance (CHC1432W and CHC1410W) are not generated as aresult of the error.


Client Administrator Response—Preceding messages in the productadministration log (accessible through Management Console) address this issue.Use the information contained in these messages to perform any corrective actionsthat are required to enable notification of performance impacts. If this error persistsafter taking corrective actions, contact your InfoSphere CDC administrator forfurther assistance.


Related reference

“CHC1432W” on page 434“CHC1410W” on page 425

CHC1412ECHC1412E The value of %GETCOL key column key in table table is NULL.

Explanation—A value in a key column referenced in a %GETCOL function call isNULL. InfoSphere CDC does not accept a %GETCOL function call when the keycolumn contains a NULL value.

Message Variables:

key—The name of the key column referenced in the %GETCOL function thatcontains a NULL value.

name— The name of the table containing the nullable key column.


System Action—The internal InfoSphere CDC task that generated this message isstopped.


Client Administrator Response—In Management Console, change the %GETCOLfunction call in the expression to reference a key column that does not contain aNULL value. If the %GETCOL function call cannot be changed, use a %IF functioncall to only retrieve data from a secondary table when the value in the key columnis not NULL.

CHC1413ECHC1413E The value of name key column key is NULL; NULL key values cannot beprocessed.

Explanation—A value in a key column passed as an input parameter to the namedcolumn function call is NULL. InfoSphere CDC does not perform a columnfunction call when a key column input parameter yields a NULL value.

Message Variables:

name—The name of the column function that has been passed a key column with aNULL value.

key—The name of the key column that contains a NULL value.


System Action—Replication to the subscription containing the table with thedefined expression or row filtering expression may end.


Client Administrator Response—Make the necessary modifications to ensure thatthe named key column does not yield a NULL value during replication.


Alternatively, use the %IF column function to filter out NULL values beforepassing key column values to the named column function.

CHC1414ECHC1414E An invalid data conversion from origin to destination was attempted forcolumn name.

Explanation—An unsupported data type conversion is required for the namedcolumn that is referenced in an expression or row filtering expression.

Message Variables:

name—The name of the column that cannot be converted.

origin—The data type of the column in the expression or row filtering expression.

destination—The resulting data type in the required data type conversion.




Client Administrator Response—Either change the data type of the column, orchange the expression or row filtering expression so that the identified data typeconversion is not required.

CHC1415ECHC1415E Only a SELECT statement may appear in a %SELECT function.

Explanation—An attempt has been made to use the %SELECT column function toperform an action other than a SQL SELECT statement. The %SELECT function canonly be used to perform a valid SQL SELECT statement during the evaluation ofexpressions and row filtering expressions.



System Action—Replication to the subscription containing the table with thedefined %SELECT function may end.


Client Administrator Response—Modify the %SELECT function invocation so thatonly a valid SQL SELECT statement is specified for the first function parameter.

CHC1416ECHC1416E Only a single %SELECT function may appear in an expression.

Explanation—A single expression or row filtering expression contains more thanone %SELECT column function invocation. An expression or row filteringexpression can only contain a single %SELECT function invocation.




System Action—Replication to the subscription containing the table with thedefined %SELECT function may end.


Client Administrator Response—Modify the expression or row filtering expressionthat contains multiple %SELECT function invocations so that only one %SELECTfunction invocation is used. If possible, spread the %SELECT function invocationsacross multiple expressions or row filtering expressions.

CHC1417ECHC1417E Insufficient parameters were specified on function name ; At least numberparameters are required

Explanation—The number of input parameters passed to the named columnfunction is fewer than what is required.

Message Variables:

name—The name of the column function which has received fewer inputparameters than what is required.

number—The minimum or correct number of input parameters that must be passedto the column function.


System Action—Replication to the subscription containing the table with thedefined column function may end.


Client Administrator Response—Modify the function invocation so that a validnumber of input parameters are specified.

CHC1418ECHC1418E The length of column name exceeds the maximum allowed (size).

Explanation—The defined length of the named column exceeds the maximum forexpressions and row filtering expressions.

Message Variables:

name—The name of the column that is too long.

size—The maximum length (measured in bytes) that the column can be for it to beincluded in an expression or row filtering expression.





Client Administrator Response—If possible, change the length of the column inthe table so that the maximum is not exceeded.

CHC1419ECHC1419E The value value cannot be converted from origin to destination.

Explanation—A value returned by an expression or row filtering expression couldnot be accepted by the mapped column. The data type of the column is notcompatible with the returned value.

Message Variables:

value—The value returned by the expression or row filtering expression that is notcompatible with the data type of the mapped column.

origin—The data type of the value returned by the expression or row filteringexpression.

destination—The data type of the mapped column.




Client Administrator Response—Either change the data type of the mappedcolumn, or change the expression or row filtering expression so that it returns avalue compatible with the data type of the mapped column.

CHC1420ECHC1420E The default value for column name in table table is incompatible; aliteral value is required.

Explanation—A default value is incompatible with the data type of the column inthe named table. Although Management Console enforces data type compatibility,this message catches any specified default value that is not the correct type.

Message Variables:

name—The name of the column in the table that has been assigned a default valueincompatible with the data type of the column.

table—The name of the table that contains the column which has been assignedan incompatible default value.





Client Administrator Response—Use the information provided in the message textto identify the default value setting in Management Console that caused thismessage to be generated. Change the default value to the correct data type, andthen restart replication activities that were stopped by this error.

CHC1421ECHC1421E The default value for column name in table table is incompatible; aconstant value is required.


Message Variables:







CHC1422ECHC1422E The default value for column name in table table is incompatible; thedata types are incompatible.


Message Variables:








CHC1423ECHC1423E The default value for column name in table table is incompatible; thecolumn not nullable.


Message Variables:







CHC1424ECHC1424E The default value for column name in table table is incompatible; thedata type is unknown.


Message Variables:








CHC1425ECHC1425E The default value for column name in table table is incompatible; theISO Date is invalid.


Message Variables:







CHC1426ECHC1426E The default value for column name in table table is incompatible; theISO Time is invalid.


Message Variables:








CHC1432WCHC1432W %GETCOL statement for table table requires an index scan. This willadversely affect performance.

Explanation—A %GETCOL function call in an expression defined in ManagementConsole requires a DB2 scan of the index for the named table. An index scan isbeing performed each time a record is updated, and will likely deteriorate overallperformance. This deterioration in performance is significant if the table is notsmall.

Message Variables:

table—The name of the table that contains the column that invokes the %GETCOLfunction through an expression.




Client Administrator Response—If performance is unacceptable, use different oradditional key columns (if they exist in the primary table) to retrieve a secondarytable column with the %GETCOL function call. Using different or additional keycolumns may cause the %GETCOL function to generate SQL statements thatcircumvent the need for a DB2 index scan.

CHC1433WCHC1433W %GETCOL statement for table table requires a multiple index} scan. Thiswill adversely affect performance.

Explanation—A %GETCOL function call in an expression defined in ManagementConsole requires a DB2 scan of multiple indexes for the named table. An indexscan is being performed each time a record is updated, and will likely deteriorateoverall performance. This deterioration in performance is significant if the table isnot small.

Message Variables:

table—The name of the table that contains the column that invokes the %GETCOLfunction through an expression.




Client Administrator Response—If performance is unacceptable, use different oradditional key columns (if they exist in the primary table) to retrieve a secondary


table column with the %GETCOL function call. Using different or additional keycolumns may cause the %GETCOL function to generate SQL statements thatcircumvent the need for a DB2 index scan.


“CHC1501E”“CHC1502E” on page 436“CHC1503E” on page 436“CHC1504I” on page 437“CHC1505I” on page 437“CHC1508W” on page 437“CHC1511I” on page 438“CHC1514W” on page 438“CHC1515W” on page 439“CHC1517E” on page 439“CHC1518E” on page 440“CHC1520E” on page 441“CHC1521E” on page 441“CHC1522E” on page 442“CHC1524E” on page 442“CHC1527E” on page 443“CHC1531W” on page 443“CHC1532W” on page 443“CHC1533W” on page 444“CHC1539E” on page 444“CHC1540E” on page 445“CHC1541E” on page 445“CHC1542E” on page 445“CHC1543I” on page 446“CHC1544I” on page 446“CHC1545I” on page 447“CHC1551I” on page 447“CHC1552I” on page 448“CHC1553I” on page 448“CHC1559W” on page 449“CHC1560W” on page 449

CHC1501ECHC1501E Table schema.table requires a describe before replication.

Explanation—The identified source table has to be described before data in thetable can be replicated. Source tables must be described before data in those tablescan be replicated. Tables can be described in Management Console or by using anInfoSphere CDC console command.

Message Variables:



table—The name of the source table that has to be described.


System Action—The attempt to start replication is unsuccessful.


Client Administrator Response—Describe the identified source table and thenrestart replication.

CHC1502ECHC1502E An error occurred in the Describe Task; please see previous messagesfor more information.

Explanation—InfoSphere CDC detected an error while sending descriptions ofsource tables to a target environment.



System Action—The InfoSphere CDC internal task responsible for sending sourcetable descriptions has stopped. This means that the transfer of source tabledescriptions to the target has stopped.


Client Administrator Response—Previous messages in the product administrationlog identify why the transfer of the description stopped. Based on the informationthat is contained in these messages, perform the necessary modifications.

CHC1503ECHC1503E Table schema.table no longer exists.

Explanation—The identified table cannot be found in the database.

Message Variables:


table—The name of the source table that could not be found.




Client Administrator Response—It is possible that the table was physicallydeleted from the database, and the replication configuration was not updated to


reflect the deletion. Recreate the identified table in the database or remove thetable from your replication configuration. Restart replication.

CHC1504ICHC1504I The describe operation has been initiated for subscription name.

Explanation—The InfoSphere CDC data task for the specified target or sourceidentifier is managing an operation to describe source tables to a targetenvironment. The data task on a server manages activity on a communications linkthat is used to transmit replicated data for a specific target or source identifier. Thistask is also used to manage the describe operation, which must be performedbefore data replication can be started.

Message Variables:






CHC1505ICHC1505I The describe operation has been ended for subscription name.

Explanation—Source table descriptions are no longer being sent to the specifiedsubscription. A describe operation completes automatically after all descriptionshave been sent.

Message Variables:






CHC1508WCHC1508W The chosen table has no qualifying index. The selected assignment typerequires a qualifying index for mirroring. Do you still want to map this table?

Explanation—An attempt was made to map a source table to a target table thatdoes not have a unique index. In this case, InfoSphere CDC cannot mirror data tothe target table.






Client Administrator Response—The message appears in a Management Consoleconfirmation box. Click the Yes button on the confirmation box to map the tableswith the knowledge that you can only refresh data to the target table. Alternatively,click the No button if you do not want to map the tables.

CHC1511ICHC1511I One or more target tables have been unmapped from source source during adescribe, a report has been written to CHCREPRT.

Explanation—A describe operation was performed in Management Console withthe AUTODEASSIGN configuration keyword set to YES. As a result, InfoSphereCDC unmapped tables and removed relevant metadata. For recovery purposes, areport providing details of the replication configuration for the mapped tables waswritten to the CHCREPRT spool data set.

Message Variables:

source—The source identifier that identifies the location of the previously mappedsource tables.


System Action—The describe operation is completed.


Client Administrator Response—In the event that assigned tables wereinadvertently unmapped, use the information presented in the generated report torestore the replication configuration involving the source and target tables thathave been unmapped.

CHC1514WCHC1514W Language Environment's Code Page Conversion Services will be used.

Explanation—InfoSphere CDC has failed to initialize Unicode Conversion Services.As a result, Language Environment’s Code Page Conversion Services will be usedto perform code page conversions.



System Action—InfoSphere CDC will use Language Environment’s Code PageConversion Services used to perform code page conversions.



Client Administrator Response—See the previous messages in the productadministration log to determine why Unicode Conversion Services could not beused.

For better performance when converting characters between different code pages,you should configure InfoSphere CDC to use Unicode Conversion Services insteadof Language Environment’s Code Page Conversion Services.

CHC1515WCHC1515W Unicode Conversion Services does not support conversion from code pageorigin to code page destination. Language Environment's Conversion Services willbe used instead.

Explanation—InfoSphere CDC has received a request to convert characters fromone code page to another. The request could not be accomplished using UnicodeConversion Services.

Message Variables:

origin—The code page name from which characters are to be converted.

destination—The code page name to which characters are to be converted.


System Action—Language Environment’s Code Page Conversion Services will beused to convert characters between the specified code pages.


Client Administrator Response—The warning could be caused by one of thefollowing:v Invalid or missing CCSIDMAP statements for code pages origin and

destination in the CHCUCSxx member in the Configuration Control data set.v Invalid or missing CONVERSION statement for code pages origin and

destination in the CHCUCSxx member in the Configuration Control data set.v Conversion from code page origin to destination is not supported in your

environment under Unicode Conversion Services.To list the supported conversions, enter the following z/OS console command:D UNI,ALLVerify that the CONVERSION statements defined in the CHCUCSxx member inthe Configuration Control data set are also displayed in the list of supportedconversions.


CHC1517ECHC1517E Unicode Conversion Services request(sub-request) request has failed.Return code=return, Reason code=reason.


Explanation—An internal error has occurred in the interface between InfoSphereCDC and the CUNLCNV system function that provides support for UnicodeConversion Services. The CUNLCNV request that failed is identified in themessage text.

Message Variables:

request—The name of the Unicode Conversion Services main request that failed.

sub-request—The name of the Unicode Conversion Services sub-request thatfailed. Together with the name of the main request, this unambiguously identifieswhich service request failed.

return—The code returned by the UCS system function. Consult the appropriateIBM publication for an explanation of this code.

reason—The reason code returned by the UCS system function. Consult theappropriate IBM publication for an explanation of this code.




Client Administrator Response— Note the UCS function return and reason codes.Consult the appropriate IBM Unicode Conversion Services publication todetermine the corrective actions that should be taken. If this message indicates thata CUNLCNV(CONNECT) request failed, contact your system programmer todetermine if Unicode Conversion Services can be installed on the server.


CHC1518ECHC1518E Initialization of Unicode Conversion Services has failed.

Explanation—Unicode Conversion Services could not be initialized. Previousmessages in the product administration log provide further clarification as to whatcaused the failure.



System Action—Language Environment’s Code Page Conversion Services will beused to perform code page conversions.


Client Administrator Response—See the previous messages in the ProductAdministration log to determine the corrective actions that should be taken.


Verify the following:v The Unicode Conversion Services are installed on the server.v The CHCUCSxx member in the Configuration Control data set is present.v No errors have been reported from the CHCUCSxx member in the

Configuration Control data set.

For better performance when converting characters between different code pages,Unicode Conversion Services should be used instead of Language Environment’sCode Page Conversion Services.

CHC1520ECHC1520E LE Conversion Services does not support conversion from codepage 'origin'to codepage 'destination'. Conversion cannot be performed.

Explanation—InfoSphere CDC tried to initiate code page conversion from originto destination and the operating system indicated it could not perform theconversion.

Message Variables:

origin—The name of the ’from’ code page.

destination—The name of the ’to code page.


System Action—Processing will end.

Operator Response—Configure the system to use Unicode Conversion Services(UCS) instead of LE Conversion Services. If UCS also cannot perform theconversion, make sure the proper conversion methods are defined.


CHC1521ECHC1521E An error occurred reading a log record. Mirroring will terminate.

Explanation—InfoSphere CDC could not read a log record. This is an internalInfoSphere CDC problem.



System Action—InfoSphere CDC stops running.

Operator Response—Further investigation is required. Note the message numberand issue the DSPACT=ALL command to obtain information about current InfoSphereCDC activity. In addition, obtain the generated diagnostic SDUMP. After collectingthe information, contact your InfoSphere CDC administrator for further assistance.



CHC1522ECHC1522E An error occurred accessing Hiper Space or a Memory File. Mirroring willterminate.

Explanation—InfoSphere CDC encountered a problem accessing Hiper Space or amemory file. It is generated when mirroring is started to a subscription. InfoSphereCDC activity may have exhausted the available memory space.



System Action—InfoSphere CDC stops running.

Operator Response—Further investigation is required. Note the message numberand issue the DSPACT=ALL command to obtain information about current InfoSphereCDC activity. In addition, obtain the generated diagnostic SDUMP. After collectingthe information, contact your InfoSphere CDC administrator for further assistance.


CHC1524ECHC1524E Staging space size for subscription name has reached 100% of limit. Allreplication activities have stopped.

Explanation—The contents of the staging space for the specified subscription hasreached its capacity. As a result, all replication activities associated with thesubscription have been stopped. The maximum staging space size for allsubscriptions is defined by the MAXSUBSCRSTAGESIZE keyword in the DB2configuration control statement.

Message Variables:

name—The name of the subscription that had its staging space exceed capacity.


System Action—All replication activities associated with the specified subscriptionend. A staging space report that provides information about the commit groupsthat caused the staging space to be exhausted is generated automatically. Thisreport is appended to the CHCREPRT spool data set.


Client Administrator Response—Consult the information provided in the stagingspace report that has been generated automatically in the CHCREPRT spool dataset. From this report, you may be able to develop strategies to avoid the stagingspace from reaching its limit in the future. Alternatively, set the maximum size ofthe staging space for all subscriptions so that the upper limit is never reached. Thisis achieved by setting the MAXSUBSCRSTAGESIZE keyword to a higher memoryspace value. After taking necessary actions or modifying the value assigned to thekeyword, synchronize mapped source and target tables with an initial refresh andthen restart mirroring for the subscription.


CHC1527ECHC1527E The associated DSL is no longer active.

Explanation—The InfoSphere CDC task responsible for scraping the DB2 Logduring mirroring has ended unexpectedly.



System Action—Active mirroring ends.


Client Administrator Response—Previous messages in the product administrationlog identify what caused to task to end unexpectedly. Based on the informationthat is contained in these messages, perform the necessary corrective actions.

CHC1531WCHC1531W CCSID ccsid cannot be resolved to an IANA encoding name.

Explanation—The specified CCSID could not be converted to an IANA encodingname because an IANAMAP statement was not specified in the CHCUCSxxconfiguration member for this CCSID.

Message Variables:

ccsid—The unresolved CCSID.




Client Administrator Response—Further errors may occur if the product cannotdetermine the proper IANA name to use by other means.

CHC1532WCHC1532W The staging space size for subscription name has exceeded 90% of limit.

Explanation—The contents of the staging space for the specified subscription hasapproached capacity (above 90% of capacity). The maximum staging space size forall subscriptions is defined by the MAXSUBSCRSTAGESIZE keyword in the DB2configuration control statement.

Message Variables:

name—The name of the subscription that had its staging space approach capacity orfall below a safe level.




Operator Response—Although replication activities continue, you may want togenerate a staging space report to obtain various items of information about thestaging space. The report may indicate problems that could surface at a later time.Use the InfoSphere CDC REPORT command to generate a staging space report.

Client Administrator Response—If the contents of the staging space hasapproached capacity (″exceeded 90%″), then increase the maximum size of thestaging space for all subscriptions by setting the MAXSUBSCRSTAGESIZEconfiguration control statement keyword to a higher memory space value. If thecontents of a staging space reaches capacity, all replication activities associatedwith the subscription automatically ends

CHC1533WCHC1533W The staging space size for subscription name has receded below 85% oflimit.

Explanation—The contents of the staging space for the specified subscription hasfallen below a certain threshold (below 85% of capacity). The maximum stagingspace size for all subscriptions is defined by the MAXSUBSCRSTAGESIZEkeyword in the DB2 configuration control statement.

Message Variables:

name—The name of the subscription that had its staging space approach capacity orfall below a safe level.



Operator Response—Although replication activities continue, you may want togenerate a staging space report to obtain various items of information about thestaging space. The report may indicate problems that could surface at a later time.Use the InfoSphere CDC REPORT command to generate a staging space report.


CHC1539ECHC1539E The FROM value is too long. The maximum length for character valuetranslations is size characters.

Explanation—In a translation defined in Management Console, a FROM value (thevalue being converted) exceeds the maximum length, as specified in the messagetext.

Message Variables:

size—The maximum length of a FROM value in the translation. For characters, upto 26 characters can be specified.


System Action—The translation is not processed.


Operator Response—Specify a ″FROM″ value whose length does not exceed thelimit.


CHC1540ECHC1540E The TO value is too long. The maximum length for character valuetranslations is size characters.

Explanation—In a translation defined in Management Console, a TO value (thevalue that is produced after the translation) exceeds the maximum length, asspecified in the message text.

Message Variables:

size—The maximum length of a TO value in the translation. For characters, up to26 characters can be specified.




Client Administrator Response—Through Management Console, either removethe offending translation, or change the TO value so that it is within the maximumnumber of characters or digits.

CHC1541ECHC1541E The FROM value is too long. The maximum length for numeric valuetranslations is size characters.

Explanation—In a translation defined in Management Console, a FROM value (thevalue being converted) exceeds the maximum length, as specified in the messagetext.

Message Variables:

size—The maximum length of a FROM value in the translation. For numericvalues, up to 18 digits can be specified.




Client Administrator Response—Through Management Console, either removethe offending translation, or change the FROM value so that it is within themaximum number of characters or digits.

CHC1542ECHC1542E The TO value is too long. The maximum length for numericvalue translations is size characters.


Explanation—In a translation defined in Management Console, a TO value (thevalue that is produced after the translation) exceeds the maximum length, asspecified in the message text.

Message Variables:

size—The maximum length of a TO value in the translation. For numeric values,up to 18 digits can be specified.




Client Administrator Response—Through Management Console, either removethe offending translation, or change the TO value so that it is within the maximumnumber of characters or digits.

CHC1543ICHC1543I Conversion from codepage origin to codepage destination using UnicodeConversion Services has been successfully initialized.

Explanation—One-way character conversion from one code page to another isavailable and that conversion has been initialized successfully. The message textalso indicates the conversion service that will be used to perform the conversion.This message is generated when conversion from origin to destination has beendetermined as being available.

Message Variables:




System Action—InfoSphere CDC will use the conversion service indicated in themessage text to convert characters between the specified code pages.



CHC1544ICHC1544I Conversion from codepage origin to codepage destination using LEConversion Services has been successfully initialized.


Message Variables:








CHC1545ICHC1545I Conversion from codepage origin to codepage destination using CopyConversion has been successfully initialized.


Message Variables:







CHC1551ICHC1551I Conversion between codepages origin and destination using name has beensuccessfully initialized.

Explanation—Full-trip character conversions between the indicated code pages areavailable and conversion has been initialized successfully. The message text alsoindicates the conversion service that will be used to perform the conversions. Thismessage is generated when conversions from origin to destination and vice versahave been determined as being available.

Message Variables:

origin—One of the code pages in the character conversion.

destination—One of the code pages in the character conversion.


name—The conversion service name. One of the following strings is inserted in themessage text at this point:v Unicode Conversion Services, if Unicode Conversion Services is used to perform

the conversion.v LE Conversion Services, if Language Environment’s Code Page conversion

services is used to perform the conversion.v Copy conversion, if copy is used to perform the conversion.





CHC1552ICHC1552I Conversion between codepages origin and destination using LE ConversionServices has been successfully initialized.

Explanation—Full-trip character conversions between the indicated code pages areavailable and conversion has been initialized successfully. The message text alsoindicates the conversion service that will be used to perform the conversions.

Message Variables:







CHC1553ICHC1553I Conversion between codepages origin and destination using Copy Conversionhas been successfully initialized.

Explanation—Full-trip character conversions between the indicated code pages areavailable and conversion has been initialized successfully. The message text alsoindicates the conversion service that will be used to perform the conversions.

Message Variables:








CHC1559WCHC1559W Code page name name cannot be resolved to a CCSID.

Explanation—The specified code page name could not be converted to a CCSIDbecause a CCSIDMAP statement was not specified in the CHCUCSxx configurationmember for this code page name.

Message Variables:

name—The code page name.




Client Administrator Response—Further errors may occur if the product cannotdetermine the proper CCSID to use by other means.

CHC1560WCHC1560W IANA encoding name name cannot be resolved to a CCSID.

Explanation—The specified IANA code set name could not be converted to aCCSID because a IANAMAP statement was not specified in the CHCUCSxxconfiguration member for this IANA encoding name.

Message Variables:

name—The IANA encoding name.




Client Administrator Response—Further errors may occur if the product cannotdetermine the proper CCSID to use by other means.


“CHC1600I” on page 450“CHC1602E” on page 451“CHC1603E” on page 451“CHC1604E” on page 451


“CHC1605E” on page 452“CHC1606E” on page 452“CHC1607E” on page 453“CHC1608E” on page 453“CHC1609E” on page 454“CHC1610E” on page 454“CHC1611E” on page 454“CHC1612E” on page 455“CHC1613E” on page 455“CHC1614E” on page 456“CHC1615E” on page 456“CHC1616E” on page 457“CHC1617E” on page 457“CHC1618E” on page 458“CHC1619E” on page 458“CHC1620E” on page 459“CHC1621E” on page 459“CHC1622E” on page 460“CHC1623E” on page 460“CHC1624E” on page 460“CHC1625E” on page 461“CHC1626E” on page 461“CHC1627E” on page 462“CHC1628E” on page 462“CHC1629E” on page 463“CHC1630E” on page 463“CHC1631E” on page 464

CHC1600ICHC1600I The remote system reports the following message: text.

Explanation—The identified message generated on the remote server has beenadded to the product administration log on the local server.

Message Variables:

text—The text of the message generated on the remote server and placed in theproduct administration log on the local server.




Client Administrator Response—Based on the message that is sent by the remoteserver (text), you may need to take appropriate actions.


CHC1602ECHC1602E DMCMVFY Options: -m -p -M -P -n -s -t -d -D -v

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified incorrectly when the STRTSCVF console command wasissued. The valid control statement flags are listed in the message text. Forinformation about the STRTSCVF command, contact your IBM representative.



System Action—The communications test is not started.


Client Administrator Response—Modify the CHCCVFxx member so that thecontrol statements are specified correctly. The flags are case sensitive, and so makesure that the proper case has been used in the various control statements. Aftermaking the necessary changes, issue the STRTSCVF command again. Forinformation about the control statements that are supported by the STRTSCVFcommand, contact your IBM representative.

CHC1603ECHC1603E DMCMVFY Option "-m <local ip>" specifies the ip address of the localinterface we want to use or a name to resolve to it.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -m control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.





Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member and they are supported by theSTRTSCVF command. Issue the STRTSCVF command again after making thenecessary corrections. For information about the control statements that aresupported by the STRTSCVF command and how they can be used, contact yourIBM representative.

CHC1604ECHC1604E DMCMVFY Option "-M <remote ip>" is a required parameter which specifiesthe ip address of the target system or the target system name.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -M control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.






Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member. The -M flag is case sensitive, and somake sure that the proper case has been used. Issue the STRTSCVF commandagain after making the necessary corrections. For information about the controlstatements that are supported by the STRTSCVF command and how they can beused, contact your IBM representative.

CHC1605ECHC1605E DMCMVFY Option "-P <remote port>" is a required parameter which specifiesthe port on which the remote system is listening.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -P control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.





Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member. The -P flag is case sensitive, and somake sure that the proper case has been used. Issue the STRTSCVF commandagain after making the necessary corrections. For information about the controlstatements that are supported by the STRTSCVF command and how they can beused, contact your IBM representative.

CHC1606ECHC1606E DMCMVFY Option "-p <local port>" specifies the port which the localsystem will use.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -p control statement is described in the messagetext.For information about the STRTSCVF command, contact your IBMrepresentative.







CHC1607ECHC1607E DMCMVFY Option "-t <time limit>" specifies the length of time the programwill run.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -t control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.





Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member. The -t flag is case sensitive, and somake sure that the proper case has been used. Issue the STRTSCVF commandagain after making the necessary corrections. For information about the controlstatements that are supported by the STRTSCVF command and how they can beused, contact your IBM representative.

CHC1608ECHC1608E DMCMVFY Option "-s <packet size>" specifies the size of the data packetsto send.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -s control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.





Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member. The -s flag is case sensitive, and somake sure that the proper case has been used. Issue the STRTSCVF command


again after making the necessary corrections. For information about the controlstatements that are supported by the STRTSCVF command and how they can beused, contact your IBM representative.

CHC1609ECHC1609E Option "-d <send delay>" specifies the length of time to wait beforesending a message to the remote system.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -d control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.





Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member. The -d flag is case sensitive, and somake sure that the proper case has been used. Issue the STRTSCVF commandagain after making the necessary corrections. For information about the controlstatements that are supported by the STRTSCVF command and how they can beused, contact your IBM representative.

CHC1610ECHC1610E Option "-D <response delay>" specifies the length of time to wait beforesending a response from the remote system.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -D control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.






CHC1611ECHC1611E DMCMVFY Option "-v <verbosity level>" specifies whether to produce anyoutput. L(low), M(edium), H(igh).


Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -v control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.





Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member. The -v flag is case sensitive, and somake sure that the proper case has been used. Issue the STRTSCVF commandagain after making the necessary corrections. For information about the controlstatements that are supported by the STRTSCVF command and how they can beused, contact your IBM representative.

CHC1612ECHC1612E DMCMVFY Option "-n <number of packets>" specifies the number of packets togenerate.

Explanation—The control statements contained in the CHCCVFxx member (in theCHCCNTRL data set) that are used by the STRTSCVF console command producedan error. Proper usage of the -n control statement is described in the message text.For information about the STRTSCVF command, contact your IBM representative.





Client Administrator Response—Verify that the control statements have beenspecified correctly in the CHCCVFxx member and they are supported by theSTRTSCVF command. Issue the STRTSCVF command again after making thenecessary corrections.For information about the control statements that aresupported by the STRTSCVF command and how they can be used, contact yourIBM representative.

CHC1613ECHC1613E dmcmvfy invalid option -flag.

Explanation—The CHCCVFxx member (in the CHCCNTRL data set) contained acontrol statement with an invalid flag specification when the STRTSCVF consolecommand was issued. The identified flag was not recognized by InfoSphere CDC.

Message Variables:

flag—The control statement flag that was not recognized by InfoSphere CDC.



System Action—The Communications Verifier is not started.


Client Administrator Response—Remove the control statement containing theinvalid flag from the CHCCVFxx member. Issue the STRTSCVF command again.For information about the control statements that are supported by the STRTSCVFcommand, contact your IBM representative.

CHC1614ECHC1614E dmcmvfy: option name is required.

Explanation—The control statement in the CHCCVFxx member (in theCHCCNTRL data set) that identifies the remote server or port number was omittedwhen the STRTSCVF console command was issued. The -M and -P controlstatements are mandatory. For information about the STRTSCVF command, contactyour IBM representative.

Message Variables:

name—The name of the option.




Client Administrator Response—In the CHCCVFxx member, add the -M or -Pcontrol statement. Issue the STRTSCVF command again. The -M and -P flags arecase sensitive, and so make sure that the proper case has been used in each controlstatement. For information about the -M and -P control statements, contact yourIBM representative.

CHC1615ECHC1615E dmcmvfy: option first conflicts with specified option second.

Explanation—The specification of a control statement in the CHCCVFxx member(in the CHCCNTRL data set) conflicted with another control statement when theSTRTSCVF console command was issued. Specific combinations of controlstatements in the member are not permitted. For information about the STRTSCVFcommand, contact your IBM representative.

Message Variables:

first—Indicates the first of the conflicting options.

second—Indicates the second of the conflicting options.





Client Administrator Response—In the CHCCVFxx member, remove theconflicting control statements or remove the control statements that are notsupported by the STRTSCVF command. Issue the STRTSCVF command again aftermaking the necessary corrections. For information about control statements for theSTRTSCVF command, contact your IBM representative.

CHC1616ECHC1616E dmcmvfy: option name argument setting exceeds maximum length of size.

Explanation—A setting for a control statement in the CHCCVFxx member (in theCHCCNTRL data set) exceeded the maximum length when the STRTSCVF consolecommand was issued. The setting and maximum length are identified in themessage text. For information about the STRTSCVF command, contact your IBMrepresentative.

Message Variables:


setting—The setting specified in a control statement that is too long.

size—The maximum length of the setting.




Client Administrator Response—In the CHCCVFxx member, modify the controlstatement so that the length of the setting is less than or equal to the identifiedmaximum length. Issue the STRTSCVF command again after making the necessarycorrections. For information about control statements for the STRTSCVF command,contact your IBM representative.

CHC1617ECHC1617E dmcmvfy: option name argument setting is not within minimum to maximum.

Explanation—A setting for a control statement in the CHCCVFxx member (in theCHCCNTRL data set) was not within the acceptable range of values when theSTRTSCVF console command was issued. The setting along with the minimumand maximum values are identified in the message text. For information about theSTRTSCVF command, contact your IBM representative.

Message Variables:


setting—The setting specified in a control statement that is not within theacceptable range of values.

minimum—The minimum value that can be assigned to the control statement.


maximum—The maximum value that can be assigned to the control statement.




Client Administrator Response—In the CHCCVFxx member, modify the controlstatement so that its value is within the acceptable range of values. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout the range of values for specific control statements, contact your IBMrepresentative.

CHC1618ECHC1618E dmcmvfy: option name was specified twice.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified twice when the STRTSCVF console command was issued.In each member, each control statement can only be specified once. For informationabout the STRTSCVF command, contact your IBM representative.

Message Variables:

name—The duplicate setting specified in a control statement.




Client Administrator Response—In the CHCCVFxx member, remove one of thetwo control statements. Issue the STRTSCVF command again after making thenecessary corrections. For information about control statements for the STRTSCVFcommand, contact your IBM representative.

CHC1619ECHC1619E dmcmvfy: option name requires an argument.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified without a setting when the STRTSCVF console commandwas issued. For information about the STRTSCVF command, contact your IBMrepresentative.

Message Variables:

name—The control statement setting that is missing a required argument.





Client Administrator Response—In the CHCCVFxx member, specify a validsetting for the control statement. Issue the STRTSCVF command again aftermaking the necessary corrections. For information about valid settings for controlstatements, contact your IBM representative.

CHC1620ECHC1620E dmcmvfy: setting is an invalid argument for option name.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid setting when the STRTSCVF consolecommand was issued. For information about the STRTSCVF command, contactyour IBM representative.

Message Variables:

setting—The invalid setting specified for the control statement.





Client Administrator Response—In the CHCCVFxx member, specify a validsetting for the control statement. Issue the STRTSCVF command again aftermaking the necessary corrections. For information about valid settings for controlstatements, contact your IBM representative.

CHC1621ECHC1621E dmcmvfy: date is an invalid date length.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid date when the STRTSCVF consolecommand was issued. The reported issue is that the length of the date specificationis incorrect. For information about the STRTSCVF command, contact your IBMrepresentative.

Message Variables:

date—The date setting that has an incorrect length




Client Administrator Response—A control statement where a date has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.


CHC1622ECHC1622E dmcmvfy: date does not follow the required date format.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid date format when the STRTSCVF consolecommand was issued. The reported issue is that dates must be specified instandard ISO format. For information about the STRTSCVF command, contact yourIBM representative.

Message Variables:

date—The date setting that has an incorrect format.




Client Administrator Response—A control statement where a date has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1623ECHC1623E dmcmvfy: date does not contain a valid month.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid month when the STRTSCVF consolecommand was issued. The reported issue is that dates must be specified instandard ISO format. For information about the STRTSCVF command, contact yourIBM representative.

Message Variables:

date—The date setting that contains an incorrect month specification.




Client Administrator Response—A control statement where a month has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1624ECHC1624E dmcmvfy: date does not contain a valid year.


Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid year when the STRTSCVF consolecommand was issued. The reported issue is that dates must be specified instandard ISO format. For information about the STRTSCVF command, contact yourIBM representative.

Message Variables:

date—The date setting that contains an incorrect year specification.




Client Administrator Response—A control statement where a year has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1625ECHC1625E dmcmvfy: date does not contain a valid day.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid day when the STRTSCVF console commandwas issued. The reported issue is that dates must be specified in standard ISOformat. For information about the STRTSCVF command, contact your IBMrepresentative.

Message Variables:

date—The date setting that contains an incorrect day specification.




Client Administrator Response—A control statement where a day has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1626ECHC1626E dmcmvfy: time is an invalid time length.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid time when the STRTSCVF console


command was issued. The reported issue is that the length of the time specificationis incorrect. For information about the STRTSCVF command, contact your IBMrepresentative.

Message Variables:

time—The time setting that has an incorrect length.




Client Administrator Response—A control statement where a time has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1627ECHC1627E dmcmvfy: time does not follow the required time format.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid time format when the STRTSCVF consolecommand was issued. The reported issue is that times must be specified instandard ISO format. For information about the STRTSCVF command, contact yourIBM representative.

Message Variables:

time—The time setting that has an incorrect format.




Client Administrator Response—A control statement where a time has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1628ECHC1628E dmcmvfy: time does not contain a valid hour.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with an invalid hour when the STRTSCVF consolecommand was issued. The reported issue is that times must be specified instandard ISO format. For information about the STRTSCVF command, contact yourIBM representative.


Message Variables:

time—The time setting that contains an incorrect hour specification.




Client Administrator Response—A control statement where an hour has to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1629ECHC1629E dmcmvfy: time does not contain valid minutes.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with invalid minutes when the STRTSCVF consolecommand was issued. The reported issue is that times must be specified instandard ISO format. For information about the STRTSCVF command, contact yourIBM representative.

Message Variables:

time—The time setting that contains an incorrect minutes specification.




Client Administrator Response—A control statement where minutes have to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again are making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1630ECHC1630E dmcmvfy: time does not contain valid seconds.

Explanation—A control statement in the CHCCVFxx member (in the CHCCNTRLdata set) was specified with invalid seconds when the STRTSCVF consolecommand was issued. The reported issue is that times must be specified instandard ISO format. For information about the STRTSCVF command, contact yourIBM representative.

Message Variables:

time—The time setting that contains an incorrect seconds specification.





Client Administrator Response—A control statement where seconds have to bespecified is not supported by the STRTSCVF command. In the CHCCVFxxmember, specify valid settings for all supported control statements. Issue theSTRTSCVF command again after making the necessary corrections. For informationabout valid settings for supported control statements, contact your IBMrepresentative.

CHC1631ECHC1631E An error was encountered while performing low level time conversion. Thecalendar time cannot be represented. The error was detected in file name at lineline.

Explanation—A date or time could not be converted into a time format recognizedon the local server.

Message Variables:

name—The file that cause the error to be generated.

line—The line in the file that resulted in the error being generated.






“CHC1800E”

CHC1800ECHC1800E EPDS API "type" request failed. Return code is code for a value of error.

Explanation—A call to the EPDS API, which is used to collect and report statisticsabout InfoSphere CDC operations, failed.

Message Variables:

type—The EPDS API request type.

code—The name of the return code.

error—The numeric error code.



System Action—The system action in response to this error depends on the type ofrequest that failed.v epdsInit—InfoSphere CDC fails to initialize.v epdsAllocate—Communications or replication activity fails to start.v epdsFind, epdsScan—Some or all of the data in the generated report is missing.v epdsRelease—Communications or replication activity will eventually terminate.v epdsTerminate—InfoSphere CDC will eventually terminate.




“CHC1902E”“CHC1904E” on page 466“CHC1905E” on page 466“CHC1906E” on page 467“CHC1907E” on page 467“CHC1908E” on page 467“CHC1909E” on page 468“CHC1910E” on page 468“CHC1914E” on page 469“CHC1915E” on page 469“CHC1921E” on page 469“CHC1922E” on page 470“CHC1923E” on page 470“CHC1924E” on page 471

CHC1902ECHC1902E Unable to allocate an ECB block for message queue name.

Explanation—An attempt to allocate a new block of ECBs was unsuccessful whenwriting to the identified communications queue.

Message Variables:

name—The name of the communications queue.


System Action—Communications or replication activity that relies on theidentified communications queue terminates abnormally.

Operator Response—Restart InfoSphere CDC with a larger address space.


Client Administrator Response—If the Operator Response does not resolve theerror, further investigation is required. Record the message number and text, andthen contact your InfoSphere CDC administrator or IBM representative forassistance.

CHC1904ECHC1904E A list operation for message queue name has failed. Operation:operation, reason: reason.

Explanation—An attempt to add a communications queue to the queue list,remove a communications queue from the list, or find a communications queue onthe list was unsuccessful. The reason behind the unsuccessful attempt is providedin the message text.

Message Variables:


operation—The name of the operation that failed.

reason—The reason for the operation failure.


System Action—The operation that attempted to modify the queue list ends.Communications and/or replication activity that relies on the queue eventuallyterminates.



CHC1905ECHC1905E An operation for message queue name has failed. Operation code: code,reason code: reason.

Explanation—An attempt to perform the specified operation on a communicationsqueue was unsuccessful. The reason behind the unsuccessful operation is providedin the message text.

Message Variables:


code—The operation code for the failed operation.

reason—The reason code for the failed operation.






CHC1906ECHC1906E A queue writer attempted to register its write ECB multiple times withcommunications queue name.

Explanation—A product component attempted to wait twice on the samecommunications queue.

Message Variables:



System Action—The product component trying to perform a double wait on thequeue ends. Communications and/or replication activity that relies on that productcomponent eventually terminates.



CHC1907ECHC1907E A latch operation for message queue name has failed. Operation:obtain.

Explanation—An attempt to obtain the latch (locking mechanism) for acommunications queue was unsuccessful.

Message Variables:






CHC1908ECHC1908E A latch operation for message queue name has failed. Operation:release.


Explanation—An attempt to release the latch (locking mechanism) for acommunications queue was unsuccessful.

Message Variables:






CHC1909ECHC1909E Failed to obtain communications queue list latch.







CHC1910ECHC1910E Failed to release communications queue list latch.








CHC1914ECHC1914E Failed post of an ECB for message queue queue. ECB type: reader,error code: code.

Explanation—An attempt to post the ECB for a user of the identifiedcommunications queue was unsuccessful.

Message Variables:


code—The numeric error code.





CHC1915ECHC1915E Failed post of an ECB for message queue name. ECB type: writer, errorcode: code

Explanation—An attempt to post the ECB for a user of the identifiedcommunications queue was unsuccessful.

Message Variables:


code—The numeric error code.





CHC1921ECHC1921E A resource operation for message queue name has failed. Operation:increment reference count. Additional information: reader ECB.

Explanation—An attempt to increment the reference count of a communicationsqueue during queue creation was unsuccessful.


Message Variables:



System Action—If the operation was to create the communications queue,communications and/or replication activity that relies on the queue does not start.If the operation was to delete the communications queue, communications and/orreplication activity that relies on the queue eventually terminates.



CHC1922ECHC1922E A resource operation for message queue name has failed. Operation:increment reference count. Additional information: writer ECB.

Explanation—An attempt to increment the reference count of a communicationsqueue during queue creation was unsuccessful.

Message Variables:






CHC1923ECHC1923E A resource operation for message queue name has failed. Operation:decrement reference count. Additional information: reader ECB.

Explanation—An attempt to decrement the reference count of a communicationsqueue during queue deletion was unsuccessful.

Message Variables:







CHC1924ECHC1924E A resource operation for message queue name has failed. Operation:decrement reference count. Additional information: writer ECB.

Explanation—An attempt to decrement the reference count of a communicationsqueue during queue deletion was unsuccessful.

Message Variables:







“CHC2000E”“CHC2001I” on page 472“CHC2002I” on page 472“CHC2007I” on page 473

CHC2000ECHC2000E The keyword keyword1 on command name is mutually exclusive with keywordkeyword2.

Explanation—A command was entered with two valid but mutually exclusivekeywords.

Message Variables:

keyword1—A keyword name.


name—A command name.

keyword2—A keyword name.


System Action—The command is not executed.

Operator Response—Consult the product documentation for the correct commandsyntax.


CHC2001ICHC2001I The value in keyword key for command name is invalid; the default willbe used.

Explanation—The DB2 statement in the PDS (partitioned data set) membercontaining DBMS configuration control statements has an incorrect keyword value.The default value for the specified keyword will be used.

Message Variables:

key—The keyword in the DB2 statement that has been assigned an incorrect value.

name—The statement in the PDS member that contains the incorrect keywordspecification.


System Action—The statement is processed with the default value for thekeyword.

Operator Response—If the default value is not acceptable, close InfoSphere CDCand edit the PDS member to specify the desired keyword value. Start InfoSphereCDC after editing the member.


CHC2002ICHC2002I Task name is not yet attached. Request has been rejected.

Explanation—An internal InfoSphere CDC task is not currently running. Thismessage is usually generated when a command issued from the operator consolerequests services from a task that is not active. The internal InfoSphere CDC taskthat is not currently running is identified in the message text.

Message Variables:

name—The three letter code that identifies the destination task that is not running.


System Action—Command issued from the operator console is not performed.


Operator Response—It is possible that this message is generated during taskinitialization. In this case, issue the command again to see if the internalInfoSphere CDC task is now running. If the same message is generated, note themessage number and issue the DSPACT=ALL command to obtain informationabout current InfoSphere CDC activity. Contact your InfoSphere CDCadministrator with the information you have collected if you require furtherassistance.


CHC2007ICHC2007I The value of setting is current.

Explanation—The named InfoSphere CDC for z/OS configuration controlstatement keyword has been set to the specified value.

Message Variables:

setting—The name of a configuration setting.

current—The value currently assigned to the named configuration setting.






“CHC3001E” on page 474“CHC3002E” on page 474“CHC3004I” on page 475“CHC3005I” on page 475“CHC3007E” on page 475“CHC3008W” on page 476“CHC3009I” on page 476“CHC3010W” on page 477“CHC3011E” on page 477“CHC3012I” on page 478“CHC3013I” on page 478“CHC3014I” on page 478“CHC3015I” on page 479“CHC3016I” on page 479“CHC3101E” on page 479“CHC3102E” on page 480“CHC3103E” on page 481“CHC3104E” on page 481


“CHC3105E” on page 482“CHC3106E” on page 482“CHC3107E” on page 483“CHC3138W” on page 483“CHC3139W” on page 484“CHC3140E” on page 484“CHC3142W” on page 485“CHC3157W” on page 485“CHC3174E” on page 486“CHC3175E” on page 486“CHC3176E” on page 487“CHC3177E” on page 487“CHC3178E” on page 488“CHC3179E” on page 488“CHC3180E” on page 489“CHC3181E” on page 490“CHC3182E” on page 490“CHC3183E” on page 491“CHC3184E” on page 491“CHC3185E” on page 492“CHC3186E” on page 492

CHC3001ECHC3001E Unable to retrieve DB2 Head of Log; the selected function is unavailable.

Explanation—An attempt to determine the highest log position (RBA/LRSN) usinga DB2 IFI request was unsuccessful. The message (CHC9210E) generated beforethis one indicates the return and reason codes produced by the unsuccessful DB2IFI request.



System Action—Active mirroring may slow or stop.


Client Administrator Response—Note the DB2 return and reason codes. Consultthe appropriate DB2 messages and codes manual to determine the correctiveactions that should be taken.Related reference


CHC3002ECHC3002E An unsupported version of DB2 has been detected; the DLP task is shuttingdown.


Explanation—InfoSphere CDC has detected an unsupported version of DB2 forz/OS during environment initialization. As a result, the InfoSphere CDC DLP taskwill end.



System Action—InfoSphere CDC initialization ends. Initialization is not completed.

Operator Response—Minimum database requirements for InfoSphere CDC mustbe met. To use InfoSphere CDC, you must first upgrade DB2 for z/OS to asupported version in your environment.


CHC3004ICHC3004I The DLP Task initialization was successful.

Explanation—The InfoSphere CDC DLP task has completed its initialization.






CHC3005ICHC3005I A COLD start has been requested.

Explanation—The InfoSphere CDC DLP or DLR (or both) tasks will perform coldstarts depending on what was specified on the STRTSDBM command. If the DLPTask is cold started, it discards the information collected in the Log Profile and willbuild the Log Profile anew. If the DLR Task is cold started, it will reset the controlinformation describing the Log Data Cache and will build the Log Data Cacheanew.



System Action—The Log Profile, the Log Data Cache or both are discarded andrebuilt anew.



CHC3007ECHC3007E An error occurred processing a type Log Record. The DLP task is endingabnormally.


Explanation—An internal error occurred during the processing of a UR log record(BEGINUR, COMMIT, or DATA). As a result, the InfoSphere CDC DLP task hasstopped unexpectedly.

Message Variables:

type—The type of the DB2 UR log record that could not be processed.


System Action—All dependent DB2 tasks and InfoSphere CDC replication tasksend.

Operator Response—Obtain dumps that may have been generated, and restart theInfoSphere CDC address space by using the START command.

Client Administrator Response—Use Management Console to restart replicationactivities that were interrupted as a result of this error.

CHC3008WCHC3008W Tablespace Drain position was encountered before subscription namefinished processing the previous drain.

Explanation—InfoSphere CDC has read a DB2 Log record identifying table spacedrain activity. This record was encountered before completion of the previous tablespace drain.

Message Variables:

position—The RBA (relative byte address) or LRSN (log record sequence number)of the DB2 Log record identifying table space drain activity.

name—The name of the subscription associated with the previous table space drain.




Client Administrator Response—No immediate corrective actions are required.However, at a convenient time, you should end mirroring to the namedsubscription, refresh source tables selected to the subscription, and restartmirroring in order to prevent the possibility of data corruption.

CHC3009ICHC3009I Tablespace drain at position was processed.

Explanation—The table space drain identified by a DB2 Log record has beencompleted.

Message Variables:

position—The RBA (relative byte address) or LRSN (log record sequence number)of the DB2 Log record identifying the table space drain that has been completed.






CHC3010WCHC3010W A deadlock or timeout was encountered on table table while processing aTablespace Drain. Retrying to access the table.

Explanation—The named system table could not be accessed during a table spacedrain due to deadlock or timeout. Access to this table was required by InfoSphereCDC during the table space drain.

Message Variables:

table—The name of the system table that could not be accessed due to deadlockor timeout.


System Action—InfoSphere CDC will make subsequent attempts to access thesystem table. After 10 unsuccessful attempts, CHC3011E is placed in the productadministration log.



“CHC3011E”

CHC3011ECHC3011E The retry limit was exceeded while processing a Tablespace Drain. Tablename is unavailable due to a deadlock or timeout.

Explanation—Ten unsuccessful attempts have been made to access the namedsystem table during a table space drain. In each attempt, a deadlock or timeoutprevented InfoSphere CDC from accessing the table.

Message Variables:

name—The name of the system table that could not be accessed after ten attemptsdue to deadlock or timeout.


System Action—An abnormal shutdown of InfoSphere CDC is initiated. Allreplication activities in the InfoSphere CDC address space are ended.


Client Administrator Response—Contact your database administrator todetermine the possible causes of the deadlock or timeout on the system table. After


corrective actions have been taken, restart the InfoSphere CDC address space,perform a refresh to synchronize source and target tables, and restart mirroring.

CHC3012ICHC3012I The DB2 SSID has been altered since the previous execution; the DLP isreinitializing.

Explanation—InfoSphere CDC has detected a new DB2 subsystem identifier sinceits previous invocation. As a result, the InfoSphere CDC task called DLP willperform a cold start.



System Action—InfoSphere CDC redefines its DB2 settings.



CHC3013ICHC3013I The DB2 Release Identifier has been altered since the previous execution;the DLP is reinitializing.

Explanation—InfoSphere CDC has detected a new DB2 release identifier since itsprevious invocation. As a result, the InfoSphere CDC task called DLP will performa cold start.






CHC3014ICHC3014I The DB2 Data Sharing mode has been altered since the previous execution;the DLP is reinitializing.

Explanation—InfoSphere CDC has detected an alteration to the DB2 Data Sharingmode since its previous invocation. As a result, the InfoSphere CDC task calledDLP will perform a cold start.







CHC3015ICHC3015I The DB2 Data Sharing group has been altered since the previous execution;the DLP is reinitializing.

Explanation—InfoSphere CDC has detected an alteration to the DB2 Data SharingGroup name since its previous invocation. As a result, the InfoSphere CDC taskcalled DLP will perform a cold start.






CHC3016ICHC3016I The DB2 Profile Version Number has been altered since the previousexecution; the DLP is reinitializing.

Explanation—InfoSphere CDC has detected an alteration to the DB2 ProfileVersion Number since its previous invocation. As a result, the InfoSphere CDC taskcalled DLP will perform a cold start.






CHC3101ECHC3101E A numerical data overflow error was encountered while formatting columnname in table owner.table. The row is identified by key col1 = txt1, col2 =txt2,..., coln =txtn. The bookmark for the entry is bmk. The row has not been modified.

Explanation—InfoSphere CDC has encountered a numeric overflow conditionduring summarization.

Message Variables:

name—The name of the target column that InfoSphere CDC was formatting whenthe error occurred.





txt1, ..., txtn—The corresponding values of the key columns in the target tablerow that InfoSphere CDC was applying when the error occurred.

bmk—The value of the bookmark on the source corresponding to the target rowthat InfoSphere CDC was applying when the error occurred.


System Action—Processing ends or continues, depending on the ENDONERRORkeyword setting.


Client Administrator Response—If possible, use a different data type for thetarget column, so that you can accommodate large, positive numeric values.

CHC3102ECHC3102E A numerical data underflow error was encountered while formatting columnname in table owner.table. The row is identified by key col1 = txt1, col2 =txt2,..., coln =txtn. The bookmark for the entry is bmk. The row has not been modified.

Explanation—InfoSphere CDC has encountered a numeric underflow conditionduring summarization.

Message Variables:





txt1, ..., txtn—The corresponding values of the key columns in the target rowthat InfoSphere CDC was applying when the error occurred.





Client Administrator Response—If possible, use a different data type for thetarget column, so that you can accommodate large, positive numeric values.


CHC3103ECHC3103E An invalid arithmetic operation was encountered while formattingcolumn name in table owner.table.

Explanation—InfoSphere CDC has encountered an invalid operation duringsummarization. Only addition and subtraction operations are allowed duringsummarization.

Message Variables:








CHC3104ECHC3104E An invalid data type was encountered while formatting column name intable owner.table.

Explanation—InfoSphere CDC has encountered an invalid or unsupported datatype during summarization.

Message Variables:









CHC3105ECHC3105E An invalid number length was encountered while formatting column name intable owner.table.

Explanation—InfoSphere CDC has encountered an invalid length for a numericcolumn during summarization.

Message Variables:








CHC3106ECHC3106E Invalid numeric data was encountered while formatting column name in tableowner.table. The row is identified by key col1 = txt1, col2 =txt2, ..., coln =txtn.The bookmark for the entry is bmk. The row has not been modified.

Explanation—InfoSphere CDC has encountered invalid numeric data duringsummarization.

Message Variables:





txt1, ..., txtn—The corresponding values of the key columns in the target tablerow that InfoSphere CDC was applying when the error occurred.







CHC3107ECHC3107E An internal arithmetic error was encountered while formatting column namein table owner.table.

Explanation—During summarization, InfoSphere CDC has encountered an internalerror in the math library.

Message Variables:








CHC3138WCHC3138W Only one row was updated for table owner.table. The duplicate rows areidentified by key col1 = txt1, col2 =txt2, ..., coln =txtn. The bookmark forthe entry is bmk.

Explanation—During consolidation one-to-one processing, InfoSphere CDC hasencountered a second row for the specified consolidation key.

Message Variables:



col1, ..., coln—The names of the consolidation key columns in the target table.

txt1, ..., txtn—The corresponding values of the consolidation key columns forthe target row that InfoSphere CDC was applying (the second row) when theproblem occurred.

bmk—The value of the bookmark on the source corresponding to the target rowthat InfoSphere CDC was applying (the second row) when the problem occurred.





Client Administrator Response—Make sure that the consolidation key is correct. Ifit is, you must manually merge the duplicate row with the primary row.

CHC3139WCHC3139W A record was not found for delete in table owner.table. The row isidentified by key col1 = txt1, col2 =txt2, ..., coln =txtn. The bookmark forthe entry is bmk.

Explanation—During adaptive apply processing, InfoSphere CDC has attempted todelete a row that could not be found.

Message Variables:




txt1, ..., txtn—The corresponding values of the key columns in the target tablefor the row that InfoSphere CDC was deleting when the problem occurred.

bmk—The value of the bookmark on the source corresponding to the target rowthat InfoSphere CDC was deleting when the problem occurred.





CHC3140ECHC3140E A Refresh While Active entry was received and not applied for tableowner.table. The bookmark for the entry is bmk.

Explanation—While summarizing data, InfoSphere CDC has encountered a sourceentry with the Refresh While Active flag set to ON. Refresh while active entriescorrespond to insert, update, or delete operations that occur during a refresh.During summarization, these entries are not allowed because they maycompromise data consistency.

Message Variables:



bmk—The source bookmark value of the row that InfoSphere CDC was applyingwhen the error occurred.





Client Administrator Response—Ensure that any refresh operations that occur onthe source do not allow changes to the source table during the refresh.

CHC3142WCHC3142W A source row Update operation has been switched into a target. Insertoperation for table owner.table. The row is identified by key col1 = txt1,col2 =txt2, ..., coln =txtn. The bookmark for the entry is bmk.

Explanation—While applying data under adaptive apply, InfoSphere CDC hasconverted a source update operation into a target insert operation because thecorresponding row could not be found in the target table.

Message Variables:




txt1, ..., txtn—The corresponding values of the key columns in the target tablefor the row that InfoSphere CDC was applying when the problem occurred.

bmk—The source bookmark value of the row that InfoSphere CDC was applyingwhen the problem occurred.





CHC3157WCHC3157W A source row Insert operation has been switched into a target Updateoperation for table owner.table. The row is identified by key col1 = txt1,col2 =txt2, ..., coln =txtn. The bookmark for the entry is bmk.

Explanation—While applying data under adaptive apply, InfoSphere CDC hasconverted a source insert into a target update because the target row alreadyexisted.

Message Variables:





txt1, ..., txtn—The corresponding values of the key columns in the target tablefor the row that InfoSphere CDC was applying when the problem occurred.

bmk—The source bookmark value of the row that InfoSphere CDC was applyingwhen the problem occurred.





CHC3174ECHC3174E A conflict was detected while inserting a row into table. A row with thekey key already exists. The bookmark for the entry is bmk from source source.

Explanation—InfoSphere CDC detected a conflict while processing an insertoperation. A row with the specified key already exists.

Message Variables:


key—The value of the key.




System Action—The row will not be inserted. Processing will continue or end,based on the end on error setting.


Client Administrator Response—Depending on whether this is considered anerror or not, investigate why a row with the specified key already exists on thetarget system.

CHC3175ECHC3175E A conflict was detected while updating a row in table. A row with thekey key does not exist. The bookmark for the entry is bmk from source source.

Explanation—InfoSphere CDC detected a conflict while processing an updateoperation. A row with the specified key does not exist in the target table.

Message Variables:







System Action—No row will be updated. Processing will continue or end, basedon the end on error setting.


Client Administrator Response—Depending on whether this is considered anerror or not, investigate why a row with the specified key does not exist on thetarget system.

CHC3176ECHC3176E A conflict was detected while deleting a row from table. A row with thekey key does not exist. The bookmark for the entry is bmk from source source.

Explanation—InfoSphere CDC detected a conflict while processing a deleteoperation. A row with the specified key does not exist in the target table.

Message Variables:






System Action—No row will be deleted. Processing will continue or end, based onthe end on error setting.


Client Administrator Response—Depending on whether this is considered anerror or not, investigate why a row with the specified key does not exist on thetarget system.

CHC3177ECHC3177E A conflict was detected while updating a row from table. The rowwith the key key does not match the before image of the row with the samekey on the source table. A conflict was detected in column name but otherconflicts may exist. The bookmark for the entry is bmk from source source.

Explanation—InfoSphere CDC detected a conflict while processing an updateoperation. A row with the specified key key exists in the target table, but thesource before image does not match the current target image. A mismatch wasdetected in the named column, but other columns might also mismatch.

Message Variables:




name—The name of the column in which a conflict was detected.




System Action—The row will not be updated. Processing will continue or end,based on the end on error setting.


Client Administrator Response—Depending on whether this is considered anerror or not, investigate why the row with the specified key does not match.

CHC3178ECHC3178E A conflict was detected while deleting a row from table. The row withthe key key does not match the before image of the row with the same key on thesource table. A conflict was detected in column name but other conflicts mayexist. The bookmark for the entry is bmk from source source.

Explanation—InfoSphere CDC detected a conflict while processing a deleteoperation. A row with the specified key key does not exist in the target table

Message Variables:



name—The name of the column in which a conflict was detected.




System Action—The row will not be deleted. Processing will continue or end,based on the end on error setting.


Client Administrator Response—Depending on whether this is considered anerror or not, investigate why the row with the specified key does not match.

CHC3179ECHC3179E A constraint violation was detected while inserting a row into table.The row with the key key exists but cannot be retrieved. The bookmark for the entryis bmk from source source.


Explanation—InfoSphere CDC detected a conflict while processing an insertoperation. The row with the specified key could not be inserted into the targettable due to a constraint violation.

Message Variables:






System Action—The row will not be inserted. Processing will continue or end,based on the end on error setting.


Client Administrator Response—This is most likely due to a duplicate key erroron an index other than the one used for mirroring.

CHC3180ECHC3180E An error occurred while applying a resolved row to the target table.InfoSphere Change Data Capture could not resolve this conflict in tab. See theConflict Resolution Audit Table to see the attempted change. The bookmark forthe entry is bmk from source system source.

Explanation—InfoSphere CDC detected a conflict while processing an insertoperation. The row with the specified key could not be inserted into the targettable due to a constraint violation.

Message Variables:





System Action—The conflict will not be resolved. An audit record will be writtento the audit table. Depending on the severity of the error and the end on errorsetting, replication might continue or end.


Client Administrator Response—This message will be accompanied by othermessages detailing the error that occurred during conflict resolution. Refer to thedescription of these messages for more detail.


CHC3181ECHC3181E An error occurred with a Conflict resolution user. The conflict couldnot be resolved by calling user exit name.

Explanation—InfoSphere CDC encountered an error while calling the conflictresolution user exit..

Message Variables:

name—The name of the user exit program.


System Action—The conflict will be not be resolved. An audit record will not bewritten to the audit table.


Client Administrator Response—This message will be accompanied by othermessages detailing the error that occurred during conflict resolution. Refer to thedescription of these messages for more detail.

CHC3182ECHC3182E A conflict was resolved, but an error occurred updating the ConflictResolution Audit Table. The conflict was detected while performing the operationoperation. The bookmark for the entry is bmk from source system source The targettable is table.

Explanation—InfoSphere CDC encountered a conflict and resolved it, but an erroroccurred while it was trying to create the audit entry.

Message Variables:

operation—The operation performed: INSERT, UPDATE or DELETE.





System Action—The conflict will be resolved. An audit record will not be writtento the audit table.


Client Administrator Response—This message will be accompanied by othermessages detailing the error that occurred. Refer to the description of thesemessages for more detail.


CHC3183ECHC3183E A conflict was not resolved and an error occurred updating the ConflictResolution Audit Table. The conflict was detected while performing the operationoperation. The bookmark for the entry is bmk from source system source. The targettable is table.

Explanation—InfoSphere CDC encountered a conflict and did not resolve it and anerror occurred while it was trying to create the audit entry.

Message Variables:

operation—The operation performed: INSERT, UPDATE or DELETE.





System Action—The conflict will be not be resolved. An audit record will not bewritten to the audit table.


Client Administrator Response—This message will be accompanied by othermessages detailing the error that occurred. Refer to the description of thesemessages for more detail.

CHC3184ECHC3184E An internal error occurred while performing conflict detection orresolution. Function name line line.

Explanation—InfoSphere CDC encountered an internal error while detecting orresolving a conflict.

Message Variables:

name—The name of the function in which the error occurred.

line—The line at which the error occurred.


System Action—The conflict will be not be resolved. An audit record will bewritten to the audit table.




CHC3185ECHC3185E An error occurred in cdrFormatField on line line while formatting columnname.

Explanation—InfoSphere CDC encountered an unexpected error while detecting orresolving a conflict.

Message Variables:


name—The name of the column which could not be formatted.


System Action—The conflict will be not be resolved. An audit record will not bewritten to the audit table. Replication will end.



CHC3186ECHC3185E An error occurred in cdrParseField on line line while formatting columnname.

Explanation—InfoSphere CDC encountered an unexpected error while detecting orresolving a conflict.

Message Variables:


name—The name of the column which could not be formatted.


System Action—The conflict will be not be resolved. An audit record will not bewritten to the audit table. Replication will end.




“CHC5002I” on page 493“CHC5003I” on page 493“CHC5099I” on page 494“CHC5101I” on page 494“CHC5102E” on page 494


“CHC5103E” on page 495“CHC5108E” on page 495“CHC5109E” on page 496“CHC5110E” on page 496“CHC5111E” on page 496“CHC5112E” on page 497“CHC5118I” on page 497“CHC5119I” on page 498“CHC5120I” on page 498“CHC5121I” on page 498“CHC5127E” on page 499“CHC5128E” on page 499“CHC5129E” on page 500“CHC5135E” on page 500“CHC5136E” on page 500“CHC5137E” on page 501“CHC5143I” on page 501“CHC5144I” on page 501

CHC5002ICHC5002I A DB2 Trace has been started in buffer name.

Explanation—A DB2 trace has been started as a result of an issued command.

Message Variables:

name—The OPn buffer that the instance of InfoSphere CDC uses for tracing.


System Action—The DB2 trace is started by the server.

Operator Response—Record the message in case an InfoSphere CDC failure at alater time does not automatically stop the trace. In this case, stop the tracemanually to release the buffer.


CHC5003ICHC5003I A DB2 Trace has been stopped in buffer name.

Explanation—A DB2 trace has been stopped as a result of an issued command.

Message Variables:

name—The OPn buffer that the instance of InfoSphere CDC uses for tracing.


System Action—The DB2 trace is stopped by the server.


Operator Response—Record the message in case an InfoSphere CDC failure at alater time does not automatically stop the trace. In this case, stop the tracemanually to release the buffer.


CHC5099ICHC5099I name Task was initialized successfully.

Explanation—This message is generated when the specified InfoSphere CDC taskhas completed initialization.

Message Variables:

name—The name of the InfoSphere CDC task.





CHC5101ICHC5101I name Task is terminating.

Explanation—The specified InfoSphere CDC task is terminating normally.

Message Variables:

name—The name of the InfoSphere CDC task that is terminating normally.





CHC5102ECHC5102E name Task is terminating abnormally.

Explanation—The named InfoSphere CDC task is terminating abnormally.

Message Variables:

name—The name of the InfoSphere CDC task that is terminating abnormally.


System Action—Dependent on the task that is terminating abnormally.




CHC5103ECHC5103E The deadband percentage value number is not in the range of 1 to 100

Explanation—The DEADBANDPERCENT keyword in the CONFIG statement hasan invalid value.

Message Variables:

number—The invalid value of the DEADBANDPERCENT keyword.


System Action—Monitoring latency for subscriptions will not be possible.


Client Administrator Response—Change the DEADBANDPERCENT keyword to avalid value and restart the InfoSphere CDC address space.

CHC5108ECHC5108E Unable to submit control operation number for replication name.

Explanation—The Monitor Agent was unable to submit a request to start or endrefresh or mirroring for the subscription identified in the message (by its name orthe corresponding source ID).

Message Variables:

number—The numeric option for the control operation:v 1 = *ALLv 2 = Flaggedv 3 = Continuousv 4 = Net Changev 5 = Controlledv 6 = Immediate



System Action—Replication does not start or end as requested.




CHC5109ECHC5109E A communications error has occurred while sending message number.The return code was code.

Explanation—The Monitor Agent was unable to send a message to IntegrationServer due to a communications error.

Message Variables:

number—The message number that could not be sent.

code—The numeric return code from the communications API.


System Action—The Management Console instances connected to the IntegrationServer to which the message could not be sent will not receive the message. Thebehavior of all Management Console instances connected to this Integration Serverwill become unpredictable.



CHC5110ECHC5110E name task initialization was successful.

Explanation—This message is generated when the specified InfoSphere CDC taskhas completed initialization.

Message Variables:

name—The task name.





CHC5111ECHC5111E name task initialization was aborted.

Explanation—This message is generated when the specified InfoSphere CDC taskhas been aborted.

Message Variables:




System Action—Depends on the task name specified in the message.



CHC5112ECHC5112E name task initialization has failed

Explanation—This message is generated when the specified InfoSphere CDC taskhas failed.

Message Variables:



System Action—Depends on the task name specified in the message.



CHC5118ICHC5118I Latency for journal name has crossed above the warning threshold of timeminutes.

Explanation—The latency for the named journal of a subscription has crossedabove the specified latency threshold.

Message Variables:

name—The name of the journal for which the latency state is being reported.

time—The specified latency threshold, in minutes.


System Action—Replication continues normally.


Client Administrator Response—Investigate possible causes of the latency.


CHC5119ICHC5119I Latency for journal name has crossed above the problem threshold of timeminutes.

Explanation—The latency for the named journal of a subscription has crossedabove the specified latency threshold.

Message Variables:







CHC5120ICHC5120I Latency for journal name has crossed below the warning threshold of timeminutes.

Explanation—The latency for the named journal of a subscription has crossedbelow the specified latency threshold.

Message Variables:







CHC5121ICHC5121I Latency for journal name has crossed below the problem threshold of timeminutes.

Explanation—The latency for the named journal of a subscription has crossedbelow the specified latency threshold.

Message Variables:








CHC5127ECHC5127E Integration Server name could not connect to the Monitor Agent because themaximum number of connections has been reached.

Explanation—The specified entity could not connect to the Monitor Agent becausethe Monitor Agent already has the maximum number of such entities connected toit.

Message Variables:

name—The name of the entity that could not connect.


System Action—No Management Console instance from the associatedworkstation will be able to connect to InfoSphere CDC.



CHC5128ECHC5128E Subscription name could not connect to the Monitor Agent becausethe maximum number of connections has been reached.

Explanation—The specified subscription could not connect to the Monitor Agentbecause the Monitor Agent already has the maximum number of suchsubscriptions connected to it.

Message Variables:

name—The name of the subscription that could not connect.


System Action—Management Console will not be able to monitor thesubscriptions.




CHC5129ECHC5129E User name could not connect to the Monitor Agent because the maximumnumber of connections has been reached.

Explanation—The specified entity could not connect to the Monitor Agent becausethe Monitor Agent already has the maximum number of such entities connected toit.

Message Variables:

name—The name of the entity that could not connect.


System Action—The user will not be able to connect to InfoSphere CDC fromManagement Console.



CHC5135ECHC5135E Integration Server name could not disconnect from the Monitor Agent.

Explanation—The specified entity could not disconnect from the Monitor Agent,likely because it has already disconnected.

Message Variables:

name—The name of the entity that could not disconnect.


System Action—Disconnecting from the Monitor Agent occurs only when theentity is shutting down. The entity continues to shut down normally.



CHC5136ECHC5136E Subscription name could not disconnect from the Monitor Agent.

Explanation—The specified subscription could not disconnect from the MonitorAgent, likely because it has already disconnected.

Message Variables:

name—The name of the subscription that could not disconnect.






CHC5137ECHC5137E User name could not disconnect from the Monitor Agent.

Explanation—The specified entity could not disconnect from the Monitor Agent,likely because it has already disconnected.

Message Variables:

name—The name of the entity that could not disconnect.





CHC5143ICHC5143I Unable to obtain status for replication name.

Explanation—The Monitor Agent was unable to obtain the status for thesubscription identified in the message (by its name or the corresponding sourceID).

Message Variables:



System Action—Normal processing continues. It is likely that this message is aresult of Management Console requesting information about a subscription thathas never been active since the InfoSphere CDC address space was started.



CHC5144ICHC5144I Unable to obtain performance metrics for replication name.

Explanation—The Monitor Agent was unable to obtain the performance metrics forthe subscription identified in the message (by its name or the corresponding sourceID).


Message Variables:



System Action—Normal processing continues. It is likely that this message is aresult of Management Console requesting information about a subscription thathas never been active since the InfoSphere CDC address space was started.




“CHC6104I” on page 504“CHC6105I” on page 505“CHC6106E” on page 505“CHC6107E” on page 506“CHC6108E” on page 506“CHC6113E” on page 507“CHC6114E” on page 507“CHC6117E” on page 508“CHC6118E” on page 508“CHC6119E” on page 508“CHC6120E” on page 509“CHC6121E” on page 509“CHC6122E” on page 510“CHC6123E” on page 510“CHC6124E” on page 510“CHC6125E” on page 511“CHC6201E” on page 511“CHC6202E” on page 512“CHC6203E” on page 512“CHC6204E” on page 512“CHC6205E” on page 513“CHC6207E” on page 513“CHC6208I” on page 514“CHC6209I” on page 514“CHC6210E” on page 514“CHC6301W” on page 515“CHC6302E” on page 515“CHC6303E” on page 516“CHC6304E” on page 516“CHC6307E” on page 516


“CHC6308E” on page 517“CHC6309E” on page 517“CHC6314E” on page 518“CHC6315E” on page 518“CHC6317E” on page 518“CHC6318E” on page 519“CHC6320E” on page 519“CHC6321E” on page 520“CHC6323W” on page 520“CHC6402E” on page 520“CHC6403E” on page 521“CHC6404I” on page 521“CHC6405I” on page 522“CHC6406I” on page 522“CHC6407E” on page 523“CHC6408I” on page 523“CHC6410I” on page 524“CHC6411I” on page 524“CHC6412I” on page 524“CHC6413I” on page 525“CHC6414I” on page 525“CHC6415W” on page 526“CHC6416W” on page 526“CHC6417W” on page 527“CHC6418W” on page 527“CHC6419E” on page 528“CHC6420E” on page 528“CHC6421E” on page 528“CHC6422I” on page 529“CHC6423I” on page 529“CHC6424E” on page 530“CHC6425I” on page 530“CHC6426E” on page 530“CHC6429I” on page 531“CHC6430W” on page 531“CHC6431W” on page 532“CHC6432W” on page 532“CHC6433W” on page 533“CHC6434W” on page 533“CHC6435W” on page 534“CHC6436W” on page 534“CHC6437W” on page 534“CHC6438W” on page 535“CHC6439E” on page 535“CHC6440W” on page 536


“CHC6445I” on page 536“CHC6446I” on page 537“CHC6448W” on page 537“CHC6451E” on page 538“CHC6452E” on page 538“CHC6453W” on page 539“CHC6454E” on page 539“CHC6455E” on page 540“CHC6456E” on page 540“CHC6457W” on page 541“CHC6458E” on page 541“CHC6459E” on page 542“CHC6460I” on page 542“CHC6465W” on page 543“CHC6466E” on page 543“CHC6467W” on page 544“CHC6468E” on page 545“CHC6471I” on page 545“CHC6472W” on page 546“CHC6473E” on page 546“CHC6501I” on page 547“CHC6502I” on page 547“CHC6503E” on page 547“CHC6504E” on page 548“CHC6505E” on page 548“CHC6506E” on page 549“CHC6509W” on page 549“CHC6511E” on page 550“CHC6512E” on page 550“CHC6513E” on page 550“CHC6514E” on page 551“CHC6515E” on page 551“CHC6516I” on page 552“CHC6801E” on page 552“CHC6802E” on page 553“CHC6803E” on page 553“CHC6804I” on page 554“CHC6903E” on page 554“CHC6995E” on page 555“CHC6998E” on page 555

CHC6104ICHC6104I Task task for target name is starting.

Explanation—The identified InfoSphere CDC communications I/O task is startingfor the specified target.


Message Variables:

task—The name of the InfoSphere CDC communications I/O task that is starting.

name—The target for which the task is starting.

Message Destination—Product administration log. To generate this message in theproduct administration log, trace type 213 must be specified.




CHC6105ICHC6105I Task name for target target is terminating with a reason code of number.The last message processed was type type.

Explanation—The identified InfoSphere CDC communications I/O task isterminating for the specified target.

Message Variables:

name—The name of the InfoSphere CDC communications I/O task that isterminating.

target—The target for which the task is terminating.

number—The numeric reason code.

type—The type of message that was processed last.





CHC6106ECHC6106E A message was too big. The message is size bytes. The maximum sizeallowed by the message queue is maximum bytes.

Explanation—An attempt was made to write a message to a communicationsqueue which was larger than the maximum message size allowed by the queue.

Message Variables:

size—The size, in bytes, of the message.

maximum—The maximum size, in bytes, of a message that can be written to acommunications queue.



System Action—Communications and/or replication activity terminatesabnormally.



CHC6107ECHC6107E The buffer is too small. The buffer size is buffer bytes. The incomingmessage is size bytes.

Explanation—An attempt was made to read a message from a communicationsqueue, but the read buffer was too small to accommodate the message.

Message Variables:

buffer—The size, in bytes, of the read buffer.

size—The size, in bytes, of the message that could not be accommodated by theread buffer.





CHC6108ECHC6108E An unexpected message of type message was received during operation oftype operation. The expected message type was type.

Explanation—The remote server transmitted an unexpected message during theprocess of communications initialization.

Message Variables:

message —The type of communications message that was received from the remoteserver.

operation—The socket operation that received the message.

type—The type of communications message that was expected from the remoteserver.



System Action—Communications are not established, and replication activity forthe subscription that requested communications is not started.



CHC6113ECHC6113E Communications task task named name is terminating abnormally.

Explanation—The named InfoSphere CDC communications task is terminatingabnormally.

Message Variables:

task—The InfoSphere CDC communications task identifier.

name—The name of the InfoSphere CDC communications task. The name of thecommunications task is usually the same as the three-letter task identifier indicatedin the message text.


System Action—If the identified communications task is CCI, CCO, CDI or CDO,communications terminates abnormally and replication activities that rely on thecommunications link terminates abnormally as well. If the task is CLS or CMO,InfoSphere CDC terminates abnormally. If the task is CVF, InfoSphere CDCcontinues to operate normally.



CHC6114ECHC6114E Communications monitor task (CMO) has been lost.

Explanation—The InfoSphere CDC communications monitor task (CMO) is notactive.



System Action—InfoSphere CDC terminates abnormally shortly after thegeneration of this message.

Operator Response—If InfoSphere CDC does not terminate shortly after thegeneration of this message, stop InfoSphere CDC manually.



CHC6117ECHC6117E Unable to allocate memory for session control blocks.

Explanation—Sufficient memory for the identified InfoSphere CDCcommunications task could not be allocated.



System Action—If the identified communications task issuing the message is CCI,CCO, CDI or CDO, communications terminates abnormally and replicationactivities that rely on the communications link terminates abnormally as well. Ifthe task is CLS or CMO, InfoSphere CDC terminates abnormally.



CHC6118ECHC6118E Unable to allocate memory for link control blocks.







CHC6119ECHC6119E Unable to allocate memory for conversation control blocks.








CHC6120ECHC6120E Unable to allocate memory for reference control blocks.







CHC6121ECHC6121E Unable to allocate memory for input buffer.








CHC6122ECHC6122E Unable to allocate memory for output buffer.







CHC6123ECHC6123E Unable to allocate memory for debug value work area.







CHC6124ECHC6124E Unable to allocate memory for Common Agent global variables.




System Action—If the identified communications task issuing the message is CCI,CCO, CDI or CDO, communications terminates abnormally and replication


activities that rely on the communications link terminates abnormally as well. Ifthe task is CLS or CMO, InfoSphere CDC terminates abnormally.



CHC6125ECHC6125E Unable to allocate memory for Monitor Agent global variables.







CHC6201ECHC6201E Unable to create communications queue name.

Explanation—An attempt to create the identified communications queue wasunsuccessful.

Message Variables:

name—The name of the communications queue that could not be created.


System Action—If the queue was to be created for communications, thecommunications link is not established and replication activities that rely on thelink are not started. If the queue was to be created for a subscription, replicationactivities for the subscription are not started.

Operator Response—If previous messages in the log indicate insufficient memory,restart InfoSphere CDC with a larger address space.

Client Administrator Response—Further investigation is required. Record themessage number and text, and then contact your InfoSphere CDC administrator orIBM representative for assistance if restarting InfoSphere CDC with a largeraddress is unsuccessful.


CHC6202ECHC6202E Unable to locate communications queue name.

Explanation—An attempt to perform a read or write operation on the identifiedcommunications queue was unsuccessful. The queue could not be found.

Message Variables:

name—The name of the communications queue that could not be found.


System Action—If communications attempted to write to the queue, thecommunications link continues normal processing. If communications attempted toread from the queue, the communications link terminates abnormally andreplication activities that rely on the link terminate abnormally as well. If asubscription attempted to read from or write to the queue, replication activities forthe subscription terminate abnormally.



CHC6203ECHC6203E Unable to read from communications queue name.

Explanation—An attempt to perform a read operation on the identifiedcommunications queue was unsuccessful.

Message Variables:

name—The name of the communications queue that could not be read.


System Action—If communications attempted to read from the queue, thecommunications link terminates abnormally and replication activities that rely onthe link terminate abnormally as well. If a subscription attempted to read from thequeue, replication activities for the subscription terminate abnormally.



CHC6204ECHC6204E Unable to write to communications queue name.

Explanation—An attempt to perform a write operation on the identifiedcommunications queue was unsuccessful.


Message Variables:



System Action—If communications attempted to write to the queue, thecommunications link is maintained. If a subscription attempted to write to thequeue, replication activities for the subscription terminate abnormally.



CHC6205ECHC6205E Unable to delete communications queue name.

Explanation—An attempt to delete the identified communications queue wasunsuccessful during InfoSphere CDC shutdown.

Message Variables:

name—The name of the communications queue that could not be deleted.


System Action—Communications and replication activities end normally.



CHC6207ECHC6207E Non-blocking write failed to add a message to queue name after timeseconds. The message type was type.

Explanation—A write to a communications queue could not be completed in thetime allowed.

Message Variables:

name—The name of the communications queue that could not be written.

time—The number of seconds that elapsed before the write attempt timed out.

type—The type of communications message that could not be sent.



System Action—If communications attempted to write to the queue, thecommunications link is maintained. If a subscription attempted to write to thequeue, replication activities for the subscription terminate abnormally.



CHC6208ICHC6208I Communications queue name was created.

Explanation—The identified communications queue was created.

Message Variables:

name—The name of the communications queue that was created.





CHC6209ICHC6209I Communications queue name was deleted.

Explanation—The identified communications queue was deleted.

Message Variables:

name—The name of the communications queue that was deleted.





CHC6210ECHC6210E Unable to obtain a message from a communications queue.

Explanation—An attempt to obtain a message from a communications queue wasunsuccessful.




System Action—If communications was unable to obtain a message, thecommunications link terminates abnormally and all replication activities that relyon the link terminate abnormally as well. If the InfoSphere CDC communicationsmonitor task was unable to obtain a message, InfoSphere CDC terminatesabnormally.



CHC6301WCHC6301W An unknown message of type type and length size was received. The messagewas ignored.

Explanation—An InfoSphere CDC communications task received an unrecognizedmessage.

Message Variables:

type—The type of communications message that was not recognized.

size—The length of the communications message.


System Action—The message is ignored and normal processing continues.



CHC6302ECHC6302E Invalid startup arguments. The argument string is string.

Explanation—An InfoSphere CDC communications task was started with aninvalid set of arguments.

Message Variables:

string—The string containing the invalid startup arguments.


System Action—The communications task is not started. Depending on whichmodule attempted to start the task, replication activities are not started or theInfoSphere CDC address space is not initialized.




CHC6303ECHC6303E Invalid process name argument. The process name is type.

Explanation—The communications module attempted to start an InfoSphere CDCcommunications task that is of an unknown type.

Message Variables:

type—The unknown type of communication task.


System Action—The communications task is not started.



CHC6304ECHC6304E Invalid queue tag argument. The queue tag is tag.

Explanation—The communications module attempted to start an InfoSphere CDCcommunications task with an invalid queue tag.

Message Variables:

tag—The invalid queue tag.





CHC6307ECHC6307E Temporary communications queue name could not be created.

Explanation—An attempt to create a temporary communications queue in order toestablish a connection to the remote server was unsuccessful.

Message Variables:

name—The name of the temporary communications queue that could not becreated.



System Action—Replication activities for a subscription are not started.



CHC6308ECHC6308E Invalid target application arguments.

Explanation—The target arguments for an InfoSphere CDC communications taskwere invalid.






CHC6309ECHC6309E Operation of type operation failed for task name with a status of type.

Explanation—A call to the communications API was unsuccessful.

Message Variables:

operation—The name of the operation that could not be performed.

name—The name of the InfoSphere CDC task that called the communications API.

type—A value indicating the status of the operation.






CHC6314ECHC6314E Operation of type operation was failed by the communications monitor fortask name with a status of type.

Explanation—A call to the communications API was rejected by thecommunications monitor task.

Message Variables:

operation—The name of the operation that could not be performed.

name—The name of the InfoSphere CDC task that called the communications API.

type—A value indicating the status of the operation.





CHC6315ECHC6315E Unable to obtain default communications parameters.

Explanation—An InfoSphere CDC communications task was unable to accessshared memory containing the default configuration parameters.



System Action—The communications task terminates abnormally.



CHC6317ECHC6317E Unable to create TCP/IP listener queue name.

Explanation—An attempt by the InfoSphere CDC TCP/IP Listener task (CLS) tocreate the identified communications queue was unsuccessful.

Message Variables:

name—The name of the communications queue that could not be created.



System Action—InfoSphere CDC terminates abnormally.



CHC6318ECHC6318E Unable to obtain key value for key name. The failure code is code.

Explanation—The communications module was unable to determine a value forthe key submitted for the InfoSphere CDC communications task duringinitialization.

Message Variables:

name—The key for the communications task.

code—The returned error code.





CHC6320ECHC6320E Unable to receive a message from a communication link.

Explanation—Messages could not be received from a communications link.



System Action—The communications link terminates abnormally. Replicationactivities that rely on the link terminate abnormally as well.

Operator Response—Verify that TCP/IP communications are active on both thelocal and remote servers, and verify that physical connections to the network fromboth the local and remote servers are operational.



CHC6321ECHC6321E Unable to send a message to a communication link.

Explanation—Messages could not be sent on a communications link.



System Action—The communications link terminates abnormally. Replicationactivities that rely on the link terminate abnormally as well.

Operator Response—Verify that TCP/IP communications are active on both thelocal and remote servers, and verify that physical connections to the network fromboth the local and remote servers are operational.


CHC6323WCHC6323W Communications monitor encountered an error processing message numbernumber return code was code.

Explanation—The InfoSphere CDC communications monitor task (CMO) could notprocess an internal message received from a remote server or another task.

Message Variables:

number—The hexadecimal identifier of the internal message that could not beprocessed.

code—The numeric error code returned as a result of not being able to process theinternal message.


System Action—Active replication may unexpectedly end after this message hasbeen generated.


Client Administrator Response—Examine the system log for other messages thatindicate an insufficient amount of memory. If such messages appear in the systemlog, restart InfoSphere CDC with a larger region.

CHC6402ECHC6402E Unable to locate temporary message queue name while processing message oftype type.

Explanation—The identified temporary communications queue could not be foundduring the processing of a communications message. The queue was required torespond to the message.

Message Variables:

name—The name of the temporary communications queue that could not be found.


type—The type of communications message that was being processed.





CHC6403ECHC6403E Unable to locate process message queue name while processing message oftype type.

Explanation—The identified process communications queue could not be foundduring the processing of a communications message. The queue was required torespond to the message.

Message Variables:

name—The name of the process communications queue that could not be found.

type—The type of communications message that was being processed.





CHC6404ICHC6404I Communications session open to remote system server in session slotentry.

Explanation—The InfoSphere CDC communications monitor task has initiated aconnection to the identified remote server. The session that has been established isrequired before communications and replication activities are started with theremote server.

Message Variables:


entry—The number of the entry in the session slot table allocated for theconnection.






CHC6405ICHC6405I Communications conversation entry was opened for local task name withremote conversation slot remote.

Explanation—A communications conversation was opened between an InfoSphereCDC task running on the local server and an entity on a remote server.

Message Variables:

entry—The number of the entry for the conversation that has been allocated in thelocal conversation table.

name—The name of the InfoSphere CDC task running on the local server.

remote—The number of the entry for the conversation that has been allocated inthe remote conversation table.





CHC6406ICHC6406I Communications conversation was allocated in conversation slot number andsession slot entry, current number of allocated conversation slots is total.

Explanation—A communications conversation table entry has been allocated inorder to start a new conversation. Each active subscription defined in ManagementConsole requires two conversations: a control conversation and a dataconversation.

Message Variables:

number—The number of the entry for the conversation in the conversation table.

entry—The number of the entry for the session that corresponds to theconversation in the session table.

total—The total number of used entries in the conversation table.






CHC6407ECHC6407E Unable to allocate a conversation slot. total conversation slots arecurrently in use.

Explanation—The communications module attempted to allocate a conversationtable entry in order to start a new conversation, but there were no available entriesto allocate.

Message Variables:

total—The total number of used entries in the conversation table.


System Action—The conversation does not start. Replication activities that rely onthe conversation do not start.



CHC6408ICHC6408I Communications session name was allocated in session slot entry on controllink link in link slot control.

Explanation—A communications session table entry has been allocated to start anew session.

Message Variables:

name—The name of the new session, which is composed of the remote server hostname and port number.

entry—The number of the session table entry that has been allocated for the newsession.

link—The name of the control link that the new session will use, which iscomposed of the remote server host name and port number.

control—The number of the link table entry used by the control link.






CHC6410ICHC6410I TCP/IP session was allocated in session slot entry from local host localto remote host remote, port number.

Explanation—A communications session table entry has been allocated to start anew TCP/IP session.

Message Variables:

entry—The number of the session table entry that has been allocated for the newsession.

local—The host name of the local server.

remote—The host name of the remote server.

number—The port number on the remote server used for TCP/IP communications.





CHC6411ICHC6411I Communications session name in session slot entry has been deallocated.

Explanation—A communications session table entry has been deallocated and isnow available for reuse.

Message Variables:

name—The name of the session that used the session table entry number.

entry—The number of the session table entry that is now available for reuse.





CHC6412ICHC6412I Communications data link named link in link slot number has been allocatedto session name in session slot entry.

Explanation—A communications link table entry has been allocated for a new datalink.


Message Variables:

link—The name of the new data link.

number—The number of the link table entry that has been allocated for the newdata link.

name—The name of the session that owns the new data link.

entry—The number of the session table entry that has been allocated for thesession.





CHC6413ICHC6413I Communications control link link in link slot number and session slotentry has been deallocated.

Explanation—A communications link table entry used by a control link has beendeallocated and is available for reuse.

Message Variables:

link—The name of the control link.

number—The number of the link table entry that has been deallocated.

entry—The number of the session table entry for the session that owned thedeallocated data link.





CHC6414ICHC6414I Communications data link link in link slot number and session slotentry has been deallocated.

Explanation—A communications link table entry used by a data link has beendeallocated and is available for reuse.

Message Variables:


link—The name of the data link.

number—The number of the link table entry that has been deallocated.

entry—The number of the session table entry for the session that owned thedeallocated data link.





CHC6415WCHC6415W Communications monitor received the invalid conversation slot numberin a message of type type.

Explanation—The InfoSphere CDC communications monitor task received acommunications message identifying a conversation slot number that did notcorrespond to an active conversation.

Message Variables:

number—The number of the conversation table entry contained in thecommunications message.

type—The type of communications message.


System Action—The message is ignored.


Client Administrator Response—If related errors occur after this message hasbeen generated, contact your InfoSphere CDC administrator for further assistance.

CHC6416WCHC6416W Communications monitor received the lapsed conversation slot numberin a message of type type.

Explanation—The InfoSphere CDC communications monitor task received acommunications message identifying a conversation slot number that has beendeallocated and reused since the message was sent.

Message Variables:

number—The number of the conversation table entry contained in thecommunications message.







CHC6417WCHC6417W Communications monitor received the invalid session slot number in amessage of type type.

Explanation—The InfoSphere CDC communications monitor task received acommunications message identifying a session slot number that did not correspondto an active session.

Message Variables:

number—The number of the session table entry contained in the communicationsmessage.






CHC6418WCHC6418W Communications monitor received the lapsed session slot number in amessage of type type.

Explanation—The InfoSphere CDC communications monitor task received acommunications message identifying a session slot number that has beendeallocated and reused since the message was sent.

Message Variables:

number—The number of the session table entry contained in the communicationsmessage.







CHC6419ECHC6419E Communications monitor was unable to allocate a queue tag for conversationslot number.

Explanation—No queue tags were available when a communications conversationwas started. As a result, one or more communications queues could not be created.

Message Variables:

number—The number of the conversation table entry allocated for the conversation.





CHC6420ECHC6420E Unable to allocate a conversation-link cxl slot, number cxl slots arecurrently in use.

Explanation—No entries were available in the cxl table when a communicationsconversation was started.

Message Variables:

number—The number of cxl table entries that were being used.





CHC6421ECHC6421E Unable to allocate a link slot. number link slots are currently in use.

Explanation—No entries were available in the link table when a communicationslink was started.

Message Variables:


number—The number of link table entries that were being used.


System Action—The link does not start. The conversation that relies on the linkdoes not start, and replication activities that rely on the conversation do not start.



CHC6422ICHC6422I Communications conversation in conversation slot number has beendeallocated.

Explanation—A communications conversation table entry used by a conversationhas been deallocated and is available for reuse.

Message Variables:

number—The number of the conversation table entry that has been deallocated.





CHC6423ICHC6423W Communications conversation in conversation slot number was abnormallyterminated by communications monitor.

Explanation—A communications conversation with the remote server hasterminated abnormally.

Message Variables:

number—The number of the conversation table entry for the conversation.


System Action—Replication activities that rely on the conversation terminateabnormally.




CHC6424ECHC6424E Conversation for remote target task type named task in local conversationslot local and remote conversation slot remote has been terminated abnormally bythe remote system.

Explanation—A communications conversation with the remote server hasterminated abnormally.

Message Variables:

type—The type of InfoSphere CDC task on the remote server that was affected bythe abnormal termination of the conversation.

task—The name of the InfoSphere CDC task on the remote server that wasaffected by the abnormal termination of the conversation.

local—The number of the conversation table entry for the conversation on thelocal server.

remote—The number of the conversation table entry for the conversation on theremote server.


System Action—Replication activities that rely on the conversation terminateabnormally.


Client Administrator Response—Consult messages generated on the remote serverto determine the cause the problem, and take appropriate actions based on thosemessages.

CHC6425ICHC6425W Conversation in slot number was closed by application before becomingoperational.

Explanation—Conversation in slot number closed by application before becomingoperational.

Message Variables:

number—The number of the conversation table entry.





CHC6426ECHC6426E Unable to allocate a session slot. number link slots are currently in use.


Explanation—No entries were available in the session table when acommunications session was started.

Message Variables:

number—The number of session table entries currently being used.


System Action—The session does not start. The conversation that relies on thesession does not start, and replication activities that rely on the conversation donot start.



CHC6429ICHC6429I Communications session to name in session slot number has become idleand will terminate.

Explanation—A communications session is not being used for replication. As aresult, the session will be terminated.

Message Variables:

name—The name of the session.

number—The number of the session table entry that has been allocated for thesession.


System Action—The session terminates.



CHC6430WCHC6430W The communications session in session slot number has failed to closeafter time seconds.

Explanation—A communications session could not be closed within an allottedamount of time.

Message Variables:


time—The maximum amount of time, in seconds, that has been allotted for thesession to close.



System Action—The session terminates abnormally.



CHC6431WCHC6431W The communications session in session slot entry has failed to stop afternumber seconds.

Explanation—A communications session could not be stopped within an allottedamount of time.

Message Variables:


number—The maximum amount of time, in seconds, that has been allotted for thesession to stop.


System Action—The session terminates abnormally.



CHC6432WCHC6432W The communications session in session slot entry has failed to open afternumber seconds.

Explanation—A communications session could not be opened within an allottedamount of time.

Message Variables:


number—The maximum amount of time, in seconds, that has been allotted for thesession to open.






CHC6433WCHC6433W The communications link for session in session slot number has failed toopen after time seconds.

Explanation—A communications link could not be opened within an allottedamount of time.

Message Variables:

number—The number of the session table entry that has been allocated for thesession using the communications link.

time—The maximum amount of time, in seconds, that has been allotted for thecommunications link to open.


System Action—The communications link does not start. Communicationcomponents and replication activities that rely on the link do not start.



CHC6434WCHC6434W The communications session in session slot entry has failed to start aftertime seconds.

Explanation—A communications session could not be started within an allottedamount of time.

Message Variables:


time—The maximum amount of time, in seconds, that has been allotted for thesession to start.






CHC6435WCHC6435W The communications link for session in session slot entry has failed tostart after time seconds.

Explanation—A communications link could not be started within an allottedamount of time.

Message Variables:


time—The maximum amount of time, in seconds, that has been allotted for thecommunications link to start.





CHC6436WCHC6436W Communications session name in session slot number and state state haslost a resource.

Explanation—A communications session has lost one of its communications linktasks.

Message Variables:



state—The state of the session when the communications link task was lost.


System Action—The session terminates abnormally. Replication activities that relyon the session terminate abnormally.



CHC6437WCHC6437W Communications link in link slot link lost its session in session slotsession. The session state is state.


Explanation—A communications link lost its session.

Message Variables:

link—The number of the link table entry that has been allocated to the link.


state—The state of the session when the communications link lost the session.


System Action—The communications link terminates abnormally. Communicationcomponents and replication activities that rely on the link terminate abnormally.



CHC6438WCHC6438W The communications link in link slot number has failed to close aftertime seconds.

Explanation—A communications link could not be closed within the allottedamount of time.

Message Variables:

number—The number of the link table entry allocated to the communications link.

time—The amount of time, in seconds, that has been allotted for thecommunications link to close.


System Action—The communications link terminates abnormally.



CHC6439ECHC6439E Communications link in link slot number for communications session namefailed to initialize within time seconds and has been terminated.

Explanation—A communications link could not complete initialization within anallotted amount of time.

Message Variables:


number—The number of the link table entry that has been allocated to thecommunications link.

name—The name of the session that is using the communications link.

time—The amount of time, in seconds, that has been allotted for thecommunications link to initialize.





CHC6440WCHC6440W The communications link for session in session slot number has failed toopen after time seconds.

Explanation—A communications link could not be opened within the allottedamount of time.

Message Variables:


time—The amount of time, in seconds, that has been allotted for thecommunications link to open.





CHC6445ICHC6445I Communications session to name in session slot number has been closed bythe remote communications monitor.

Explanation—A communications session to a remote server has been closed by theInfoSphere CDC communication monitor task on the remote server.

Message Variables:








CHC6446ICHC6446I Communications link in link slot number has been closed by the remotecommunications monitor.

Explanation—A communications link has been closed by the InfoSphere CDCcommunication monitor task on the remote server.

Message Variables:






CHC6448WCHC6448W Communications link in link slot number has terminated abnormally.

Explanation—A communications link terminated abnormally.

Message Variables:







CHC6451ECHC6451E Task task in link slot link for session name in session slot number hasterminated abnormally with link state state.

Explanation—An InfoSphere CDC communications I/O task terminatedabnormally.

Message Variables:

task—The name of the task.

link—The number of the link table entry that has been allocated to thecommunications link associated with the I/O task.

name—The name of the session that is using the communications link.


state—The state of the communications link when the error occurred.





CHC6452ECHC6452E Remote application remote named name paired with local application local inconversation slot number has failed to close a conversation after time seconds.

Explanation—A remote application (replication) could not close a conversationwith a local application (replication) within the allotted amount of time. The localapplication had already terminated and closed the conversation.

Message Variables:

remote—The type of the remote application that could not close a conversation.

name—The name of the remote application.

local—The type of the local application.

number—The number of the conversation table entry that has been allocated to theconversation.

time—The amount of time, in seconds, that has been allotted for the remoteapplication to close the conversation.



System Action—The communications module deallocates the conversation andnormal processing continues.



CHC6453WCHC6453W Communications conversation in conversation slot number and state statehas lost a resource.

Explanation—A communications conversation has lost one of its links.

Message Variables:


state—The state of the conversation when this message was generated.


System Action—The conversation terminates abnormally. Replication activities thatrely on the conversation terminate abnormally.



CHC6454ECHC6454E The communications conversation in conversation slot number has failedto start within the allowed time of time seconds.

Explanation—A communications conversation could not start within the allottedamount of time.

Message Variables:


time—The amount of time, in seconds, that has been allotted for the conversationto start.






CHC6455ECHC6455E The remote start of application type named name for conversation inconversation slot number has failed to start within the allowed time of timeseconds.

Explanation—A remote application (replication) for a conversation could not startwithin the allotted amount of time.

Message Variables:

type—The type of the remote application that could not be started.



time—The amount of time, in seconds, that has been allotted for the remoteapplication to start.




Client Administrator Response—Further investigation is required. Record themessage number and text, and then contact your InfoSphere CDC administrator forthe remote server or your IBM representative for assistance.

CHC6456ECHC6456E Local application local paired with remote application remote named name inconversation slot number has failed to close a conversation after time seconds.

Explanation—The remote application (replication) for a conversation closed aconversation, but the local application (replication) could not close the conversationwithin the allotted amount of time. The remote application may have terminatedwithout notifying the local application.

Message Variables:

local—The type of the local application that could not close the conversation.

remote—The type of the remote application that closed the conversation.


number—The number of the conversation table entry that has been allocated toconversation.


time—The amount of time, in seconds, that has been allotted for the localapplication to close.


System Action—The conversation is deallocated. Replication activities that rely onthe conversation terminate abnormally.



CHC6457WCHC6457W Communications conversation in conversation slot number has failed toinitialize.

Explanation—A communications conversation was not initialized.

Message Variables:






CHC6458ECHC6458E Source application type in conversation slot conversation on session namein session slot session has ended abnormally.

Explanation—A source application task (replication or communications verifier)using a conversation has terminated abnormally.

Message Variables:

type—The type of source application that terminated abnormally.

conversation—The number of the conversation table entry that has been allocatedto the conversation.

name—The name of the session that owns the conversation.

session—The number of the session table entry that has been allocated to thesession owning the conversation.



System Action—The conversation closes so that the remote server can determinethat the source application task terminated.



CHC6459ECHC6459E Target application type in conversation slot conversation on session namein session slot session has ended abnormally.

Explanation—A target application task (replication or communications verifier)using a conversation has terminated abnormally.

Message Variables:

type—The type of target application that terminated abnormally.

conversation—The number of the conversation table entry that has been allocatedto the conversation.

name—The name of the session that owns the conversation.

session—The number of the session table entry that has been allocated to thesession owning the conversation.


System Action—The conversation closes so that the remote server can determinethat the target application task terminated.



CHC6460ICHC6460I Communications link name on session session has timed out after timeseconds.

Explanation—The identified communications link was continuously idle for theduration of the specified timeout period.

Message Variables:

name—The name of the communications link.

session—The name of the session that owns the communications link.


time—The amount of time, in seconds, that the communications link wascontinuously idle.


System Action—The communications link terminates.



CHC6465WCHC6465W Session name in session slot number has not received a poll requestresponse in time seconds, has missed missed consecutive replies and missed totalreplies in total.

Explanation—A communications session did not receive a response to a pollrequest from the remote server within the specified period of time.

Message Variables:


number—The number of the entry in the session table that has been allocated to thesession.

time—The maximum amount of time, in seconds, for a response to be receivedfrom the remote server.

missed—The number of consecutive responses to poll requests that have not beenreceived.

total—The total number of responses to poll requests that have not been received.





CHC6466ECHC6466E Remote system on session name in session slot number has failed to respondto missed consecutive poll requests and total poll requests in all, each with atimeout of time seconds; all communications with the remote system will beterminated.

Explanation—A communications session did not receive a response to a pollrequest from the remote server within the specified period of time.

Message Variables:




missed—The number of consecutive responses to poll requests that have not beenreceived.

total—The total number of responses to poll requests that have not been received.

time—The maximum amount of time, in seconds, for a response to be receivedfrom the remote server.


System Action—The session terminates abnormally. Communication componentsand replication activities that rely on the session terminate abnormally.



CHC6467WCHC6467W Session name in session slot number has received a late response to a pollrequest in time seconds instead of maximum seconds; there have been late successivelate replies and total late replies in total.

Explanation—A communications session received a late response to a poll requestfrom the remote server.

Message Variables:



time—The amount of time, in seconds, it took for the session to receive a responsefrom the remote server.

maximum—The maximum amount of time, in seconds, for a response to be receivedfrom the remote server.

late—The number of consecutive responses to poll requests that have been late.

total—The total number of responses to poll requests that have been late.






CHC6468ECHC6468E Communications session in session slot entry cannot start a session toremote system server. The status is status.

Explanation—A communications session could not establish a session to theidentified remote server.

Message Variables:

entry—The number of the entry in the session table that has been allocated to thesession.


status—The status of the session when the message was generated.





CHC6471ICHC6471I Communications conversation name allocated in conversation slot entry. Thecurrent number of conversations is number.

Explanation—An entry in the communications conversation table has beenallocated to a new conversation.

Message Variables:

name—The name of the new conversation.

entry—The number of the entry in the conversation table that has been allocatedto the new conversation.

number—The number of entries in the conversation table that are currently beingused.






CHC6472WCHC6472W Application type named name in conversation slot number has terminatedunexpectedly.

Explanation—A local application (replication) was terminated unexpectedly.

Message Variables:

type—The type of the local application that terminated unexpectedly.

name—The name of the local application.

number—The number of the entry in the communications conversation table thathas been allocated to the application.


System Action—The conversation closes so that the remote server can determinethat the local application terminated.



CHC6473ECHC6473E The local start of application type named name for conversation inconversation slot number has failed to start within the allowed time of timeseconds.

Explanation—The local application (replication) for a conversation could not startwithin the allotted amount of time.

Message Variables:

type—The type of the local application that could not start within the allottedamount of time.

name—The name of the local application.


time—The maximum amount of time, in seconds, that has been allotted for theapplication to start.






CHC6501ICHC6501I Normal shutdown of link number, process code has been initiated by theremote partner.

Explanation—A communications link I/O task was instructed to shutdownnormally by the remote server.

Message Variables:

number—The number of the entry in the communications link table that has beenallocated to the link.

code—A code identifying the terminating process in the link.





CHC6502ICHC6502I Normal shutdown of link number, process code has been initiated by thelocal monitor.

Explanation—A communications link I/O task was instructed to shutdownnormally by the local communications monitor task.

Message Variables:







CHC6503ECHC6503E Communications link to server abnormally terminated by remote system(link number, process code).


Explanation—A communications link was terminated abnormally by the remoteserver.

Message Variables:








CHC6504ECHC6504E Communications link to server was abnormally terminated by local monitor(link number, process code).

Explanation—A communications was terminated abnormally by the localcommunications monitor task.

Message Variables:








CHC6505ECHC6505E Communications monitor message queue name was not found.

Explanation—A communications link could not locate the communications queuefor the communications monitor task.

Message Variables:







CHC6506ECHC6506E Communications process message queue name was not found.

Explanation—A communications link I/O task could not locate its communicationsqueue.

Message Variables:






CHC6509WCHC6509W Application message queue name was not found.

Explanation—An InfoSphere CDC communications task cannot locate thecommunications queue for an application (replication or communications verifier).

Message Variables:



System Action—The communications message intended for the missing queue isdiscarded. Normal processing continues.




CHC6511ECHC6511E Target communications task failed to accept connection from remote partner.The error code is code.

Explanation—A communications link I/O task was unable to accept the connectionfrom its partner task on the remote server.

Message Variables:

code—The error code as a result of the connection failure.


System Action—The communications link does not start. The conversation thatrelies on the link does not start, and replication activities that rely on theconversation do not start.



CHC6512ECHC6512E Communications task in state state received an incorrect message of typetype.

Explanation—A communications link I/O task received an unexpected messagefrom its partner task on the remote server during initialization.

Message Variables:

state—The state of the communications I/O task when this message wasgenerated.

type—The type of the unexpected communications message.





CHC6513ECHC6513E Communications task started as type typ1 but the remote partner requires itto be of type typ2.


Explanation—A communications link I/O task was started as a specific type oftask, but its partner task on the remote server requires that the local task be adifferent type.

Message Variables:

typ1—The actual type of the communications link I/O task.

typ2—The type of communications link I/O task expected on the remote server.





CHC6514ECHC6514E Source communications task failed to initiate a connection with the remotepartner. The error code is code

Explanation—A communications link I/O task was unable to initiate a connectionwith its partner task on the remote server.

Message Variables:

code—The error code as a result of the connection failure.





CHC6515ECHC6515E Local and remote communications could not support a compatible version.Local communications requested version ver1 and offered version ver2.Remote communications requested version ver3 and offered version ver4.

Explanation—A communications link I/O task was unable to negotiate acompatible version of the communications protocol with its partner task on theremote server.

Message Variables:


ver1—The version of the communications protocol requested by the local server.

ver2—The version of the communications protocol offered by the local server.

ver3—The version of the communications protocol requested by the remote server.

ver4—The version of the communications protocol offered by the remote server.



Operator Response—The version of InfoSphere CDC running on the local server isnot compatible with the version of InfoSphere CDC running on the remote server.Install compatible versions on the local and remote servers, and restart replication.Contact your IBM representative for information about version compatibility.


CHC6516ICHC6516I Local and remote communications versions differ but compatible version ver1has been negotiated. Local communications requested version ver2 and offered versionver3. Remote communications requested version ver4 and offered version ver5.

Explanation—A communications link I/O task was able to negotiate a compatibleversion of the communications protocol with its partner task on the remote servereven though different versions are used.

Message Variables:

ver1—The compatible version of the communications protocol that has beennegotiated.

ver2—The version of the communications protocol requested by the local server.

ver3—The version of the communications protocol offered by the local server.

ver4—The version of the communications protocol requested by the remote server.

ver5—The version of the communications protocol offered by the remote server.





CHC6801ECHC6801E TCP/IP Listener failed to initialize.


Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task could not beinitialized.



System Action—The InfoSphere CDC address space is not initialized.

Operator Response—Previous messages in the logs provide more informationabout the problem. Based on the information that is contained in these messages,take appropriate actions and restart the InfoSphere CDC address space.


CHC6802ECHC6802E TCP/IP Listener received a connection request from an unknown task type oftype.

Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task received aconnection request from a task of an unknown type. The listener task expects toreceive connections requests from communications link I/O tasks and ManagementConsole processes running on client workstations.

Message Variables:

type—The unknown type of the task.


System Action—The connection request is rejected.

Operator Response—Contact your network administrator to verify that networktraffic is normal.

Client Administrator Response—If network traffic is normal, record the messagenumber and contact the InfoSphere CDC administrator for the remote server oryour IBM representative for assistance.

CHC6803ECHC6803E TCP/IP Listener was unable to start a task of type type

Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task accepted aconnection request but was unable to start a task to implement the connection.

Message Variables:

type—The type of the task that could not be started to implement the connection.






CHC6804ICHC6804I TCP Listener was initialized on service name name, port number.

Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task has been initializedsuccessfully and is listening on the identified port.

Message Variables:

name—The service name corresponding to the port that is being used to listen forcommunications.

number—The port number that is being used to listen for communications.





CHC6903ECHC6903E Unable to allocate storage for an ECB resource.

Explanation—Sufficient memory could not be obtained for an ECB resource duringinitialization of a communications task or a communications API call.



System Action—During initialization of the CMO or CLS task, the task is notinitialized and the InfoSphere CDC address space is not initialized. Duringinitialization of a communications link I/O task, the communications link does notstart. The conversation that relies on the link does not start and replicationactivities that rely on the conversation do not start. During initialization of a CVFtask, the communications test does not start. During a communications API call,the call is unsuccessful, and replication activities that initiated the API callterminate abnormally.


Client Administrator Response—If the Operator Response does not resolve theerror, further investigation is required. Record the message number and text, andthen contact your InfoSphere CDC administrator or IBM representative forassistance.


CHC6995ECHC6995E A communications internal error occurred.

Explanation—A severe internal error occurred as a result of an operation withinthe communications module.



System Action—The current operation within the communications module ends.As a result, other problems may occur.



CHC6998ECHC6998E Unable to create or find a communications queue. Reason: text.

Explanation—An operation within the communications module was unable tocreate or locate a communications queue.

Message Variables:

text—A brief description explaining why the communications queue could not becreated or located.


System Action—The current operation within the communications module ends.




“CHC7052E” on page 556“CHC7053E” on page 557“CHC7054E” on page 557“CHC7055E” on page 558“CHC7057E” on page 559“CHC7058E” on page 559“CHC7059E” on page 560“CHC7060E” on page 560“CHC7061E” on page 561


“CHC7064E” on page 561“CHC7065E” on page 561“CHC7069E” on page 562“CHC7070E” on page 562“CHC7071E” on page 563“CHC7072E” on page 563“CHC7073E” on page 563“CHC7074E” on page 564“CHC7075I” on page 564“CHC7077I” on page 565“CHC7078I” on page 565“CHC7079I” on page 565“CHC7081E” on page 566“CHC7082E” on page 566“CHC7083E” on page 567“CHC7084E” on page 567“CHC7085E” on page 567“CHC7086E” on page 568“CHC7087E” on page 568“CHC7088E” on page 569“CHC7089W” on page 569“CHC7094E” on page 570“CHC7095I” on page 570“CHC7099E” on page 571

CHC7052ECHC7052E TCP/IP failure to get remote host information for server. The error code iscode.

Explanation—A communications link I/O task was not able to obtain informationabout the identified remote server.

Message Variables:


code—The error code as a result of the inability to obtain information about theremote server. The possible codes and their explanations are as follows:v 1—The host name of the remote server was not found in the host table or on the

domain name server.v 2—The remote server did not receive a response from an authoritative server. An

attempt to obtain a response at a later time may succeed.v 3—An unrecoverable error occurred.v 4—The host name of the remote server is valid, but there is no corresponding IP

address.




Operator Response—Verify that TCP/IP is active and properly configured.

Client Administrator Response—Perform the actions corresponding to thefollowing error codes (code):v 1—Specify the correct host name or update the host table or domain name

server to include an entry for the host name.v 2—Verify that the local host information is defined in the host table or on the

domain name server. If you are using an external domain name server, verifythat its IP address is configured correctly and is accessible.

v 3—Record the message number. Contract your InfoSphere CDC administrator orIBM representative for assistance.

v 4—Verify that the host name entry on the domain server is correct and complete.

CHC7053ECHC7053E Failure to create TCP/IP socket. The returned errno is text for a valueof number.

Explanation—A communications link I/O task could not create a TCP/IP socket.

Message Variables:

text—The text error code returned as a result of not creating a TCP/IP socket.

number—The numeric error code returned as a result of not creating a TCP/IPsocket.




Client Administrator Response—Verify that the InfoSphere CDC address space isconfigured to use the correct TCP/IP stack by inspecting the SUBSYSTEM TCP/IPconfiguration control statement keyword.

CHC7054ECHC7054E Failure to get TCP/IP local host name. The returned errno is text for avalue of number.

Explanation—A communications link I/O task was not able to resolve the hostname.

Message Variables:

text—The text error code returned as a result of not resolving the host name.


number—The numeric error code returned as a result of not resolving the hostname.




Client Administrator Response—Verify that the host name is specified correctly inyour replication configuration.

CHC7055ECHC7055E TCP/IP failure to get local host information for server. The error codeis code.

Explanation—A communications link I/O task was not able to obtain informationabout the identified local server.

Message Variables:

server—The host name of the local server.

code—The error code as a result of the inability to obtain information about thelocal server. The possible codes and their explanations are as follows:v 1—The host name of the local server was not found in the host table or on the

domain name server.v 2—The local server did not receive a response from an authoritative server. An

attempt to obtain a response at a later time may succeed.v 3—An unrecoverable error occurred.v 4—The host name of the local server is valid, but there is no corresponding IP

address.




Client Administrator Response—Perform the actions corresponding to thefollowing error codes (code):v 1—Specify the correct host name or update the host table or domain name

server to include an entry for the host name.v 2—Verify that the local host information is defined in the host table or on the

domain name server. If you are using an external domain name server, verifythat its IP address is configured correctly and is accessible.

v 3—Record the message number. Contract your InfoSphere CDC administrator orIBM representative for assistance.

v 4—Verify that the host name entry on the domain server is correct and complete.


CHC7057ECHC7057E TCP/IP failure to connect to remote port number. The returned errno istext for a value of number.

Explanation—A communications link I/O task could not establish a connection tothe InfoSphere CDC TCP/IP Listener port on a remote server.

Message Variables:

number—The port number on the remote server.

text—The text error code returned as a result of not establishing a connection withthe remote server.

number—The numeric error code returned as a result of not establishing aconnection with the remote server.




Client Administrator Response—Verify that your replication configurationreferences the correct port number on the remote server, and the InfoSphere CDCTCP/IP Listener is active on the remote server.

CHC7058ECHC7058E Unable to bind TCP/IP socket to port number of host server.The returned errno is text for a value of number.

Explanation—A communications link I/O task could not bind its socket to theidentified port on the local server.

Message Variables:

number—The port number on the local server

server—The host name of the local server.

text—The text error code returned as a result of not being able to bind a socket.

number—The numeric error code returned as a result of not being able to bind asocket.





Client Administrator Response—If the TCP/IP stack is active and properlyconfigured, record the message number. Contact your InfoSphere CDCadministrator or IBM representative for assistance.

CHC7059ECHC7059E Failure in TCP/IP listen. The returned errno is text for a value ofnumber.

Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task could not listen onthe configured listening port.

Message Variables:

text—The text error code returned as a result of not being able to listen on theport.

number—The numeric error code returned as a result of not being able to listen onthe port.


System Action—The InfoSphere CDC TCP/IP Listener task is not initialized, andas a result, the InfoSphere CDC address space is not initialized.


Client Administrator Response—Verify that the service name for the InfoSphereCDC TCP/IP Listener port is configured correctly by inspecting theSERVICENAME TCP/IP configuration control statement keyword.

CHC7060ECHC7060E Failure in TCP/IP accept. The returned errno is text for a value ofnumber.

Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task or acommunications link I/O task could not accept a connection.

Message Variables:

text—The text error code returned as a result of not accepting a connection.

number—The numeric error code returned as a result of not accepting a connection.






CHC7061ECHC7061E Failure in TCP/IP send. The returned errno is text for a value ofnumber.

Explanation—A communications link I/O task could not send messages on itsTCP/IP socket.

Message Variables:

text—The text error code returned as a result of not sending messages.

number—The numeric error code returned as a result of not sending messages.





CHC7064ECHC7064E Failure in TCP/IP receive. The returned errno is text for a value ofnumber.

Explanation—A communications link I/O task could not receive messages on itsTCP/IP socket.

Message Variables:

text—The text error code returned as a result of not receiving messages.

number—The numeric error code returned as a result of not receiving messages.





CHC7065ECHC7065E Failure in TCP/IP close. The returned errno is text for a value ofnumber.

Explanation—A communications link I/O task was unable to close its TCP/IPsocket during termination.

Message Variables:


text—The text error code returned as a result of not closing the socket.

number—The numeric error code returned as a result of not closing the socket.


System Action—The communications link eventually terminates.



CHC7069ECHC7069E Overflow in TCP/IP receive. The buffer size is buffer. The incoming datasize is size.

Explanation—A communications link I/O task received a message that was largerthan the size of the buffer. In this case, size > buffer.

Message Variables:

buffer—The size, in bytes, of the buffer that receives messages.

size—The size, in bytes, of the incoming message.




Client Administrator Response—If TCP/IP is active and properly configured,record the message number. Contact the InfoSphere CDC administrator for theremote server or your IBM representative for assistance.

CHC7070ECHC7070E GETIBMOPT call failed. The error is text for a value of number.

Explanation—A GETIBMOPT call to obtain a list of active TCP/IP stacks wasunsuccessful during initialization of the TCP/IP InfoSphere CDC Listener (CLS)task.

Message Variables:

text—The text error code returned as a result of the unsuccessful GETIBMOPTcall.

number—The numeric error code returned as a result of the unsuccessfulGETIBMOPT call.





Client Administrator Response—If TCP/IP is active and properly configured,record the message number. Contact your InfoSphere CDC administrator or IBMrepresentative for assistance.

CHC7071ECHC7071E There are no TCP/IP stacks running.

Explanation—No active TCP/IP stacks were found during initialization of theInfoSphere CDC TCP/IP Listener (CLS) task.





Client Administrator Response—If TCP/IP is active and properly configured,record the message number. Contact your InfoSphere CDC administrator or IBMrepresentative for assistance.

CHC7072ECHC7072E The configured TCP/IP stack name was not found.

Explanation—The configured TCP/IP stack could not be found duringinitialization of the InfoSphere CDC TCP/IP Listener (CLS) task.

Message Variables:

name—The name of the configured TCP/IP stack.




Client Administrator Response—Verify that InfoSphere CDC is configured to usethe correct TCP/IP stack by inspecting the SUBSYSTEM TCP/IP configurationcontrol statement keyword.

CHC7073ECHC7073E The configured TCP/IP stack name was not active.

Explanation—The configured TCP/IP stack was found but not active duringinitialization of the InfoSphere CDC TCP/IP Listener (CLS) task.


Message Variables:






CHC7074ECHC7074E SETIBMOPT call failed. The error is text for a value of number.

Explanation—A SETIBMOPT call to select which TCP/IP stack to use wasunsuccessful during initialization of the InfoSphere CDC TCP/IP Listener (CLS)task.

Message Variables:

text—The text error code returned as a result of the unsuccessful SETIBMOPT call.

number—The numeric error code returned as a result of the unsuccessfulSETIBMOPT call.





CHC7075ICHC7075I The configured TCP/IP stack name was successfully selected.

Explanation—The configured TCP/IP stack was selected successfully duringinitialization of the InfoSphere CDC TCP/IP Listener (CLS) task. The stack will beused for all socket operations.

Message Variables:







CHC7077ICHC7077I Failure to obtain host name via gethostbyaddr. IP address ip will beused.

Explanation—A communications link I/O task could not use an IP address toretrieve a host name. The task will use the IP address instead of the host name.

Message Variables:

ip—The IP address used by the communications link I/O task.





CHC7078ICHC7078I TCP/IP connection was opened to partner port number, host server.

Explanation—A communications link I/O task opened a connection to its partnertask on the remote server.

Message Variables:

number—The port number on the remote server used for the connection.






CHC7079ICHC7079I TCP/IP connection was accepted from partner: server.

Explanation—A communications link I/O task accepted a connection from itspartner task on the remote server.

Message Variables:







CHC7081ECHC7081E A TCP/IP Listener child task has failed to complete startup after timeseconds.

Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task could not initializea communications link I/O task within the allotted amount of time.

Message Variables:

time—The maximum amount of time, in seconds, for the communications link I/Otask to initialize.





CHC7082ECHC7082E A TCP/IP Listener child task has failed to take its socket after timeseconds.

Explanation—A communications link I/O task started by the InfoSphere CDCTCP/IP Listener (CLS) task could not take its socket from the listener task withinthe allotted amount of time.

Message Variables:

time—The maximum amount of time, in seconds, for the communications link I/Otask to take its socket from the listener task.






CHC7083ECHC7083E Failure in TCP/IP takesocket. The error is text for a value of number.

Explanation—A communications link I/O task could not take its socket from theInfoSphere CDC TCP/IP Listener (CLS) task due to a problem calling takesocket.

Message Variables:

text—The text error code returned as a result of the unsuccessful TCP/IPtakesocket call.

number—The numeric error code returned as a result of the unsuccessful TCP/IPtakesocket call.





CHC7084ECHC7084E Failure to close TCP/IP socket. The error is text for a value of number.

Explanation—A communications link I/O task was unable to close its socket.

Message Variables:

text—The text error code returned as a result of not closing the TCP/IP socket.

number—The numeric error code returned as a result of not closing the TCP/IPsocket.


System Action—The communications link eventually terminates.



CHC7085ECHC7085E The local host name is of length byte1 which is too large for the internalbuffer size of byte2.

Explanation—The length of the local server host name for a communications linkI/O task is too large for a fixed-size internal buffer. In this case, byt1 > byt2.


Message Variables:

byte1—The length, in bytes, of the host name for the local server.

byte2—The size, in bytes, of the internal buffer.




Client Administrator Response—Specify an alias for the host name in the hosttable and reference the alias in your replication configuration. Alternatively,reference the IP address instead of the corresponding host name in the replicationconfiguration.

CHC7086ECHC7086E Failure in setsockopt for option name. The returned errno is text for avalue of number.

Explanation—A communications link I/O task was unable to set an option on itssocket.

Message Variables:

name—The option that could not be set.

text—The text error code returned as a result of not setting the option.

number—The numeric error code returned as a result of not setting the option.





CHC7087ECHC7087E Failure in ioctl. Reason: text.

Explanation—A communications link I/O task was unable to use ioctl tomanipulate its socket.

Message Variables:

text—A brief description of the operation that was attempted.






CHC7088ECHC7088E Failure in selectex. The returned errno is text for a value of number.

Explanation—A communications link I/O task encountered a problem when usingselectex to wait for activity on its socket.

Message Variables:

text—The text error code returned as a result of the problem with selectex.

number—The numeric error code returned as a result of the problem with selectex.





CHC7089WCHC7089W A pending TCP/IP connection has timed out and has been discarded.

Explanation—The InfoSphere CDC TCP/IP Listener (CLS) task received aconnection request but no data was received on the connection within the allottedtime of ten seconds.



System Action—The connection is discarded and normal processing resumes.

Operator Response—Contact your network administrator to verify that networktraffic is normal.

Client Administrator Response—If network traffic is normal, record the messagenumber and contact the InfoSphere CDC administrator for the remote server forassistance.


CHC7094ECHC7094E Communications link has missed one or more inbound messages, expectingmessage number expected, received message number received of size byte.

Explanation—A communications link I/O task received a message that was not inthe correct sequence. All messages sent through communications links containsequence numbers.

Message Variables:

expected—The sequence number of the message that was expected.

received—The sequence number of the message that was not expected.

byte—The size of the message, in bytes, that contained the unexpected sequencenumber.



Operator Response—Verify that the network is operational, and test theconnection to the remote server to determine whether or not packets have beendropped.

Client Administrator Response—If the network and remote server connection areworking properly, record the message number. Contact your InfoSphere CDCadministrator or IBM representative for assistance.

CHC7095ICHC7095I The remote system has reduced the maximum message size from byte1 tobyte2.

Explanation—The communications module on the remote server reduced themaximum size of a communications message during the connection process. Thechange in the maximum size of a communications message could be caused bydifferent versions of InfoSphere CDC running on the local and remote servers.However, replication between the two servers is supported.

Message Variables:

byt1—The maximum size of a communications message as defined on the localserver.

byt2—The maximum size of a communications message that has been imposed bythe remote server on the local server.






CHC7099ECHC7099E Unsupported communications protocol: protocol.

Explanation—A communications link I/O task was requested to use a protocolother than TCP/IP. TCP/IP is the only communications protocol supported byInfoSphere CDC.

Message Variables:

protocol—The communications protocol that is not supported by InfoSphere CDC.




Client Administrator Response—An incompatible version of InfoSphere CDC maybe running on the remote server. Record the message number and contact theInfoSphere CDC administrator for the remote server or your IBM representative forassistance.


“CHC9101I” on page 575“CHC9102I” on page 576“CHC9104I” on page 576“CHC9105I” on page 576“CHC9106I” on page 577“CHC9107I” on page 577“CHC9110T” on page 577“CHC9155E” on page 578“CHC9201I” on page 578“CHC9204W” on page 579“CHC9205I” on page 579“CHC9208I” on page 579“CHC9209I” on page 580“CHC9210E” on page 580“CHC9212E” on page 580“CHC9213E” on page 581“CHC9214E” on page 581“CHC9217E” on page 582“CHC9218E” on page 582“CHC9219E” on page 582“CHC9220W” on page 583“CHC9221W” on page 583“CHC9222W” on page 584


“CHC9228I” on page 584“CHC9229I” on page 584“CHC9230I” on page 585“CHC9231I” on page 585“CHC9500E” on page 586“CHC9502W” on page 586“CHC9504E” on page 587“CHC9506E” on page 587“CHC9510W” on page 588“CHC9512I” on page 588“CHC9514W” on page 589“CHC9516W” on page 589“CHC9518W” on page 589“CHC9521I” on page 590“CHC9522I” on page 590“CHC9523I” on page 591“CHC9524I” on page 591“CHC9525I” on page 592“CHC9526I” on page 592“CHC9527I” on page 593“CHC9528I” on page 593“CHC9600I” on page 594“CHC9601I” on page 594“CHC9605I” on page 595“CHC9606W” on page 595“CHC9607I” on page 595“CHC9608I” on page 596“CHC9609I” on page 596“CHC9610I” on page 597“CHC9611I” on page 597“CHC9612I” on page 597“CHC9613I” on page 598“CHC9614I” on page 598“CHC9615I” on page 598“CHC9616W” on page 599“CHC9618W” on page 600“CHC9619W” on page 600“CHC9650E” on page 600“CHC9651E” on page 601“CHC9652E” on page 601“CHC9653E” on page 601“CHC9654E” on page 602“CHC9655E” on page 602“CHC9656I” on page 603“CHC9657I” on page 603


“CHC9659E” on page 604“CHC9660W” on page 604“CHC9661I” on page 605“CHC9662I” on page 605“CHC9664I” on page 605“CHC9665I” on page 606“CHC9666E” on page 606“CHC9667E” on page 606“CHC9669E” on page 607“CHC9670W” on page 607“CHC9671W” on page 608“CHC9672I” on page 608“CHC9673E” on page 609“CHC9674E” on page 609“CHC9675E” on page 609“CHC9676W” on page 610“CHC9677W” on page 610“CHC9679W” on page 610“CHC9680W” on page 611“CHC9681I” on page 612“CHC9683W” on page 612“CHC9684W” on page 613“CHC9685W” on page 613“CHC9686W” on page 614“CHC9690E” on page 615“CHC9691E” on page 615“CHC9692I” on page 616“CHC9693I” on page 616“CHC9694W” on page 616“CHC9695W” on page 617“CHC9696E” on page 617“CHC9698I” on page 618“CHC9699E” on page 618“CHC9700E” on page 619“CHC9702E” on page 619“CHC9703E” on page 619“CHC9705E” on page 620“CHC9706E” on page 621“CHC9712E” on page 621“CHC9713E” on page 621“CHC9714W” on page 622“CHC9715E” on page 622“CHC9719E” on page 623“CHC9720E” on page 624“CHC9721E” on page 624


“CHC9722E” on page 625“CHC9723E” on page 625“CHC9733I” on page 626“CHC9742I” on page 626“CHC9743E” on page 627“CHC9744E” on page 627“CHC9745E” on page 628“CHC9746E” on page 628“CHC9751I” on page 628“CHC9753I” on page 629“CHC9756E” on page 629“CHC9757E” on page 630“CHC9758E” on page 630“CHC9764E” on page 630“CHC9765E” on page 631“CHC9766E” on page 631“CHC9767E” on page 632“CHC9768E” on page 632“CHC9769E” on page 632“CHC9770E” on page 633“CHC9776I” on page 633“CHC9777I” on page 634“CHC9778I” on page 634“CHC9779I” on page 635“CHC9780I” on page 636“CHC9786I” on page 636“CHC9787I” on page 637“CHC9788I” on page 638“CHC9789I” on page 638“CHC9795L” on page 639“CHC9796L” on page 639“CHC9798E” on page 640“CHC9799I” on page 640“CHC9800I” on page 641“CHC9801I” on page 641“CHC9802I” on page 642“CHC9803I” on page 643“CHC9804I” on page 644“CHC9805I” on page 645“CHC9812E” on page 646“CHC9813E” on page 646“CHC9814E” on page 647“CHC9815E” on page 647“CHC9816E” on page 647“CHC9817I” on page 648


“CHC9818I” on page 648“CHC9819I” on page 649“CHC9830I” on page 649“CHC9831I” on page 650“CHC9832I” on page 651“CHC9833I” on page 651“CHC9834I” on page 652“CHC9835I” on page 652“CHC9840I” on page 653“CHC9841I” on page 654“CHC9842I” on page 655“CHC9843I” on page 655“CHC9844I” on page 656“CHC9845I” on page 657“CHC9846I” on page 657“CHC9847I” on page 658“CHC9853I” on page 659“CHC9854I” on page 660“CHC9855I” on page 661“CHC9856I” on page 662“CHC9857I” on page 663“CHC9858I” on page 664“CHC9859I” on page 665“CHC9860I” on page 666

CHC9101ICHC9101I IBM InfoSphere CDC for z/OS VversionRnumberMlevel is initializing.

Explanation—IBM InfoSphere CDC is in the process of initializing. This is the firstmessage issued by IBM InfoSphere CDC after it has been started.

Message Variables:

version—The product version number.

number—The product release number.

level—The product modification level.






CHC9102ICHC9102I IBM InfoSphere Change Data Capture for z/OS initialization is complete.

Explanation—All necessary subcomponents have been initialized successfully.






CHC9104ICHC9104I IBM InfoSphere Change Data Capture for z/OS maintenance levels:

Explanation—The product maintenance levels currently in place for the productinstallation will be listed after this message. Maintenance level information isrecorded in the audit log, and may be requested by Technical Support fordiagnostic purposes.






CHC9105ICHC9105I text.

Explanation—Identifies product maintenance level information pertaining to theproduct installation. This information is generated during initialization phases, andis recorded in the audit log. Technical Support may request this information fordiagnostic purposes.

Message Variables:

text—A string that contains maintenance level information.






CHC9106ICHC9106I Configuration settings from member: name.

Explanation—Identifies configuration control statement keyword settings in thespecified member when InfoSphere CDC for z/OS was started. A number ofconfiguration control statement keyword settings are currently supported. Defaultand explicitly specified keyword settings are placed in the audit log. IBM TechnicalSupport may request this information for diagnostic purposes.

Message Variables:

name—The name of the member in the configuration control data set that containsthe statement.





CHC9107ICHC9107I Command from console number: command.

Explanation—The identified InfoSphere CDC command was submitted from thespecific console.

Message Variables:

number—The console number identifying the origin of the submitted command.

command—The name of the InfoSphere CDC command that was submitted from theidentified console.





CHC9110TCHC9110T Trace point was reached by name.

Explanation—The internal InfoSphere CDC task has reached a trace point. Thismessage is only issued if the product is being executed with external executiontracing activated. It does not require attention from the console operator or theclient administrator.

Message Variables:

name—The internal InfoSphere CDC task.






CHC9155ECHC9155E SAF userid id is not the same as metadata owner owner.

Explanation—An attempt has been made to start an InfoSphere CDC addressspace with a Security Access Facility (SAF) security identifier that is not the sameas the DB2 owner of the InfoSphere CDC metadata tables. To start an InfoSphereCDC address space, the security identifier and owner must be identical.

Message Variables:

id—The SAF security identifier that was used to start an InfoSphere CDC addressspace.

owner—The DB2 owner of the InfoSphere CDC metadata tables.


System Action—The InfoSphere CDC address space will not start.

Operator Response—Change the SAF security identifier or DB2 owner of themetadata tables so that they coincide. Restart the InfoSphere CDC address space.


CHC9201ICHC9201I Attempting to reconnect to DB2.

Explanation—InfoSphere CDC will make an attempt to reconnect to DB2. Thismessage is issued after InfoSphere CDC has received confirmation from DB2 that itis stopping.




Operator Response—See “CHC9220W” on page 583, “CHC9221W” on page 583 or“CHC9222W” on page 584 in the system log for more information about the DB2shutdown.



Related reference

“CHC9221W” on page 583“CHC9222W” on page 584“CHC9220W” on page 583

CHC9204WCHC9204W DB2 is not available; waiting for it to start.

Explanation—After creating an InfoSphere CDC address space, DB2 has not yetcompleted its initialization procedures.



System Action—InfoSphere CDC waits for DB2 to complete its initializationprocedures.

Operator Response—Monitor the system log for possible DB2 initializationproblems.


CHC9205ICHC9205I DB2 is now available.

Explanation—DB2 initialization procedures have been completed.






CHC9208ICHC9208I DB2 Log read retry successful. The processing continues.

Explanation—An attempt to reread data from the DB2 Log after having waitedseveral seconds for it to become available was successful.



System Action—InfoSphere CDC operations continue.




CHC9209ICHC9209I DB2 Log is unavailable; retrying in time seconds.

Explanation—An attempt to read data from the DB2 Log was unsuccessful, as itwas temporarily unavailable. Another attempt to read from the DB2 Log is madeafter the specified period of time has elapsed. If a subsequent attempt is successful,CHC9208I is generated.

Message Variables:

time—The number of seconds before the next attempt is made to read from theDB2 Log.


System Action—InfoSphere CDC waits until the next attempt is made to read fromthe DB2 Log, as indicated in the message text.




CHC9210ECHC9210E DB2 CAF type request has failed. ReturnCode=return, ReasonCode=reason.

Explanation—A CAF request has failed.

Message Variables:

type—The CAF requrest type.

return—The DB2 return code.

reason—The DB2 reason code.


System Action—The database connection is not initialized or started.

Operator Response—Note the DB2 return and reason codes. To determine thecorrective actions that should be taken, consult the appropriate DB2 messages andcodes manual and look for another message that may be placed in the system log(CHC9217E) for additional information. Retry the request.



CHC9212ECHC9212E The metadata owned by id is being used by another region.


Explanation—During initialization, InfoSphere CDC metadata that should be usedby an InfoSphere CDC address space is currently being used by another InfoSphereCDC address space.

Message Variables:

id—The security identifier that was specified during installation to allowInfoSphere CDC to access the DB2 catalog tables and log.


System Action—InfoSphere CDC waits for the STRTSDBM command to be issuedbefore attempting to access the metadata again.

Operator Response—Investigate the reasons why the InfoSphere CDC metadata islocked, and take the necessary corrective actions to unlock the metadata. Issue theSTRTSDBM command to continue InfoSphere CDC initialization, or issue theSHUTDOWN command to stop InfoSphere CDC.


CHC9213ECHC9213E DB2 Trace could not be started; DB2 error messages follow.

Explanation—A DB2 MONITOR TRACE command was not successfully issued.The command was rejected by DB2.



System Action—DB2 messages that provide an explanation as to why thecommand was not successful are directed to the system log.

Operator Response—Examine the DB2 messages directed to the system log todetermine the corrective actions that should be taken.


CHC9214ECHC9214E DB2 Trace could not be started. All OPx trace buffers are in use.

Explanation—A DB2 MONITOR TRACE command was not successfully issued,since none of the DB2 OPx buffers were available for the trace.



System Action—InfoSphere CDC stops DB2 activity.

Operator Response—Release at least one of the allocated DB2 OPx buffers. RestartInfoSphere CDC using the START command.



CHC9217ECHC9217E DB2 CAF Message: text.

Explanation—A message that has been generated by the DB2 Call Attach Facility(CAF). The message may provide more information about an unsuccessful DB2CAF request that is detailed in the CHC9210E message (OPEN, IFI-COMMAND,IFI-READA/IFI-READS, or CONNECT/CLOSE/DISCONNECT/TRANSLATE).

Message Variables:

text—The text message generated by DB2 CAF.



Operator Response—If the DB2 CAF message indicates that an error has occurred,consult the appropriate DB2 messages and codes manual to determine thecorrective actions that should be taken. Depending on the message that isgenerated, the InfoSphere CDC address space may have to be restarted using theSTART command.


CHC9218ECHC9218E name task is unable to initialize environment for READS IFI.

Explanation—The identified InfoSphere CDC task could not initialize itsenvironment to issue an IFI-READS request.

Message Variables:

name—The three-letter name of the InfoSphere CDC task that could not initialize itsenvironment.


System Action—If DLR is the identified task, DB2 Log caching is also disabled. IfDSL is the identified task, records from the DB2 Log cannot be read and as aresult, active replication for the subscription associated with the task unexpectedlyends.

Operator Response—Rebind the DB2 plan for the task or increase the storageallocated to the ECSA subpool 241.


CHC9219ECHC9219E DB2 IFI has returned non-zero status in a Log Record at position,QW0306RC = return, QW0306RS = reason, QW0306DG = code.

Explanation—The DB2 READS IFI has failed to successfully read a record from theDB2 Log.


The most common reason is a failure by the IFI to decompress the log record. Thisis indicated by these values showing in the message:

QW0306RC = X'00000008', QW0306RS = X'00C90063', QW0306DG =X'00C90064'

Message Variables:

position—The log position at which the read was attempted from the DB2 Log.This will be either an RBA or LRSN.

return—Return code from the log record.

reason—Reason code from the log record.

code—Diagnostic code from the log record.


System Action—If the log record was read by a mirroring subscription, thesubscription terminates abnormally. If the log record was read by the DB2 LogCache, the DB2 Log Cache terminates.


Client Administrator Response—If the failure is due to a decompression error, thetable or tables contained in the tablespace must be refreshed if replication is to beresumed. If other values are shown in the message, contact IBM Technical Support.

CHC9220WCHC9220W DB2 is undergoing a normal shutdown. Ending DB2 dependent tasks.

Explanation—Identifies the type of DB2 for z/OS shutdown that has occurred.This message is issued after InfoSphere CDC has received confirmation from DB2that it is stopping.



System Action—InfoSphere CDC responds by gracefully ending all source systemand target tasks, and disconnecting from DB2.



CHC9221WCHC9221W DB2 is undergoing a forced shutdown. Ending DB2 dependent tasks.








CHC9222WCHC9222W DB2 is undergoing an abnormal shutdown. Ending DB2 dependent tasks.







CHC9228ICHC9228I SVC DUMP REQUESTED, SEQ(number)

Explanation—A diagnostic SDUMP has been requested to collect diagnosticinformation.

Message Variables:

number—The sequence number of the diagnostic SDUMP. The sequence numberdecreases by one for each successive SDUMP. When the sequence number reacheszero, additional SDUMPs are not produced.



Operator Response—If a diagnostic SDUMP is generated, obtain it and contactyour InfoSphere CDC administrator if you require further assistance.


CHC9229ICHC9229I SVC DUMP IGNORED, SEQ(number)

Explanation—A diagnostic SDUMP has not been requested because the configuredlimit on the number of SDUMPS has been reached


Message Variables:






CHC9230ICHC9230I SVC DUMP COMPLETED SUCCESSFULLY, SEQ(number)

Explanation—A diagnostic SDUMP request has completed successfully.

Message Variables:

number—A diagnostic SDUMP request has completed successfully





CHC9231ICHC9231I SVC DUMP ENDED WITH RC (code), SEQ(number).

Explanation—The system did not collect a requested diagnostic SDUMP.

Message Variables:

code—The code that is returned as a result of an unsuccessful attempt to produce adiagnostic SDUMP.







CHC9500ECHC9500E TCP/IP name(string) service call has failed. The returned errno is textfor value of number.

Explanation—During execution, InfoSphere CDC issued an unsuccessful TCP/IPservice function call. This message identifies the function call that failed andreturns an error number that can be used to identify the source of the problem.

Message Variables:

name—The name of the service.

string—An optional text string that provides more detail about the intent of thefailed service function call.

text—The error text interpretation of the error number returned by the failedservice function call. This error text may be sufficient to determine the cause of theerror. If it is insufficient, then this error text or the error number can be used todiagnose the problem by consulting the appropriate manual.

number—The error number returned by the failed service function call. If the textstring has been provided, then it is the text interpretation of this error number.Note the error number and consult the appropriate TCP/IP manual to identify thesource of the problem.


System Action—The external request or internal process that led to the failedservice function call being issued is stopped.

Operator Response—Based on the interpretation of the specific TCP/IP servicefunction call, operations or network operations action may be required on the localor remote machine to correct the error. If the error can be corrected, then theterminated external request can be retried.

The following error codes indicate issues with the connection to the remotepartner:v ECONNRESET—The connection to the remote partner has been closed

unexpectedly. This indicates a failure in either the remote partner or thenetwork. InfoSphere CDC for z/OS is functioning correctly.

v ECONNREFUSED—The connection to the remote partner could not beestablished. This indicates a failure in either the remote partner or the network,or an incorrectly configured subscription. InfoSphere CDC for z/OS isfunctioning correctly. Check to ensure that the remote Listener is active.

Client Administrator Response—Based on the interpretation of the specificTCP/IP service function call, DBA administrative action may be required on thelocal or remote machine to correct the error. If the error can be corrected, then theterminated external request can be retried.

CHC9502WCHC9502W No defined TCP/IP Subsystem address spaces are active.

Explanation—During initialization, InfoSphere CDC was unable to detect an activeTCP/IP subsystem address space.




System Action—InfoSphere CDC operations continue without TCP/IPcommunications.

Operator Response—Convey this message to the system programmer who isresponsible for TCP/IP For MVS. After taking corrective actions, the STRTSCOMcommand should be issued in an attempt to reestablish TCP/IP communicationsfor InfoSphere CDC.


CHC9504ECHC9504E Specified TCP/IP Subsystem name is not defined.

Explanation—During initialization, InfoSphere CDC was unable to locate adefinition of the named TCP/IP subsystem address space specified through theSUBSYSTEM keyword in the TCP/IP statement contained in the CHCCMMxxmember.

Message Variables:

name—The name of the TCP/IP subsystem address space, as specified through theSUBSYSTEM keyword.



Operator Response—Determine the name of the TCP/IP subsystem address spaceto be used by InfoSphere CDC, and set the value of the SUBSYSTEM keyword tothe subsystem name. After taking corrective actions, the STRTSCOM commandshould be issued in an attempt to reestablish TCP/IP communications forInfoSphere CDC.


CHC9506ECHC9506E Specified TCP/IP Subsystem name is not Active.

Explanation—During InfoSphere CDC initialization, the named TCP/IP subsystemaddress space specified through the SUBSYSTEM keyword in the TCP/IPstatement contained in the CHCCMMxx member was not active.

Message Variables:

name—The name of the inactive TCP/IP subsystem address space, as specifiedthrough the SUBSYSTEM keyword.




Operator Response—Activate the TCP/IP subsystem address space or set thevalue of the SUBSYSTEM keyword to the name of an active address space. Aftertaking corrective actions, the STRTSCOM command should be issued in an attemptto reestablish TCP/IP communications for InfoSphere CDC.


CHC9510WCHC9510W TCP/IP maxdesc() service call could only set number socket handles.

Explanation—During initialization, InfoSphere CDC issued a TCP/IP maxdescservice function call to set the maximum number of sockets that can be used byInfoSphere CDC. The maximum number of sockets permitted by TCP/IP is lowerthan the number of sockets that was requested. This message indicates that adiminished number of sockets are available to InfoSphere CDC, as indicated by theTCP/IP maxdesc service function call.

Message Variables:

number—The number of sockets that can be used by InfoSphere CDC, as indicatedby the TCP/IP maxdesc service function call.


System Action—InfoSphere CDC continues executing, but with a reducedcapability to communicate with a large number of subscriptions.

Operator Response—This message should be conveyed to the system programmerwho is responsible for TCP/IP. If the problem is corrected, InfoSphere CDC mustbe stopped and then restarted again in order to regain the use of all availablesockets.


CHC9512ICHC9512I Using TCP/IP Subsystem address space name.

Explanation—During initialization, the product encountered more than onedefinition of a TCP/IP subsystem address space. The address space named in themessage text was active and being used by the product. The named address spaceis either the default or specified through the SUBSYSTEM keyword in the TCP/IPstatement contained in the CHCCMMxx member.

Message Variables:

name—The name of the active TCP/IP subsystem address space that is being usedby InfoSphere CDC.


System Action—InfoSphere CDC operations continue by using the named addressspace.




CHC9514WCHC9514W Due to prior noted errors, Auto-Discovery will not be available.

Explanation—During initialization, InfoSphere CDC encountered problems whileinitializing resources required for autodiscovery. For more information aboutautodiscovery, see your Access Manager documentation.



System Action—InfoSphere CDC continues executing, but autodiscovery will notbe enabled.

Operator Response—Examine preceding messages in the system log for furtherinformation about the inability to enable autodiscovery. Use the informationcontained in these messages to perform corrective actions.


CHC9516WCHC9516W Due to prior noted errors, Auto-Discovery will not be able to use the nameIP Interface.

Explanation—During initialization, InfoSphere CDC encountered problems whileinitializing resources for the named IP interface used for autodiscovery broadcasts.For more information about autodiscovery, see your Access Managerdocumentation.

Message Variables:

name—The name of the IP interface that could not be initialized for autodiscoverybroadcasts.


System Action—InfoSphere CDC continues executing, but autodiscoverybroadcasts will not be conducted through the named IP interface.

Operator Response—Examine preceding messages in the system log for furtherinformation about the IP interface used for autodiscovery broadcasts. Use theinformation contained in these messages to perform corrective actions.


CHC9518WCHC9518W IP Interface Name name does not correspond to any detected IP Interface.

Explanation—During initialization, InfoSphere CDC was unable to locate thenamed IP interface specified through the AUTODISCEXCLUDE keyword in the


TCP/IP statement contained in the CHCCMMxx member. The IP interface is usedfor autodiscovery broadcasts. For more information about autodiscovery, see yourAccess Managerdocumentation.

Message Variables:

name—The name of the IP interface, as specified through the AUTODISCEXCLUDEkeyword.


System Action—InfoSphere CDC continues executing.

Operator Response—An incorrect IP interface name specified through theAUTODISCEXCLUDE keyword might result in autodiscovery broadcasts beingconducted through an IP interface that should not be used for this purpose.Therefore, determine the correct IP interface name that you want to use forautodiscovery broadcasts, and modify the value of the AUTODISCEXCLUDEkeyword. The new value assigned to this keyword is established the next timeInfoSphere CDC is started.


CHC9521ICHC9521I TCP/IP Communication Support is inactive.

Explanation—During initialization, termination, or execution, InfoSphere CDCcommunications has either achieved an intended state, or is already in a requestedstate. This message may be generated when processing an operator command orduring normal initialization, execution or termination processing. It is issued toinform the operator of the current state of communication support withinInfoSphere CDC. Inactive indicates the current or achieved state of InfoSphereCDC’s communication support, which is currently not available. The STRTSCOMoperator command is required before any communication can occur.



System Action—InfoSphere CDC continues to run within the limitations of thecurrent state of the communication support.

Operator Response—If this message is generated as a result of having processedan operator command, use this message to determine the outcome of thatcommand.


CHC9522ICHC9522I TCP/IP Communication Support is already inactive.

Explanation—During initialization, termination, or execution, InfoSphere CDCcommunications has either achieved an intended state, or is already in a requestedstate. This message may be generated when processing an operator command orduring normal initialization, execution or termination processing. It is issued to


inform the operator of the current state of communication support withinInfoSphere CDC. Note that “already” appears in the message if the operatorentered a command requesting that InfoSphere CDC’s communication supportimplementation be changed to a new state, when that state had already beenachieved at the time the command was entered. Inactive indicates the current orachieved state of InfoSphere CDC’s communication support, which is currently notavailable. The STRTSCOM operator command is required before anycommunication can occur.






CHC9523ICHC9523I TCP/IP Communication Support is active.

Explanation—During initialization, termination, or execution, InfoSphere CDCcommunications has either achieved an intended state, or is already in a requestedstate. This message may be generated when processing an operator command orduring normal initialization, execution or termination processing. It is issued toinform the operator of the current state of communication support withinInfoSphere CDC. ’Active’ indicates the current or achieved state of InfoSphereCDC’s communication support, which is available.






CHC9524ICHC9524I TCP/IP Communication Support is already active.

Explanation—During initialization, termination, or execution, InfoSphere CDCcommunications has either achieved an intended state, or is already in a requestedstate. This message may be generated when processing an operator command orduring normal initialization, execution or termination processing. It is issued toinform the operator of the current state of communication support withinInfoSphere CDC. Note that “already” appears in the message if the operator


entered a command requesting that InfoSphere CDC’s communication supportimplementation be changed to a new state, when that state had already beenachieved at the time the command was entered. ’Active’ indicates the current orachieved state of InfoSphere CDC’s communication support, which is available.






CHC9525ICHC9525I TCP/IP Communication Support is quiescing.

Explanation—During initialization, termination, or execution, InfoSphere CDCcommunications has either achieved an intended state, or is already in a requestedstate. This message may be generated when processing an operator command orduring normal initialization, execution or termination processing. It is issued toinform the operator of the current state of communication support withinInfoSphere CDC. Note that “already” appears in the message if the operatorentered a command requesting that InfoSphere CDC’s communication supportimplementation be changed to a new state, when that state had already beenachieved at the time the command was entered. ’Quiescing’ indicates the currentor achieved state of InfoSphere Change Data Capture’s communication support.

Communications support is currently available, but is being gracefully terminated.This state is probably the result of issuing a SHUTDOWN=CNTRLD operator command.Any active communications using the communications medium are allowed tocontinue, but no new communication connections are allowed to start. When thelast active communication connection using the communication medium hasterminated, the current state automatically changes to Inactive.






CHC9526ICHC9526I TCP/IP Communication Support is already quiescing.


Explanation—During initialization, termination, or execution, InfoSphere CDCcommunications has either achieved an intended state, or is already in a requestedstate. This message may be generated when processing an operator command orduring normal initialization, execution or termination processing. It is issued toinform the operator of the current state of communication support withinInfoSphere CDC. Note that “already” appears in the message if the operatorentered a command requesting that InfoSphere CDC’s communication supportimplementation be changed to a new state, when that state had already beenachieved at the time the command was entered. ’Quiescing’ indicates the currentor achieved state of InfoSphere Change Data Capture’s communication support.

Communications support is currently available, but is being gracefully terminated.This state is probably the result of issuing a SHUTDOWN=CNTRLD operator command.Any active communications using the communications medium are allowed tocontinue, but no new communication connections are allowed to start. When thelast active communication connection using the communication medium hasterminated, the current state automatically changes to Inactive.






CHC9527ICHC9527I TCP/IP Communication Support is terminating.

Explanation—During termination, InfoSphere CDC communications has eitherachieved an intended state, or is already in a requested state. This message may begenerated when processing an operator command or during normal terminationprocessing. It is issued to inform the operator of the current state ofcommunication support within InfoSphere CDC.






CHC9528ICHC9528I TCP/IP Communication Support is already terminating.


Explanation—During termination, InfoSphere CDC communications has eitherachieved an intended state, or is already in a requested state. This message may begenerated when processing an operator command or during normal terminationprocessing. It is issued to inform the operator of the current state ofcommunication support within InfoSphere CDC.






CHC9600ICHC9600I name command was accepted.

Explanation—InfoSphere CDC has received the START, MODIFY, or STOPcommand from the console operator.

Message Variables:

name—The name of the command.


System Action—The command is either performed or rejected if an error isencountered.


Client Administrator Response—Monitor the product administration log throughManagement Console to confirm that the command was performed.

CHC9601ICHC9601I An internal shutdown request was received from name task.

Explanation—An internal request was received from the named InfoSphere CDCtask to stop the product address space.

Message Variables:

name—The name of the InfoSphere CDC task that submitted the request to stop theproduct address space.


System Action—The InfoSphere CDC address space stops. All active replication isstopped.


Operator Response—Check the logs for other messages that provide moreinformation about the shutdown. Restart the InfoSphere CDC address space usingthe START command.


CHC9605ICHC9605I Storage Manager is not active.

Explanation—The STGMGR command was entered but the Storage Manager is notactive.






CHC9606WCHC9606W User name is not an active Storage Manager user.

Explanation—The user name specified on a STGMGR, STATUS,NAME=name commandis not an active Storage Manager user.

Message Variables:

name—A user name.



Operator Response—Issue a STGMGR,STATUS command to get a list of all activeusers.


CHC9607ICHC9607I Storage Manager information:

Explanation—This message is issued in response to a STGMGR,STATUS command. Itis immediately followed by further messages detailing the Storage Manager status.







CHC9608ICHC9608I configured size: size, used: used (percentage%), free extents: ext,overhead: amount.

Explanation—This message is issued in response to a STGMGR,STATUS command. Itdisplays the current configured size and usage of the Storage Manager.

Message Variables:

size—The currently configured storage size of the Storage Manager.

used—The amount of storage currently used by the Storage Manager.

percentage—The percentage of currently configured storage used by StorageManager.

amount—The amount of storage used by the Storage Manager to manage itsfunctions.





CHC9609ICHC9609I users: count, maximum used: used, 31–bit spills: spills

Explanation—This message is issued in response to a STGMGR,STATUS command. Itdisplays the current number of users and maximum usage of the Storage Manager.

Message Variables:

count—The current number of users of the Storage Manager.

used—The maximum amount of storage used by Storage Manager for thisexecution of InfoSphere CDC for z/OS.

spills—The number of times the Storage Manager has had to obtain below thebar storage to service its users for this execution of InfoSphere CDC for z/OS.



Operator Response—Too many spills to 31–bit storage will affect performance. Themaximum amount used can be used as guidance to adjust the initial storage spaceallocated to the Storage Manager.



CHC9610ICHC9610I waiting users: users, number of waits: number, average wait time:time sec.

Explanation—This message is issued in response to a STGMGR,STATUS command. Itdisplays information about Storage Manager user waits.

Message Variables:

users—The current number of users waiting for Storage Manager space.

number—The number of times Storage Manager users have had to wait for storagefor this execution of InfoSphere CDC for z/OS.

time—The average time Storage Manager users have had to wait for storage forthis execution of InfoSphere CDC for z/OS.



Operator Response—A large amount of waits or waiting users can indicate thattoo little space has been allocated to the Storage Manager. In this case, considerincreasing the amount if space allocated to the Storage Manager.


CHC9611ICHC9611I NAME: name - description.

Explanation—This message is issued in response to a STGMGR,STATUS command. Itdisplays the name and description of a Storage Manager user.

Message Variables:

name—The name of the user passed when it connected to the Storage Managerspace.

description—The description of the user passed when it connected to the StorageManager.





CHC9612ICHC9612I connected since: connection, waiting since: waiting.

Explanation—This message is issued in response to a STGMGR,STATUS command. Itdisplays connection and waiting times for a Storage Manager user.


Message Variables:

connection—The date and time the user connected to the Storage Manager.

waiting—If the user is waiting, the data and time it started waiting. Otherwise, itis blank.





CHC9613ICHC9613I Users statistics:

Explanation—This message is issued in response to a STGMGR,STATUS command. Itsignified the start of the user statistics display.






CHC9614ICHC9614I Name Init Limit Current Max Writes Reads Ext Wait.

Explanation—This message is issued in response to a STGMGR,STATUS command. Itdisplays the header for the Storage manager users report. It is followed by one ormore instances of message CHC9615I.






CHC9615ICHC9615I name initial limit current maximum writes reads ext wait.

Explanation—This message is issued in response to a STGMGR,STATUS command. Itdisplays statistics for a Storage Manager user.


Message Variables:

name—The name the user passed when it connected to the Storage Manager.

initial—The initial space requested by the user when it connected to the StorageManager.

limit—The maximum space requested by the user passed when it connected to thestorage manager.

current—The current space being used by this user.

maximum—The maximum space used by this user since it connected to the StorageManager.

writes—The number of Storage Manager writes performed by this user since itconnected.

reads—The number of Storage Manager reads performed by this user since itconnected.

ext—The number of times the Storage Manager had to obtain storage below thebar for this user since it connected.

wait—’Yes’ will be displayed if this user is currently waiting for Storage Managerspace, otherwise ’No’ will be displayed.





CHC9616WCHC9616W The Storage Manager could not obtain size megabytes of above the barstorage due to MEMLIMIT constraints. Below the bar storage will be used for thestorage cache.

Explanation—The Storage Manager could not obtain the amount of 64–bit storagespecified in the STG64LIMIT parameter because the operating systemMEMLIMIT prevented it. The Storage Manager will operate with 31–bit storageonly.

Message Variables:

size—The size specified on the STG64LIMIT configuration parameter.



Operator Response—Either reduce the amount of space requested on theSTG64LIMIT parameter or increase the operating system MEMLIMIT.



CHC9618WCHC9618W Storage Manager usage has reached number% of capacity.

Explanation—Storage Manager use has reached the specified percentage.

Message Variables:

number—The percentage of configured Storage Manager space currently in use.



Operator Response—When usage hits 100%, the Storage Manager will start toobtain 31–bit storage to satisfy further requests. If this happens frequently, considerincreasing the amount of space allocated by raising the size specified in theSTG64LIMIT parameter.


CHC9619WCHC9619W Storage Manager usage has fallen below number% of capacity.

Explanation—Storage Manager use has fallen below the specified percentage.

Message Variables:

number—The percentage of configured Storage Manager space currently in use.





CHC9650ECHC9650E Invalid Command/Statement Parsing Structure was detected.

Explanation—The structure that is used to parse commands received from theoperator console or PDS (partitioned data set) member has unexpectedly failed.This is an internal InfoSphere CDC problem.



System Action—The command is not performed.

Operator Response—Note the message number and contact your InfoSphere CDCadministrator if you require further assistance.



CHC9651ECHC9651E Unable to open PDS Member member in the CHCCNTRL data set.

Explanation—A PDS (partitioned data set) member does not exist or theCHCCNTRL data set does not reference the correct member.

Message Variables:

member—The PDS member that it is unable to open.


System Action—InfoSphere CDC is in an inoperable state.

Operator Response—Stop InfoSphere CDC and resolve the problem by eitherrecreating the PDS member or correcting the reference to the member. RestartInfoSphere CDC after taking the corrective action.


CHC9652ECHC9652E Unable to locate the type statement in CHCCNTRL name member.

Explanation—A configuration control statement in a PDS (partitioned data set)member cannot be located.

Message Variables:

type—The type of configuration control statement that is missing in the PDSmember.

name—The PDS member that has a missing configuration control statement.



Operator Response—Add the missing configuration control statement to the PDSmember, and then reinitialize the communication and/or DBMS environment.


CHC9653ECHC9653E The type statement is missing the required key keyword.

Explanation—A required keyword was omitted from an operator consolecommand or configuration control statement in a PDS (partitioned data set)member.

Message Variables:


type—The type of configuration control statement or the operator consolecommand that has a missing keyword.

key—The keyword that is missing from the operator console command orconfiguration control statement.


System Action—The operator console command is not performed. If the keywordis missing from a configuration control statement, InfoSphere CDC is in aninoperable state.

Operator Response—Issue the operator console command again with the keywordthat is required or correct the configuration control statement in the PDS member.


CHC9654ECHC9654E The type statement keyword key has a value which is not within the rangeminimum:maximum.

Explanation—A keyword specified in an operator console command orconfiguration control statement in a PDS (partitioned data set) member has beenassigned a value that is outside of the acceptable range. This message applies tothose keywords that can only be set to a value within a limited range. Forexample, PALRETPD, which can only be set to a value from 1 to 9999 inclusively,and BUFTHRESHOLD, which can only be set to a value from 1 to 99 inclusively.

Message Variables:

type—The type of configuration control statement or the operator consolecommand that has a keyword value outside of the allowable range.

key—The keyword in the operator console command or configuration controlstatement that has a value outside of the allowable range.

minimum—The minimum value that can be assigned to the keyword.

maximum—The maximum value that can be assigned to the keyword.


System Action—The value is not assigned to the keyword. The configurationcontrol statement may be processed or the console command may be performedwith a default value assigned to the keyword in place of the specified value.


Client Administrator Response—Correct the configuration control statement orreissue the console command with a valid keyword value as indicated in themessage text.

CHC9655ECHC9655E A corrupted Command/Statement Parsing Structure was detected, Type typeStatement name


Explanation—An error was detected during validation of a keyword submittedthrough a command or statement. The data type of the keyword value is notcompatible.

Message Variables:

type—The data type of the keyword value specified through the command orstatement.

name—The name of the command or statement that contained an incorrect keywordvalue.





CHC9656ICHC9656I key is not a valid value for the name command.

Explanation—An incorrect keyword value was detected in the specified command.

Message Variables:

key—The keyword that was assigned an incorrect value.

name—The name of the command that contained the incorrect keyword value.



Operator Response—Submit the command again with the correct keyword values.


CHC9657ICHC9657I An unrecognized keyword key was encountered.

Explanation—A configuration control statement in a PDS (partitioned data set)member contains an unrecognized keyword. Configuration control statements areread during InfoSphere CDC initialization. These statements can be customized toyour working environment.

Message Variables:

key—The keyword in the configuration control statement that is not recognized byInfoSphere CDC.



System Action—The keyword is ignored.

Operator Response—Correct the keyword in the statement that cannot berecognized by InfoSphere CDC. If necessary, restart InfoSphere CDC if initializationcould not be completed as a result of this error.


CHC9659ECHC9659E Unrecognized command name.

Explanation—A submitted console command could not be recognized. IBMTechnical Support may refer to this message for diagnostic purposes.

Message Variables:

name—The name of the console command that could not be recognized.



Operator Response—For information about the console commands that aresupported by InfoSphere CDC, see InfoSphere CDC commands.

Client Administrator Response—NoneRelated concepts

“InfoSphere CDC commands” on page 91

CHC9660WCHC9660W Invalid or unsupported task name: name.

Explanation—A submitted TRACE command invocation contains a reference to aninvalid or unsupported task. IBM Technical Support may refer to this message fordiagnostic purposes.

Message Variables:

name—The name of the invalid or unsupported task specified in the TRACEcommand.


System Action—The TRACE command is not applied to the specified task. If a listof tasks is provided, the command is applied to any valid task in the list.

Operator Response—See the TRACE command to determine the tasks that can bespecified.



Related reference

“TRACE” on page 42

CHC9661ICHC9661I Trace status was modified for task name.

Explanation—A TRACE command invocation applied to the specified task wassuccessful. IBM Technical Support may refer to this message for diagnosticpurposes.

Message Variables:

name—The name of the task referenced in the TRACE command.





CHC9662ICHC9662I Active traces for task name: pt1, pt2, pt3,...

Explanation—Identifies the active trace points for the specified task. This messageis generated when the TRACE console command is invoked with the LIST option.IBM Technical Support may refer to this message for diagnostic purposes.

Message Variables:

name—The name of the task referenced in the TRACE command.

pt1, pt2, pt3,..—The active trace points for the task.





CHC9664ICHC9664I A Trace request was queued for delivery to the next qualifying task.

Explanation—The TRACE command was applied to a specific InfoSphere CDCtask in an inactive state. The request was queued, and will wait for the next activetask.







CHC9665ICHC9665I GTF is not active; trace data will not be captured until GTF is started.

Explanation—InfoSphere CDC trace information was sent to an inactive GTF. GTFmust be active in order to accept trace information from InfoSphere CDC.



System Action—InfoSphere CDC trace information is not captured.

Operator Response—Activate GTF by specifying the appropriate parameters oruse the InfoSphere CDC TRACEDEST command to direct trace information to aSPOOL data set.


CHC9666ECHC9666E An error occurred processing the name statement.

Explanation—An error occurred during processing of a configuration controlstatement.

Message Variables:

name—The name of the configuration control statement that was being processedwhen the error occurred.


System Action—Processing of the identified configuration control statement isincomplete.


Client Administrator Response—Use other related messages placed in the productadministration log to determine the cause of the error. To ensure that theconfiguration control statement is processed successfully, inform the operator thatthe InfoSphere CDC address space must be reinitialized after the problem has beendetermined and resolved.

CHC9667ECHC9667E The value in keyword key for statement name is invalid.


Explanation—A keyword value in the identified configuration control statementhas been specified incorrectly. This message applies to those keywords that canonly be set to specific values. For example, USELOADER, which can only be set toYES or NO.

Message Variables:

key—The name of the keyword in the configuration control statement that wasassigned an incorrect value.

name—The name of the configuration control statement that has an incorrectkeyword value.


System Action—Processing of the identified configuration control statement isincomplete.


Client Administrator Response—To ensure that the configuration controlstatement is processed successfully, inform the operator that the InfoSphere CDCaddress space must be reinitialized after the problem has been determined andresolved.Related concepts

“Modifying general product configuration control statements” on page 27“IBM InfoSphere Change Data Capture installation or upgrade” on page 1

CHC9669ECHC9669E The CVF start request could not be completed.

Explanation—An InfoSphere CDC task for testing communications with a remoteserver could not be started. A maximum of eight tasks for runningcommunications tests can be active on the local server at the same time. Thismessage is generated when eight tasks are currently running and an attempt ismade to start another task for testing communications with a remote server.Communications tests are performed by running the STRTSCVF console command.For information about this command, contact your IBM representative.



System Action—The InfoSphere CDC task for testing communications is notstarted.

Operator Response—Wait until one of the active InfoSphere CDC tasks for testingcommunications terminates and then issue the STRTSCVF console command again.


CHC9670WCHC9670W Task name cannot process the command at this time; try again later.


Explanation—A MODIFY console command issued a DEBUG, TRACE, or REPORTcommand to a task within the InfoSphere CDC address space. The task was in astate that did not allow processing of the command.

Message Variables:

name—The three-letter task identifier.


System Action—The command is ignored and normal processing continues.

Operator Response—Issue the command later.


CHC9671WCHC9671W The intended recipient of a name command does not exist. The intendedrecipient is task id.

Explanation—A console command could not be directed to the identifiedInfoSphere CDC task. The task is not running in the InfoSphere CDC addressspace. When invoking the REPORT or TRACE command, you must identify thetasks for which information is returned.

Message Variables:


task—The name of the task that was not running in the InfoSphere CDC addressspace when the command was invoked.

id—The task identifier.


System Action—The command is not performed. Active replication continues.

Operator Response—Reissue the command by identifying tasks that are runningin the InfoSphere CDC address space.


CHC9672ICHC9672I Command name was processed successfully.

Explanation—The previously entered console command name was processedsuccessfully.

Message Variables:







CHC9673ECHC9673E An error occurred while processing the name command.

Explanation—The previously entered console command name encountered an error.

Message Variables:




Operator Response—This message will be accompanied by error messagesdetailing the exact problem. Check for these messages in the system log and theevent log for more information.


CHC9674ECHC9674E POSITION should contain 1 to 16 hexadecimal digits.

Explanation—The SETLOGPOS command was entered with an invalid POSITIONvalue.




Operator Response—Reenter the command with the proper POSITION value.


CHC9675ECHC9675E A duplicate keyword key was detected for command name.

Explanation—A duplicate keyword was specified on the specified command

Message Variables:

key—The name of the duplicate keyword.





Operator Response—Reenter the command with the proper syntax.


CHC9676WCHC9676W A duplicate name statement was detected in CHCCNTRL's member member.

Explanation—A duplicate statement or a statement that could not be recognizedhas been detected in a configuration member.

Message Variables:

name—The configuration control statement that is either duplicated orunrecognized

member—The member that contains the duplicated or unrecognized statement.


System Action—The statement is ignored.



CHC9677WCHC9677W An unrecognized statement statement was detected in CHCCNTRL's namemember.

Explanation—A duplicate statement or a statement that could not be recognizedhas been detected in a configuration member.

Message Variables:

statement—The configuration control statement that is either duplicated orunrecognized.

name—The member that contains the duplicated or unrecognized statement.


System Action—The statement is ignored.



CHC9679WCHC9679W The MBR keyword must be specified with a non-zero value if and only if theconnected DB2 subsystem is a member of a Data Sharing Group.

Explanation—Either:


1. The ENDUR command has been issued without the MBR keyword specified, orwith it specified with a value of 0000, and the connected DB2 subsystem is amember of a DB2 Data Sharing Group, or

2. The ENDUR command has been issued with the MBR keyword specified andwith a value other than 0000, and the connected DB2 subsystem is not amember of a DB2 Data Sharing Group.


Message Destination—System Console that originated the ENDUR command.

System Action—The ENDUR command is ignored.

Operator Response—Reissue the ENDUR command with the MBR keywordspecified or omitted, as is appropriate for the operational environment of theconnected DB2 subsystem.


“ENDUR—End unit of recovery” on page 120

CHC9680WCHC9680W URID=X'urid' and MBR=X'mbrid' do not identify an incomplete unit ofrecovery in subscription name

Explanation—While processing an ENDUR command, a subscription’s stagingspace has been examined to locate a Unit of Recovery with the specified URID andMember Identifier, but none was found.

Message Variables:

urid—The URID of the Unit of Recovery that was specified on the ENDURcommand.

mbrid—The Member Identifier of a DB2 subsystem within a Data Sharing Groupthat was specified on the ENDUR command.

name—The subscription name that was specified on the ENDUR command.


System Action—The ENDUR command is ignored.

Operator Response—Verify that the proper URID and Member Identifier werecorrectly specified, and reissue the ENDUR command with them specifiedcorrectly, if they were not. These items of information can be obtained from aStaging Space Report.



Related reference


CHC9681ICHC9681I A SQLstatement has been generated for the incomplete unit of recovery withURID=X'urid' and MBR=X'mbrid' within subscription name

Explanation—Processing for an ENDUR command has successfully located thespecified Unit of Recovery within the specified subscription’s Staging Space, andgenerated the effective SQL statement that was requested.

Message Variables:

SQLstatement—The effective SQL statement action, either COMMIT or ROLLBACKthat was requested on the ENDUR command.

urid—The URID of the Unit of Recovery that was specified on the ENDURcommand.

mbrid—The Member Identifier of a DB2 subsystem within a Data Sharing Groupthat was specified on the ENDUR command.

name—The subscription name that was specified on the ENDUR command.


System Action—Changes within the Unit of Recovery that are currently in theStaging Space will undergo disposition processing, as requested on the ENDURcommand.




CHC9683WCHC9683W value is an incorrectly specified Numeric Data value for the key keywordof the statement statement in the name member.

Explanation—An incorrect value has been specified for the named keyword in aconfiguration control statement contained in a PDS (partitioned data set) member.Configuration control statements are read during InfoSphere CDC initialization.These statements can be customized to your working environment.

Message Variables:

value—The value assigned to the keyword that is not accepted by InfoSphereCDC.

key—The keyword in the configuration control statement assigned a value that isnot accepted by InfoSphere CDC.

statement—The configuration control statement that contains the keyword with theincorrect value.


name—The name of the PDS member that contains the keyword with the incorrectvalue.



Operator Response—Modify the configuration control statement to assign a validvalue to the named keyword. If necessary, restart InfoSphere CDC if initializationwas not successfully completed as a result of this condition. Note that subsequentmessages in the system log will indicate an initialization failure.


CHC9684WCHC9684W value is an incorrectly specified Alphanumeric Data value for the keykeyword of the statement statement in the name member.


Message Variables:









CHC9685WCHC9685W value is an incorrectly specified IP Address value for the key keywordof the statement statement in the name member.

Explanation—An incorrect value has been specified for the named keyword in aconfiguration control statement contained in a PDS (partitioned data set) member.


Configuration control statements are read during InfoSphere CDC initialization.These statements can be customized to your working environment.

Message Variables:









CHC9686WCHC9686W value is an incorrectly specified Method Character value for the keykeyword of the statement statement in the name member.


Message Variables:










CHC9690ECHC9690E An unexpected ICM Request was received by task1 Task, from task2 Task,Class (class), Type(type), Modifier modifier.

Explanation—An internal InfoSphere CDC task has received an unrecognized ICMrequest from another task. The message text identifies the tasks that sent andreceived the request. It also identifies the message type and class.

Message Variables:

task1—The three-letter code that identifies the task that received the unrecognizedICM

task2—The three-letter code that identifies the task that received the unrecognizedICM

class—The first level of message ICM type information. For each type of messagein the first level, there is a subset of message types in the second level.

type—The second level of message type information. For each type of message inthe first level, there is a subset of message types in the second level.

modifier—Internal modifier information associated with the message class type.


System Action—The request is ignored and placed in the system log.



CHC9691ECHC9691E An unexpected ICM Reply was received by task Task, Class(class),Type(type), Modifier modifier, Return Code: return, Reason Code: reason

Explanation—An internal InfoSphere CDC task has received an unrecognized ICMrequest from another task. The message text identifies the tasks that received therequest. It also identifies the message type and class.

Message Variables:

task—The three-letter code that identifies the task that sent the unrecognized ICM.

class—The first level of message ICM type information. For each type of messagein the first level, there is a subset of message types in the second level.


type—The second level of message type information. For each type of message inthe first level, there is a subset of message types in the second level.

modifier—The internal modifier information associated with the message classtype.

return—The InfoSphere CDC return code.

reason—The InfoSphere CDC reason code.


System Action—The reply is placed in the system log.



CHC9692ICHC9692I DBMS has not been started; the request was rejected.

Explanation—A request was sent to the DBMS environment after an InfoSphereCDC address space was created without the environment being initialized.



System Action—The request sent to the DBMS environment is rejected.

Operator Response—Initialize the DBMS environment.


CHC9693ICHC9693I COMM has not been started; the request was rejected.

Explanation—A request was sent to the communications environment after anInfoSphere CDC address space was created without the environment beinginitialized.



System Action—The request sent to the communications environment is rejected.

Operator Response—Initialize the communications environment.


CHC9694WCHC9694W Communications API name request failed. The return code is code for valueof number.


Explanation—A communications API request was unsuccessful.

Message Variables:

name—The name of the communications API request that was unsuccessful.

code—The text error code returned as a result of the unsuccessful API request.

number—The numeric error code returned as a result of the unsuccessful APIrequest.


System Action—Replication does not start.



CHC9695WCHC9695W CHC "name" Request has failed. The return Code is code.

Explanation—While InfoSphere CDC was running, an internal request was issuedfor the specified native service function call. The native service function call wasnot successfully completed. The message text identifies the native service functioncall that failed.

Message Variables:

name—The name of the internal service which failed.

code—The numeric code that reveals why the native service function call did notcomplete successfully.


System Action—The external request or internal process that caused the nativeservice function call to fail is stopped.

Operator Response—This message may be preceded or followed by additionalmessages that provide more information about the failure of the native servicefunction call. Interpretation of this and other messages may help to determinewhat corrective actions should be performed. However, the failure of a nativeservice function call usually indicates a problem with InfoSphere CDC. Note themessage number and contact your InfoSphere CDC administrator if you requirefurther assistance.


CHC9696ECHC9696E Data Protocol API name request has failed. The return code is code.

Explanation—An error occurred as a result of a data protocol API request.


Message Variables:

name—The name of the data protocol API request.

code—The return code resulting from the data protocol API request.





CHC9698ICHC9698I Address space is shutting down. The request was rejected.

Explanation—A console command was not performed. The product address spacewas in the process of shutting down and could not accept the command.



System Action—The console command is ignored.



CHC9699ECHC9699E An unexpected message of type type was received from the remote partner.

Explanation—A subscription received an unexpected message from the remotesystem. This most often happens when a subscription is shut down and quicklyrestarted. The target side of the subscription sometimes fails to completelyterminate before the source side restarts. The target side of the subscription, whichis in the process of shutting down, is not expecting to receive a request from thesource to start the subscription.

Message Variables:

type—The type of message that was unexpectedly received from another server.


System Action—Active replication terminates abnormally.


Client Administrator Response—Wait five minutes to allow the target side of thesubscription to completely terminate, then try to restart the subscription. If theproblem persists, record the message number and contact your administrator orSupport representative for assistance.


CHC9700ECHC9700E LE/370 CEEPIPI "name" Request failed. The return Code is code.

Explanation—While InfoSphere CDC was running, a service function call to theLanguage Environment Pre-Initialization Program Interface was issued. TheCEEPIPI service function call was not successfully completed. The function thatfailed is identified in the message text.

Message Variables:

name—The name of the CEEPIPI service that failed.

code—The numeric code that identifies why the CEEPIPI service function callfailed.


System Action—An error executing a CEEPIPI service function call usually meansthat a severe error has occurred. In this case, InfoSphere CDC stops running.

Operator Response—Diagnostic data should be collected for analysis andresolution. The following diagnostic data should be collected before contactingyour InfoSphere CDC administrator: The dump of the InfoSphere CDC addressspace, if one was created. The system log messages generated up to the pointwhere InfoSphere CDC detected the failed CEEPIPI service function call. Aftertaking the necessary corrective actions, start InfoSphere CDC to continueoperations.


CHC9702ECHC9702E Invalid content in message field name of message type type was receivedby the describe receiver.

Explanation—The identified InfoSphere CDC component received an internalmessage containing invalid data.

Message Variables:

name—The field in the internal message that contains the invalid data.

type—The type of message that contains the field.


System Action—Replication terminates abnormally.



CHC9703ECHC9703E DB2 Log Cache DLL "name" request has completed abnormally. The returncode is code for value of number.


Explanation—A call to the DB2 Log cache DLL was unsuccessful. The type ofrequest that could not be completed and the return code are identified.

Message Variables:

name—The name of the Log Cache DLL request the completed abnormally.


number—The numeric return code generated from the unsuccessful call.


System Action—If the message is issued by a DSL task, the associated subscriptionceases to use the DB2 Log Cache. If the message is issued by the DLR task, theDB2 Log Cache is deactivated.


Client Administrator Response—Further investigation is required. Record themessage number, the type of request that was unsuccessful, and the return code.Contact your InfoSphere CDC administrator or IBM representative for assistance.

CHC9705ECHC9705E LE/370 Enclave for CHC type Task has terminated abnormally. The LE/370Reason code is code.

Explanation—While running InfoSphere CDC, a call_main or call_sub servicefunction call to the Language Environment Pre-Initialization Program Interface wasissued, naming an InfoSphere CDC task. This task exists in an enclave, as definedin the Language Environment publications. The task’s enclave was terminatedabnormally. The message text identifies the internal InfoSphere CDC task in theenclave that ended abnormally.

Message Variables:

type —The three-letter code identifying the type of the subtask whose enclave wasterminated abnormally.

code —The numeric code that identifies why the program enclave was abnormallyterminated.


System Action—An abnormal termination of a program enclave usually meansthat a severe error has occurred. The program enclave is part of the programminglogic of InfoSphere CDC. In this case, InfoSphere CDC will stop running.

Operator Response—Diagnostic data should be collected for analysis andresolution. The following diagnostic data should be collected before contactingyour InfoSphere CDC administrator: The dump of the InfoSphere CDC addressspace, if one was created. The system log messages generated up to the pointwhere the enclave was abnormally terminated. After taking the necessarycorrective actions, start InfoSphere CDC to continue operations.



CHC9706ECHC9706E name service call has failed. The return code = code, reason code =reason.

Explanation—A call to the specified system service failed with the specified returncode and reason code.

Message Variables:



reason—The reason code.


System Action—Unpredictable. Depends on the nature of the failure.



CHC9712ECHC9712E A fatal error was detected in function name() at line number number.

Explanation—A fatal error has occurred.

Message Variables:

name—The name of the function in which the error occurred.

number—The line number where the error occurred.


System Action—Dependent on where the error has occurred.



CHC9713ECHC9713E C library name(module) function failed. The returned errno is text forvalue of number.

Explanation—A call to the specified C library service function was unsuccessful.The type of request that could not be completed and the return code are identified.

Message Variables:

name—The name of the C-language load module management function that failed.


module—The name of the load module that was not successfully managed.


number—The numeric return code generated from the unsuccessful call.


System Action—The external request or internal process that caused the functioncall to fail is stopped.

Operator Response—This message may be preceded or followed by additionalmessages that provide more information about the failure of the function call.Interpretation of this and other messages may help to determine what correctiveactions should be performed. However, the failure of a function call usuallyindicates a problem with the programmed logic in InfoSphere CDC. Note themessage number and contact your InfoSphere CDC administrator if you requirefurther assistance.


CHC9714WCHC9714W Message from name Task => text

Explanation—While InfoSphere CDC was running, a C library perror servicefunction call was issued. Normally, Language Environment directs these messagesto a SPOOL data set, where they can remain unnoticed for some time. Thismessage is generated to present the content of the message issued by the perrorservice function to a more readily accessible medium. The internal InfoSphere CDCtask under which the perror service function call was issued is identified in themessage text.

Message Variables:

name—The name of the C library perror service function.

text—The message text that the perror service function generated.


System Action—Depends on the message issued by the perror service function.

Operator Response—Depends on the message issued by the perror servicefunction.


CHC9715ECHC9715E C Language name(module) request has failed. The returned errno is text forvalue of number.


Explanation—While InfoSphere CDC was initializing or terminating a process, a Clibrary service function call to manage an executable module was issuedunsuccessfully. The C library service function that was called is identified in themessage text.

Message Variables:

name—The name of the C-language load module management function that failed.

module—The name of the load module that was not successfully managed.


number—The error number returned by the failed service function call. If the textstring has been provided, then it is the text interpretation of this error number.Note the error number and consult the appropriate C Library Services manual toidentify the source of the problem.


System Action—Modules are managed during component initialization andtermination. When a module management request is unsuccessful, initialization ortermination of the affected component fails, and InfoSphere CDC stopsprematurely.

Operator Response—This message may be accompanied by additional messagesgenerated by InfoSphere CDC for z/OS. Inform the system programmer of thefailure to manage the module by providing the information from this and anyother related messages.


CHC9719ECHC9719E VSAM Cluster name is full. Resize the cluster and restart.

Explanation—The VSAM cluster containing the product metadata that is notstored in DB2 tables is full.

Message Variables:

name—The name of the VSAM cluster containing the product metadata.


System Action—All replication activities are stopped.

Operator Response—Stop the InfoSphere CDC address space by using the STOPcommand, and increase the size of the VSAM cluster. Restart the InfoSphere CDCaddress space by using the START command.


Client Administrator Response—After the InfoSphere CDC address space hasbeen restarted by the console operator, restart all replication activities that werestopped as a result of the full VSAM cluster.

CHC9720ECHC9720E z/OS "name" Service has failed. The return code is code.

Explanation—While InfoSphere CDC was running, an z/OS service function calldid not complete successfully. The service function that failed is identified in themessage text.

Message Variables:


code—The numeric code that identifies why the z/OS service function call did notcomplete successfully.


System Action—The external request or internal process that caused the z/OSservice function call to fail is stopped. If this message was issued duringinitialization of InfoSphere CDC, then InfoSphere CDC will stop.

Operator Response—This message may be accompanied by additional messagesgenerated by InfoSphere CDC for z/OS. Inform the system programmer of thefailure to manage the dynamic load library by providing the information from thisand any other related messages.


CHC9721ECHC9721E Failure of z/OS LOAD request for module name ABEND Code=code, Reason Code=reason.

Explanation—While InfoSphere CDC is running, an z/OS LOAD service functioncall to load a module was issued, but failed to locate or load the module. Thismessage is issued to provide the name of the load module and information aboutwhy it failed to load.

Message Variables:

name—The name of the load module that was not successfully loaded into theaddress space.

code—The hexadecimal code that identifies the load module that could not beloaded.

reason—The numeric code that identifies why the load module could not beloaded.



System Action—Modules are loaded during component initialization. When amodule fails to load, initialization of the affected component fails, and InfoSphereCDC stops.

Operator Response—This message may be accompanied by additional messagesgenerated by InfoSphere CDC for z/OS. The information provided in this message(the ABEND and reason codes) is documented in the appropriate z/OSpublication. Inform the system programmer of the failure to load the module byproviding the information from this and any other related message.


CHC9722ECHC9722E Failure of z/OS LINK request for module name ABEND Code=code.

Explanation—While InfoSphere CDC was running, an z/OS LINK service functioncall to load and transfer control to a module was issued, but failed to locate orload the module. This message is issued to identify the name of the load moduleand a code that identifies why the module could not be loaded.

Message Variables:

name—The name of the load module that was not successfully loaded into theaddress space.

code—The hexadecimal code that identifies why the module could not be loaded.


System Action—Modules are loaded during component initialization. When amodule fails to load, initialization of the affected component fails, and InfoSphereCDC stops.

Operator Response—This message may be accompanied by additional messagesgenerated by InfoSphere CDC for z/OS. The information provided in this message(the ABEND and reason codes) is documented in the appropriate z/OSpublication. Inform the system programmer of the failure to load the module byproviding the information from this and any other related message.


CHC9723ECHC9723E A delete from VSAM metadata failed for subscription name.

Explanation—InfoSphere CDC failed to delete all notifications metadata thatresides in a VSAM metadata cluster. The deletion of the alarms and alerts metadatais a result of deleting the subscription.

Message Variables:

name—The name of the target or source identifier, as defined in ManagementConsole.






CHC9733ICHC9733I V5 Communications: Connections = number.

Explanation—Provides information about the number of open V5 communicationslinks that are being used by the InfoSphere CDC address space for variouspurposes. This message is issued in response to a DSPACT=COMM orDSPACT=ALL command issued from the operator console.

Message Variables:

number: The number of open V5 communications links that are being used byInfoSphere CDC for various purposes.





CHC9742ICHC9742I DBMS: Repository Type = DB2 , ID = id, Log(Monitor/Scraper) =monitor/scraper, Replication(admin/source/apply) = administration/source/apply,HoL type = log

Explanation—A report of a specific DB2 repository that InfoSphere CDC issupporting. This message is issued in response to a DSPACT=DBMS or DSPACT=ALLcommand issued from the operator console.

Message Variables:

id—The identifier associated with the repository. The format of the identifier is<DB2 subsystem identifier>.<InfoSphere CDC metadata owner>.

monitor—The number of active log monitor tasks.

scraper—The number of active log scraper tasks.

administration—The number of active administration tasks.

source—The number of active source tasks.

apply—The number of active apply tasks.

type—Indicates if the log value is either the head of log RBA (relative byteaddress) or LRSN (log record sequence number)


log—This is the RBA/LRSN of the last DB2 Log data block that was written at thetime that the DSPACT command was processed. This is not necessarily the highestDB2 Log record RBA/LRSN, since the last DB2 Log data block could contain morethan one DB2 Log record.





CHC9743ECHC9743E An error occurred while processing CHCCNTRL member name. Error: I/O Error

Explanation—An error occurred while processing configuration control statementsin the specified member contained in the CHCCNTRL data set.

Message Variables:

name—The name of the member in the CHCCNTRL data set that was beingprocessed when the error occurred.



Operator Response—Review the configuration control statements to ensure thatthey are specified correctly.


CHC9744ECHC9744E An error occurred while processing CHCCNTRL member name. Error: Unexpectedend of file.


Message Variables:







CHC9745ECHC9745E An error occurred while processing CHCCNTRL member name. Error: Statementtoo long.


Message Variables:






CHC9746ECHC9746E An error occurred while processing CHCCNTRL member name. Error: error.


Message Variables:


error—Specifies the error that occurred during processing.





CHC9751ICHC9751I Replication: Log(Monitor/Scraper) = monitor/scraper, Replication(source/apply) = source/apply

Explanation—A report of replication activity within the InfoSphere CDC addressspace. The report is a summary across all supported repository types. This messageis issued in response to a DSPACT=REPLIC or DSPACT=ALL command issued from theoperator console.

Message Variables:

monitor—The number of active log monitor tasks.


scraper—The number of active log scraper tasks.

source—The number of active source tasks.

apply—The number of active apply tasks.





CHC9753ICHC9753I Replication: number active subscriptions.

Explanation—The number of subscriptions that are currently involved inreplication activity within the InfoSphere CDC address space. This message isissued in response to a DSPACT=REPLIC or DSPACT=ALL command issued from theoperator console.

Message Variables:

number—The number of subscriptions currently involved in replication activity.





CHC9756ECHC9756E Sign on was rejected for source source, reason: source could not becreated.

Explanation—A target received a request to create a source identifier in responseto a change in Management Console, but the operation could not be performed.This message is generated when replication is started for the associatedsubscription.

Message Variables:

source—The source identifier, as defined in Management Console.


System Action—The source identifier is not created and replication is not started.



Client Administrator Response—It is likely that the request could not beperformed because a source identifier with the same name already exists. InManagement Console, specify a source identifier that is unique on the target, andrestart replication.

CHC9757ECHC9757E Sign on rejected for source source, reason: source could not be updated.

Explanation—A target received a request to update a source identifier in responseto a change in Management Console, but the operation could not be performed.This message is generated when replication is started for the associatedsubscription.

Message Variables:



System Action—The source identifier is not updated and replication is not started.



CHC9758ECHC9758E Sign on rejected for source source, reason: source could not be renamed.

Explanation—A target received a request to rename a source identifier in responseto a change in Management Console, but the operation could not be performed.This message is generated when replication is started for the associatedsubscription.

Message Variables:



System Action—The source identifier is not renamed and replication is not started.



CHC9764ECHC9764E Catalog Services Interface failure. Reason: the dataset name was toolong name


Explanation—A call to the interface to Catalog Services (IGGCSI00) to process oneor more datasets has failed for the specified reason.

Message Variables:

name—If present, the dataset name of the dataset for which processing failed.


System Action—Processing of the datasets is unsuccessful. If the dataset is theLevel 2 DB2 Log Cache dataset, the DB2 Log Cache becomes inactive.


Client Administrator Response—Contact your InfoSphere CDC administrator ifyou require further assistance.

CHC9765ECHC9765E Catalog Services Interface failure. Reason: unable to allocate work areaname.


Message Variables:






CHC9766ECHC9766E Catalog Services Interface failure. Reason: the work area was too smallname


Message Variables:







CHC9767ECHC9767E Catalog Services Interface failure. Reason: an incorrect number of fieldswas returned name.


Message Variables:






CHC9768ECHC9768E Catalog Services Interface failure. Reason: an error in the entry for datacomponent for name.


Message Variables:






CHC9769ECHC9769E Catalog Services Interface failure. Reason: a field length error for name


Message Variables:







CHC9770ECHC9770E Catalog Services Interface failure. Reason: unable to fetch high allocatedRBA for name.


Message Variables:






CHC9776ICHC9776I Agent Communications: Connections = datastore, Admin(Act/Pnd) =active/pending, State = Started, Shutdown = type

Explanation—A summary of current communications support within theInfoSphere CDC address space. This message is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console. The Statevalue indicates the current state of communications in the InfoSphere CDC addressspace; a state of ’Started’ indicates that communications support has begun, buthas not yet completed initialization.

Message Variables:

datastore—The number of InfoSphere CDC datastores that have a communicationconnection to Management Console currently open.

active—The number of replication agents that are currently engaged in anexchange with remote Management Console sessions.

pending—The number of datastores that are attempting to initiate an exchangewith remote Management Console sessions.

type—Indicates the manner in which processing is being shut down (CNTRLD,QUICK, and IMMED) within the InfoSphere CDC communications support.


Note: InfoSphere CDC communications support is not in a Terminating state, andso the manner in which processing is shut down is not applicable.





CHC9777ICHC9777I Agent Communications: Connections = datastore, Admin(Act/Pnd) =active/pending, State = Initialized, Shutdown = type

Explanation—A summary of current communications support within theInfoSphere CDC address space. This message is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console. The Statevalue indicates the current state of communications in the InfoSphere CDC addressspace; a state of ’Initialized’ indicates that communications support has completedinitialization, but all supported communications media are currently not yetactivated. Communications media can be activated through the STRTSCOMoperator console command.

Message Variables:










CHC9778ICHC9778I Agent Communications: Connections = datastore, Admin(Act/Pnd) =active/pending, State = Processing, Shutdown = type

Explanation—A summary of current communications support within theInfoSphere CDC address space. This message is issued in response to a


DSPACT=COMM or DSPACT=ALL command issued from the operator console.The State value indicates the current state of communications in the InfoSphereCDC address space; a state of ’Processing’ indicates that communications supporthas completed initialization and at least one communications medium (onlyTCP/IP at this time) has been activated.

Message Variables:










CHC9779ICHC9779I Agent Communications: Connections = datastore, Admin(Act/Pnd) =active/pending, State = Terminating, Shutdown = type

Explanation—A summary of current communications support within theInfoSphere CDC address space. This message is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console.The State value indicates the current state of communications in the InfoSphereCDC address space; a state of ’Terminating’ indicates that communications supportis being terminated (as a result of a SHUTDOWN command issued from theoperator console) but at least one communications medium is not yet inactive.When all communications media have become inactive, this state changes toTerminated.

Message Variables:











CHC9780ICHC9780I Agent Communications: Connections = datastore, Admin(Act/Pnd) =active/pending, State = Terminated, Shutdown = type

Explanation—A summary of current communications support within theInfoSphere CDC address space. This message is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console. The Statevalue indicates the current state of communications in the InfoSphere CDC addressspace; a state of ’Terminated’ indicates that communications support has beenterminated (as a result of a SHUTDOWN command issued from the operatorconsole). Communication between the InfoSphere CDC address space and otherInfoSphere CDC servers or clients is no longer possible.

Message Variables:










CHC9786ICHC9786I Source name = datastore, Medium = TCP/IP, Paths = path, Sends = send,Recvs = receive


Explanation—A report of the communications activity associated with the specifiedsubscription server in the InfoSphere CDC address space. This message is issued inresponse to a DSPACT=COMM or DSPACT=ALL command issued from the operatorconsole.

Message Variables:

datastore—The name of the source datastore defined in the InfoSphere CDCmetadata.

path—The number of paths between the specified source system and the currentInfoSphere CDC address space. A single path is required to support a singlereplication event.

send—The number of whole data segments that have been sent to the specifiedsource system.

receive—The number of whole data segments that have been received from thespecified source system.





CHC9787ICHC9787I Target name = datastore, Medium = TCP/IP, Paths = path, Sends = send,Recvs = receive


Message Variables:

datastore—The name of the target datastore defined in the InfoSphere CDCmetadata.

path—The number of paths between the specified target and the currentInfoSphere CDC address space. A single path is required to support a singlereplication event.

send—The number of whole data segments that have been sent to the specifiedtarget.

receive—The number of whole data segments that have been received from thespecified target.






CHC9788ICHC9788I Datastore name = datastore, Medium = TCP/IP, Paths = path, Sends = send,Recvs = receive


Message Variables:

datastore—The name of the datastore defined in the InfoSphere CDC metadata.


send—The number of whole data segments that have been sent to the specifieddatastore.

receive—The number of whole data segments that have been received from thespecified datastore.





CHC9789ICHC9789I *Undefined* name = datastore, Medium = TCP/IP, Paths = path, Sends = send,Recvs = receive


Message Variables:

datastore—The name of the source system, target, or datastore defined in theInfoSphere CDC metadata.


send—The number of whole data segments that have been sent to the specifiedsource system or target.


receive—The number of whole data segments that have been received from thespecified source system or target.





CHC9795LCHC9795L Obtained z/OS area Storage from Subpool id at address address for a lengthof size bytes.

Explanation—Identifies the commonly addressable storage area from whichstorage has been obtained. This message is issued when InfoSphere CDC requiresthe use of storage obtained from commonly addressable system storage areas. It isonly sent to the system log, and it allows the system programmer to monitor theuse of commonly addressable system storage by InfoSphere CDC.

Message Variables:

area—The commonly addressable storage area from which storage has beenobtained.

id—The subpool identifier of the commonly addressable system storage area fromwhich storage has been obtained.

address—The virtual storage address of the commonly addressable system storagearea that has been obtained.

size—The length of the commonly addressable storage that has been obtained.





CHC9796LCHC9796L Released z/OS area Storage from Subpool id at address address for a lengthof size bytes.

Explanation—Identifies the commonly addressable storage area that received thereleased storage. This message is issued when InfoSphere CDC no longer requiresstorage that it obtained from a commonly addressable system storage area. Thismessage is only sent to the system log, and it allows the system programmer tomonitor the use of commonly addressable system storage by InfoSphere CDC.

Message Variables:


area—The commonly addressable storage area from which storage has beenobtained.

id—The subpool identifier of the commonly addressable system storage area thatthe released storage has been returned to.

address—The virtual storage address of the commonly addressable system storagearea that has been released.

size—The length of the commonly addressable storage that has been released.





CHC9798ECHC9798E Not APF Authorized. IBM InfoSphere Change Data Capture for z/OS cannotexecute.

Explanation—InfoSphere CDC is not executing in an APF Authorized addressspace during initialization. APF Authority is required by this product in order toobtain access to the DB2 resources and services that it must use.



System Action—InfoSphere CDC is stopped.

Operator Response—Note the message number and contact the systemprogrammer who is responsible for installing and/or maintaining InfoSphere CDCin your working environment.


CHC9799ICHC9799I IBM InfoSphere Change Data Capture for z/OS has terminated.

Message Variables:

Explanation—InfoSphere CDC is no longer running. This is the last messageissued by the product after it has stopped.







CHC9800ICHC9800I Target Data name = name, Sends = smg, Send Bytes = sby, Recvs = rmg,Recv Bytes = rby, CPU Used = time

Explanation—Provides information about a single communications link. In the caseof Target Data, it is a data channel used by a target to receive replicated data froma source system. It is issued in response to a DSPACT=COMM or DSPACT=ALL commandissued from the operator console. The message is issued for each communicationslink that was active when the DSPACT command was issued.

A data channel exists for each replication path between a local and remote server.A single control channel exists between a local and remote server to manage datareplication on all defined data channels. The control channel consists of a sourceand target control pairing (Source Control and Target Control).

Message Variables:

name—The name of the communications link. For a data channel, the name of acommunications link is the name of a target or source identifier defined inManagement Console. For a control channel, the name of a communications link iscomposed of a remote server host name and port number. For a Monitor Agentchannel, the name of the communications link is composed of a remote client hostname and port number.

smg—The total number of messages sent on the link at the time this message wasgenerated.

sby—The total number of bytes sent on the link at the time this message wasgenerated.

rmg—The total number of messages received on the link at the time this messagewas generated.

rby—The total number of bytes received on the link at the time this message wasgenerated.

time—The number of seconds of CPU time consumed by the link to date.





CHC9801ICHC9801I Source Data name = name, Sends = smg, Send Bytes = sby, Recvs = rmg,Recv Bytes = rby, CPU Used = cpu

Explanation—Provides information about a single communications link. In the caseof Source Data, it is a data channel used by a source system to replicate data to atarget. It is issued in response to a DSPACT=COMM or DSPACT=ALL command issued


from the operator console. The message is issued for each communications linkthat was active when the DSPACT command was issued. In the message text, eachcommunications link is identified as follows:


Message Variables:






cpu—The number of seconds of CPU time consumed by the link to date.





CHC9802ICHC9802I Monitor Agent name = namee, Sends = smg, Send Bytes = sby, Recvs = rmg,Recv Bytes = rby, CPU Used = cpu

Explanation—Provides information about a single communications link. In the caseof Monitor Agent, it is a data channel used by the Monitor Agent to report thestatus of replications to Management Console. It is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console. Themessage is issued for each communications link that was active when the DSPACTcommand was issued. In the message text, each communications link is identifiedas follows:



Message Variables:











CHC9803ICHC9803I Source Control name = name, Sends = smg, Send Bytes = sby, Recvs = rmg,Recv Bytes = rby, CPU Used = cpu

Explanation—Provides information about a single communications link. In the caseof Source Control, it is the control channel used by a source system to manage datareplication on data channels. It is issued in response to a DSPACT=COMM orDSPACT=ALL command issued from the operator console. The message is issued foreach communications link that was active when the DSPACT command wasissued. In the message text, each communications link is identified as follows:


Message Variables:












CHC9804ICHC9804I Target Control name = name, Sends = smg, Send Bytes = sby, Recvs = rmg,Recv Bytes = rby, CPU Used = cpu

Explanation—Provides information about a single communications link. In the caseof Target Control, it is the control channel used by a target to manage datareplication on data channels. It is issued in response to a DSPACT=COMM orDSPACT=ALL command issued from the operator console. The message is issued foreach communications link that was active when the DSPACT command wasissued. In the message text, each communications link is identified as follows:


Message Variables:












CHC9805ICHC9805I *Unknown* name = name, Sends = smg, Send Bytes = sby, Recvs = rmg,Recv Bytes = rby, CPU Used = time

Explanation—Provides information about a single communications link. In the caseof *Unknown*, the purpose of the communications link could not be determined. Itis issued in response to a DSPACT=COMM or DSPACT=ALL command issued from theoperator console. The message is issued for each communications link that wasactive when the DSPACT command was issued. In the message text, eachcommunications link is identified as follows:


Message Variables:






time—The number of seconds of CPU time consumed by the link to date.






CHC9812ECHC9812E Deferred DLL Initialization for DLL name was unsuccessful. The subordinateDLLs failed initialization.

Explanation—This message summarizes a failure to manage a DLL (Dynamic LinkLibrary) during initialization or termination of an InfoSphere CDC process

Message Variables:

name—The name of the dynamic load library module that was not successfullymanaged.





CHC9813ECHC9813E Deferred DLL Initialization for DLL name was unsuccessful. The DLL wasalready being terminated.


Message Variables:







CHC9814ECHC9814E Deferred DLL Initialization for DLL name was unsuccessful. The DLL was notinitialized


Message Variables:






CHC9815ECHC9815E Deferred DLL Initialization for DLL name was unsuccessful. The DLL wasalready being initialized.


Message Variables:






CHC9816ECHC9816E Deferred DLL Initialization for DLL name was unsuccessful. The subordinateDLLs failed termination.



Message Variables:






CHC9817ICHC9817I Medium = TCP/IP, State = Inactive, Shutdown = type

Explanation—A report of how the TCP/IP medium is being used within theInfoSphere CDC address space. This message is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console. The ’State’setting indicates the current state of InfoSphere CDC’s specified communicationsupport; in the case of Inactive, the specified communications support is currentlynot available. The STRTSCOM operator command must be issued beforecommunications using the specified communication medium can occur.

Message Variables:

type—Indicate the manner in which communications support’s processing is beingshut down. A shut down is initiated by a SHUTDOWN command issued from theoperator console. If the communications support’s processing is not in a Quiescingstate, then the manner in which the communications support’s processing is shutdown is not applicable.





CHC9818ICHC9818I Medium = TCP/IP, State = Active, Shutdown = type

Explanation—A report of how the TCP/IP medium is being used within theInfoSphere CDC address space. This message is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console. The State


setting indicates the current state of InfoSphere CDC’s specified communicationsupport; in the case of Active, the communications support is currently available.

Message Variables:






CHC9819ICHC9819I Medium = TCP/IP, State = Quiescing, Shutdown = type

Explanation—A report of how the TCP/IP medium is being used within theInfoSphere CDC address space. This message is issued in response to aDSPACT=COMM or DSPACT=ALL command issued from the operator console. The statesetting indicates the current state of InfoSphere CDC’s specified communicationsupport; in the case of Quiescing, the communications support is currentlyavailable but is being gracefully terminated. This state is probably the result ofissuing a SHUTDOWN=CNTRLD operator command. Any active communications usingthe communications medium are allowed to continue, but no new communicationconnections are allowed to start. When the last active connection has terminated,the current state automatically changes to Inactive.

Message Variables:






CHC9830ICHC9830I DBMS: Repositories = number, State = Started, Shutdown = type

Explanation—A report of the database management system support in theInfoSphere CDC address space. This message is issued in response to aDSPACT=DBMS or DSPACT=ALL command issued from the operator console. The State


setting (Started, Processing, or Terminating) indicates the current state of databasemanagement system support in the InfoSphere CDC address space; in the case ofStarted, the Database management system support has begun, but has not yetcompleted initialization.

Message Variables:

number—The number of DB2 repositories that InfoSphere CDC is supporting.

type—Indicates the manner in which processing is being shut down. A shut downis initiated by a SHUTDOWN command issued from the operator console. IfInfoSphere CDC database management system support is not in a Terminatingstate, then the manner in which processing is being shut down is not applicable.





CHC9831ICHC9831I DBMS: Repositories = number, State = Initialized, Shutdown = type

Explanation—A report of the database management system support in theInfoSphere CDC address space. This message is issued in response to aDSPACT=DBMS or DSPACT=ALL command issued from the operator console. The Statesetting indicates the current state of database management system support in theInfoSphere CDC address space.v Started—Database management system support has begun, but has not yet

completed initialization.v Processing—Database management system support has completed initialization

and is currently processing database requests.v Terminating—Database management system support is being terminated (as a

result of a SHUTDOWN command issued from the operator console).

Message Variables:








CHC9832ICHC9832I DBMS: Repositories = number, State = Processing, Shutdown = type

Explanation—A report of the database management system support in theInfoSphere CDC address space. This message is issued in response to aDSPACT=DBMS or DSPACT=ALL command issued from the operator console. The Statesetting indicates the current state of database management system support in theInfoSphere CDC address space; in the case of ’Processing’, the Databasemanagement system support has completed initialization and is currentlyprocessing database requests.v v Started—Database management system support has begun, but has not yet

completed initialization.v v Processing—Database management system support has completed initialization

and is currently processing database requests.v v Terminating—Database management system support is being terminated (as a


Message Variables:







CHC9833ICHC9833I DBMS: Repositories = number, State = Terminating, Shutdown = type





Message Variables:








CHC9834ICHC9834I DBMS: Repositories = number, State = Terminated, Shutdown = type





Message Variables:







CHC9835ICHC9835I DBMS: Repositories = number, State = Started, Shutdown = type

Explanation—A report of the database management system support in theInfoSphere CDC address space. This message is issued in response to a


DSPACT=DBMS or DSPACT=ALL command issued from the operator console. The Statesetting indicates the current state of database management system support in theInfoSphere CDC address space; in the case of ’Processing’, the Databasemanagement system support has completed initialization and is currentlyprocessing database requests.v v Started—Database management system support has begun, but has not yet




Message Variables:







CHC9840ICHC9840I Subscription name = name, Repository type = DB2, Activity = activity,State = Comm. Deallocating, Shutdown = state, Current type = position, Writtenat = time

Explanation—A report of replication activity to the subscription identified in themessage text. This message is issued in response to a DSPACT=REPLIC or DSPACT=ALLcommand issued from the operator console.

Message Variables:

name—The name of the subscription being reported.

activity—Identifies the specific replication activity (source table describe, refresh,or mirroring) that has been started to the subscription.

state—Identifies the current state of replication to the subscription.

type—The possible values for type are: RBA (relative byte address) or LRSN (logrecord sequence number).

position—The current RBA (relative byte address) or LRSN (log record sequencenumber) for reading DB2 Log data during mirroring activities. This RBA/LRSNwill advance as the source server advances through the DB2 Log, collecting data to


be sent to the target server. If refresh activities are being performed when theDSPACT command is invoked, then ″*NA*″ appears in the message text at thispoint.

time—The timestamp when the current RBA or LRSN identified in the messagewas written to the DB2 Log. If mirroring is not being performed when theDSPACT command is invoked, then ″*NA*″ appears in the message text at thispoint.





CHC9841ICHC9841I Subscription name = name, Repository type = DB2, Activity = activity,State = Not Connected, Shutdown = state, Current type = position, Written at = time


Message Variables:





position—The current RBA (relative byte address) or LRSN (log record sequencenumber) for reading DB2 Log data during mirroring activities. This RBA/LRSNwill advance as the source server advances through the DB2 Log, collecting data tobe sent to the target server. If refresh activities are being performed when theDSPACT command is invoked, then ″*NA*″ appears in the message text at thispoint.







CHC9842ICHC9842I Subscription name = name, Repository type = DB2, Activity = activity,State = Connecting, Shutdown = state, Current type = position, Written at = time


Message Variables:











CHC9843ICHC9843I Subscription name = name, Repository type = DB2, Activity = activity,State = Connected, Shutdown = state, Current type = position, Written at = time


Message Variables:












CHC9844ICHC9844I Subscription name = name, Repository type = DB2, Activity = activity,State = Processing, Shutdown = state, Current type = position, Written at = time


Message Variables:


activity—Identifies the replication method of the subscription. This could bemirroring or a refresh.










CHC9845ICHC9845I Subscription name = name, Repository type = DB2, Activity = activity,State = Ending, Shutdown = state, Current type = position, Written at = time


Message Variables:











CHC9846ICHC9846I Subscription name = name, Repository type = DB2, Activity = activity,State = Not Active, Shutdown = state, Current type = position, Written at = time



Message Variables:











CHC9847ICHC9847I Subscription name = name, Repository type = DB2, Activity = activity,State = Unknown, Shutdown = state, Current type = position, Written at = time


Message Variables:





position—The current RBA (relative byte address) or LRSN (log record sequencenumber) for reading DB2 Log data during mirroring activities. This RBA/LRSNwill advance as the source server advances through the DB2 Log, collecting data to


be sent to the target server. If refresh activities are being performed when theDSPACT command is invoked, then ″*NA*″ appears in the message text at thispoint.






CHC9853ICHC9853I Source name = source, Activity = activity, State = Comm. Deallocating,Shutdown = setting

Explanation—A report of replication activity from the source system identified inthe message text. This message is issued in response to a DSPACT=REPLIC orDSPACT=ALL command issued from the operator console.

Message Variables:

source—The source identifier that identifies the source of replicated data.

activity—Identifies the current replication activity being performed on the sourcesystem. The possible values are:v Describe_Tables—The identified source system is sending source table

descriptions.v Start_Mirror—The identified source system is starting to mirror data.v Start_Refresh—The identified source system is starting a refresh data.v Stop_Replication—The replication (mirroring or refresh) of data from the

identified source system is ending.

setting—Indicates the manner in which replication activity from the identifiedsource system is being stopped. The possible values are:v CNTRLD—Replication activity with the identified source system is being

stopped in a controlled manner. Typically, this is the method you will use to endreplication explicitly on the source system.

v IMMED—Replication activity with the identified source system is being stoppedimmediately.

v ABNORMAL—Replication activity with the identified source system has endedunexpectedly as a result of a problem or error.

v *N/A*—Replication activity is not in a Comm. Deallocating or Ending state, andso the manner in which replication activity is stopped is not applicable.

Replication activity is stopped explicitly by running the ENDTSRSH or ENDTSMIRcommand from the operator console.






CHC9854ICHC9854I Source name = source, Activity = activity, State = Not Connected,Shutdown = setting


Message Variables:
















Related reference

“ENDTSMIR—End mirroring” on page 104“ENDTSRSH—End refresh” on page 108

CHC9855ICHC9855I Source name = source, Activity = activity, State = Connecting,Shutdown = setting


Message Variables:
















Related reference


CHC9856ICHC9856I Source name = source, Activity = activity, State = Connected,Shutdown = setting


Message Variables:
















Related reference


CHC9857ICHC9857I Source name = source, Activity = activity, State = Processing,Shutdown = setting


Message Variables:
















Related reference


CHC9858ICHC9858I Source name = source, Activity = activity, State = Ending, Shutdown =setting.


Message Variables:
















Related reference


CHC9859ICHC9859I Source name = source, Activity = activity, State = Not Active, Shutdown =setting


Message Variables:
















Related reference


CHC9860ICHC9860I Source name = source, Activity = activity, State = Not Active, Shutdown =setting.


Message Variables:

















Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Canada Limited Office of the Lab Director8200 Warden AvenueMarkham, OntarioL6G 1C7CANADA

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM’s suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating


platform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksThe following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both:

DB2HiperspaceIBMInfoSphereLanguage EnvironmentLiveAuditMVSMVS/SPRACFTransformation Serverz/Architecturez/OSzSeries

Microsoft®, Windows, Windows NT®, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, or service names may be trademarks or service marks ofothers.

Notices 669


��

Printed in USA

Documents

CDC Installation