For information see TCP/IP V3R2 for MVS: Customization and Administration, SC31-7134. Softcopy is available as part of the TCP/IP V3R2 for MVS Online Library, Collection Kit SK2T-6012.
AUTOLOG RXPROC ENDAUTOLOG
col 1 | V #NFS.MAPPING **.SYSADATA .ADT **.COBOL .CBL **.COBCOPY .CPY **.OBJ .OBJ **.LOAD .EXE **.CLIST .CMD **.SIGYCLST .CMD **.CNTL .JCL **.JCL .JCL **.LISTING .LST **.OUTLIST .OUTUsers can use this default mapping file or create individual mapping files. (See Notes: Network File System Name Mapping for reference material on file mapping.)
For information see DFSMS/MVS V1 Customizing and Operating the Network File System Server, SC26-3190-01, or DFSMS/MVS V1R3 NFS Customization and Operation, SC26-7029-01.
NFS R4 (FMID HDZ11SM) is a separately orderable feature of DFSMS/MVS 1.3. You can order NFS R4 separately and install it on a DFSMS/MVS 1.2 system. This document specifically refers to the DFSMS/MVS NFS feature.
You can use DFSMS/MVS V1R2 NFS to access the host files, but it does not provide the file extension name mapping support provided by DFSMS/MVS V1R3 NFS Server, so file names appear on the workstation without file extensions.
DFSMS/MVS V1R3 NFS Server allows you to define a mapping from host PDS and PDSE names to workstation file extensions so that host file names appear on the workstation with appropriate file extensions. The File Extension Mapping support is available only when the PTF for APAR OW25973 is installed. See the APAR for additional information.
Additional benefits to having workstation file extensions added by the host are:
DFSMS/MVS V1R3 NFS requires OpenEdition MVS (see DFSMS/MVS V1R3 NFS Software prerequisites for information). If OpenEdition MVS is not available, use DFSMS/MVS V1R2 NFS Server; host file extension mapping will not be available.