There is an entry in the default configuration XML file to define file mappings, these are mappings between generic remote file names and the suffix which is used on the client-side. Among other things, the suffix on the client-side defines which editor is used to open the file.
Element | Attribute | Description |
---|---|---|
fileMappings* | Main element for all file mappings. | |
fileMapping | genericName* | The generic z/OS file name pattern this mapping should apply for.
Examples:
|
suffix* | The suffix (without the dot) that should be given to files which match the generic name pattern.
Examples:
|
|
type | The type of file the generic name should be matched with. Valid values include:
|
|
remoteCodePage | The code page that should be used for editing files that match the generic name pattern. Do not define this attribute if
the code page from the remote system connection should be used.
Examples:
|
|
localCodePage | The code page of the encoded local file. | |
transferMode | How the file should be transferred when read or copied. Currently only the value Text is supported. |
<defaultConfigurations> <fileMappings> <fileMapping genericName="*.XML" suffix="xml" remoteCodePage="IBM037"/> <fileMapping genericName="COB*" suffix="cbl" type="member"/> </fileMappings> </defaultConfigurations>