## Network File System Name Mapping

NFS provides the ability to map PDS member names to workstation format consisting of the member name plus an extension. This helps workstation facilities, such as WorkFrame, that were designed to process workstation files with extensions. In order to use NFS name mapping, the server on the host must have the PTF for APAR #OW25973 installed.

The following extensions have special meaning within a WorkFrame project&colon.

CBL
  COBOL source (input to the COBOL compiler)
CPY
  COBOL copy file (used by the COBOL COPY statement)
OBJ
  Object code (input to the linkage editor)
EXE
  Load module (output of the linkage editor)
CMD
  CLIST or REXX procedure
JCL
  Job control language (JCL) on the host used for batch job submission
LST
  Compilation or link edit listing
ADT
  Compilation ADATA (SYSADATA)
PPR
  Preprocessor output
OUT
  Host job SYSOUT output

#### NFS Mapping Side Files

The association of member name and extension is specified in an NFS mapping side file. There might be an NFS default side file defined at your site, and there can also be optional user-defined side files. If no NFS default side file has been defined at your site, you must provide one if you want NFS name mapping. For each host drive, you can specify whether to use only the default side file or both a user-specified side file and the default side file. If both are used, specifications in the user-defined side file take precedence over specifications in the default side file. Check with your host system programmer to determine what is in the default side file. If the default side file meets your needs, you will get better performance if you don't specify any user-defined side files.

The Remote E/C/D Setup Wizard creates an NFS side file based on the information you enter in the Name Mapping panel. You can upload it to your host system if you prefer to use your own side file. See :link refid=nfs reftype=hd .NFS Mapping Side File Characteristics:elink. for more information about the content and data characteristics of the side file.

### NFS Mapping Side File Characteristics

A mapping side file must have the following characteristics:

- The data set name (DSNAME) must end with the qualifiers NFS.MAPPING.
- The data set must be physical sequential (DSORG=PS). PDS is not supported.
- The data set contains fixed length records (RECFM=FB) with a logical record length of 80 (LRECL=80). RECFM=F is not supported.
- The first line of the file contains `#NFS.MAPPING` starting in column 1.
- Any line starting with # in column 1 is treated as a comment and ignored.
- Any data in columns 73 through 80 is ignored and hence can be used to contain sequence numbers.
- Each mapping specification consists of the following:

  `pattern extension`

  Where `pattern` is a data set name pattern and `extension` is the associated workstation file extension, including the leading period as in .CBL. The pattern can start in any column and there can be one or more blanks between the pattern and the extension. Any partitioned data set whose data set name matches the pattern has its member names appended with the associated extension. The first matching pattern found is used. If no matching patterns are found, the member names remain the same (no extension). Neither the pattern nor the extension are case-sensitive and are folded to uppercase.

  The pattern consists of normal data-set-name characters plus the following wildcard characters:

  *
    Means zero or more characters within a single data-set-name qualifier The characters cannot cross a period boundary.
  **
    Means zero or more characters including characters that cross data-set-name qualifiers. The characters can include one or more periods. If the pattern contains three or more asterisks in a row, they are treated the same as **.

  For example, the pattern **.COBOL matches all data set names whose low-level qualifier is COBOL. The pattern **.COB* matches all data set names whose low-level qualifier starts with COB (such as COB, COBOL and COBCOPY).

  An example side file content is:

      #NFS.MAPPING
      **.COBOL   .CBL
      **.COBCOPY .CPY
      **.COPYLIB .CPY
      **.CNTL    .JCL
      **.JCL     .JCL
      **.LISTING .LST

  This example provides for the following mapping:

  - Members of data sets with the low-level qualifier COBOL have the extension .CBL, hence data set MYUSER.TEST.COBOL member MYPROG is shown with the workstation file name MYPROG.CBL.
  - Members of data sets with the low-level qualifier COBCOPY or COPYIST have the extension .CPY, hence data set MYUSER.TEST.COPYLIB member MYCOPY is shown with the workstation file name MYCOPY.CPY.
  - Members of data sets with the low-level qualifier CNTL or JCL have the extension .JCL, hence data set MYUSER.TEST.CNTL member MYJOB is shown with the workstation file name MYJOB.JCL.
  - Members of data sets with the low-level qualifier LISTING have the extension .LST, hence data set MYUSER.TEST.LISTING member MYPROG is shown with the workstation file name MYPROG.LST.
  - If the default side file does not specify any mapping, members of all other data sets are shown without extensions; otherwise, members of all other data sets are shown based on the mapping in the default side file.