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

Copybook Types Supported in Data Maps

Copybook Types Supported in Data Maps

You select the type of copybook to import in the
Type
list in the
Import Copybook - Source Details
dialog box.
The type of copybook that you can import depends on the data source type of the data map into which you are importing the copybook, as follows:
  • Data maps for all data source types except DB2
    . Import a COBOL or PL/I copybook from the local or a remote system to define the layout of records and fields.
  • Adabas data maps
    . You can import both a field definition table (FDT) and a copybook into an Adabas data map, as follows:
    • FDT
      . Each database file has a corresponding FDT, which defines the record structure and the content of each field in the physical file. For each field in the record, the FDT defines the level, name, length, format, options, and special field and descriptor attributes. An FDT provides short names and no scale information. After you import an FDT, it is cached on the local system for subsequent sessions.
      You can display an FDT for an Adabas data map. When you display the FDT, you can optionally refresh the locally saved FDT with data from the FDT on the remote system.
    • ADACMP
      . A file created by using the ADACMP utility.
    • DDM
      . A Natural data definition module (DDM) for Adabas for z/OS sources. Provides long name and scale information.
    • PREDICT
      . A Predict data dictionary. Provides long names and scale information.
    • TEXT
      . A text file that uses an Informatica internal delimited format.
    • COBOL
      or
      PL/1
      . If you import a COBOL or PL/I copybook into an Adabas data map, you must edit table properties in the data map to associate the imported field definitions with Adabas field definitions.
  • Datacom data maps
    . Import a COBOL or PL/I copybook, or import a DATACOM copybook from a remote z/OS system or a local .dcm file. A DATACOM copybook provides combined CA Datacom/DB schema and COBOL copybook information.
  • IDMS data maps
    . Import a COBOL or PL/I copybook, or import an IDMS copybook from a remote z/OS system or a local .idm file. An IDMS copybook provides combined CA IDMS/DB schema and COBOL copybook information.
  • DB2 for i5/OS, DB2 for Linux, UNIX, and Windows, DB2 for z/OS, and DB2 unload file data maps
    . You can import a DB2 catalog.
  • DB2 for i5/OS data maps that are accessed sequentially
    . Import a COBOL or PL/I copybook, or import a data description specifications (DDS), which describe data attributes in file descriptions that are external to the application program that processes the data.
  • IMS DL/1 batch and ODBA data maps
    . Import a database description block (DBD) to add segment, key field, search field, and CCK field definitions from the IMS database, and to add tables to the data map. Importing a DBD also defines the hierarchical sequence of segments.
    After you import a DBD, import a COBOL or PL/I copybook into each segment in the data map to overlay the segment with its COPYLIB. This action redefines the data map while maintaining the hierarchical metadata for the database.

0 COMMENTS

We’d like to hear from you!