Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Storage Classifications
  24. Appendix A: Datetime and Numeric Formatting
  25. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Step 4. Import z/OS Metadata

Step 4. Import z/OS Metadata

Use the Enterprise Data Manager (EDM) to import metadata for each z/OS data source.
  1. To launch the Enterprise Data Manager, log in to Data Archive and select
    Accelerators > Enterprise Data Manager
    .
  2. To create an application version for the data source, right-click
    Custom Apps Only
    in the navigator pane, select
    New Application Version
    , and enter an application name and description.
  3. To import PowerExchange metadata for the application version that you created, complete the following tasks:
    1. Highlight the object and click
      File > Import Metadata from Database
      . The
      Connect to Import Metadata from Database
      dialog box appears.
    2. If you defined a connection, select it and enter your z/OS user name and password.
    3. If you are defining a conection, enter the data source name and the z/OS user name and password.
    The
    Database Mining
    wizard appears.
  4. Select the schema and list of tables for the data source.
  5. At the prompt to mine child tables of the selected tables, click
    No
    .
    Because the PowerExchange NRDB2 access method does not support foreign key relationships, you cannot mine child tables. By clicking
    No
    , you ensure that the PowerExchange Listener on z/OS does not spawn multiple subtasks that would return empty result sets. If you enabled the ILMBRIDGE or NOFKEYS Compatibility option for the PowerExchange ODBC connection, the PowerExchange Listener does not spawn multiple empty subtasks, regardless of what you select for this option.

0 COMMENTS

We’d like to hear from you!