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 CA-Datacom Table wizard

Use the New CA-Datacom Table wizard to map information from a copybook to a new table for CA-Datacom.

The copybook from which you want to create a table must be listed in the COBOL Copybooks folder in your data project.

CA-Datacom is not supported as a data source for change capture or replication.

Specify Location and COBOL Copybook page

Use this page to select the database model and the schema under which you want to create the table. Also, select the copybook on which to base the table.

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.
Copybook
Type the path and name of the copybook on which you want to base your table. For example, if your project is named MyProject and your copybook is named copybook1, type \MyProject\copybook1. You can click Browse to select a copybook that is located on your file system.
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.
Create view
Use these controls to indicate whether you want to create a view on the table.
No
Specifies that you do not want to create a view.
Yes
Specifies that you want to create a view on the table. This option allows you to create a view for Classic federation. You can use the view to filter record types and to filter rows and columns.

Specify CA-Datacom Information page

Use this page to select the 01 level that will be the first column in your table, to name the table, and to specify the location of the data structures in your database.

Select 01 level
If the copybook has more than one 01 level, select the 01 level that contains the elements that you want to map as columns in the table.
Table name
Type a name for the table that you want to create. By default, the wizard uses the name of the 01 level that you specify. You can change this default.
Record entity-occurrence name
Type an identifier of 1 to 32 characters for the CA-Datacom table that the Classic table definition references. The name follows CA-Datacom/DB entity naming conventions.
Status/Version
Select or type the status and version of the CA-Datacom table that contains the elements that you want to map to. The status and version can contain explicit values of TEST, PROD, or HIST or a value that begins with a T or H followed by a three digit number.
User requirement table
Type the name of the User Requirements Table (URT) that is used to access the CA-Datacom table that contains the elements that you want to map to. The name must exist in a data set that is referenced by the server's STEPLIB DD statement or reside in the link pack area. The name follows z/OS® load module naming conventions.

A User Requirements Table (URT) must be provided on every request for service that is sent to CA-Datacom. Every service request is validated against an open User Requirements Table. This technique provides security (by restricting access) and efficient allocation of CA-Datacom resources. When you define your User Requirements Tables, consider the security implications. You must decide whether to have one User Requirements Table per CA-Datacom table that you map into the metadata catalog, or have only a few User Requirements Tables for all CA-Datacom tables that you map into the metadata catalog. Fewer User Requirements Tables result in more relaxed security.

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.

Select Elements to Map to Columns page

Use this page to select the elements that you want to map to columns in the logical table.

Default OCCURS processing options
Specify how to map record arrays. Your selection applies to the record arrays in the entire table. You can override this default by selecting an OCCURS statement and clicking Change OCCURS processing for the selected array.
Create record arrays
Specifies to map record arrays as arrays. This option is available if you chose to use the table for queries only, not for modifying data or for change capture.
Expand each occurrence
Specifies to map all arrays as sets of columns. The number of sets that are mapped for an array depends on the maximum number that is specified in the OCCURS statement for that array. For example, an array with three elements and five maximum occurrences is mapped into 15 columns: five sets of three columns.
Expand first occurrence
Specifies to map only the first occurrence of all arrays as sets of columns. For example, an array with three elements and five maximum occurrences is mapped into only one set of columns.
Table
Lists the records that are available to be mapped to columns. The following list describes the meaning of the different icons:
The record is not selected.
The record is not selected.
The record is selected.
The record is selected.
The record can be mapped to a column, but is not currently selected.
The record can be mapped to a column, but is not currently selected.
The record cannot be mapped to a column.
The record cannot be mapped to a column.
The record will be mapped to a column.
The record will be mapped to a column.
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.
(Tree view)
Displays the elements in the selected record. Select records to map to columns.
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 record (Map the highlighted group record, if it is selected.)
Maps the highlighted group record, if it is selected. By default, selecting a group record causes the child records to be mapped, but does not cause the group element to be mapped. If you want to map the group element, highlight it and click this button.
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 element (Rename the selected element)
Opens the Rename window so that you can rename the element that is highlighted in the tree view.
Rename all elements (Rename all elements)
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

Specify Search Condition for View page

If you chose to create a view, use this page to build the search condition for the WHERE clause in the subselect for the view.

View name
Provide a name for the view.
Table
The table lists the parameters that you create for the search condition.
Adds a criterion to the WHERE clause.
Adds a parameter to the search condition.
Deletes a criterion from the WHERE clause.
Deletes a parameter from the search condition.
Moves the criterion up.
Moves the parameter up.
Moves the criterion down.
Moves the parameter down.

Summary page

Use this page to verify the columns of the table that will be created when you generate and run the DDL.

If you are creating a view on the table, you can view the SELECT statement that Classic Data Architect will base the view on.

You can click Finish to generate the model for the table.



Feedback

Update icon Last updated: 2007-10-09