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

Datacom Data Map Items

Datacom Data Map Items

In a Datacom data map, define elements and keys to optimize CA Datacom/DB data access.
An element is the unit of transfer used between CA Datacom/DB and applications issuing CA Datacom/DB commands. An element consists of one or more contiguous columns, or FIELD entity occurrences. An element should contain columns that an application program uses at run time. Each table has at least one and no more than 255 elements.
Keys and key segments set the sort order for data retrieval. A key is composed of columns, which can be non-contiguous and in any sequence. Each column in a key can be either ascending or descending in value. Each key can be up to 180 characters long. Define a maximum of 99 keys for a table and 999 keys for a database. Define any key as unique, if each row in the table specifies a unique value for the key.
You must define a master key and a native key for each table in a Datacom data map. The master key behaves like other keys, but you can enable or disable changes to the master key. The native key dictates the physical sequence in which the data is stored. The native key can be the same as the master key.

0 COMMENTS

We’d like to hear from you!