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


New Adabas Table wizard

Use the New Adabas Table wizard to map information from an Adabas database to a table.

You specify the location of the data structure that you want to base the table on. Classic Data Architect will connect to the data server, which in turn will connect to the Adabas database to retrieve the information that you specified.

Select Database and Schema page

Use this page to select the data model and schema in which you want to create the table in your project.

Database model
Type the path and name of the database model in which you want to create the table. For example, if your project is named MyProject and your database model is named MyModel, type \MyProject\MyModel. You can click Browse to select a database model.
Schema name
Select the schema in which you want to create the table, or type a new schema.

Select Connection page

Use this page to select the connection that you want to use to connect to the Adabas database. You can use an existing connection or create a new one.

If you choose to create a new connection, click Next to set up this connection.

Create a new connection
Select if you need to create a connection to a data server that is configured to access an Adabas database. You can create the new connection when you click Next.
Use an existing connection
Select if you want to access your Adabas database through an existing connection to a data server.
Existing connections
Select from the existing connections to data servers. The data server that you connect to must be configured to access the Adabas database that contains the information to map to your table. When you click Next, Classic Data Architect prompts you for a user ID and password and attempts to connect to the data server.

Connection Parameters page

If you chose to create a new connection, use this page to set up the connection.

Connection identification
Use these controls to give a name to the connection.
Use default naming convention
Select to give the connection the name that you provide in the Data source field.
Connection name
If you do not want to use the default naming convention, provide the name that you want to give the connection.
JDBC driver
Verify that the value is Classic Integration Server JDBC Driver. This driver is located in the eclipse\plugins\com.ibm.datatools.db2.cac_1.0.0\driver directory.
Connection URL details
Use these controls to build the connection URL.
Data source
Specify the name of the query processor that you want to connect to. A query processor is often referred to as a data source because it receives requests from client applications and accesses data for the client.
Host
Specify the IP address or host name for the data server to which you want to connect.
Port number
Specify the number of the port on which the query processor is listening for requests.
Code page
Specify the code page that you will use for messages that are sent to the data server. Data servers support only EBCDIC data on z/OS®. Because Java™ uses Unicode to represent string and character data, the JDBC driver converts the Unicode strings into EBCDIC format. The driver uses the code page property or parameter to do the conversion.
JDBC driver class
Verify that the driver class is com.ibm.cac.jdbc.Driver.
Class location
Verify that the path that is displayed points to the file cacjdbc21.jar. This file is in the directory plugins\com.ibm.datatools.db2.cac_1.0.0\driver\.
Connection URL
Displays the URL that will be used for connections to the specified query processor on the data server. The URL is generated from the values that you provide in the other fields for the connection URL details. You can edit the URL directly.

Adabas options page

Use this page to set various options for the DDL that the wizard will generate to define the table. You also specify how you plan to use the table.

Date format
Select the format to use for Adabas DATE fields. For a description of the choices, see DATE and TIME data types for Adabas databases.

You can specify an alternate format for the DATE data type if you do not want to use the default format MM/DD/YY.

The following DATE formats are supported by Classic Data Architect, where DD is the day of the month, MM is the month of the year (as in "01" for January), YY is a two-digit year (as in "06" for 2006) and YYYY is century and year information (as in "2006"). The examples that follow each format are for January 31, 2006.

Table 1. Date formats that are supported by Classic Data Architect
Format of DATE data type Rendering of January 31, 2006
DD/MM/YY 31/01/06
DD.MM.YY 31.01.06
YY-MM-DD 06-01-31
DD/MM/YYYY 31/01/2006
DD.MM.YYYY 31.01.2006
YYYY-MM-DD 2006-01-31
MM/DD/YYYY 01/31/2006
MM/DD/YY 01/31/06
YYYYMMDD 20060131
Instead of being rendered as two digits, the month can be rendered with the first three characters of its US English name or its full US English name in lowercase:
Table 2. US English name date formats that are supported by Classic Data Architect
Format of DATE data type Rendering of January 31, 2006
DD mmm YYYY 31 Jan 2006
DD mmmmmmmmm YYYY 31 January 2006

Classic Data Architect also supports representing the month and day in Julian format using the DDD syntax:

Table 3. Julian date format that is supported by Classic Data Architect
Format of DATE data type Rendering of January 31, 2006
YYYYDDD 2006031
Time format
Select the format to use for Adabas TIME fields. For a description of the choices, see DATE and TIME data types for Adabas databases.

You can specify an alternate format for the TIME data type if you do not want to use the default format HH/MI/SS.

The following TIME formats are supported by Classic Data Architect, where HH is the hour of the day in 24-hour clock notation, MI is the minute of the hour, and SS is the seconds.. The examples that follow each format are for 3:29:45 PM, January 31, 2006.

Table 4. Date and time formats supported by Classic Data Architect
Format of TIME data type Rendering of 3:15 PM, January 31, 2006
DD/MM/YYYY HH:MI:SS 31/01/2006 15:29:45
DD.MM.YYYY HH:MI:SS 31.01.2006 15:29:45
YYYY-MM-DD HH:MI:SS 2006-01-31 15:29:45
YYYYMMDD HH:MI:SS 20060131 15:29:45
YYYYDDD HH:MI:SS 2006031 15:29:45
MM/DD/YYYY HH:MI:SS 01/31/2006 15:29:45
MM/DD/YY HH:MI:SS 01/31/06 15:29:45
DD mmm YYYY HH:MI:SS 31 Jan 2006 15:29:45
VARCHAR maximum length
Type the maximum length to allow for VARCHAR fields. If you want to override this value for individual columns, you can do so in the Properties view for those columns after you create the table in your project.

To see the Properties view for a column, in the Data Project Explorer expand the table and select the column.

LVARCHAR maximum length
Type the maximum length to allow for LVARCHAR fields. If you want to override this value for individual columns, you can do so in the Properties view for those columns after you create the table in your project.

To see the Properties view for a column, in the Data Project Explorer expand the table and select the column.

Maximum occurs
Type the maximum number of occurrences for all fields that occur multiple times in an Adabas file. This default applies to the entire table, although you can overwrite the default for individual fields. If you do not specify a value, Classic Data Architect uses the occurrence count value that Predict specifies. If Predict is not available, the value 0 is used.
Select table usage
Specify how the table will be used.
Query
Specifies that the table will be used for retrieving data by Classic Federation.
Update
Specifies that the table will be used for updates of data by Classic Federation.
Change capture
Specifies that the table will be used as a source table for a publication or a subscription.
Comments
Type any comments that you want to associate with the table, such as the time and date that you created it and the records it contains.

Adabas Discovery Options page

Use this page to supply values for parameters to help Classic Data Architect locate the Adabas information to base your table on.

View name
Type the name of the Predict view that describes the contents of an Adabas file that has fields that you want to map to columns. Classic Data Architect retrieves the Adabas Field Description Table (FDT) information for the Adabas file that is referenced by the view. If you want Classic Data Architect to access an Adabas file's FDT directly, do not provide a view name. Instead, provide the number of the Adabas file in the File number field.
Predict dictionary
If you supplied a view name, you must type the number of the Adabas file where the Predict definitions are stored.
Predict password
Optional: Type the Adabas read password for the file that the Predict information is stored in, if a password is needed for accessing the file. Passwords are DES encrypted into hexadecimal format when passed to the data server and then decrypted when passed to Adabas.
File number
Type the number of the Adabas file that has the information that you want to map to columns. You must provide a file number if you do not provide a view name in the View name field. If you do provide a name in the View name field, the field number is optional.

With this information, Classic Data Architect can access directly the Field Description Table (FDT) for the Adabas file. When Classic Data Architect accesses an FDT directly, Classic Data Architect requests information for all fields and Special Descriptor Table information that is defined for the file.

File DBID
Optional: Type the identifier of the database in which the Adabas file is stored. This Adabas file is either the file that is identified in the File number field or the file that is referenced by the Predict view. The default value is 0, in which case normal Adabas DBID resolution will occur. The identifier, if specified, must be between 1 and 65535.
File read password
Optional: Type the Adabas read password, if a password is needed, for the file with the Field Description Table that contains information about the fields that you want to map to columns.
File modify password
Optional: Type the Adabas modify password, if a password is needed for updating the contents of the Adabas file.
Table name
Specify the name of the table that you are creating. You can specify a two-part qualified name with the table owner as the authorization ID.
Use synonyms
Select if you want Predict synonyms to be used for column names.
Comment
Add any comments to describe the table.

Column Selection page

Use this page to select the fields that you want to map to columns in your table.

Explanation of the tree view

After Classic Data Architect returns information to the New Adabas Table wizard about the fields in the Adabas file that you specified, the wizard displays the fields so that you can select the ones that you want to map to columns.

If you do not supply the name of a Predict view, the default naming convention for columns is used. This default naming convention is FILE%1_%2 where %1 is replaced with the contents of the FILE column with leading zeros removed, and %2 is the two-character Adabas field name.

If you supply the name of a Predict view and select the Use Synonym check box, and if a synonym was specified in the Predict definition for a FDT definition, the synonym is used as the name of a column. If you do not select the Use Synonym check box, or the synonym contains spaces, the Predict field name is used as the name of a column.

Predict synonyms and field names are converted into SQL names. Any dashes in the Predict name are converted to underscores.

You can change any of the column names in one of these ways:

  • Edit the name on the Summary page of the wizard.
  • After you create the table, you can expand the table in the Data Project Explorer. Select the column and change its name in the Properties view.
  • After you create the table, you can expand the table in the Data Project Explorer. Click the name of the column twice (but do not double-click the name) and then edit the name.

The names of the fields contain, at a minimum, the two-character Adabas field name that is extracted from the FDT/SDT definition. Additional information that is appended to the end of an Adabas field name indicates when a column is to be used as a "count" column and when the column references an Adabas field that exists within a periodic group (PE), multiple value (MU) fields, or both.

Count columns
The value “C,2” is appended to the end. These values tell the Adabas connector that the column with one of these field names is to be treated as count column and that its length is 2 bytes long. The column should be treated as a SMALLINT SQL data type.
If the FDT field name that the count column references is both a periodic group (PE) and multiple value field (MU), a “1” is inserted after the two-character field name and before the “C,2” is appended to the name.
References to periodic groups and multiple value fields
A “1” is appended after the two character Adabas field name to indicate that the Adabas field contains repeating data. If the Adabas FDT is both a periodic group (PE) and multiple value (MU) field, “(1)” is appended after the “1” to indicate that the Adabas field repeats within repeating data.
Controls on this page of the wizard
Default PE/MU processing options
Provides options for mapping PE and MU fields.
Create record arrays
Specifies to map record arrays as arrays. This option is available if you chose to use the table only for queries, not for modifying data or for change capture.
Expand each occurrence
Specifies to map each array element as an individual column. The number of columns for an array depends on the maximum number specified in the OCCURS statement for that array. For example, an array with 3 elements and 5 maximum occurrences is mapped into 15 columns.
Map the first occurrence only
Specifies to map only the first occurrence of each array.
Find
Lets you search for text within the tree view.
Search flashlight
Click to search for the text that you entered in the Find field.
PE/MU processing
Opens a window that lets you specify processing for a count field that is associated with a PE or MU field.
(Tree view)
Select the fields that you want to map to columns in the table.
Expand all (Expand all)
Expands all nodes that are displayed in the tree view.
Collapse all (Collapse all)
Collapses all nodes that are displayed in the tree view.
Map the selected group element (Map the selected group element)
Change OCCURS processing for the selected array (Change OCCURS processing for the selected array)
Specifies OCCURS processing options for a record array that is highlighted in the tree view.
Rename the selected fields (Rename the selected fields)
Opens the Rename window so that you can rename the element that is highlighted in the tree view.
Rename all fields (Rename all fields)
Opens the Rename All Elements window so that you can add prefixes and suffixes to the names of all of the elements or remove prefixes and suffixes.

Summary page

Use this page to verify the columns that will be created in the table, modify column names, change column null values, and indicate whether an index should be defined on the column. By default, Y is displayed in the Create Index column for all table columns that are mapped to fields with the DE option.

Adabas formats are converted to SQL data types according to the types, lengths, and options settings for the formats.

Adabas columns support DATE and TIME SQL data types that can be obtained from Predict information. Also, if Predict information is available, the Predict data type information overrides the default data type assignment.

The following table lists the SQL data types that correspond to Adabas format types, lengths, and options.

Table 5. SQL data types that correspond to Adabas formats
SQL data type Adabas format type Adabas format length Adabas format options
CHAR A Non-zero LA OPTIONS2 bit not set
VARCHAR A Zero LA OPTIONS2 bit not set
LONG VARCHAR A Zero  
SMALLINT B Less than 2  
INTEGER B 3 or 4  
SMALLINT F 2  
INTEGER F 4  
REAL G 4  
DOUBLE PRECISION G 8  
DECIMAL P or U    


Feedback

Update icon Last updated: 2007-07-11