Remote-to-local file mapping
A mapping indicates how IBM Explorer for z/OS processes file transfers between z/OS and the workstation; specifically, the mapping indicates whether file transfers are based on an exchange of text (in which case ASCII/EBCDIC conversions occur) or on an exchange of binary data. A mapping also helps you to know, at a glance, the general purpose of a particular file.
If you use the same low-level qualifier for several data sets, the same mappings affect file transfers for each of those data sets. Given the mappings that are included in IBM Explorer for z/OS, for example, you can transfer members of the partitioned data sets USER01.COBOL and USER01.TEST.COBOL to and from workstation-based files that have the extension .cbl.2
You can see remote-to-local file mappings in the z/OS File System Mapping view of the RSE perspective perspective. The following screen capture shows this view.
You can customize these mappings to match the naming conventions on your remote system either through the z/OS File System Mapping view or on the Mapping page of the Properties window. For more information about customizing these mappings, see Mapping data sets and partitioned data set members. For more information about the properties of file mappings, see the remaining sections of this topic.
Workstation file extension
The type of a file is indicated by its workstation file extension. In the mappings that are shown in the screen capture, a .cbl extension, for example, is considered to be a COBOL source file. Each file can have only one file type. JCL with embedded COBOL source, for example, is not supported. The default workstation file extension for a new mapping is undefined.
The transfer mode can be either text, indicating that a conversion between ASCII and EBCDIC occurs, or binary. The default transfer mode for a new mapping is text.
Each file can have only one code page, but you can specify a group of files as having the same code page. When you specify code pages, specify both a local and a host code page and keep them consistent. The default host and local code pages for a new mapping are inherited from the system properties of the remote and local file systems.
For a list of supported host code pages, see Supported host code pages. The availability of local code pages is based on the text file encodings that are supported by the Eclipse text editor. Be sure to specify code pages to be consistent with the compiler settings of your files.
|Mapping Criterion||Workstation File Extension||Transfer Mode||Host Code Page||Local Code Page||Priority|
|**COBOL||.cbl||default (text)||default (inherited)||default (inherited)||1|
|**COBOL*||default (undefined)||binary||default (inherited)||default (inherited)||2|