Table of Contents

Search

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

Customizing the PowerExchange Logger Configuration File for Remote Logging

Customizing the PowerExchange Logger Configuration File for Remote Logging

For the PowerExchange Logger for Linux, UNIX, and Windows to log data from a remote z/OS source, you must customize the PowerExchange Logger configuration file on the system with the PowerExchange Logger log files will reside.
PowerExchange provides a sample configuration file, named pwxccl, in the PowerExchange installation directory on the Linux, UNIX, or Windows system. You can copy this file and customize the copy.
For a complete list of PowerExchange Logger configuration parameters, see the PowerExchange Logger for Linux, UNIX, and Windows chapter in the
PowerExchange CDC Guide for Linux, UNIX, and Windows
.
The following table describes the parameters that used for remote logging from a z/OS source:
Parameter
Description
CAPTURE_NODE
Required for remote logging. The node name that the PowerExchange Logger uses to retrieve capture registrations and change data from the z/OS source system. This name must be defined in a NODE statement in the dbmover configuration file on the system where the PowerExchange Logger runs. The PowerExchange Logger uses this node name to connect to the PowerExchange Listener on the source system. This name should correspond to the node name in the LISTENER statement on the source system.
CAPTURE_NODE_EPWD or CAPTURE_NODE_PWD
Optional. An encrypted password (EPWD) or clear text password (PWD) that is associated with the user ID specified in the CAPTURE_NODE_UID parameter.
If you specify CAPTURE_NODE_UID, you must specify either CAPTURE_NODE_EPWD or CAPTURE_NODE_PWD. However, do not specify both CAPTURE_NODE_EPWD and CAPTURE_NODE_PWD.
CAPTURE_NODE_UID
A user ID that controls PowerExchange Logger read access to capture registrations and change data on the remote node that is specified in the CAPTURE_NODE parameter. Whether this parameter is required depends on the operating system of the remote node and the SECURITY setting in the DBMOVER configuration file for the PowerExchange Listener on that node.
If CAPTURE_NODE specifies a z/OS node that has a SECURITY setting of 0, do not specify this parameter. PowerExchange uses the user ID under which the PowerExchange Listener job runs to control access to capture registrations and change data.
If CAPTURE_NODE specifies a z/OS node that has a SECURITY setting of 1, you must enter a valid operating system user ID for this parameter. Otherwise, error message PWX-00231 is issued, indicating a signon failure. However, PowerExchange uses the user ID under which the PowerExchange Listener job runs to control access to capture registrations and change data.
If CAPTURE_NODE specifies a z/OS node that has a SECURITY setting of 2, you must enter a valid operating system user ID for this parameter. Otherwise, error message PWX-00231 is issued, indicating a signon failure. PowerExchange uses this user ID to control access to capture registrations and change data. If the specified user ID does not have the authority that is required to read capture registrations or change data, access fails.
CONDENSENAME
Optional. A name for the command-handling service for a PowerExchange Logger for Linux, UNIX, and Windows process to which pwxcmd commands are issued.
This service name must match the service name in the associated SVCNODE statement in the dbmover configuration file.
CONN_OVR
Recommended. The name of the override CAPI_CONNECTION statement to use for the PowerExchange Logger. If you do not enter CONN_OVR, the PowerExchange Logger uses the default CAPI_CONNECTION in the dbmover configuration file, if specified.
For z/OS data sources, enter the name of the UOW Cleanser (UOWC) CAPI_CONNECTION statement.
Informatica recommends that you specify CONN_OVR because it is the only type of override that the PowerExchange Logger can use.
DB_TYPE
Required. The source database type. For z/OS sources, options are:
  • ADA
    . For Adabas sources.
  • DB2
    . For DB2 for z/OS sources.
  • DCM
    . For Datacom sources.
  • IDL
    . For IDMS log-based CDC sources.
  • IMS
    . For IMS sources.
  • VSM
    . For VSAM sources.
DBID
Required. A source identifier, sometimes called the
instance
name, that is defined in capture registrations. When used with DB_TYPE, it defines selection criteria for capture registrations in the CCT file.
This value must match the instance or database name that is displayed in the Resource Inspector of the PowerExchange Navigator for the registration group that contains the capture registrations.
Enter one of the following values, depending on the source type:
  • For Adabas, enter the
    Instance
    name that is displayed for the registration group.
  • For Datacom, enter the
    MUF Name
    value that is displayed for the registration group. Alternatively, enter the value of REG_MUF parameter in the ECCRDCMP member of the RUNLIB library.
  • For DB2 for z/OS, enter the
    Instance
    name that is displayed for the registration group. This name should match the RN parameter value in the DB2 statement in the RUNLIB(REPDB2OP) member.
  • For IDMS Log-based CDC, enter the
    Logsid
    value that is displayed for the registration group. This value should match the LOGSID parameter value in the RUNLIB(ECCRIDLP) member.
  • For IMS, enter the
    IMSID
    value that is displayed for the registration group. For IMS log-based CDC, this value should match the first parameter value in the IMSID statement in the RUNLIB(CAPTIMS) member.
  • For VSAM, enter the
    Instance
    name that is displayed for the registration group.
EXT_CAPT_MASK
Required. An existing directory path and a unique prefix to be used for generating the PowerExchange Logger log files.

0 COMMENTS

We’d like to hear from you!