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.
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.
A mapping side file must have the following characteristics:
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:
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: