Defining PDS Types for use with Source Connect
When using the Mainframe Express (MFE) Source Connect function, it is often necessary for the Type, or file extension, to be defined for each PDS. This article covers how this can be defined individually and globally.
When users first start using the Source Connect functions within MFE, they often encounter a problem with their compiles failing because their copy books (files) are not found, even after they have added their PDS as a dependency folder. This is usually because the extensions on their PDS Type associations are not what are expected.
Source connect uses the last qualifier of the mainframe PDS name as the "type" for the member. For example, if the mainframe PDS name is MY.COPY.BOOK then the MFE project will, by default, treat a member named "Z" as a PC file named Z.BOOK.
To associate a particular PDS with a specific type (PC extension) select the following options within the MFE IDE:
Options > Server Access Configuration
SourceConnect tab
Configure your datasets
Partitioned tab
Add
In the resulting dialog box, enter the PDS name (MY.COPY.BOOK) and the type you want to use (normally this is defined as CPY). Select the Add button to finalize the entry.
If you have multiple PDS's with the same last qualifier (.BOOK in our example), defining them individually could be tedious and prone to error. In this case, the Global Extension Override function is better suited to the task. To define this, select the following options within the MFE IDE:
Options > Server Access Configuration
SourceConnect tab
Configure your datasets
Extensions tab
Override tab
AddEnter the last qualifier for the PDS's you wish to override (BOOK in our example), and the type you wish to use (CPY). After defining your entries, select the Add button to finalize the entry.
Note: Do not use a leading period ('.') when specifying the type (extension) to be associated with the PDS.
