![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
To assist in the definition of ADA tables, Adabas file definitions can be extracted so that their table information is available for the definition process. Your system administrator extracts the Adabas file definition information and stores it in TIBCO Object Service Broker.After extracting the Adabas file definition into TIBCO Object Service Broker, you can use it to create a TIBCO Object Service Broker ADA table. If this information does not exist or was not extracted, the definition is based on the known structure of the Adabas file structure. If there is no extracted data, the Table Definer is unable to verify that the structure is correct and issues a warning message before the definition is saved.
The extracted Adabas file definition information is stored in a TIBCO Object Service Broker TDS table. Because the extracted data is static, you must re-extract the table information whenever changes are made to new or existing Adabas table definitions.
• The Execution Environment performing the extract must have the Adabas interface program ADALNK available. The load name and load DD can be customized with the @CONFIGURESERVER tool.Refer to Configuration Parameters for information about using @CONFIGURESERVER.
1. Execute the @ADAEXTRACT rule using the EX execute rule option on the workbench.
2007-01-20 ADABAS EXTRACT UTILITIES USR40
Cmd ==>
Select Extract Functionality
Extract one definition : _
List all extracted definitions : _
List all possible definitions : _
Extract all possible definitions : _
Extract all non-extracted definitions : _
PFKEYS: 2=LOGS 3=EXIT 12=EXIT
2. On the displayed screen, position your cursor on one of the following menu options and press Enter:
Extract one definition You can use this to specify the Database ID and the File Number of a file to be extracted in isolation. List all extracted definitions Displays a list of all Adabas files whose definitions were extracted. List all possible definitions Displays a list of all extracted definitions including Adabas files not yet extracted. Extract all possible definitions Extracts definitions from all the Database IDs and File Numbers defined to Adabas. The process also deletes existing definitions before running the new extract. Extract all non-extracted definitions Performs the same processing as above except for deleting or re-extracting previously extracted file definitions.Extracting or listing multiple definitions could take a significant time to complete, depending on the number of Adabas databases and files in your configuration. If you select List all extracted definitions, an Extract Screen listing similar to the one shown below appears:
2007-01-20 ADABAS EXTRACT UTILITIES USR40
Cmd ==>
Database File Extract
ID No Date Description
--- --- 2007-01-19 employees
_ 1 2 2007-01-19 vehicles
_ 1 3 2007-01-19 miscellaneous
_ 1 4 2007-01-19 agent info
_ 1 21 2007-01-19
_ 1 22 2007-01-19
_ 1 23 2007-01-19
_ 1 24 2007-01-19
_ 1 25 2007-01-19
_ 1 26 2007-01-19
_ 1 27 2007-01-19
_ 1 66 2007-01-19
_ 1 71 2007-01-19
_ 1 99 2007-01-19
S=Edit Description D=Delete X=Extract
PFKEYS: 3=EXIT 12=CANCEL
Deletes the extracted data from the TIBCO Object Service Broker definition database. When you issue the S line command to edit the description, a screen similar to the one shown below appears, enabling you to edit extracted Adabas file descriptions.
2007-01-20 ADABAS EXTRACT UTILITIES USR40
Cmd ==>
Database Id: 1 File Id: 2
Description: vehicles
PFKEYS: 3=EXTRACT & SAVE 12=CANCEL
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |