Rational Developer for System z

Remote to local file mapping

When you define a remote system, you map (associate) the lowest level qualifier in each MVS™ data set to a file name extension that is used for the related workstation-based file in your subprojects. For example, a default mapping associates the z/OS-based qualifier COBOL to the .cbl file name extension.

Mapping

A mapping indicates how Rational® Developer for System z® oversees 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 default mappings, 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.

In the workbench, a preference related to the System z LPEX Editor causes workstation-based files of a particular type to be treated in a particular way. In accordance with a default preference, for example, a file of type .cbl is presented with the syntax highlighting that is appropriate to a COBOL source file. However, when the editor processes a z/OS-based data set, the mapping of a qualifier (like COBOL) to a file name extension (like .cbl) determines how the data set is processed.

The following table lists the default mappings. Unless otherwise specified, data is transferred as text.

Low-level qualifier on z/OS File-name extension on workstation Description of member
ASM asm Assembler source file
ASSEMBLE asm Assembler source file
BMS bms BMS map file
C c Csource file
COBCOPY cpy COBOL COPY file
COBOL cbl COBOL source
CLIST cmd CLIST
CNTL jcl Job control language
COPYLIB cpy COBOL COPY file
CPP cpp C++ source file
EXEC rex REXX file
H h C include file
HPP hpp C++ include file
INCLUDE inc PL/I INCLUDE file
JCL jcl Job control language
LISTING lst Compilation or link-edit listing
LOAD exe Load module, which is transferred as binary data
MACRO mac Macro file
OBJ obj Object code, which is transferred as binary data
OUTLIST out Job output
PLI pli PL/I source file
REXX rex REXX file
SIGYCLST cmd REXX EXECs
XML xml Extensible Markup Language file

These system-wide mappings are listed in the z/OS File System Mapping 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 through the Mapping pane in the Properties window. Refer to Mapping data sets and partitioned data set members for more information on customizing these mappings.

Code pages

Each file can only have one code page, but you can specify a group of files as having the same code page. When specifying code pages, specify both a local and host code page and keep them consistent. The default host and local code pages for a system are defined as system properties. The following host code pages are supported:

IBM-037 IBM-273 IBM-277 IBM-278 IBM-280
IBM-284 IBM-285 IBM-297 IBM-420 IBM-424
IBM-425 IBM-500 IBM-803 IBM-870 IBM-871
IBM-875 IBM-930 IBM-933 IBM-935 IBM-937
IBM-939 IBM-1026 IBM-1047 IBM-1140 IBM-1141
IBM-1142 IBM-1143 IBM-1144 IBM-1145 IBM-1146
IBM-1147 IBM-1148 IBM-1149 IBM-1153 IBM-1390
IBM-1399 IBM-1364 IBM-1371 IBM-1388 UTF-8
UTF-16 UTF16BE UTF-16LE    

The availability of local code pages is based on the text file encodings supported by the Eclipse text editor. Be sure to specify code pages to be consistent with the compiler settings of your files.

File types

The type of a file is indicated by its local file extension. For example, using the default mappings, a .cbl is considered to be a COBOL source file. Thus, each file can only have one file type. For example, JCL with embedded COBOL source is not supported.


Feedback