This document covers the following topics:
See the section Adabas SQL Server in the Predict and Other Systems documentation.
See also Concepts of Incorporation for basic information on how to use incorporation functions.
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)
|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||
|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.|
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.|
|Remark||Any of the following type-specific remarks or blank. For type-independent remarks see Remarks which apply to all Object Types.|
Corresponding Adabas tables/views and Predict file objects of type A and B are identified by file ID.
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.
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.
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.
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.
|List incorporated code||
Enter parameters on the next line in positional or keyword form.
|Tables or Views||TYPE||2|
|List incorporated code||LIST||6|
To incorporate the table "TDEPT", code the command:
INCORPORATE ESQ TABLE=TDEPT,TYPE=T,,,SUB-FUNCTION=I
INCORPORATE ESQ TDEPT,T,,,I
The example above uses the Natural parameters