Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

CAPI_CONNECTION - CAPX Statement

CAPI_CONNECTION - CAPX Statement

The CAPX CAPI_CONNECTION statement specifies a named set of parameters that the Consumer API (CAPI) uses for continuous extraction of change data from PowerExchange Logger for Linux, UNIX, and Windows log files.
Linux, UNIX, and Windows
Yes for continuous extraction mode
CAPI_CONNECTION=([DLLTRACE=
trace_id
]   ,NAME=
capi_connection_name
  [,TRACE=
trace_name
]   ,TYPE=(CAPX     ,DFLTINST=
instance_name
   [,FILEWAIT={
seconds
|
1
}] [,NOSEQVAL={
N
|Y}]    [,RSTRADV=
seconds
] [,RSTRANMODE={
N
|Y}] [,VALIDATEREGS={
N
|Y}]    ) )
DLLTRACE=
trace_id
Optional. User-defined name of the TRACE statement that activates internal DLL tracing for this CAPI. Specify this parameter only at the direction of Informatica Global Customer Support.
NAME=
capi_connection_name
Required. Unique user-defined name for this CAPI_CONNECTION statement.
Maximum length is eight alphanumeric characters.
TRACE=
trace_name
Optional. User-defined name of the TRACE statement that activates the common CAPI tracing. Specify this parameter only at the direction of Informatica Global Customer Support.
TYPE=(CAPX, ... )
Required. Type of CAPI_CONNECTION statement. For continuous extraction mode, this value must be CAPX.
DFLTINST=
instance_name
Required. A source instance identifier that is specified for the registration group. This value must match the DBID value that is specified in the PowerExchange Logger configuration file.
To determine this value, view the registration group properties in the PowerExchange Navigator. Depending on the source type, enter one of the following values:
  • For Adabas, Db2 for i (i5/OS), Db2 for z/OS, MySQL, Oracle, and VSAM, enter the name that is displayed in the
    Instance
    field for the registration group in the
    Resource Inspector
    .
  • For Datacom, enter the name of the Multi-User Facility (MUF) in the
    MUF Name
    field.
  • For a Db2 source on Linux, UNIX, or Windows, enter the name of the database in the
    Database
    field.
  • For an IDMS log-based source, enter the name of the database in the
    DB Name
    field.
  • For an IMS source, enter the recon identifier for the database in the
    RECON ID
    field.
  • For Microsoft SQL Server, this value depends on whether you specify the optional DISTSRV and DISTDB parameters in the PowerExchange Logger configuration file as follows:
    • If you specify the DISTSRV and DISTDB parameters, enter the DBID name that you use as the collection identifier for all of the registrations. This name overrides the instance name that is associated with the individual registrations.
    • If you do not specify the DISTSRV and DISTDB parameters, enter the value that the PowerExchange Navigator generates and displays in the
      Instance
      field of the
      Resource Inspector
      for the registration group. The generated value is composed of the first four characters of the database name followed by a generated number, which starts at 000.
Maximum length is eight alphanumeric characters.
FILEWAIT={
seconds
|
1
}
Optional. The number of seconds that PowerExchange waits before checking for new PowerExchange Logger log files.
For the
seconds
variable, enter a number from 1 through 86400. Default is 1.
NOSEQVAL={
N
|Y}
Optional. If you receive error message PWX-36944 after starting a CDC session, the sequence token that PWXPC passed to PowerExchange is earlier than the sequence token that is recorded in the PowerExchange Logger CDCT file. If you want the session to continue and you can tolerate some data loss, you can set this parameter to Y. The Log Reader then begins extracting the earliest available data in the log files. With the default value of N, the session fails.
RSTRADV=
seconds
Optional. The time interval, in seconds, that PowerExchange waits before advancing the restart and sequence tokens for a registered data source during periods when UOWs contain no changes of CDC interest for a data source. When the wait interval expires, PowerExchange returns the next committed "empty UOW," which includes only updated restart information.
For the
seconds
variable, enter a number from 0 through 86400. No default value is provided. A value of 0 causes PowerExchange to return an empty UOW after each UOW processed. Consequently, a value of 0 can degrade performance.
PowerExchange resets the wait interval to 0 when one of the following events occur:
  • PowerExchange completes processing a UOW that includes changes of CDC interest.
  • PowerExchange returns an "empty UOW" because the RSTRADV wait interval expired without any new changes of CDC interest having been received.
For example, if you specify 5, PowerExchange waits 5 seconds after it completes processing the last UOW or after the previous RSTRADV interval expires. Then PowerExchange returns the next committed "empty UOW" that includes the updated restart information and resets the wait interval to 0.
If you specify the RSTRADV parameter with any valid value, PowerExchange always advances the restart and sequence tokens when the Log Reader reaches the end of a Logger log file, even if the RSTRADV interval has not expired. This behavior ensures that restart and sequence tokens are advanced even when the CDC session run time is shorter than the RSTRADV interval. This situation is most likely to occur if you have source tables that have a low level of update activity.
If you do not specify RSTRADV, PowerExchange does not advance restart and sequence tokens for a registered source during periods when PowerExchange receives no changes of interest. In this case, when PowerExchange warm starts, it reads all changes, even those not of CDC interest, from the restart point.
For Db2 for i (i5/OS) sources, Informatica recommends that you use this parameter if the change records that PowerExchange reads from i5/OS journal receivers are created under commitment control. If the change records are created without commitment control, do not specify this parameter.
RSTRANMODE={
N
|Y}
Optional. If you are migrating from real-time extraction mode to continuous extraction mode for CDC sessions that have not previously used the PowerExchange Logger for Linux, UNIX, and Windows, set this parameter to Y. This setting enables PowerExchange to convert restart token information to the format that PowerExchange Logger requires, when CDC sessions run. Retain the Y setting until PowerExchange completes converting the restart tokens for all registered source tables and all CDC sessions that use this CAPX CAPI_CONNECTION. Then, set this parameter to N or delete it. Default is N.
VALIDATEREGS={
N
|Y}
Optional. Controls whether the PowerExchange extraction of data from PowerExchange Logger for Linux, UNIX, and Windows ends or continues if it detects a source entry in the CDC interest list for which the PowerExchange Logger is
not
capturing change data. In this situation, the extraction process issues message PWX-36947, either as error message or informational message.
Options are:
  • Y
    . The PowerExchange Logger extraction process issues message PWX-36947 as an error message and then ends.
  • N
    . The PowerExchange Logger extraction process issues message PWX-36947 as an informational message and continues processing.
Default is N.