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

Named Pipes on Linux and UNIX

Named Pipes on Linux and UNIX

On Linux and UNIX, PowerExchange can read text files from named pipes in the same manner as normal disk files. However, if the final record contains a binary zero, the record is truncated.
When processing named pipes, PowerExchange cannot use the ftell() API. Instead, PowerExchange uses one of the following values as the record length:
  • For the last record, the number of bytes preceding the binary zero terminator
  • For records other than the last record, the number of bytes preceding the LF terminator
If you must read named pipes on Linux or UNIX, you can work around the restrictions by using one of the following methods:
  • Have the program writing the data write an extra trailer record prior to closing the pipe.
  • Write a user access method program to read the pipe. For more information, see the appendix, "User Access Method Programs," in the
    PowerExchange Navigator User Guide
    .
The maximum record size that PowerExchange can process is 147,456 bytes (144 KB). However, certain variable types that use NUM16 integers enforce a 32-KB limit, such as VB12, VBX2, and VBP2.

0 COMMENTS

We’d like to hear from you!