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

Rules and Guidelines for Multiple-Record Writes to Sequential File or VSAM Targets

Rules and Guidelines for Multiple-Record Writes to Sequential File or VSAM Targets

Review the rules and guidelines that pertain to multiple-record writes to sequential file or VSAM targets before you configure a workflow that uses this feature.
For more information, see the
PowerExchange Interfaces for PowerCenter
.

Source and Target Files

The following rules and guidelines apply to sources and targets:
  • PowerExchange supports multiple-record writes to VSAM ESDS, KSDS, and RRDS targets. PowerExchange does not support multiple-record writes to VSAM VRRDS targets.
  • PowerExchange does not support changing the values inside header or trailer records.
  • A parent must precede its children in the source data.

Data Maps, Source Definitions, and Target Definitions

The following rules and guidelines apply to data maps, source definitions, and target definitions:
  • In PowerCenter, you must create new source and target definitions for multiple-record writes. Existing definitions without sequencing information do not work for multiple-record writes. You can continue to use existing definitions for workflows that do not use multiple-record writes.
  • A data map for a sequential source or target uses the SEQ access method. A data map for a VSAM target uses one of the following access methods: ESDS, KSDS, or RRDS.
  • The source data map must specify unique record ID conditions so that each record in the input file is distributed to one and only one table. If the same record is distributed to more than one table, processing fails. This situation can occur if record ID conditions overlap or if you do not define record ID conditions in the data map.
  • Verify that all tables that form a complete hierarchy are included in the data map. The import process does not verify hierarchical completeness.
    To ensure that all of the required tables in the data map are included in the source definition, define them in the data map as simple tables. A
    simple table
    is based on a single record.
    If the data map includes complex tables, PowerExchange does not include them in the source or target definition. A
    complex table
    is based on more than one record.
  • You cannot select which tables in the data map to import. PowerCenter imports all of the simple tables in the data map.
  • The data map must have exactly one table for each record.

Mappings and Transformations

The following rules and guidelines apply to PowerCenter mappings and transformations:
  • Mapping transformations might drop rows. In this case, ensure that the mapping does not create any orphan rows. When a multiple-record write workflow runs, it drops orphan rows instead of writing them to the target.
  • The mapping must not alter the position or the name of the generated sequence fields or drop them.
  • Transformations that insert records into a mapping are not supported.
  • Transformations that might alter row IDs, including the Sorter, Joiner, and Rank transformations, are not supported.

Connections

The following rules and guidelines apply to connections and connection properties:
  • You can use multiple-record writes with PWXPC NRDB Batch connections only. PowerExchange ODBC connections are not supported.
  • Select
    Filter After
    for the
    Offload Processing
    source and target connection attributes. If you select a different value, PowerExchange changes the value to
    Filter After
    .
    PowerExchange and PWXPC perform offload processing on the Integration Service machine before writing the output records to
    z/OS
    .
  • Multithreaded processing is not supported for sequential or VSAM source or target connections.
    If you set the
    Worker Threads
    connection attribute to a nonzero value, the setting is ignored.
  • Select
    Off
    for the
    Confirm Write
    source and target connection attributes. If you select a different value, PowerExchange changes the value to
    Off
    .
  • In certain cases, you might need to change the value of the
    CSQ_MEMSIZE
    parameter of the
    PWX Override
    connection attribute. This parameter defines the maximum amount of memory that the cache can consume for multiple-record writes.

Session Properties

The following rules and guidelines apply to PowerCenter session properties:
  • Pipeline partitioning is not supported on the reader or writer for sources or targets that were defined with sequencing enabled.
  • You can specify the
    File Name Override
    property for sequential or VSAM sources and targets.
  • For sources, the
    Flush After N Blocks
    property specifies the maximum number of block flushes that can occur across all groups without a given block being flushed. Define this property to ensure that all blocks are flushed at regular intervals.
  • For SEQ targets on z/OS, PowerExchange can allocate the target data sets based on z/OS data set allocation properties that you optionally define in the session properties.

0 COMMENTS

We’d like to hear from you!