Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

Considerations for Adabas Bulk Data Movement

Considerations for Adabas Bulk Data Movement

Review the following considerations before implementing bulk data movement for an Adabas source or target.
  • PowerExchange imports Long Alpha (LA) fields with a default length of 1,024 bytes. You can override this default length from the PowerExchange Navigator by editing the data map. Open the
    Record
    window of an Adabas file and then open the
    Field Properties
    dialog box for the LA field. In the
    Length
    field, you can enter an override value of up to 16,381.
  • If the Adabas field definition table (FDT) for an Adabas source or target is password-protected, the Adabas FDT password is required to connect to the Adabas source or target during a PowerCenter batch session. To enter the Adabas FDT password, edit the session in Task Developer. On the
    Mapping
    tab of the
    Edit Tasks
    dialog box, under
    Sources
    or
    Targets
    , click the Adabas source or target definition. In the right pane under
    Properties
    , enter the FDT password in the
    ADABAS Password
    attribute.
  • If you use Adabas 8.2.2 or later on z/OS, PowerExchange supports Adabas files that contain spanned records as data sources. A spanned record is a logical record that is composed of a single physical primary record and up to four second secondary records. Each record is stored in a separate data storage block.
  • If an Adabas descriptor field has the null suppression (NU) attribute, a PowerCenter workflow that accesses the field might return unexpected results. A descriptor field with the NU attribute is excluded from indexes. If a workflow attempts to perform a write based on the key field value, a SQLCODE=256 failure code or other error condition might result.

0 COMMENTS

We’d like to hear from you!