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 IMS Table wizard

Use the Map IMS™ Table wizard to map information from an existing DBD and copybook to a new table.

The DBD from which you want to create a table must be listed in the IMS References folder in your project.

Each table that maps an IMS database represents a path of one or more segments in the database. The path is defined by a leaf segment and all segments up the parent chain to the root segment of the hierarchy. The selected leaf segment can be any segment in the DBD.

If no index is defined, access is assumed to be through the physical hierarchical view as defined in the IMS DBD. If you map tables using IMS secondary indexes, IMS inverts the hierarchy if the index is not on the root segment. The index segment becomes the implied root of the new IMS hierarchy. All access to the defined table must be through the selected secondary index. This requirement ensures a consistent hierarchical view of the IMS database.

Specify Location and DBD File page

Use this page to select the database model and the schema that you want to create the table in. Also, use this page to select the DBD 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.
DBD file
Type a short identifier for the name of the IMS DBD (database definition) that the table will reference. The DBD name corresponds to the name that is specified on the NAME parameter on the DBD statement in the DBDGEN source definition for the IMS logical or physical database that the IMS table references. The DBD name follows z/OS® load module naming conventions.
Schema name
Select the schema in which you want to create the table, or type a new schema.

Specify IMS Information and Table Usage page

DBD name
Displays the name of the IMS DBD (database definition) that the table will reference.
DBD type
Displays the name of the IMS DBD (database definition) that the table will reference.
Leaf segment
Select the name of an IMS segment definition. Each table that you map to IMS data represents a path of one or more segments. The path is defined by a leaf segment and all segments up the parent chain to the root segment of the hierarchy. The selected leaf segment can be any segment in the DBD.
For a logical or physical database that does not contain secondary indexes, the leaf segment must be a direct dependent of the root segment. You determine the hierarchy by following the parent chain (PARENT= parameter on the SEGM statement in the DBD) from the leaf segment to the root segment.
For a database that contains secondary indexes and has a secondary data structure, you determine the hierarchy by following either of these two paths of segments:
  • The path that is explicitly defined by the PARENT parameter
  • The path that is implicitly defined by the secondary data structure that is created by the secondary index
Index root
Optional: Type a name for either of these two objects:
  • The physical or logical root segment of the IMS database that is identified by the DBD.
  • The perceived root segment of the IMS database of a secondary data structure that is created by a secondary index definition that exists in the DBD.
The default index root is the root segment of the physical or logical database the DBD references.
Table name
Type the name to give to the logical table. by default, the wizard specifies the name of the leaf segment as the name of the table. You can change the default.
IMS subsytem
Optional: Type the 4-character name for the IMS subsystem that is used by the ODBA interface to access the IMS database that is identified by the DBD. The IMS subsystem ID is used only when the server is operating in an RRS two-phase commit environment. The IMS subsystem ID follows IMS naming conventions for subsystem identifiers.

The IMS subsystem ID must correspond to the value that is specified on the IMSID parameter on the IMSCTRL macro in the system definition of the target online IMS subsystem that is used to access or update the IMS data in Classic federation.

The IMS subsystem ID value is ignored for other forms of IMS data access (DRA or BMP/DBB/DLI) and when the table mapping is used for change capture.

Standard PSB name
Optional: Type the name of the PSB that is scheduled to access the IMS database that is identified by the DBD. This name is used if you are using a DRA or ODBA interface to access IMS data. The standard PSB corresponds to a PSB definition that is defined to the IMS online system that is being accessed. The PSB also corresponds to a PDS member of the same name in the active ACB library of the source IMS subsystem. The standard PSB name follows z/OS load module naming conventions.

You cannot specify a PSB for which the value of the PSBGEN keyword is "P/LI".

Join PSB name
Optional: Type the name of the PSB that is scheduled to access the IMS database that is identified by DBD. The name is used if you are using a DRA or ODBA interface to access IMS data. The JOIN PSB corresponds to a PSB definition that is defined to the IMS online system that is being accessed. The PSB also corresponds to a PDS member under the same name in the active ACB library of the target IMS subsystem. The JOIN PSB name follows z/OS load module naming conventions. The JOIN PSB is scheduled when an SQL SELECT statement is executed that contains a JOIN predicate that references multiple IMS tables and this is the first table referenced in the JOIN.

You cannot specify a PSB for which the value of the PSBGEN keyword is "P/LI".

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.
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.
Yes with change capture
Specifies that you want to create a view on the table. This option allows you to create a view for change capture. You can use the view to filter record types and to filter rows. The view must reference all of the columns that are in the table.
Comments
Type any comments that you want to associate with the table, such as the time and date that you created the table and what records it contains.

PCB Selection

Use this page to specify the method that Classic federation can use to select a PCB to access your IMS database. This page applies only to Classic federation.

PCB selection method and PCB selection criteria
Verification
PCB selection by verification involves the query processor issuing DL/I calls to verify that the selected PCB can successfully access the database path for this table. PCB verification also requires the proper PROCSEQ to be specified if columns that map to an XDFLD is specified in a WHERE clause. This is the default method that the query processor uses to select a PCB for processing.
Prefix
Indicates that you want to provide a prefix for use in identifying the PCB to use to access or update your IMS database.
PCB prefix
Type a name of 1 to 7 characters for one or more PCBs in a PSB that are eligible to be used to access or update the source IMS database. The PCB prefix corresponds to the first n-characters (where n is the length of the PCB prefix) of a PCB that was assigned a name in the PSB that is being accessed or updated. The PCB name can be specified in the PSB source definition as either the label on the PCB statement or the PCBNAME parameter on the PCB macro statement. The PCB prefix follows IMS PCBNAME naming conventions.
Name
Specify up to five PCB names that Classic federation can use to access your IMS database for this table. Multiple names are required if this table is referenced more than once in an SQL statement, or when the same PCB name is associated with more than one table and these additional tables are referenced in a single SQL statement.
PCB name 1 through 5
Type the PCB names.
Number
Specify up to 10 PCB numbers that Classic federation can use to access your IMS database for this table. Specifying multiple numbers is required if the this table is referenced more than once in an SQL statement, or when these three conditions are true:
  • The same PSB is associated with more than one table.
  • The PCBs in the PSB have sensitivity to the segments that the table is accessing.
  • The same PCB ordinal numbers are specified for these tables and these additional tables are referenced in a single SQL statement.
You can specify up to ten ranges of PCB numbers. These PCB numbers can be listed in any order and represent the order in which a PSB is checked to determine whether a PCB can be used to access the IMS database.
PCB range 1 through 10
Specify the ranges of PCB numbers.

Map Segment segment-name for Table table-name page

Use this page to select the copybook that contains the fields for the segment that is displayed in the Current Segment field. Also, use this page to select the fields that you want to map to columns in the table.

Copybook
Type the path to or click Browse to select the copybook that contains the fields for the segment.
Select 01 level
If the copybook contains more than one 01 levels, select the 01 level that contains the fields that you want to map as columns in the table.
Default OCCURS processing options
Specify how to map record arrays. You 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 fields 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 fields and five maximum occurrences is mapped into only one set of columns.
Current segment
Displays all of the segments in the path of segments and highlights the segment that the fields in the tree view belong to. When you are finished mapping fields in the highlighted segment, click Next to map fields for the next segment.
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 fields for the selected record. Select fields 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 field (Map the selected group field)
Highlight the parent field of a group of fields and click this icon to map the parent field to a column.
Change OCCURS processing for the selected array (Change OCCURS processing for the selected array)
Specifies the OCCURS processing options for a highlighted record array in the tree view.
Rename the selected field (Rename the selected field)
Opens the Rename window so that you can rename the highlighted field 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 fields 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: 2006-12-15