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. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

CAPI_SRC_DFLT Statement

CAPI_SRC_DFLT Statement

The CAPI_SRC_DFLT statement specifies the CAPI_CONNECTION statement that PowerExchange uses by default for a specific data source type when a CAPI connection override is not supplied.
Informatica recommends that you specify this statement for each source type to ensure that the appropriate type of CAPI_CONNECTION statement is used for accessing a source. If you have multiple source types that run on different platforms and do not specify a CAPI_SRCE_DFLT statement for each source type, source access problems might occur in certain situations during PowerCenter data previews or CDC sessions.
All
All
CAPI_CONN_NAME and CAPI_CONNECTION
No
CAPI_SRC_DFLT=(
source_type
,
capi_connection_name
)
source_type
Required. The CDC source type. The following table identifies the valid source-type options:
Option
Source Type
ADA
Adabas sources
AS4
Db2 for i (i5/OS) sources
CAPX
Sources for which you are extracting data in continuous extraction mode and using the PowerExchange Logger for Linux, UNIX, or Windows or PowerExchange Condense
DB2
Db2 for z/OS sources
DCM
CA Datacom sources
IDL
CA IDMS/DB log-based CDC sources
IML
IMS log-based CDC sources
IMS
IMS synchronous CDC sources
MSS
Microsoft SQL Server sources
MYS
MySQL sources
ORA
Oracle sources
PGS
PostgreSQL sources
UDB
Db2 sources on Linux, UNIX, or Windows
VSAM or VSM
VSAM sources
capi_connection_name
Required. Unique name of the CAPI_CONNECTION statement to use as the default for the specified source type. This name must match the NAME value in a CAPI_CONNECTION statement that has a TYPE value that is compatible with the CAPI_SRC_DFLT
source_type
.
The following table shows, for each CAPI_SRC_DFLT option, the compatible CAPI_CONNECTION type:
CAPI_SRC_DFLT Option
CAPI_CONNECTION Statement Type
AS4
UOWC
CAPX
CAPX
ADA, DB2, DCM, IDL, IDM, IML, IMS, VSAM, or VSM
UOWC
ORA
ORAD for PowerExchange Express CDC for Oracle
MSS
MSQL
MYS
MYSQL
PGS
PG
UDB
UDB
  • If you define multiple CAPI_CONNECTION statements for a source type, you can define a CAPI_SRC_DFLT statement to identify the default CAPI_CONNECTION for that source type. The CAPI_SRC_DFLT statement must point to a CAPI_CONNECTION statement of a compatible type.
  • You can optionally define a CAPI_CONN_NAME statement that specifies an overall default statement, out of all of the CAPI_CONNECTION statements in the DBMOVER file.
  • Instead of or in addition to specifying defaults, you can use the following CAPI connection name overrides to point to a specific CAPI_CONNECTION statement for CDC sessions or database row tests:
    • For CDC sessions, use the
      CAPI Connection Name Override
      attribute on the PWX CDC application connection.
    • For PowerExchange Condense, use the CONN_OVR parameter in CAPTPARM configuration file.
    • For the PowerExchange Logger for Linux, UNIX, and Windows, use the CONN_OVR parameter in pwxccl.cfg configuration file.
    • For DTLUAPPL utility operations that generate restart tokens, use the CONN_OVR parameter in the DTLUAPPL control statement.
    • For CAPXRT database row tests in the PowerExchange Navigator, use the
      CAPI Connection Name
      value in the
      CAPXRT Advanced Parameters
      dialog box. If you add an SQL statement for generating restart tokens, you can include the CONNAME parameter to point to the override CAPI_CONNECTION.
    • For PowerExchange ODBC connections, use the DTLCONN_OVR parameter in the odbc.ini file or the SQL escape sequence override DTLCONNOVR.

0 COMMENTS

We’d like to hear from you!