WebSphere logo Classic Federation Server for z/OS, Version 9.1
WebSphere logo Classic Replication Server for z/OS, Version 9.1
WebSphere logo Classic Data Event Publisher for z/OS, Version 9.1
WebSphere logo Data Integration Classic Connector for z/OS, Version 9.1


Creating Adabas tables and views for Classic federation

To query or update data in an Adabas database, you must create a relational table that maps to that database. You can also create a view on the table. You use the New Adabas Table wizard to create a table and a view.

Show me!

Before you begin

Restrictions

About this task

For more information about creating tables and views that map to Adabas databases, see the related links for Adabas syntax diagrams and for views.

Procedure

To create an Adabas table and optionally a view for Classic federation:

  1. Optional: Use the Adabas page of the Preferences window to set these default values:
    • The name of the Predict dictionary that you want to use.
    • The date format that Classic Data Architect should convert dates to.
    • The time format that Classic Data Architect should convert times to.
    • The maximum length for VARCHAR data.
    • The maximum length for LVARCHAR data.
    • The maximum number of occurrences for all fields that occur multiple times in an Adabas file.
    • Whether to use the User Synonym field from the Predict Dictionary when this field is defined.
  2. Map your Adabas database to a relational table by using the New Adabas Table wizard.
    1. Open this wizard by right-clicking either the database in your data design project or one of the schemas within the database. Select Add Classic Object > Adabas table.
    2. Select the model and schema in which you want to create the table.
    3. Choose whether or not to create a view on the table.
    4. Choose whether to connect to your Adabas database through an existing connection to a data server or whether you want to create a new connection to a data server. Either data server must be configured to access the Adabas database.
    5. Specify the format of dates and times, the lengths of VARCHAR and LVARCHAR data types, and the maximum number of occurs. The default values that appear are either the global defaults that are set for the Adabas database or the defaults that are set in the Adabas page of the Preferences window.
    6. Specify whether you plan to use the table (and view, if you are creating one) for queries, updates, or both.
    7. Provide either the Predict or Adabas information that is necessary for the discovery process.
    8. Select the Adabas fields that you want to map to columns in your relational table.
    9. Optional: In the ISN name field, provide a name for the column that maps to the Adabase Internal Sequence Number (ISN).

      The default column name is ISN.

    10. If you are creating a view, specify the criteria for the WHERE clause.
    11. Modify the names of columns and provide null values.
    When you finish the wizard, the new table appears under the selected schema. If you created a view, it also appears under the selected schema.
  3. Optional: Modify the table properties or add privileges. Select the table, and make any changes in the Properties view.
  4. Optional: Generate the DDL for the table. You can generate the DDL later, if you do not want to generate it now. You can also generate the DDL for all of the objects within the same schema. See Generating DDL.
    1. Right-click the table and select Generate DDL.
    2. In the Generate DDL wizard, follow these steps:
      1. Choose to generate CREATE statements.
      2. Choose to generate DDL for tables.
      3. Name the file in which to save the DDL within your project.
      4. Choose whether to run the DDL on a data server. After you run the DDL, check the Data Output view to determine if the DDL ran successfully.
      5. Choose whether to open the DDL for editing.
  5. Optional: If you ran the DDL successfully on a data server, validate the table by running a test query against your Adabas database. Be sure that the data server is connected to that database.
    1. In the Database Explorer, search your data server for the schema that you created the table in. Expand the schema and expand the Tables folder.
    2. Right-click the table and select Data > Sample Contents.
    3. Check the Data Output view to determine whether the test query ran successfully.
  6. Optional: If you created a view, you can generate the DDL for the view now or later. You can also generate a DDL for all of the objects within the same schema. See Generating DDL.
    1. Right-click the view and select Generate DDL.
    2. In the Generate DDL wizard, follow these steps:
      1. Choose to generate CREATE and ALTER statements.
      2. Choose to generate DDL for views.
      3. Name the file in which you want to save the DDL within your project.
      4. Choose whether to run the DDL on a data server. After running the DDL, check the Data Output view to find out whether the DDL ran successfully.
      5. Choose whether you want to open the DDL for editing.
  7. Optional: If you ran the DDL successfully on a data server, validate the view by running a test query against your Adabas database. Be sure that the data server is connected to that database.
    1. In the Database Explorer, search your data server for the schema that you created the view in. Expand the schema and expand the Views folder.
    2. Right-click the view and select Data > Sample Contents.
    3. Check the Data Output view to determine whether the test query ran successfully.
Related concepts
Mapping data for Classic federation
Array processing
Creating views on existing tables
Viewing and modifying objects
Populating metadata catalogs
Related tasks
Creating CA-Datacom tables and views for Classic federation
Creating CA-IDMS tables and views for Classic federation
Creating CICS VSAM tables and views for Classic federation
Creating tables and views for DB2 for z/OS databases
Creating IMS tables and views for Classic federation
Creating sequential tables and views for Classic federation
Creating VSAM tables and views for Classic federation
Modifying the PCB selection for IMS tables or indexes
Mapping tables and views for redefined data
Creating indexes
Creating stored procedures
Related information
Views


Feedback

Update icon Last updated: 2007-10-09