Importing Remote VSAM Files With and Without Matching Local Files from COBOL FD Files (CICS) - MVS-OS/390
If you have local and remote VSAM Customer KSDS CICS file definitions (the CONNX sample ones are CNXCSTK and CNXCSTX) that point to different physical VSAM datasets with identical file attributes, record counts, and formats, you can improve performance by importing the indexes from the local file (CNXCSTK in this example). CONNX supports SQL requests against remote files without matching local files.
To import remote VSAM files:
1. Click the Import button in the CONNX Data Dictionary Manager window.
2. Select VSAM COBOL FD files in the Import Type list box.
3. Type a CICS user name and password in the User Name and Password text boxes.
The TCPIP port number is set to 6500 by default, but can be configured via the CONNX NX01 CICS transaction.
4. Select a Destination Database from the list box.
5. Type a COBOL FD partitioned data set and member name in the Enter a COBOL FD data set member text box.
6. Specify the fully qualified PDS (partitioned data set) and member name for the COBOL FD and click OK.
For example, CONNX.VVRR.COPYBOOK(CUSTOMRX)
A COBOL FD specification does not contain the corresponding CICS File Control Table (FCT) name; therefore, it must be specified on the Table Properties tab in the CONNX Data Dictionary Manager window when the data is returned.
All of the record layouts in the specified file are imported and no additional logon information is required.
7. Select each imported file and do the following:
a. Select the VSAM file definition in the upper pane and click the Table Properties tab in the CONNX Data Dictionary Manager window.
b. Do one of the following:
If importing without matching local files, type the remote CICS RDO or FCT name for the file in the CICS File Name text box. For example, the CICS short file name for the remote CONNX VSAM KSDS sample customer file is CNXCSTX.
If importing with matching local file, type the matching local CICS RDO or FCT name for the remote file in the CICS File Name text box. For example, the local CICS short file name for the CONNX VSAM KSDS sample customer file is CNXCSTK. In this example, both the local and the remote Customers VSAM files are defined as KSDS files with identical attributes, but only the local CICS short file name contains complete information such as record length, key offset, and key length. To import this information into the CONNX CDD, key in the matching local CICS short file name (CNXCSTK)
c. Tab out of the CICS File Name text box to display the CONNX Database Logon dialog box. Click the OK button.
d. Click the Table Indexes tab to display the key information for the imported CICS VSAM file.
e. If you're importing with matching local files, select the Table Properties Tab, change the CICS short file name to the remote file name (CNXCSTX), and save the CDD file without tabbing out of the CICS File Name text box.
The definition of the remote Customer VSAM KSDS files (using the matching local file attribute if set) to the CONNX Data Dictionary file is complete. SQL queries against CUSTOMERS_VSAM_REMOTE are mapped to remote file CNXCSTX.