Table of Contents

Search

  1. Preface
  2. PowerExchange Navigator Introduction
  3. Data Maps
  4. Data Maps for Specific Data Sources
  5. Copybooks
  6. Registration Groups and Capture Registrations
  7. Extraction Groups and Extraction Maps
  8. Personal Metadata
  9. Database Row Test
  10. PowerExchange Navigator Examples
  11. Appendix A: PowerExchange Functions for User-Defined Fields
  12. Appendix B: User Access Method Programs
  13. Appendix C: Application Groups and Applications
  14. Appendix D: Data Map Properties
  15. Appendix E: Record, Field, and Table Properties
  16. Appendix F: DTL__CAPXTIMESTAMP Time Stamps
  17. Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook

Navigator User Guide

Navigator User Guide

Adabas Data Maps

Adabas Data Maps

You can import a copybook, an Adabas field definition table (FDT), and Adabas keys when you add an Adabas data map or after you add it.
The FDT defines the layout of the data in a data source. When you import an FDT, the data definitions in the data map are stored on the local system. If you import Adabas keys into the data map, you can add these keys to tables in the data map.
You can refresh the FDT after you add the data map.
You can import any of the following copybook types into an Adabas data map:
  • COBOL copybook. If you import a COBOL copybook, you must edit the data map to associate the imported field definitions with Adabas field definitions.
  • PL/I copybook. If you import a PL/I copybook, you must edit the data map to associate the imported field definitions with Adabas field definitions.
  • File created by using the ADACMP utility.
  • Natural Data Definition Module (DDM). To import a DDM, you must enter the FDIC database ID and file number values.
    If you import DDM metadata for Adabas databases on z/OS that contain wide character datatypes, PowerExchange does not select the
    Wide Char
    option on the
    Code Page
    tab for these fields. You must either import Predict or FDT metadata, or edit field properties in the data map to select the Wide Char option for all wide-character datatypes.
  • Adabas field definition table (FDT) that contains the database definition, which provides short names and no scale information. An FDT enables validation of Adabas-related information such as field names, array sizes, and override lengths. After you import an FDT, it is cached for subsequent sessions, which enables certain validation checks to occur prior to run time. You can refresh an imported FDT.
  • Predict data dictionary, which provides long name and scale information. To import a Predict data dictionary, you must enter the FDIC database ID and file number values.
  • Text file, which uses a delimited Informatica internal format.
You can subdivide, or redefine, any PowerExchange field mapped to an Adabas field. To subdivide a field, define it as a group field with subfields that remap the group.
To test an Adabas data map, run a database row test.

0 COMMENTS

We’d like to hear from you!