Overview

Importing metadata is a prerequisite before defining any bulk transfer, batch compare, or CDC process that involves ADABAS files. The import wizard in the RDRS Dashboard supports both ADABAS on z/OS and ADABAS on LUW. The same wizard is used for both platforms.

Prerequisites

• An ADABAS data source must be defined in the RDRS Dashboard. For more information, refer Configuring ADABAS on LUW platforms.
• The RDRS agent must be able to connect to the ADABAS database.
• The ADABAS files to be imported must exist and have a valid FDT (field definition table).

Start the import

You can start the import of ADABAS file definitions into the RDRS repository from several places in the RDRS Dashboard:

1. From an existing data source definition: Use the Import of metadata button on the data source properties panel, or right-click the data source in the navigation tree and select Import of metadata from the context menu.

   For more information, refer Edit an existing Data Source.

2. From an output target definition: Use the Import of metadata button on the output target properties panel, or right-click and select Import of metadata from the context menu.

   This imports target structures for ADABAS output targets. For more information, refer Edit an existing Output Target.

3. From the repository tree: Right-click on the repository root node, the Input node, or a specific source type node and select Import of metadata from the context menu. When started from a source type node, the available ADABAS data sources are listed directly for selection.

   For more information, refer Metadata Information Maintenance.

4. From process definition: Select Import of metadata from the input file/table selection drop-down, or use the Import of metadata button in the input section. This allows importing metadata without leaving the process definition.

   For more information, refer ADABAS Files with Direct Access.

The import wizard guides through the necessary steps to define which ADABAS files to import and how to resolve the ADABAS field definitions.

Predict integration (optional)

Software AG Predict is a data dictionary product that provides descriptive (long) field names for ADABAS files. Without Predict, ADABAS fields are identified only by their short names (two-character codes such as AA, AB, AC).

With Predict, these are resolved to meaningful names such as PERSONNEL_ID, NAME, DEPARTMENT.

Predict configuration on LUW

For ADABAS/LUW with Predict, follow these steps:

1. Select the Use Predict check box in the import wizard.
2. Enter the Predict database number and file number.
3. Enter the Predict password.
4. Select the Predict database and file number, or select a DDM (Data Definition Module) file for import.
5. If no Predict is available but a DDM file exists, select the Use DDM check box and specify the DDM location.

File selection and object name

For the file selection step:

1. Select the file number for the ADABAS database. All objects of the selected database are listed.
2. If Predict is used, the object tree is displayed for selection. When an object is selected, the object name text field is filled automatically.
3. Enter or confirm the file number and object name of the object to be used.
4. Enter the password if the ADABAS file is cipher-protected.

Reimport of existing structures

If an ADABAS file has already been imported, the import wizard offers two options:

• Full reimport: The file is imported completely, replacing the existing structure definition.
• Structure refresh: Only the structural information is renewed, preserving existing process references and mappings. This is useful when the FDT has been updated. For example, new fields are added while existing processes should not be disrupted.

Descriptor selection

Select the descriptor to be used for the imported file. The descriptor determines the read order for bulk transfer and batch compare operations. Available descriptors are read from the ADABAS FDT. Descriptive field names, such as PERSONNEL_ID, are only displayed if Predict was selected in a previous step.

If the ADABAS file uses cipher codes for encryption, the cipher code must be specified here for decryption during data access.

Multiple value (MV) field options

This section is displayed if the ADABAS file uses Multiple Value fields. Multiple Value fields can contain more than one value per record.

• Multiple Value Field Counter: The maximum number of values in a Multiple Value field.
• Create sub tables: If selected, separate sub-tables are created for MV fields.
• Generate index field: Creates an additional index field for each sub-table.

Periodic group options

This section is displayed if the ADABAS file uses Periodic Groups. Periodic Groups are repeating groups of fields within a record.

• Periodic Group Counter: The maximum number of occurrences of the periodic group.
• Create sub tables: Separate sub-tables are created for periodic groups.
• Generate index field: Creates an additional index field for each sub-table.

For more information on handling recurring fields in RDRS, refer to Handling OCCURS fields.

Output object settings

During import, RDRS can optionally create output objects (target structures) automatically. This is useful when the ADABAS file will be replicated to an output target with the same structure. For more information, refer to Output Object Settings.

Platform specific notes

The following table outlines platform-specific differences in access methods and connectivity for z/OS and LUW platforms.