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

Introduction to Bulk Data Movement for Sequential Files

Introduction to Bulk Data Movement for Sequential Files

PowerExchange, in conjunction with PowerCenter, can move bulk data from or to sequential data sets on z/OS or files on i5/OS, Linux, UNIX, or Windows. These types of sources and targets use the SEQ access method.
Hereafter, the term
sequential file
is used to refer to sequential data sets on z/OS and files on i5/OS, Linux, UNIX, or Windows systems.
You must create a data map that uses the SEQ access method in the PowerExchange Navigator for a sequential file source or target. PowerExchange uses the data map to access data and metadata and to create a relational type view of the records. PowerExchange requires a relational view to use SQL‑type statements to read bulk data.
Also, run a PowerExchange Listener on the system where the source is located. Verify that this PowerExchange Listener can communicate with the system or systems where the PowerExchange Navigator, PowerCenter Client, and PowerCenter Integration Service run.
When reading a sequential file, the system determines the record length according to what has been specified in the NRDB data map properties and the operating system file APIs, then maps it into columns ready for processing by a relational system.
When writing a sequential file, the system appends the column data into a record using the data map field sizes and then writes it according to what has been specified in the NRDB data map properties.

0 COMMENTS

We’d like to hear from you!