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

Overwriting Existing Files on z/OS

Overwriting Existing Files on z/OS

In a PowerCenter workflow with a sequential file target, PowerExchange can overwrite an existing file on disk or tape. PowerExchange reuses the existing RECFM, LRECL and BLKSIZE attributes, regardless of the values that you specify in the session attributes for the connection.
Technically, PowerExchange calls the fopen() API, which uses the existing file attributes.
A PowerCenter workflow can also overwrite an existing tape file. However, in certain cases the process might be affected by constraints from the virtual tape system. PowerExchange calls the fldata() API to retrieve the attributes of the existing tape file. PowerExchange uses these attributes when it reopens the file.

0 COMMENTS

We’d like to hear from you!