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

Moving VSAM Bulk Data

Moving VSAM Bulk Data

Use the following procedure to perform a VSAM bulk data movement operation. This procedure assumes that you are using PWXPC to integrate PowerExchange with PowerCenter.
Before you begin, get the following information:
  • Fully-qualified VSAM data set name
  • Fully-qualified data set name and member name of any COBOL or PL/I copybook that you want to use to define the layout of source or target records
  • z/OS user ID and password, if required by the PowerExchange SECURITY statement setting
To move VSAM bulk data:
  1. In the PowerExchange Navigator, create a data map. Include the following information:
    • In the
      Access Method
      list, select
      ESDS
      ,
      KSDS
      , or
      RRDS
      , depending on type of VSAM data set that you are using as the source or target.
    • Select the
      Import Record Definitions
      option to be prompted to import metadata for VSAM records from a COBOL or PL/I copybook. If you do not select this option, you can import a copybook later by clicking
      File
       
      >
       
      Import Copybook
      .
    • Select the
      Prefix record with XRBA value
      option for an ESDS data set or the
      Prefix record with RRN value
      option for an RRDS data set if you want PowerExchange to add an 8-byte XRBA or RRN value as a prefix in each record. If you select either option, make sure that the record layout in the data map includes sufficient space to accommodate the XRBA or RRN length.
    • Select the
      CI ACCESS
      option if you want the PowerExchange to access the contents of the entire control interval rather than individual data records when reading VSAM data set. If you want to extract all data from the control interval, this option might improve sequential read performance. However, if you specify a WHERE clause, this option does not improve performance.
    • For KSDS data sets, set the
      Offload Processing
      option to control if PowerExchange offloads processing for converting and merging data records from the PowerExchange Listener on the z/OS system to the system where extraction processing occurs. The extraction system is usually the system where the PowerCenter Client and PowerCenter Integration Service run.
    • In the
      Number of Data Buffers
      field, enter the number of I/O buffers to use for the data control intervals that PowerExchange requests VSAM to allocate. Increase the number of buffers to improve sequential access performance. In the
      Number of Index Buffers
      field, for KSDS, RRDS, and VRDS data sets only, you can also specify the number of I/O buffers to use for index control intervals. These buffer values override the VSAM statement, if specified, in the DBMOVER configuration member on the z/OS system.
      Complete the other fields as needed. Click
      Finish
      when you are done.
      Restriction:
      PowerExchange does not support the CI ACCESS option for compressed data or spanned records.
      If you did not select the
      Import Record Definitions
      option, go to step Moving VSAM Bulk Data.
      If you selected the
      Import Record Definitions
      option, The
      VSAM Copybook - Source Details
      page is displayed.
  2. Import a local or remote COBOL or PL/I copybook, if available, to define the layout of all or selected VSAM records.
    Depending on how you set the configuration options for the copybook import, the PowerExchange Navigator can prompt you to indicate for each record whether to import the record definition and to specify the record or field definition to use when alternative ones are defined in the copybook.
  3. Open the data map in the Resource Explorer, and click the nonrelational record view or the relational table view to verify that the metadata was successfully retrieved.
  4. To send the data map to the PowerExchange Listener on the remote z/OS system, select the data map in the Resource Explorer and click
    File
     
    >
     
    Send to Remote Node
    .
    In the
    Location
    field, enter the PowerExchange Listener node name that is specified in the NODE statement of the dbmover.cfg file on the local PowerExchange system. Complete the other fields, as needed.
    If you do not complete this step, you are prompted to send the data map to the remote node when you run a database row test.
  5. Run a database row test on the table view of the metadata to verify that actual data can be returned from the VSAM source database.
    If you need to change the data map to get the data you want, re-run the database row test on the revised data map.
  6. In the PowerCenter Designer, import the PowerExchange data map and create a mapping.
    When you import the data map, in the
    Location
    field, enter the PowerExchange Listener node name that you specified in the NODE statement of the dbmover.cfg file. Also, specify
    VSAM
    in the
    Source Type
    field (also displayed for targets).
  7. In the PowerCenter Workflow Manager, define a workflow and session and configure a PWX NRDB Batch application connection. Then start the workflow to perform the bulk data movement.

0 COMMENTS

We’d like to hear from you!