### Host configuration for remote edit/compile

Before you can communicate with the host using TCP/IP, you must complete the following steps:

1. Install, configure, and start TCP/IP V3 R2 for MVS ESA.

   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.

2. Install and configure the Remote Execution Server (REXECD) for MVS
   For full details, see the above-cited Customization and Administration manual. In summary:
   - Install the Remote Execution Server that is included with the base TCP/IP product. Do not install the one included with the OpenEdition Applications feature.
   - Setup TCP/IP to make REXECD start automatically by adding the following statements to dataset hlq.PROFILE.TCPIP:

          AUTOLOG
            RXPROC
          ENDAUTOLOG

   - Customize the TCP/IP startup proc "RXPROC" for your installation standards.
3. Install DFSMS/NFS SERVER
   For full details, see the NFS Customization and Operation manual. In summary:
   - Choose which level of NFS to install -
     you can use either DFSMS/MVS V1R2 NFS or DFSMS/MVS V1R3 NFS. The most advanced level of NFS is DFSMS/MVS V1R3 NFS, FMID HDZ11SM, which requires OpenEdition be active (the other levels do not). This level of NFS provides File Extension Mapping support, a usability enhancement.
   - Install NFS and customize the NFS Site Attributes dataset
   - If you have installed NFS FMID HDZ11SM, apply the PTF for APAR OW25973
   - In the Site Attributes dataset, change the default parameter 'nopcnfsd' to 'pcnfsd'
   - To enable File Extension Mapping, if you have installed NFS FMID HDZ11SM and the PTF for APAR OW25973, make the following changes to the Site Attributes dataset:
   - Change the default parameter 'sfmax=0' to 'sfmax=1'.
   - Change the default parameter 'nofileextmap' to 'fileextmap'.
   - Optionally, provide a default file extension mapping dataset by adding the parm 'sidefile(mapping_dsn)', where mapping_dsn is the name of the File Extension Mapping dataset. This dataset must have a name of the form hlq.NFS.MAPPING, where hlq can be any high level qualifier. It must be allocated with DCB=(recfm=fb,lrecl=80,blksize=400). Sample contents are:

         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 .OUT

     Users 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 trouble-shooting, trace the NFS - OE component. The first places to look are the NFS server log dataset (pointed to by the NFSLOGnn DDcard) and the NFS client log dataset (pointed to by the NFSCMSnn DDcard) in the NFS startup proc.
4. If you have not yet done so, Install the Remote Edit/Compile/Debug host component.
5. Start
   1. OMVS address space, if using NFS FMID HDZ11SM
   2. TCP/IP
   3. DFSMS/NFS server

#### Additional notes

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:

- You can use tools and execs which expect workstation file names to have extensions.
- File types of files can be readily distinguished by the extension which indicates the type of file, so you don't have to read the fully qualified dataset name.
- Within a COBOL project, the file extensions allows appropriate actions to be available for different types of files.
- You are protected against inadvertent actions on the wrong data set when manipulating host files.

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.