Testing CONNX for VSAM Started Task/Batch Job SCT Metadata Import Functionality

You can use the CONNX Administrator to import SCT metadata from the SCT COBOL master file copybooks. The following shows how to import metadata for the SCT VSAM master AAFILE.

1. Run CONNX Data Dictionary.

2. In the CONNX Data Dictionary Manager dialog box, click Import. The Import CDD dialog box appears.

3. To process SQL queries against SCT VSAM master files, the metadata defined in SCT COBOL copybooks must be imported into a CONNX CDD. Select VSAM SCT COBOL FD files from the Import Type list box.

In the Enter a COBOL FD data set member text box, enter a fully qualified partitioned data set (member) name; for example, the default file layout for the SCT AAFILE resides in SCT.SISBASE.SOURCE(ACAARC).

4. In the Server text box, enter the symbolic or dotted numeric TCP/IP address of the target host, and then enter your TSO user name and password. Enter a TCP/IP port number.

5. Enter a TCP/IP Port number.

6. Select a database container in the destination database list box. Click OK.

The CONNX Data Dictionary Manager imports the AAFILE record layouts, automatically detects COBOL REDEFINES clauses, and creates one or more virtual tables for each record segment. For SCT COBOL copybooks, the CONNX Data Dictionary Manager automatically detects the JCL DDNAME (AAFILE), and imports file attributes such as key offset and length and index field name(s) from the corresponding JCL physical data set name.

7. Select a table. The Table Properties tab appears.

8. To display the primary and alternate keys, click the Table Indexes tab.

Note:

For SCT Master file copybooks, the CONNX CDD Administrator automatically detects the DDNAMEs of the corresponding SCT VSAM Master files and sets the File Name text box to the DDNAME. After importing one or more SCT VSAM master files, you can save the information in a CONNX CDD file, define an ODBC data source which points to the new CDD file, and use the CONNX InfoNaut application to execute queries against the new data source files.

Refer to Stopping the CONNX Started Task/Batch Job TCP/IP Listener for instructions on how to stop the listener process.

This scenario assumes that the started tasks/batch jobs CNXVSAM and CNXVSCT are not running simultaneously. These tasks/jobs are not mutually exclusive, but running both simultaneously requires two different values for the =CNXRUNPORT environment variable. Running the CNXVSAM and CNXVSCT batch jobs simultaneously requires pointing each JCL procedure to a separate CNXPARMS PDS control record member in CONNX.STASK.CNTL. To do so, copy member CNXPARMS to a new member in the *.CNTL PDS; then change the =CNXRUNPORT=nnnn entry to point to a different TCP/IP port. Next, change the CNXPARMS symbolic JCL parameter in either procedure CNXVSAM or CNXVSCT to point to the new PDS member; for example: CNXPARMS=CNXPARMZ.