Importing from Different Sources
The examples in this task are written for importing from VAX or Alpha CDD Repository. You can follow the steps in this task to also import:
Powerhouse PDL (Powerhouse Definition Language) files (RMS only) - Select RMS Powerhouse PDL in step 2 and specify the full name for the PDL in step 3, for example DKA600:[MYDIR]QSHOGEN.PDL
RMS COBOL FD (File Definition) files (RMS only) - Select RMS COBOL FD files in step 2 and specify the full name for the COBOL FD file in step 3, for example DKA600:[MYDIR]CUSTOMER.FD
Existing DIBOL table definition (RMS only) - Select RMS DIBOL files in step 2 and specify the full path to the DIBOL record definitions, for example DKA600:[MYDIR]CUSTOMER.DBL.
Existing formatted DDL (Data Definition Language) table definitions - Select RMS DIBOL files in step 2 and specify the full path to the DDL record definition in step 3, for example DKA600:[MYDIR]CUSTOMER.DDL
RMS VAX Basic MAP files - Select RMS VAX Basic files in step 2 and specify a path and file name to the VAX Basic file in step 3, for example DKA600:[MYDIR]CUSTOMER_MAP.BS
RMS SCT COBOL FD (File Definition) files - Select RMS SCT COBOL FD files in step 2 and type an SCT COBOL FD pat hand file in step 3, for example SI$SOURCE:ACADRC.LIB.
You can use Use the SI$SOURCE:*RC.LIB wildcard syntax to import multiple SCT COBOL FD files from the SIS module.
This procedure is site-specific for SCT customers. If you do not use the standard SCT logicals, refer to the SCTLOGICAL import setting. See also CONNX and SCT Import Rules
RMS Text File - Select RMS Text Specification File in step 2 and specify the full RMS path to the file, for example DKA600:[MYDIR]MYIMPORT.TXT.
To import a VAX or Alpha CDD:
1. Click the Import button in the CONNX Data Dictionary Manager window.
2. Select RMS VAX or Alpha CDD in the Import Type list box.
3. Type the dictionary path for the CDD record definitions, and then click OK.
Notes:
When importing from a VAX or Alpha CDD, the full CDD record name must be specified, for example, cdd$top.products.customer_record.
You can use wildcard characters in the dictionary path.
If CONNX detects more than one record layout when importing, CONNX will create a data dictionary entry for each layout.
Multiple files can be specified in the text box by separating each file name with a comma. The allowable limit is 255 characters.
You can also use the Browse button to locate the files you want to import. If you use the Browse button, you have to be connected to a VMS server. Once you're connected, you'll be able to browse to the files and import them.
4. Enter the following in the Import CDD dialog box and click the OK button:
Type the server name or IP address, a user name, and password in the corresponding text boxes on the Logon Information tab.
The default port is 6500. Any change made to the port setting in the text box becomes a permanent change to the port setting of the imported database. See Editing the OpenVMS Site-Specific Startup Command Procedure for more information.
Select the destination database from the Destination Database list box.
The imports from
VAX or Alpha CDD
Powerhouse PDL
COBOL FD
DIBOL
Formatted DDL
VAX Basic MAP
do not contain the RMS data file name, therefore, the RMS data file must be specified manually or by using the Browse button on the Table Properties tab in the CONNX Data Dictionary Manager window after the import is complete. See Using the CONNX Browse button (RMS Only). Because the RMS file name is unknown, the indexes must also be refreshed. You need to do the following for each table you want to import:
1. Click the Table Properties tab in the CONNX Data Dictionary Manager window.
2. Type the data file name and path in the RMS file name text box.
3. Click the Table Indexes tab in the CONNX Data Dictionary Manager window, and then click the Refresh Indexes button. A message saying the indexes are successfully refreshed appears.
4. Save the CDD by clicking Save on the File menu.
For SCT COBOL FD imports, the RMS data files name is automatically entered in the table properties using the standard SCT data logicals, for example, SI$DATA:ADFILE.DAT. See CONNX and SCT Import Rules for more information on the import logic.