2 Configuring the OracleAS CDC Adapter for VSAM

This chapter describes how to configure a change data capture using the OracleAS CDC Adapter for VSAM.

Most of the configurations are done using Oracle Studio. To use Oracle Studio, you first configure it to enable access to the z/OS computer where the VSAM data resides. Then you set up a VSAM data source and finally create the change data capture solution.

This chapter contains the following topics:

Setting Up the IBM z/OS Platform in Oracle Studio
Securing Access to Oracle Connect
Setting up Metadata for the OracleAS VSAM Data Source
Setting Up a Change Data Capture with the OracleAS CDC Adapter for VSAM

Note:

These tasks assume you have permission to access the IBM z/OS platform and that the Oracle Connect daemon is running on this computer.

Check with the system administrator to ensure these requirements are fulfilled.

Setting Up the IBM z/OS Platform in Oracle Studio

Using Oracle Studio, perform the following steps to configure the IBM z/OS platform:

From the Start menu, select Programs, Oracle, and then select Studio. Oracle Studio opens.
Right-click Machines in the Configuration Explorer and select Add Machine. The Add Machine screen is displayed.

Figure 2-1 The Add Machine screen

Description of "Figure 2-1 The Add Machine screen"
Enter the name of the computer you want to connect to, or click Browse to select the computer from the list of computers that is displayed and which use the default port 2551.
Specify the user name and password of the user who was specified as the administrator when Oracle Connect was installed.

Note:
Selecting Anonymous connection enables anyone having access to the computer to be an administrator, if this was defined for the computer.
Click Finish.

The computer is displayed in the Configuration Explorer.

Securing Access to Oracle Connect

Oracle Studio includes mechanisms to secure access to Oracle Connect both during modeling and run time.

During modeling the following security mechanisms can be applied:

Setting Password Access to Oracle Studio
Specifying Users with Administrative Rights

During run time client access to Oracle Connect is provided by the user profile:

Setting Up Run-Time User Access to the IBM z/OS Platform

Setting Password Access to Oracle Studio

Initially, any operation performed using Oracle Studio does not require a password. You can set a password so that the first operation that involves accessing the server from Oracle Studio requires a password to be entered.

Perform the following steps to set the password:

From the Start menu, select Programs, Oracle, and then select Studio.
Select Window from the menu bar and then select Preferences. The Preferences screen is displayed.
Select the Studio node, as shown in the following figure:

Figure 2-2 The Preferences screen

Description of "Figure 2-2 The Preferences screen"
Click Change master password. The Change Master Password screen is displayed as shown in the following figure:

Figure 2-3 The Change Master Password screen

Description of "Figure 2-3 The Change Master Password screen"
Leave the Enter current master password field blank and type a new master password in the Enter new master password field.
Enter the new passoword again in the Confirm new master password field.
Click OK.

Specifying Users with Administrative Rights

By default, only the user who was specified during the installation as an administrator has the authorization to modify settings on that computer from Oracle Studio. This user can then authorize other users to make changes or to view the definitions for a selected computer. Adding a computer to Oracle Studio is described in "Setting Up the IBM z/OS Platform in Oracle Studio".

Note:

The default during installation is to enable all users to be administrators.

From the Start menu, select Programs, Oracle, and then select Studio.
In the Design perspective Configuration view, Right-click the computer and select Administration Authorization.

The Administration Authorization screen is displayed as shown in the following figure.

Figure 2-4 The Administration Authorization Identities tab

Description of "Figure 2-4 The Administration Authorization Identities tab"

The screen has the following sections:

Administrators: Administrators can view and modify all the definitions in Oracle Studio for the selected computer. On initial entry to Oracle Studio, every user is defined as a system administrator.

Designers: Designers can view all the definitions for the computer in Oracle Studio and can modify any of the definitions under the Bindings and Users nodes for the selected computer. For example, Oracle Studio database administrator can add new data sources and adapters and can change metadata definitions for a table in a data source.

Users: Users can view all the definitions for the computer in Oracle Studio for the selected computer. Regular users cannot modify any of the definitions.
Add users or groups of users by clicking Add User or Add Group for the relevant sections.

The user or group that is added must be recognized as a valid user or group for the computer. Once a name has been added to a section, only the user or group that logs on with that user name has the relevant authorization.

Setting Up Run-Time User Access to the IBM z/OS Platform

During run time, client access to Oracle Connect is provided by the user profile. A user profile contains name and password pairs that are used to access a computer, data source or application at run time, when anonymous access is not allowed.

From the Start menu, select, Programs, Oracle, and then select Studio. Oracle Studio opens.
From the Design perspective, Configuration view, expand the Machines folder, then expand the machine where you want to set the user name and password.
Expand Users.
Right-click NAV and select Open The NAV user profile editor is displayed.

Figure 2-5 The User Editor

Description of "Figure 2-5 The User Editor"
In the User editor, click Add. The Add Authenticator screen is displayed :

Figure 2-6 The Add Authenticator screen

Description of "Figure 2-6 The Add Authenticator screen"
Select Remote Machine from the Resource Type list.
Enter the name of the IBM z/OS computer defined in Oracle Studio.
Enter the name and password used to access the computer and confirm the password.
Click OK.

Setting up Metadata for the OracleAS VSAM Data Source

Setting up a change data capture with the OracleAS CDC Adapter for VSAM and VSAM under CICS is done using Oracle Studio. The first step is to define a VSAM or VSAM (CICS) data source and import the metadata. The definitions are created on a z/OS computer.

Note:

The type of VSAM data source that you select depends whether you are working under CICS. If you are working under CICS you must select a VSAM (CICS) data source and also select VSAM (CICS) when Setting Up a Change Data Capture with the OracleAS CDC Adapter for VSAM.

This section contains the following:

Setting Up the VSAM Data Source
Configuring the Data Source Driver
Importing Metadata for the VSAM Data Source
Verifying the Metadata Definition

Setting Up the VSAM Data Source

You should configure a VSAM data source as the first step in setting up the CDC adapter.

Perform the following steps to set up the VSAM data source:

From the Start menu, select Programs, Oracle and then select Studio.
In the Design perspective, Configuration view expand the Machines folder.
Expand the machine defined in Setting Up the IBM z/OS Platform in Oracle Studio.
Expand the Bindings folder. The binding configurations available on this computer are listed.
Expand the NAV binding. The NAV binding configuration includes branches for data sources and adapters that are located on the computer.
Right-click Data sources and select New Data source.

The New Data Source wizard is displayed.

Figure 2-7 The New Data Source screen

Description of "Figure 2-7 The New Data Source screen"
Enter a name for the VSAM data source. The name can contain letters and numbers and the underscore character only.
In the Type field, select VSAM (CICS) or VSAM.
Click Next. The Data Source Connect String screen is displayed.
Enter the parameters for the Data source connect string.

If you are using a VSAM (CICS) data source, enter information for the following parameters:
- CICS Application ID: The VTAM applid of the CICS target system. The default value is CICS. This parameter is used when updating VSAM data. You can determine this value by activating the CEMT transaction on the target CICS system. On the bottom right corner of the screen appears the legend APPLID=target_system.
- Transaction ID: The mirror transaction within CICS that receives control through MRO, which transfers the transaction from the Oracle Connect for VSAM environment to CICS. The default value is EXCI.
- VTAM NetName: The VTAM netname of the specific connection being used by EXCI (and MRO) to relay the program call to the CICS target system. For example, if you issue to CEMT the following command:
```
CEMT INQ CONN
```
  The display screen displays the netname BATCHCLI (this is the default connection supplied by IBM upon the installation of CICS). The default value is ATYCLIEN.
- Program Name: The UPDTRNS program that is supplied by Oracle Connect for VSAM to enable updating VSAM data.
- Trace Queue: The name of queue for output which is defined under CICS when tracing the output of the UPDTRNS program. When not defined, the default CICS queue is used.
If you are using a VSAM data source, enter information for the following parameters:
- Data HLQ: The high-level qualifier where the data files are located.
- Disk Volume Name: The high-level qualifier (volume) where the data resides.
  
  The values specified are used in the Data File field in the Oracle Studio Design perspective, Metadata tab. For tables created using the CREATE TABLE statement, the values specified are used to create the data files. If values are not specified, then data files are written to the DEF high-level qualifier under the high-level qualifier where Oracle Connect is installed.
  
  When SMS is used to manage the volumes, leave this value empty and set the newFileSMSStorageClass and newFileSMSDataClass properties as described in VSAM Properties.
Click Finish.

The new data source is displayed in the Configuration Explorer.

Configuring the Data Source Driver

After setting up the VSAM data source, you can set its driver properties according to specific requirements. To edit the properties:

In the Configuration view, right-click the VSAM data source that you created and select Open.
Click the Configuration tab.

The VSAM or VSAM (CICS) data source configuration is displayed in the editor. This editor has two sections.

The Connection section shows the connections you defined when Setting Up the VSAM Data Source.

The Properties section displays the properties that can be configured for the data source. For a list of the properties, see the following:
Click Save to save the changes you made to the configuration properties.

VSAM (CICS) Properties

The following properties can be configured for the VSAM (CICS) data source. You set the properties in Oracle Studio, Design perspective.

allowUpdateKey: When set to true, this parameter specifies that the key is updatable.
disableExplicitSelect: When set to true, this parameter disables the ExplicitSelect ADD attribute; every field is returned by a SELECT * FROM... statement.
trigger: A name of a user defined trigger or user exit that can be set up. User code is activated on specific events such as PRE-UPDATE and POST-READ. Triggers are normally used for either compression/decompression code or advanced logic for filtering.

VSAM Properties

The following properties can be configured for the VSAM data source. You set the properties in Oracle Studio, Design perspective. For information on how to set data source properties in Oracle Studio.

disableExplicitSelect: When set to true, this parameter disables the ExplicitSelect ADD attribute; every field is returned by a SELECT * FROM... statement.
filepoolCloseOnTransaction: This parameter specifies that all files in the file pool for this data source close at each end of transaction (commit or rollback).
filepoolSize: This parameter specifies how many instances of a file from the file pool may be open concurrently.
newFileSMSStorageClass: This parameter specifies the storage class when SMS is used to manage volumes.
newFileSMSDataClass: This parameter specifies the data class when SMS is used to manage volumes.
trigger: A name of a user defined trigger or user exit that can be set up. User code is activated on specific events, such as PRE-UPDATE and POST-READ. Triggers are normally used for either compression/decompression code or advanced logic for filtering.
useGlobalFilepool: This parameter specifies whether a global file pool that can span multiple sessions is used.

Configuring the Data Source Driver Advanced Properties

You configure the advanced properties for a data source in the Advanced tab of the data source editor. The advanced settings are the same for every data source. Advanced settings let you do the following:

Define the transaction type
Edit the syntax name
Provide a table owner
Determine if a data source is updatable or readable
Provide repository information
Set the virtual view policy

Use the following procedure to configure the data source advanced features.

Open Oracle Studio.
In the Design Perspective Configuration View, expand the Machine folder and then expand the machine where you want to configure the data source.
Expand the Data sources folder, right click the data source you are configuring, then select Open.
Click the Advanced tab and make the changes. The table below describes the available fields:

Table 2-1 Data Source Advanced Configuration

Field	Description
Properties
Transaction type	The transaction level (0PC, 1PC or 2PC) that is applied to this data source, no matter what level the data source supports. The default is the data source's default level.
Syntax name	A section name in the `NAV.SYN` file that describes SQL syntax variations. The default syntax file contains the following predefined sections: OLESQL driver and the SQL Server 7 OLE DB provider (SQLOLEDB): `syntaxName`="`OLESQL_SQLOLEDB`" OLESQL driver and JOLT: `syntaxName`="`OLESQL_JOLT`" Rdb driver and Rdb version: `syntaxName`="`RDBS_SYNTAX`" ODBC driver and EXCEL data: `syntaxName`="`excel_data`" ODBC driver and SQL/MX data: `syntaxName`="`SQLMX_SYNTAX`" ODBC driver and SYBASE SQL AnyWhere data: `syntaxName`="`SQLANYS_SYNTAX`" Oracle driver and Oracle case sensitive data: `syntaxName`="`ORACLE8_SYNTAX`" or, `syntaxName`="`ORACLE_SYNTAX`" For case sensitive table and column names in Oracle, use quotes (") to delimit the names. Specify the case sensitivity precisely.
Default table owner	The name of the table owner that is used if an owner is not indicated in the SQL
Read/Write information	Select one of the following: Updatable data: Select this to update the data on the data source. Read only data: Select this to allow users to only view the data on the data source.
Repository Directory
Repository directory	Enter the location for the data source repository.
Repository name	Enter the name of a repository for a data source. The name is defined as a data source in the binding configuration. It is defined as the type `Virtual` and is used to store Oracle Connect views and stored procedures for the data source, if required instead of using the default SYS data.
Virtual View Policy
Generate sequential view	Select this to map a non-relation file to a single table. This parameter is valid only if you are using virtual array views. You configure virtual array views in the Modeling section of thewhen Configuring a Binding Environment.
Generate virtual views	Select this to have an individual table created for every array in the non-relational file. This parameter is valid only if you are using virtual array views. You configure virtual array views in the Modeling section when Configuring a Binding Environment.
Include row number column	Select this to include a column that specifies the row number in the virtual or sequential view. This parameter is valid only if you are using virtual array views. You configure virtual array views in the Modeling section when Configuring a Binding Environment.
All parent columns	Select this for virtual views to include all the columns in the parent record. This parameter is valid only if you are using virtual array views. You configure virtual array views in the Modeling section when Configuring a Binding Environment.

Importing Metadata for the VSAM Data Source

Oracle Connect requires metadata describing the VSAM data source records and the fields in these records. Use the Import Metadata procedure in Oracle Studio to import metadata for the VSAM data source from COBOL copybooks, which describe the data.

The metadata import procedure is has the following steps:

Select the COBOL Copybooks
Applying Filters
Selecting Tables
Import Manipulation
Create VSAM Indexes (VSAM Batch only)
Assigning File Names (VSAM under CICS only)
Assigning Index File Names (VSAM under CICS only)
Metadata Model Selection
Importing the Metadata

Select the COBOL Copybooks

Perform the following steps to select the COBOL copybooks.

From the Start menu, select Programs, Oracle, and then select Studio.
In the Design perspective, Configuration view expand the Machines folder.
In the Design perspective Configuration view, expand the machine defined in Setting Up the IBM z/OS Platform in Oracle Studio.
Expand Bindings folder. The binding configurations available on this computer are listed.
Expand the NAV binding.
Expand the Data sources folder.
Right-click the VSAM data source defined in Setting Up the VSAM Data Source.
Select Show Metadata View to open the Metadata tab, with the VSAM data source displayed under the data sources list.
Right-click the VSAM data source and select New Import.

The New Import screen is displayed.
Enter a name for the import. The name can contain letters and numbers and the underscore character only.
Select the import type from the Import Type list, as shown in the following figure:

Figure 2-8 The Metadata Import screen

Description of "Figure 2-8 The Metadata Import screen"

Note:
The same New Import screen is displayed for both VSAM imports (VSAM under CICS and VSAM direct), except for the Import type field value: either VSAM Under CICS Import Manager or VSAM Import Manager, respectively)
Click Finish. The Get Input Files screen is displayed.

Figure 2-9 The Get Input Files screen

Description of "Figure 2-9 The Get Input Files screen"
Click Add.

The Select Resources screen is displayed, which provides the option to select files from the local computer or copy the files from another computer.

Figure 2-10 The Add Resource screen

Description of "Figure 2-10 The Add Resource screen"
If the files are on another machine, then right-click My FTP Sites and select Add.

The Add FTP Site screen is displayed. Enter the correct information to connect to the FTP site.
Enter the server name where the COBOL copybooks are located and, if not using anonymous access, enter a valid user name and password to access that computer. The user name is then used as the high-level qualifier.
Click OK. After accessing the remote computer, you can change the high-level qualifier by right-clicking the machine in the Add Resource screen, and selecting Change Root Directory.
Select the files to import and click Finish to start the file transfer. When complete, he selected files are displayed in the Get Input Files screen.

To remove any of these files, select the required file and click Remove.
Click Next (The Apply Filters screen opens) to continue to the Applying Filters step.

Applying Filters

This section describes the steps required to apply filters on the COBOL copybooks used to generate the Metadata. It continues the Select the COBOL Copybooks procedure. Do the following to apply filters:

Expand all in the Apply Filters screen.
Apply the required filter attributes to the COBOL copybooks. The available filters are listed and described in the table that describes the Metadata Filters.
Click Next (The Select Tables screen opens) to continue to the Selecting Tables step.

This figure shows the Apply Filters screen.

Figure 2-11 The Apply Filters screen

Description of "Figure 2-11 The Apply Filters screen"

The following table lists the available filters:

Table 2-2 Metadata Filters

Filter	Description
COMP_6 switch	The MicroFocus COMP-6 compiler directive. Specify either COMP-6'1' to treat COMP-6 as a COMP data type or COMP-6'2' to treat COMP-6 as a COMP-3 data type.
Compiler source	The compiler vendor. The following are available: z/OS AS400 HP NonStop VMS MICROFOCUS Hardware (UNIX vendor) Default/Not known/Other
Storage mode	The MicroFocus Integer Storage Mode. Select one of the following: `NOIBMCOMP` for byte storage mode. `IBMCOMP` for word storage mode.
Ignore after column 72	When set to `true`, ignores columns 73 to 80 in the COBOL copybook.
IgnoreFirst6	When set to `true`, ignores the first six columns in the COBOL copybook.
Replace hyphens (-) in record and field names with underscores (_)	When set to `true`, replaces all hyphens in either the record or field names in the metadata generated from the COBOL with underscore characters.
Prefix nested columns	When set to `true`, prefix all nested columns with the previous level heading.
Case sensitive	Specifies whether to be sensitive to the search string case.
Find	Searches for the specified value.
Replace with	Replaces the value specified for Find with the value specified here

Selecting Tables

This section describes the steps required to select the tables from the COBOL copybooks. The import manager identifies the names of the records in the COBOL copybooks that are imported as tables.

Do the following to select the required tables. This continues the Applying Filters procedure.

From the Select Tables screen, select the tables to access. To select all tables, click Select All. To deselect all selected tables, click Unselect All.

Figure 2-12 The Select Tables screen

Description of "Figure 2-12 The Select Tables screen"
Click Next (the Import Manipulation screen opens) to continue to the Import Manipulation step.

Import Manipulation

This section describes the operations available for manipulating the imported records (tables). It continues the Selecting Tables procedure.

The import manager identifies the names of the records in the DDM Declaration files that are imported as tables. You can manipulate the general table data in the Import Manipulation Screen. The following describes how to manipulate the records in the tables.

From the Import Manipulation screen (see the Import Manipulation Screen figure), right-click the table record marked with a validation error, and select the relevant operation. For more information, see the table, Table Manipulation Options for the available operations.
Repeat step 1 for all table records marked with a validation error. You resolve the issues in the Import Manipulation Screen.

Once all the validation error issues have been resolved, the Import Manipulation screen is displayed with no error indicators.
Click Next. .

If you are importing metadata for a VSAM data source, continue to the Create VSAM Indexes step.

If you are importing metadata for a VSAM (CICS) data source, continue to the Assigning File Names step

Import Manipulation Screen

The Import Manipulation screen is shown in the following figure:

Figure 2-13 Import Manipulation Screen

Description of "Figure 2-13 Import Manipulation Screen"

The upper area of the screen lists the COBOL files and their validation status. The metadata source and location are also listed.

The Validation tab at the lower area of the screen displays information about what must be resolved to validate the tables and fields generated from the COBOL. The Log tab displays a log of what has been performed (such as renaming a table or specifying a data location).

The following operations are available in the Import Manipulation screen:

Resolving table names, where tables with the same name are generated from different files during the import.
Selecting the physical location for the data.
Selecting table attributes.
Manipulating the fields generated from the COBOL, as follows:
- Merging sequential fields into one (for simple fields).
- Resolving variants by either marking a selector field or specifying that only one case of the variant is relevant.
- Adding, deleting, hiding, or renaming fields.
- Changing a data type.
- Setting the field size and scale.
- Changing the order of the fields.
- Setting a field as nullable.
- Selecting a counter field for array for fields with dimensions (arrays). You can select the array counter field from a list of potential fields.
- Setting column-wise normalization for fields with dimensions (arrays). You can create new fields instead of the array field where the number of generated fields are determined by the array dimension.
- Creating arrays and setting the array dimension.

The following table lists and describes the available operations when you right-click a table entry:

Table 2-3 Table Manipulation Options

Option	Description
Fields Manipulation	Customizes the field definitions, using the Field Manipulation screen. You can also access this screen by double-clicking the required table record.
Rename	Renames a table. This option is used especially when multiple tables with the same name are generated from the COBOL.
Set data location	Sets the physical location of the data file for the table.
Set table attributes	Sets the table attributes.
XSL manipulation	Specifies an XSL transformation or JDOM document that is used to transform the table definitions.
Remove	Removes the table record.

You can manipulate the data in the table fields in the Import Manipulation Screen. Double-click a line in the Import Manipulation Screen to open the Field Manipulation Screen.

Field Manipulation Screen

The Field Manipulation screen lets you make changes to fields in a selected table. You get to the Field Manipulation screen through the Import Manipulation Screen. The Field Manipulation screen is shown in the following figure.

Figure 2-14 Field Manipulation Screen

Description of "Figure 2-14 Field Manipulation Screen"

You can perform all of the available tasks in this screen through the menu or toolbar. You can also right click anywhere in the screen and select any of the options available in the main menus from a shortcut menu. The following table describes the tasks that are done in this screen. If a toolbar button is available for a task, it is pictured in the table.

Table 2-4 Field Manipulation Screen Commands

Command	Description
General menu
Undo	Click to undo the last change made in the Field Manipulation screen.
Select fixed offset	The offset of a field is usually calculated dynamically by the server at run time according the offset and size of the proceeding column. Select this option to override this calculation and specify a fixed offset at design time. This can happen if there is a part of the buffer to skip. When you select a fixed offset you pin the offset for that column. The indicated value is used at run time for the column instead of a calculated value. Note that the offset of following columns that do not have a fixed offset are calculated from this fixed position.
Test import tables	Select this table to create an SQL statement to test the import table. You can base the statement on the Full table or Selected columns. When you select this option, the following screen opens with an SQL statement based on the table or column entered at the bottom of the screen. Enter the following in this screen: Data file name: Enter the name of the file that contains the data you want to query. Limit query results: Select this to limit the results to a specified number of rows. Enter the amount of rows you want returned in the following field. 100 is the default value. Define Where Clause: Click Add to select a column to use in a Where clause. In the table in the middle of the screen, you can add the operator, value and other information. Click the columns to make the selections. To remove a Where Clause, select the row with the Where Clause you want t remove and then click Remove. The resulting SQL statement with any Where Clauses that you added are displayed at the bottom of the screen. Click OK to send the query and test the table.
Attribute menu
Change data type	Select Change data type from the Attribute menu to activate the Type column, or click the Type column and select a new data type from the list.
Create array	This command lets you add an array dimension to the field. Select this command to open the Create Array screen. Enter a number in the Array Dimension field and click OK to create the array for the column.
Hide/Reveal field	Select a row from the Field manipulation screen and select Hide field to hide the selected field from that row. If the field is hidden, you can select Reveal field.
Set dimension	Select this to change or set a dimension for a field that has an array. Select Set dimension to open the Set Dimension screen. Edit the entry in the Array Dimension field and click OK to set the dimension for the selected array.
Set field attribute	Select a row to set or edit the attributes for the field in the row. Select Set field attribute to open the Field Attribute screen. Click in the Value column for any of the properties listed and enter a new value or select a value from a list.
Nullable/Not nullable	Select Nullable to activate the Nullable column in the Field Manipulation screen. You can also click in the column. Select the check box to make the field Nullable. Clear the check box to make the field Not Nullable.
Set scale	Select this to activate the Scale column or click in the column and enter the number of places to display after the decimal point in a data type.
Set size	Select this to activate the Size column or click in the column and enter the number of total number of characters for a data type.
Field menu
Add	Select this command or use the button to add a field to the table. If you select a row with a field (not a child of a field), you can add a child to that field. Select Add Field or Add Child to open the following screen: Enter the name of the field or child, and click OK to add the field or child to the table.
Delete field	Select a row and then select Delete Field or click the Delete Field button to delete the field in the selected row.
Move up or down	Select a row and use the arrows to move it up or down in the list.
Rename field	Select Rename field to make the Name field active. Change the name and then click outside of the field.
Sturctures menu
Columnwise Normalization	Select Columnwise Normalization to create new fields instead of the array field where the number of generated fields are determined by the array dimension.
Combining sequential fields	Select Combining sequential fields to combine two or more sequential fields into one simple field. The following dialog box opens: Enter the following information in the Combining sequential fields screen: First field name: Select the first field in the table to include in the combined field End field name: Select the last field to be included in the combined field. Ensure that the fields are sequential. Enter field name: Enter a name for the new combined field.
Flatten group	Select Flatten Group to flatten a field that is an array. This field must be defined as `Group` for its data type. When you flatten an array field, the entries in the array are spread into a new table, with each entry in its own field. The following screen provides options for flattening. Do the following in this screen: Select Recursive operation to repeat the flattening process on all levels. For example, if there are multiple child fields in this group, you can place the values for each field into the new table when you select this option. Select Use parent name as prefix to use the name of the parent field as a prefix when creating the new fields. For example, if the parent field is called `Car Details` and you have a child in the array called `Color`, when a new field is created in the flattening operation, it is called `Car Details_Color`.
Mark selector	Select Mark selector to select the selector field for a variant. This is available only for variant data types. Select the Selector field form the following screen.
Replace variant	Select Replace variant to replace a variant's selector field.
Select counter field	Select Counter Field opens a screen where you select a field that is the counter for an array dimension.

Create VSAM Indexes

This wizard page is used to create VSAM indexes. It is valid only for VSAM data sources. If you are using a VSAM CICS data sources, go to the Assigning File Names step. This step continues the Import Manipulation step.

This figure shows the Create VSAM Indexes step.

Figure 2-15 Create Indexes (For VSAM (ADD) only)

Description of "Figure 2-15 Create Indexes (For VSAM (ADD) only)"

To create VSAM Indexes

Click Next to go to the Metadata Model Selection step. The indexes are created automatically.

Note:

Ensure that the data location is supplied in the Import Manipulation step.

Assigning File Names

This section describes the steps required to specify the physical file name (including the high-level qualifier), and the CICS logical file name for each record. It is valid only for VSAM CICS data sources. If you are using a VSAM data source, go to the Create VSAM Indexes step. This step continues the Import Manipulation step. Do the following to assign file names.

In the Assign File Names screen enter the physical file name, including the high-level qualifier, for each record listed.
Specify the CICS logical file name for each record listed.
Click Next (The Assign Index File Names screen opens) to continue to the Assigning Index File Names step.

This figure shows the Assign File Names step.

Figure 2-16 The Assign File Names screen

Description of "Figure 2-16 The Assign File Names screen"

Assigning Index File Names

This section describes the steps required to specify the physical index file name, and the CICS logical index file name for each record. It continues the Assigning File Names step. Do the following to assign index file names.

In the Assign Index File Names screen, enter the physical index file name for each record listed.
Specify the CICS logical index file name for each record listed.
Click Next (The Import Metadata screen opens) to continue to the Metadata Model Selection step.

This figure shows the Assign Index File Names screen.

Figure 2-17 The Assign Index File Names screen

Description of "Figure 2-17 The Assign Index File Names screen"

Metadata Model Selection

This section lets you generate virtual and sequential views for imported tables containing arrays. In addition, you can configure the properties of the generated views. It continues the Create VSAM Indexes step if you are using a VSAM data source or it continues the Assigning Index File Names procedure if you are using a VSAM CICS data source. This step lets you flatten tables that contain arrays.

In the Metadata Model Selection step, you can select configure values that apply to all tables in the import or set specific settings for each table. Do the following to configure the mdtadata model.

Select one of the following:
- Default values for all tables: Select this to configure the same values for all the tables in the import. Make the following selections when using this option:
  - Generate sequential view: Select this to map non-relational files to a single table.
  - Generate virtual views: Select this to have individual tables created for each array in the non-relational file.
  - Include row number column: Select one of the following:
    
    true: Select true, to include a column that specifies the row number in the virtual or sequential view. This is true for this table only, even if the data source is not configured to include the row number column.
    
    false: Select false, to not include a column that specifies the row number in the virtual or sequential view for this table even if the data source is configured to include the row number column.
    
    default: Select default to use the default data source behavior for this parameter.
  - Inherit all parent columns: Select one of the following:
    
    true: Select true, for virtual views to include all the columns in the parent record. This is true for this table only, even in the data source is not configured to include all of the parent record columns.
    
    false: Select false, so virtual views do not include the columns in the parent record for this table even if the data source is configured to include all of the parent record columns.
    
    default: Select default to use the default data source behavior for this parameter.
- Specific virtual array view settings per table: Select this to set different values for each table in the import. This overrides the data source default for that table. Make the selections in the table under this selection.

When you are finished configuring the metadata model, click Next to go to the Importing the Metadata procedure.

The Metadata Model Selection screen is shown in the following figure:

Figure 2-18 The Metadata Model Selection Screen

The image shows the Metadata Model Selection screen.

Description of "Figure 2-18 The Metadata Model Selection Screen"

Importing the Metadata

This section describes the steps required to import the metadata to the target computer. It continues the Metadata Model Selection step.

You can now import the metadata to the computer where the data source is located, or import it later (in case the target computer is not available).

Note:

To update the metadata using the VSAM data source, and then access the data under CICS, you must:

Close the file in CICS
Make the updates in with the VSAM data source
Exit navcmd. This closes the file in VSAM
Return to CICS and open the file there. The data should be available and you can now read the file.

Do the following to import the metadata.

Select Yes to transfer the matadata to the target computer or No to transfer the metadata later.
Click Finish.

If you specified Yes, then the metadata is imported to the target computer immediately.

The Import Metadata screen is shown in the following figure:

Figure 2-19 The Import Metadata screen

Description of "Figure 2-19 The Import Metadata screen"

After performing the import, you can view the metadata in the Metadata tab in Oracle Studio. You can also make any fine adjustments to the metadata and maintain it, as necessary.

Verifying the Metadata Definition

After you finish Importing Metadata for the VSAM Data Source, you must verify that the metadata is correct. Do the following to verify that the metadata was imported correctly.

From the Start menu, select Programs, Oracle and then select Studio.
In the Design perspective, Configuration view expand the Machines folder.
Expand the machine defined in Setting Up the IBM z/OS Platform in Oracle Studio.
Expand the Bindings folder. The binding configurations available on this computer are listed.
Expand the NAV binding. The NAV binding configuration includes branches for data sources and adapters that are located on the computer.
Expand the Data Sources folder.
Right-click the data source that you set up when Setting Up the VSAM Data Source, and select Show Metadata View. The Metadata view opens with the data source you selected expanded.
Expand the Tables folder.
Right-click the table or tables where you carried out the metadata import and select Test. The Test wizard opens.
Click Next to view the metadata. The tables are displayed from the metadata. Check to see that the correct information is displayed.

Setting Up a Change Data Capture with the OracleAS CDC Adapter for VSAM

You must set up the Oracle Connect CDC adapter for VSAM on the z/OS platform to handle capture changes to the VSAM data.

To work with the VSAM under CICS CDC adapter, you must set up the CICS user journal on the z/OS compouter. To work with the VSAM Batch adapter, you must set up the CDC Logger. After you finish making the required configurations on the z/OS computer, configure the change data capture using the Oracle Studio CDC Solution perspective. Oracle Studio must be installed on a Windows or UNIX computer

Perform the following to set up the change data capture and configure the OracleAS CDC Adapter for VSAM under CICS

Managing the CICS User Journal (VSAM CICS Only)
Configuring the Logger (VSAM Batch Only)
Setting up a Change Data Capture in Oracle Studio
Deploying a Change Data Capture

Managing the CICS User Journal (VSAM CICS Only)

The following are the tasks used for managing the VSAM CDC adapter:

Setting up the CICS User Journal for VSAM
Print the CICS User Journal Content

Setting up the CICS User Journal for VSAM

This section describes how to set up the CICS user journal for VSAM. Do the following to set up the CECS user journal for VSAM.

Check if a relevant CICS User Journal is available by entering the following CICS command:
```
CEMT I JO
```
This displays the list of all the available CICS Journals, for example:
```
Jou(DFHJ77) Mvs Ena Str(CICSTS13.CICS.DFHJ77)
Jou(DFHJ66) Mvs Ena Str(CICSTS13.CICS.DFHJ66)
Jou(DFHLOG) Mvs Ena Str(CICSTS13.CICS.DFHLOG)
…
```
Each User Journal has the CICS name DFHJxx, where xx is the number of the journal. You can use any of them as the CDC Logger. Its logstream name (for example, CICSTS13.CICS.DFHJ77) should be provided as CDC Logger Name property.

If you cannot use an available journal, go to steps 2 and 3. If you can use a journal in the list, go to step 4.
Create an MVS logstream that can be used as a CICS journal. A sample job for the creation of DASD MVS logstream called ORACLE.CDC.VSAMBTCH is supplied in the <HLQ>.USERLIB(LOGCRVSM) member. For more information, see IBM's MVS Setting Up a Sysplex manual.

Define and install the log stream as a user journal by entering the following CICS command:

CEDA DEF JO(<journal name>) GR(<CICS group name>) TY(MVS) STR(<logstream name>)
CEDA INST JO(journal name) GR((<CICS group name>)

For each VSAM cluster to be captured, use the CICS command CEDA DI FI, and edit the properties as shown in the following example:
```
+ JOurnal : <journal number>
JNLRead : Updateonly
JNLSYNCRead : Yes
JNLUpdate : Yes
JNLAdd : AFter
JNLSYNCWrite : Yes
RECOVERY PARAMETERS
RECOVery : Backoutonly
Fwdrecovlog : No
BAckuptype : Static
SECURITY
RESsecnum : 00
```
The value JNLRead means that before images are also written to the journal. The value JNLSYNCWrite means that CICS writes the changes to the journal immediately, instead of saving them in a buffer and writing them to the journal in blocks.

Close the VSAM cluster by using the following CICS command:
```
CEMT S F(<CICS file name>) CLOSE
```
Reinstall the cluster by using the following CICS command:
```
CEDA INST F(<CICS file name>) GR(<CICS group name>)
```
Open the cluster by using the following CICS command:
```
CEMT S F(<CICS file name>) OPEN
```

Print the CICS User Journal Content

You can print a CICS journal content running a job as described in the following example:

//PRINTLOG JOB 'RR','TTT',MSGLEVEL=(1,1),CLASS=C
// MSGCLASS=X,NOTIFY=&SYSUID
//PRNTJNL EXEC PGM=DFHJUP
//STEPLIB DD DSNAME=<HLQ>.SDFHLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=A,DCB=RECFM=FBA
//SYSUT1 DD DSNAME=<logstream name>,
// DCB=BLKSIZE=32760,
// SUBSYS=(LOGR,DFHLGCNV,
//
* 'FROM=(2003/261,22:07:16),TO=(2004/007,23:59:15),
LOCAL')
'FROM=(2003/261,22:07:16),TO=YOUNGEST,LOCAL')
//* 09/18/2003 22:07:15
//* 09/19/2003 15:35:34
//SYSIN DD *
*-----------------------------------------------------* CONTROL STATEMENT :
DEFAULTS *
* INPUT = SYSUT1 *
* OUTPUT = SYSPRINT *
* SELECTION QUALIFIERS : *
* 1. DEFAULT = ALL INPUT RECORDS *
*----------------------------------------------------*
OPTION PRINT
END
*----------------------------------------------------*
/*

where:

DSNAME: This is the name of the journal logstream.
FROM: This is the earliest change you want to print.
TO: This is the latest change you want to print (TO=YOUNGEST prints all the entries up to the last change logged).

Configuring the Logger (VSAM Batch Only)

To use the OracleAS CDC Adapter for VSAM Batch solutions, perform the following:

Creating the Logstream
Creating the CDC$PARM Data Set
Updating Jobs and Scripts

Creating the Logstream

A sample job for the creation of DASD MVS logstream called ORACLE.CDC.VSAMBTCH is supplied in the <HLQ>.USERLIB(LOGCRVSM) member. For additional information, see IBM's MVS Setting Up a Sysplex manual.

Managing the MVS Logstream

The ATYLOGR program provided is used to manage MVS logstreams. It has the following options:

Delete all events
Delete events to a specific time stamp
Delete the newest events
Print events between two time stamps
Print all the events from the oldest to a specified time stamp
Print all the events from the newest to a specified time stamp
Print all the events

A sample job for managing the default VSAM Batch CDC MVS Logstream called ORACLE.CDC.VSAMBTCH is supplied in the <HLQ>.USERLIB(RUNLOGR) member.

Creating the CDC$PARM Data Set

CDC$PARM is the name of the DD card used to configure the JRNAD and Logical Transaction Manager. It can be any QSAM data set or member with the LRECL=80 definition. For example, you can build it as a member of the <HLQ>.USERLIB library.

The data set contains parameters, one per a line, according to the follow syntax:

<parameter name>=<parameter value>

The parameters and their valid values are described in CDC$PARM Properties (VSAM Batch Only).

The minimal set of the parameters for any solution can be taken from Project Information section of Deployment Summary screen of Oracle Studio Solution Perspective.

If the CDC$PARM data set is not provided to the JRNAD or Logical Transaction Manager, it is managed as follows:

DSNAME=*
LOGSTREAM=ORACLE.CDC.VSAMBTCH

Updating Jobs and Scripts

To ensure that the changes are captured, you must update the jobs and REXX scripts used to change the VSAM data.

Updating Jobs for Activating CDC JRNAD
Updating Jobs for Using the Logical Transaction Manager
Update the REXX Scripts

Updating Jobs for Activating CDC JRNAD

To get the CDC JRNAD program that is being called, add three DD cards to each step that activates a program that is being updated, as shown in this example:

STEPLIB DD DSN=<HLQ>.LOADCDCY,DISP=SHR
ATYLIB DD DSN=<HLQ>.LOADAUT,DISP=SHR
CDC$PARM DD DSN=<CDC$PARM DS name>,DISP=SHR

Ensure that that the <HLQ>.LOADAUT load library is APF authorized.

Updating Jobs for Using the Logical Transaction Manager

To use the Logical Transaction manager, add additionl steps to the jobs used as a part of the logical transaction.

Start a Logical Transaction: To begin a logical transaction, add the following step as the first step in a job:

//BEGINLT EXEC PGM=ATYLTRAN,// PARM='BEGIN,TRAN_NAME=<logical transaction name>'//STEPLIB DD DSN=<HLQ>.LOADAUT,DISP=SHR//CDC$PARM DD DSN=<CDC$PARM DS name>, DISP=SHR

Move a Logical Transaction to another job: To move a logical transaction to another job, add the following step as the last step of the job:
```
//MOVELT EXEC PGM=ATYLTRAN,COND=(4,LT)//STEPLIB DD DSN=<HLQ>.LOADAUT,DISP=SHR//CDC$PARM DD DSN=<CDC$PARM DS name>, DISP=SHR
```

Continue Logical Transaction: To continue a logical transaction in another job, add the following step as the first step of this job:

//CONTLT EXEC PGM=ATYLTRAN,// PARM='TRAN_NAME='<logical transaction name>'//STEPLIB DD DSN=<HLQ>.LOADAUT,DISP=SHR//CDC$PARM DD DSN=<CDC$PARM DS name>, DISP=SHR

Terminate Logical Transaction: To terminate a logical transaction, add the following two steps as the last steps of this job:
```
//COMMITLT EXEC PGM=ATYLTRAN,COND=(4,LT),// PARM='COMMIT'//STEPLIB DD DSN=<HLQ>.LOADAUT,DISP=SHR//CDC$PARM DD DSN=<CDC$PARM DS name>, DISP=SHR//RLBCKLT EXEC PGM=ATYLTRAN,COND=(EVEN,(0,EQ,COMMIT))// PARM='ROLLBACK'//STEPLIB DD DSN=<HLQ>.LOADAUT,DISP=SHR//CDC$PARM DD DSN=<CDC$PARM DS name>, DISP=SHR
```
The COND clause in the COMMITLT step should provide the condition when the Logical Transaction terminates successfully by COMMIT. The COND clause in the RLBCKTL step always writes a ROLLBACK to the logstream when COMMITLT is not executed or fails.

Update the REXX Scripts

If you use REXX scripts to run VSAM update programs, you should change them for this purpose. The member NVCMDCDC in <HLQ>.USERLIB is supplied as an example of a REXX script.

Setting up a Change Data Capture in Oracle Studio

You set up the change data capture in Oracle Studio. Oracle Studio can be installed on Windows XP or Vista operating systems, or on UNIX.

A change data capture is defined in the CDC Solution perspective, which contains a series of links to guide you through the CDC set up process. The CDC solution perspective guides display the following symbols in front of a link to show you what tasks should be done, and what tasks were completed.

Triangle: This indicates that there are subtasks associated with this link. When you click the link, the list expands to display the subtasks.
Asterisk (*): This indicates that you should click that link and perform the tasks and any subtasks presented. If multiple links have an asterisk, you can perform the marked tasks in any order.
Check mark (✓): This indicates that the tasks for this link and any sublink are complete. You can double click the link to edit the configuration at any time.
Exclamation mark (!): This indicates a potential validation error.

Carry out the following to set up a change data capture:

Create a CDC Project
Set up the CDC Server
Set up the Staging Area Server

Create a CDC Project

Do the following to create a CDC Project

From the Start menu, select, Programs, Oracle, and then select Studio.
Open the CDC Solution perspective, click the Perspective button on the perspective toolbar and select CDC Solution from the list.

The CDC Solution perspective opens with the Getting Started guide in the left pane of the workbench.
Click Create new project.

The Create new project screen opens.
In the Project name field, enter a name for your project.

The types of projects available are listed in the left pane.
Select Change Data Capture.

From the right pane, select VSAM-CICS or VSAM-BATCH.

Figure 2-20 Create New Project

Description of "Figure 2-20 Create New Project"
Click Finish. The Project Overview guide is displayed in the left pane.
Click Design. The Design wizard opens. Use this wizard to enter the basic settings for your project.

Note:
The wizard screens are divided into sections. Some sections provide information only and other sections let you to enter information about the project. If you do not see any information or fields for entering information, click the triangle next to the section name to expand the section.

Figure 2-21 Design Wizard (Design Options)

Description of "Figure 2-21 Design Wizard (Design Options)"
In the Client Type you can select Oracle SOA/ODI only. The Use staging area is selected and cannot be changed, you must use a staging area with the OracleAS CDC Adapter for VSAM.
Click Next.

The Design Wizard's second screen is displayed. In this step you configure the computers used in your solution. Enter the following information:
- Server Machine Details: Information about the computer where Oracle Connect is installed. The selection here is always Server Machine and Mainframe.
- Staging Area Details: Information about the computer platform where the staging area is located.
  
  For the server computer Name, select one of the following:
  - CDC Stream Service: Select this if the Staging Area is on a staging area computer. This is the default selection.
  - Server Machine: Select this if the staging area is on the same machine where Oracle Connect is installed.
  - Client Machine: Select this if the Staging area is on the local compuer.
  In the Platform list, select the operating system for the staging area. This can be Windows, Linux or UNIX. The available options are:
  - Microsoft Windows
  - HP-UX
  - IBM AIX
  - Sun Solaris
  - Linux (Red Hat)
  - Suse (Linux)
Figure 2-22 Design Wizard (Configure Solution Machines)

Description of "Figure 2-22 Design Wizard (Configure Solution Machines)"
Click Finish. The wizard closes.

Set up the CDC Server

Click Implement in the Getting Started guide to open the Implementation guide.

In the Implementation guide, do the following to set up the CDC server:

Set up the Machine
Configure the VSAM Data Source
Copy the Metadata
Set up the CDC Service

Set up the Machine

You do the following to define the IP Address/host name and Port for the CDC server machine.

Click Machine.

The machine definition screen is displayed:

Figure 2-23 Machine Definition

Description of "Figure 2-23 Machine Definition"
In the IP address/host name field, do one of the following:
- Enter the server computer's numeric IP address.
- Click the Browse button and select the host computer from the ones presented, then click Finish.
  
  Figure 2-24 Select Machine
  
  Description of "Figure 2-24 Select Machine"
  
  Note:
  The machine you enter must be compatible with the platform designated in the Design Wizard (Configure Solution Machines) screen.
Enter the port number.

The default port number is 2551.
To connect with user authentication, enter a user name and password, with confirmation, in the Authentication Information area.
Select the Connect via NAT with a fixed IP address check box if you are using Network Access Translation and want to always used a fixed IP address for this machine.
Click OK.

Continue setting up the CDC Server on the z/OS computer.

Configure the VSAM Data Source

In this step, configure the VSAM data source that is part of the VSAM CICS CDC solution. Carry out the following procedure to configure the data source.

In the CDC Solution perspective, click Implement.
In the Server Configuration section, click Data Source. The Data Source Configuration window is displayed.
Define the parameters for your data source in the Data Source Configuration window.

If you are using a VSAM CICS data source define the following parameters:
- CICS Application ID: Enter the VTAM ID of the CICS target system (mandatory).
- Transaction ID Enter the EXCI or other CICS transaction that activates DFHMIRS CICS program.
- VTAM NetName Enter the VTAM network name of the specific connection being used by EXCI (and MRO) to relay the program call to the CICS target system (mandatory).
- Program Name: Enter the UPDTRNS program (supplied with the OracleAS CDC Adapter for VSAM under CICS).
- Trace Queue Enter the name of queue for output which is defined under CICS when tracing the output of the UPDTRNS program. When not defined, the default CICS queue is used.
If you are using a VSAM Batch data source define the following parameters:
- Data HLQ: The high-level qualifier where the data files are located.
- Disk volume Name: The high-level qualifier (volume) where the data resides.
  
  The values specified are used in the Data File field in the Oracle Studio Design perspective, Metadata tab. For tables created using the CREATE TABLE statement, the values specified are used to create the data files. If values are not specified, then data files are written to the DEF high-level qualifier under the high-level qualifier where Oracle Connect is installed.
  
  When SMS is used to manage the volumes, leave this value empty and set the newFileSMSStorageClass and newFileSMSDataClass properties as described in VSAM Properties.
Click Finish.

Continue setting up the CDC Server on the z/OS computer.

Copy the Metadata

In this step, copy the metadata that you imported when Importing Metadata for the VSAM Data Source. Do the following to copy the metadata.

Click Metadata.

The Create metadata definitions view is displayed.

Note:
The Select Metadata Source link has an asterisk (*) next to it to indicate that you must carry out this operation first.
Click the Select Metadata Source link.
Select Copy from existing metadata.
Click Finish. The screen closes.
Click Copy from existing metadata source.

The Copy Existing Metadata Source screen is displayed showing your local computer and with metadata compatible with the data source selected.

Figure 2-25 Copy Existing Metadata Source

Description of "Figure 2-25 Copy Existing Metadata Source"
From the sources in the left pane, expand the list until you see the tables from the data source you configured when Importing Metadata for the VSAM Data Source.
Using the arrow buttons, select the required tables and move them into the right pane.
Once you have selected all the desired tables, click Finish.
Click Customize Metadata.

The customize metadata screen is displayed.

Note:
If you do not want to make any custimizations to the metadata, click Finish to close this screen. A check mark (✓) appears next to Customize Metadata indicating that this step is complete.
Continue with another step in the design wizard.

Figure 2-26 Customize Metadata

Description of "Figure 2-26 Customize Metadata"
To change a table name, right-click in the any field under Customize Metadata, and select Add.
Enter the table name in the field presented, and click OK.

Note:
You may have validation errors in the tables created, which you can correct by the end of the procedure.
To make changes to any field in a table, right-click the table created and select Fields Manipulation.

The Field Manipulation screen is displayed.

Figure 2-27 Field Manipulation

Description of "Figure 2-27 Field Manipulation"
Right-click in the upper pane and select Field|Add|Field.
Enter the name of the field in the screen provided, and click OK.
Default values are entered for the table. To manipulate table information or the fields in the table, right-click the table and choose the option you want. The following options are available:
- Add table: Add a table.
- Field manipulation: Access the field manipulation window to customize the field definitions.
- Rename: Rename a table name. This option is used especially when multiple tables are generated from the COBOL with the same name.
- Set data location: Set the physical location of the data file for the table.
- Set table attributes: Set table attributes.
- XSL manipulation: You specify an XSL transformation or JDOM document that is used to transform the table definition.
The Validation tab at the bottom of the window displays information about what you must do to validate the tables and fields generated from the COBOL. The Log tab displays a log of what has been performed (such as renaming a table or specifying a data location).
Correct any remaining validation errors.
Click Finish to generate the metadata.

Continue setting up the CDC Server on the z/OS computer.

Set up the CDC Service

In this step you define the starting point or event for the change capture and then indicate the name of the change logger. Do the following to set up the CDC service.

In the CDC Solution perspective, click Implement.
In the Server Configuration section, click CDC Service. The CDC Service wizard is displayed.
In the first screen select one of the following to determine the Change Capture starting point:
- All changes recorded to the journal
- On first access to the CDC (immediately when a staging area is used, otherwise, when a client first requests changes
- Changes recorded in the journal after a specific date and time.
  
  When you select this option, click Set time, and select the time and date from the dialog box that is displayed.
Click Next to define the logger. The following is displayed.

Figure 2-28 CDC Logger Definition Window

Description of "Figure 2-28 CDC Logger Definition Window"
In the Logger Name field, enter the name of the MVS logstream used for the data capture.
Click Next to go to the next step where you set the CDC Service Logging. Select the log level to use from the Logging level list.

Figure 2-29 Logging Level

Description of "Figure 2-29 Logging Level"

Select one of the following from the list:
- None
- API
- Debug
- Info
- Internal Calls
Click Finish.

Continue setting up the CDC Server on the z/OS computer.

Set up the Staging Area Server

Click Implement in the Getting Started guide to open the Implementation guide.

In the Implementation guide, do the following under the Stream Service Configuration section, to set up the staging area server:

Set Up the Staging Area Machine
Set up the Stream Service
Configure the Access Service Manager

Set Up the Staging Area Machine

To set up the machine for the staging area, do the following.

Under the Stream Service Configuration section, click Machine.
Use the same configurations used to Set up the Machine for the CDC server.

Continue setting up the staging area Server.

Set up the Stream Service

In this step you set up the stream service. The Stream Service configures the following:

Staging area
Filtering of changed columns
Auditing

Note:

Null filtering is currently unsupported. Filtering empty values is supported. Space values are truncated and are handled as empty values.

Click Stream Service. The Stream Service wizard opens.

Figure 2-30 Staging Area

Description of "Figure 2-30 Staging Area"

Note:
This screen appears only if you selected the inclusion of a staging area in your solution.
You can configure the following parameters in this screen:
- Select Eliminate uncommitted changes to eliminate uncommitted changes from your CDC project.
- Select the Use secured connection check box to configure the staging area to have a secured connection to the server. This is available only if you logged into the server using user name and password authentication.
- Set the event expiration time in hours.
- Under File Locations, click the Browse buttons to select the location of the changed files, and temporary staging files, if necessary.
Click Next to select the tables to include in the filtering process.

Figure 2-31 Select Tables

Description of "Figure 2-31 Select Tables"
Click the required tables in the left pane and move them to the right pane using the arrow keys.

Note: You can remove the tables and add new ones to be captured after you add the tables to the right pane. For more information, see Adding and Removing Tables.
Click Next. From the tables selected above, select the columns that receive changes. Select the check box next to the table to use all columns in the table.

Figure 2-32 Column Selection

Description of "Figure 2-32 Column Selection"

Note:
Table headers appear grouped in a separate table at the beginning of the list. You can also request the receipt of changes in the headers' columns.

Any data changes in the columns selected are recorded.
Click Next. The Filter selection screen is displayed. the types of changes you want to receive in the tables and which columns to display.

Figure 2-33 Filter Selection

Description of "Figure 2-33 Filter Selection"
You can do the following in this screen:

Select the actions from which you want to receive change information:
- - Update
  - Insert
  - Delete
  Note:
  These items are all selected by default.
- Under the Changed Columns Filter column, select the columns for which you want to receive notification of changes.
  Notes:
  - If you do not select a column, you receive notification of all changes.
  - If you select only one column, you receive change information only if the field selected undergoes a change.
  - If you select multiple columns, but not all, you receive change information only if any or all of the selected fields undergo a change.
In the Content Filter column of the Filter screen, double-click a table column and then click the Browse button to filter content from the selected column.

The Content Filter screen is displayed.

Figure 2-34 Content Filter

Description of "Figure 2-34 Content Filter"
Select a filter type:
- Select In for events to be returned where the relevant column value equals the values you specify (if a column is NULL, it is not captured).
- Select Not In for events to be returned where the column value is not in the values you specify (if the column is NULL, it is captured).
- Select Between for when the column value is between the two values you specify (if a column is NULL, it is not captured).
Click Add in the lower-left corner of the Content Filter screen.

Note:
If you select multiple conditions, you receive the change information if one of the conditions is true.
Depending on your selection, do one of the following:
- If you selected In/Not In, continue with step12.
- If you selected Between, continue with step 14.
Click Add in the Add items to the list screen. Enter a value for events to be returned where the column value appears (or does not appear) in that value. To filter empty values ('') for the Not In filter type, leave this field blank in the dialog box that is displayed.

Figure 2-35 Add Items (In or Not In)

Description of "Figure 2-35 Add Items (In or Not In)"
Repeat steps 12 as many times as necessary, and then proceed to step 16.
Click Add in the Add items to list screen.

The Add between values screen is displayed.

Figure 2-36 Add Items (Between)

Description of "Figure 2-36 Add Items (Between)"
Enter values for events to be returned where the column value is between the two values you specify.
In the content filter screen, click Next.

Figure 2-37 Auditing Configuration

Description of "Figure 2-37 Auditing Configuration"
Select the required auditing level when receiving changes. Your options are:
- None: For no changes.
- Summary: For an audit that includes the total number of records delivered, system messages, and error messages.
- Headers: For an audit that includes the total number of records delivered, system and error messages, and the record headers for each captured record.
- Detailed: For an audit that includes the total number of records delivered, system and error messages, the record headers for each captured record, and the content of the records.
Click Finish.

Continue setting up the staging area Server.

Configure the Access Service Manager

In this step you set up a daemon workspace for the CDC adapter. Do the following to configure the access service manager.

Click Access Service Manager.

The Setup Workspace wizard opens.

Figure 2-38 Select Scenario

Description of "Figure 2-38 Select Scenario"
Select the scenario that best meets your site requirements:
- Application Server using connection pooling
- Stand-alone applications that connect and disconnect frequently
- Applications that require long connections, such as reporting programs and bulk extractors
Click Next.

The Application Server with connection pooling scenario screen is used to create a workspace server pool. The parameters available depend on the selection you made in the first screen. The following are the available parameters:
- If you selected Application Server using connection pooling:
  - What is the average number of expected concurrent connections? Enter the number of expected connections, which cannot be greater than the number of acutal available connections.
  - What is the maximum number of connections you want to open? Enter the number of connections you want opened.
- If you selected Stand-alone applications that connect and disconnect frequently, in addition to the choices listed in the item above, you can also set the following:
  - What is the minimum number of server instances you want available at any time? Enter the number of instances, which cannot be greater than the number of actual available instances.
  - What is themaximum number of server instances you want available at any time? Enter the number of instances you want to be available.
- If you selected Stand-alone applications that connect and disconnect frequently:
  - How many connections do you want to run concurrently? Enter the number of concurrent connections to run.
Click Next. In the next screen you set time out parameters. These parameters should be changed if the system is slow or overloaded. The parameters are:
- How long do you want to wait for a new connection to be established? Enter the amount of time you want to wait for a new connection to be established (in seconds).
- How long do you want to wait for a response that is usually quick? Change this parameter if you have a fast connection. Enter the amount of time to wait for a response (in seconds).
Click Next. In the next screen you set security parameters. You should consult with the site security manager before changing these parameters.

Edit the following parameters in this screen:
- Enter the operating system account (user name) used to start server instances.
- Select Allow anonymous users to connect via this workspace, to allow this option.
- Enter the permissions for the workspace. You can allow All users to access the workspace, or select Selected users only to allow only the users/groups to have exclusive access.
- Select Do you want to access server instances via specific ports, to allow this option. If this option is cleared, the defaults are used.
  
  If you select this option, indicate the From port and To port and ensure that you reserve these ports in the TCP/IP system settings.
Figure 2-39 Site Security

Description of "Figure 2-39 Site Security"
Click Next.

The summary screen opens.

Figure 2-40 Workspace Setup Summary

Description of "Figure 2-40 Workspace Setup Summary"
Click Save and then click Finish.

When you complete all the Implementation operations, a check mark (✓) is displayed next to every link. Click Done to return so you can begin Deploying a Change Data Capture.

Continue setting up the staging area Server.

Deploying a Change Data Capture

After you complete the design and implementation guides, the following procedures are available.

Deployment Procedure: This section is used to deploy the project.
Control: This section is used to activate or deactivate workspaces after the project is deployed and you are ready to consume changes. In this section, you can deactivate the workspace anytime you want to suspend consumption of changes from the staging area.

Do the following to deploy the CDC solution:

Click Deploy. The Deployment Procedure and Control sections are displayed in the Deployment view.
Click Deploy in the Deployment Procedure section.

Oracle Studio processes the naming information. This may take a few minutes. If there are naming collisions, a message is displayed asking if you want Oracle Studio to resolve them.

Figure 2-41 Resolve Naming Collision

Description of "Figure 2-41 Resolve Naming Collision"
Click Yes to resolve any naming collisions.

The Deployment Guide screen is displayed.

Figure 2-42 Deployment Guide

Description of "Figure 2-42 Deployment Guide"
If you are ready to deploy, click Finish.

Otherwise, click Cancel and you can return to Create a CDC Project, Set up the CDC Server, or Set up the Staging Area Server to make any changes.

If this project was deployed previously, you are notified that re-deployment overrides the previous instance.
Notes:
- When you redeploy a project where the metadata is changed, the Staging Area (SA) tables should be deleted so that no incorrect information is reported.
- When you re-deploy a solution, a new binding is created for the solution. The new binding is created with the default parameters only. Any temporary features that were added are lost.
Where applicable, click OK to redeploy.
Click the Deployment Summary link.

The Deployment Summary is displayed. It includes the ODBC connection string, JDBC connection string, and specific logger scripts to enable CDC capturing.

Figure 2-43 Deployment Summary

Description of "Figure 2-43 Deployment Summary"
Cut and paste any information required from the Deployment Summary screen to your environment as necessary.
If there is nothing wrong with your deployment results, click Finish.

If you found problems, click Cancel and to return Create a CDC Project, Set up the CDC Server, or Set up the Staging Area Server to modify the solution.

Note:

If you are redeploying a solution you must follow these directions to ensure that the context and adapter_context fields of the SERVICE_CONTEXT table must be saved. Follow these directions to save the fields:

In the staging area data source run: select context, agent_context from SERVICE_CONTEXT; and save the returned values.
Delete the SERVICE_CONTEXT table physical files.
Redeploy the solution.
Activate the router to create the SERVICE_CONTEXT table.
Disable the router.
In the staging area data source run: insert into SERVICE_CONTEXT (context, agent_context) values('XXX', 'YYY'). This inserts the saved values to the SERVICE_CONTEXT table.
Activate the solution.

Activating and Deactivating Solution Workspaces

In the Project guide for your OracleAS CDC Adapter solution, click Deploy, then do one of the following to activate or deactivate the workspaces for a solution

To activate workspaces, under the Control section iclick the Activate Workspaces link.
To deactivate workspaces, click the Deactivate Workspaces link.

During the activation/deactivation process, you may receive messages indicating that the daemon settings on one or more of the computers involved in your solution have changed. Click Yes to proceed.