Incorporating Adabas Tables and Views

#### Search Results

Search

# Incorporating Adabas Tables and Views

This document covers the following topics:

- Prerequisites for Adabas Tables/Views

- Selecting Adabas Tables/Views

- Incorporation Functions for Adabas Tables/Views

- Incorporating Adabas Tables and Views in Batch Mode

## Prerequisites for Adabas Tables/Views

See the section Adabas SQL Server in the Predict and Other Systems documentation.

Note
See also Concepts of Incorporation for basic information on how to use incorporation functions.

## Selecting Adabas Tables/Views

    10:00:30             *****  P R E D I C T  *****             2007-05-31
    Plan   0             - Incorporate Adabas Tables/Views -

    Table / View name ....

    Select options
      Tables or Views ...*
      Creator name .......

    Processing option
      Connect automatic .. N (Y,N)

Parameters
Table / view name | The name in Adabas SQL Server of the tables and views from which the data dictionary objects are to be created. Asterisk notation is allowed.
Tables or views |
Limit the function to files of one type. Valid values:
T | Adabas tables (files of type A(SQL) or Adabas SQL Server base tables (files of type AT or A(SQL).
V | Adabas views.
Creator name | The schema name of the tables and views in Adabas SQL Server from which the data dictionary objects are to be created. Asterisk notation is allowed.
Connect automatic |
Y | Adabas table/views and the Predict object are connected by the Compare function (code T) if no differences were detected between the field lists of the two objects.

    13:09:11             *****  P R E D I C T  *****             2007-05-31
                          - Incorporate Adabas Tables/Views -
    Search-crit.: Table/View name=ALL,Creator=ALL
                                                 Doc.
    Cmd Creator            Table/View name    T  exists  Remark

    __  ESQ                FILE150            T  No
    __  ESQ                FILE151            T  No
    __  ESQ                FILE152            T  No
    __  ESQ                FILE153            T  No

Columns in the List
Creator | Schema ID in Adabas SQL.
Table/view name | Name of the table/view.
T |
Type:
T | Adabas table
V | Adabas view
Doc. exists |
Y | Predict object exists for the table/view.
Remark | Any of the following type-specific remarks or blank. For type-independent remarks see Remarks which apply to all Object Types.
Master missing | The specified Adabas view cannot be incorporated in Predict until an object for a related Adabas file or Adabas view has been created, or file of type AT cannot be incorporated because the related Adabas file is not documented in Predict.
Different file type | The type of the specified Adabas table or view does not match the type of the corresponding Predict object: the file type of the data dictionary object is either not A (Adabas file) or not B (Adabas view).
Lev0 table exists | The base table in Adabas SQL Server has level 0, a corresponding Adabas file and an AT file not at level 0 exist in Predict, but the files have different IDs.

## Incorporation Functions for Adabas Tables/Views

Valid functions:

- Compare - Code T

- Connect - Code C

- Display Masters - Code M

- Incorporate - Code I

Note
Corresponding Adabas tables/views and Predict file objects of type A and B are identified by file ID.

### Compare - Code T

Compares Adabas table/views and corresponding Predict file object. Differences between field lists and attributes of the tables/views are reported.

If no differences between the field lists are found and Connect automatic is set to Y, the Adabas table/view and the Predict file object are connected.

### Connect - Code C

Connects Adabas tables/views to Predict file object and copies current information from the Adabas SQL Server directory to the dictionary object. Writes to the generation log of the Predict file object that a corresponding implemented table/view existed when the connection was established.

### Display Masters - Code M

A higher level object must be documented in Predict before the Adabas view can be incorporated. The function Display Masters finds all tables/views that are not documented but must be documented before table/views can be incorporated.

### Incorporate - Code I

#### Scope of the Incorporation

- One Predict file object is created for each table or view. The ID of the new file object consists of the creator name and name of the table or view joined by a hyphen.

- One field object is created for each field in the table or view. The ID assigned to each new field object will be the name of the field in Adabas SQL. For each view that is incorporated, the appropriate parts of the subselect specification in the SQL statement CREATE will be copied to the file and field objects created.

- One Predict field object (type SP) for each composite index or key is created.

- One file relation object is created for each referential constraint.

Incorporation Option
List incorporated code |
Y | The values of all attributes incorporated for the table or view are to be listed.

## Incorporating Adabas Tables and Views in Batch Mode

Command: `INCORPORATE ESQ`

Enter parameters on the next line in positional or keyword form.

Field | Keyword | Position
--- | --- | ---
Table/View name | TABLE | 1
Tables or Views | TYPE | 2
Creator name | CREATOR | 3
Connect automatic | AUTO-CONNECT | 4
Function | SUB-FUNCTION | 5
List incorporated code | LIST | 6

#### Example

To incorporate the table "TDEPT", code the command:

    INCORPORATE ESQ
    TABLE=TDEPT,TYPE=T,,,SUB-FUNCTION=I

or

    INCORPORATE ESQ
    TDEPT,T,,,I

The example above uses the Natural parameters `ID=,` and `IA==`.

### On this page

- Prerequisites for Adabas Tables/Views
- Selecting Adabas Tables/Views
- Incorporation Functions for Adabas Tables/Views
- Incorporating Adabas Tables and Views in Batch Mode